From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick McHardy Subject: Re: dangerous? Setting mark in nat table Date: Wed, 14 Mar 2007 12:02:47 +0100 Message-ID: <45F7D657.8070907@trash.net> References: <45F6CD7C.40708@ufomechanic.net> <1173868532.26913.39.camel@henriknordstrom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: netfilter-devel@lists.netfilter.org, Jan Engelhardt , Amin Azez To: Henrik Nordstrom Return-path: In-Reply-To: <1173868532.26913.39.camel@henriknordstrom.net> 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 Henrik Nordstrom wrote: > It's due to the relation of the per-packet nfmark being as a channel to > return routing information from netfilter to the kernel. Thats true, routing by nfmark in the OUTPUT chain needs the rerouting done by the mangle table, but nowadays there are other uses for nfmark, so if someone feels motivated to send a patch to get rid of this pretty arbitary restriction I think I would take it.