NetFilter
[Top] [All Lists]

iptables NEW TABLE request. WAS[Re: Catching un-DNAT'ed packets]

To: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
Subject: iptables NEW TABLE request. WAS[Re: Catching un-DNAT'ed packets]
From: Покотиленко Костик <casper@meteor.dp.ua>
Date: Fri, 26 Jan 2007 13:21:12 +0200
Cc: netfilter@lists.netfilter.org
Delivered-to: sp-com-lists@consult.net
Delivered-to: netfilter-list1@securepoint.com
In-reply-to: <459102EC.50402@plouf.fr.eu.org>
List-archive: </pipermail/netfilter>
List-help: <mailto:netfilter-request@lists.netfilter.org?subject=help>
List-id: General discussion and user questions <netfilter.lists.netfilter.org>
List-post: <mailto:netfilter@lists.netfilter.org>
List-subscribe: <https://lists.netfilter.org/mailman/listinfo/netfilter>, <mailto:netfilter-request@lists.netfilter.org?subject=subscribe>
List-unsubscribe: <https://lists.netfilter.org/mailman/listinfo/netfilter>, <mailto:netfilter-request@lists.netfilter.org?subject=unsubscribe>
Organization: СК "Метеор"
References: <1167054030.16171.10.camel@localhost.localdomain> <459102EC.50402@plouf.fr.eu.org>
Reply-to: casper@meteor.dp.ua
Sender: netfilter-bounces@lists.netfilter.org
Hi.

After analizing the situation I have come to decide to request NEW TABLE
in iptables.

Considering the scheme at:

http://www.meteor.dp.ua/casper/firewill.pdf

how would I make a "feature request" to ask for, say, "mangle2" table
that is just after "nat" in POSTROUTING? The only reason for this move
is the need for ability to catch un-DNAT'ed packets with -j ULOG or
(better) to -j QUEUE.

В Вто, 26/12/2006 в 12:09 +0100, Pascal Hambourg пишет:
> Hello,
> 
> Pokotilenko Kostik a écrit :
> > 
> > Is it possible to catch un-DNAT'ed packets with iptables' -j ULOG
> > target?
> 
> I'm afraid no.
> 
> > Where does the un-DNAT occurs and is there table/chain that is
> > processed after un-DNAT?
> 
> In 2.4 kernels, when DNAT occurs in the PREROUTING chain, un-DNAT occurs 
> at the same place as (and in place of) the POSTROUTING chain of the 
> 'nat' table, and there is no chain after it. In 2.4 kernels >= 2.4.19, 
> when DNAT occurs in the OUTPUT chain, un-DNAT occurs after the INPUT 
> chain of the 'filter' table, and there is no chain after it either. I 
> suppose it has not changed in 2.6 kernels.
> 
> > The problem I have is that replay packets got catched with real source
> > address, not the one the client has initially connected to. I was
> > catching replay packets in mangle/POSTROUTING.
> 
> The POSTROUTING chain of the 'mangle' table is just before the un-DNAT 
> place.
> 
> 
-- 
Покотиленко Костик <casper@meteor.dp.ua>



<Prev in Thread] Current Thread [Next in Thread>