From: "Покотиленко Костик" <casper@meteor.dp.ua>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: netfilter@lists.netfilter.org
Subject: Re: iptables NEW TABLE request. WAS[Re: Catching un-DNAT'ed packets]
Date: Wed, 31 Jan 2007 11:14:48 +0200 [thread overview]
Message-ID: <1170234888.4464.9.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61.0701301901470.13737@yvahk01.tjqt.qr>
В Вто, 30/01/2007 в 19:02 +0100, Jan Engelhardt пишет:
> On Jan 30 2007 11:46, Jan Engelhardt wrote:
> >>Excuse me for double asking, but is this the place for such a feature
> >>request?
> >
> >At least it's not the wrong place.
>
> For the mailinglist record, the solutions is:
>
> -t nat -A POSTROUTING -m conntrack --ctstate DNAT --ctorigdst x.x.x.x
Just to make sure. This rule will match the packets with canntrack state
"DNAT" and whose original (before DNAT) destination address was x.x.x.x,
right?
If I add -j ULOG to this rule what would be logged packet source address
for replay packet (Server->Client)? Original, that client was initially
connected to, or real, that was set during DNAT?
By the way does -m conntrack --ctstate DNAT --ctorigdst x.x.x.x match
request or replay packets or packets belonging to connection which was
originally made to x.x.x.x?
--
Покотиленко Костик <casper@meteor.dp.ua>
next prev parent reply other threads:[~2007-01-31 9:14 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 ` Покотиленко Костик
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 ` Покотиленко Костик [this message]
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=1170234888.4464.9.camel@localhost.localdomain \
--to=casper@meteor.dp.ua \
--cc=jengelh@linux01.gwdg.de \
--cc=netfilter@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.