netdev - any way to reset all marked connections when using CONNMARK?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <4D55A927.7060703@genband.com>
Date:	Fri, 11 Feb 2011 15:24:55 -0600
From:	Chris Friesen <chris.friesen@...band.com>
To:	netdev@...r.kernel.org, netfilter-devel@...r.kernel.org,
	netfilter@...r.kernel.org, coreteam@...filter.org
Subject: any way to reset all marked connections when using CONNMARK?

Hi,

We've got a scenario where we want to use CONNMARK to mark connections
that have passed a large number of rules in order to allow packets from
those connections to skip rules in the future (for performance reasons).

However, when we add new rules we want to ensure that all the
connections need to pass the new rules as well.

It has been proposed to add a custom patch to clear the mark for all
marked connections--is there a better way of doing this?

I thought maybe we could use the CONNMARK as a generation count and
bumping it up each time a rule is added.  This would require updating
the bypass rule each time we modify the other rules though.  If there
are better options I'd like to hear them.

Thanks,
Chris

-- 
Chris Friesen
Software Developer
GENBAND
chris.friesen@...band.com
www.genband.com
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html