From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick McHardy Subject: Re: Follow packets in rules Date: Mon, 18 Jun 2007 14:49:36 +0200 Message-ID: <46767F60.5080208@trash.net> References: <466FB176.7040306@netfilter.org> <467020F6.2050906@trash.net> <46713EE8.6060906@trash.net> <46714F7D.4010309@trash.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: netfilter-devel@lists.netfilter.org To: Jozsef Kadlecsik Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: netfilter-devel-bounces@lists.netfilter.org Errors-To: netfilter-devel-bounces@lists.netfilter.org List-Id: netfilter-devel.vger.kernel.org Jozsef Kadlecsik wrote: > Attached you can find the reworked TRACE target, which does not suffer > from backward incompatibility. Unfortunately I had to steal one unused > bit from skbuff to be able to mark the packets so that it surely does > not clash with any rules using the standard "MARK" target. Logging > level, flags and type are hardcoded. What do you think? Looks pretty good. Maybe we can avoid using the skb bit though, what do you think about letting the user set a special "trace-mark" value through /proc and using that? Not sure if thats better or worse :)