From: Patrick Schaaf Subject: Re: REJECT target Date: Thu, 26 Jun 2003 17:19:47 +0200 Sender: netfilter-devel-admin@lists.netfilter.org Message-ID: <20030626151947.GA10045@oknodo.bof.de> References: <1012141349.20030626165642@habitat-b.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: netfilter-devel@lists.netfilter.org Return-path: To: DarKRaveR Content-Disposition: inline In-Reply-To: <1012141349.20030626165642@habitat-b.de> Errors-To: netfilter-devel-admin@lists.netfilter.org List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: List-Id: netfilter-devel.vger.kernel.org > Okay, admitted. I would be glad to do that in the filtering table, the > question is: How can I identify those packets, when the were modified > in the nat table ? One approach that I used in some places, and which could be workable for your scenario, is to use the MARK target at mangle/PREROUTING, and then use the mark match both in the NAT decision, and in the filter table. The firewall mark stays with the packet, regardless of application of a NAT action. The CONNMARK stuff may be even more useful / cover more cases. best regards Patrick