From: "Покотиленко Костик" <casper@meteor.dp.ua>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: netfilter@lists.netfilter.org,
Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
Subject: Re: iptables NEW TABLE request. WAS[Re: Catching un-DNAT'ed packets]
Date: Fri, 26 Jan 2007 14:33:15 +0200 [thread overview]
Message-ID: <1169814795.5004.11.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61.0701261223430.22295@yvahk01.tjqt.qr>
В Птн, 26/01/2007 в 12:24 +0100, Jan Engelhardt пишет:
> >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.
>
> And -t nat -A POSTROUTING -m conntrack ! --ctstate DNAT
> as a last rule won't do?
This will (probably) catch packets that hasn't been DNAT'ed.
BUT, the thing I need it to catch replay packets that has already passed
"un-DNAT" procedure.
--
Покотиленко Костик <casper@meteor.dp.ua>
next prev parent reply other threads:[~2007-01-26 12:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-25 13:40 Catching un-DNAT'ed packets Покотиленко Костик
2006-12-26 11:09 ` Pascal Hambourg
2006-12-26 16:25 ` Покотиленко Костик
2007-01-26 11:21 ` iptables NEW TABLE request. WAS[Re: Catching un-DNAT'ed packets] Покотиленко Костик
2007-01-26 11:24 ` Jan Engelhardt
2007-01-26 12:33 ` Покотиленко Костик [this message]
2007-01-26 16:12 ` Jan Engelhardt
2007-01-26 16:27 ` Покотиленко Костик
2007-01-29 15:58 ` Покотиленко Костик
2007-01-30 10:46 ` Jan Engelhardt
2007-01-30 18:02 ` Jan Engelhardt
2007-01-31 9:14 ` Покотиленко Костик
2007-01-31 11:38 ` Pascal Hambourg
2007-01-31 13:01 ` Покотиленко Костик
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1169814795.5004.11.camel@localhost.localdomain \
--to=casper@meteor.dp.ua \
--cc=jengelh@linux01.gwdg.de \
--cc=netfilter@lists.netfilter.org \
--cc=pascal.mail@plouf.fr.eu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox