From: Rusty Russell <rusty@rustcorp.com.au>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: linux-kernel@vger.kernel.org, tcpdump-workers@tcpdump.org
Subject: Re: Linux 2.4 and iptables: output includes NAT
Date: Wed, 30 Jan 2002 15:20:45 +1100 [thread overview]
Message-ID: <20020130152045.345e3288.rusty@rustcorp.com.au> (raw)
In-Reply-To: <87elk9rkv4.fsf@deneb.enyo.de>
In-Reply-To: <87elk9rkv4.fsf@deneb.enyo.de>
On Tue, 29 Jan 2002 20:57:19 +0100
Florian Weimer <fw@deneb.enyo.de> wrote:
> On Linux 2.4.14 with the following iptables rule,
>
> iptables -t nat -A POSTROUTING -o eth1 -p tcp -d $TARGET -j SNAT --to $NEW
>
> tcpdump version 3.6.2 with libpcap 0.6.2 (Debian GNU/Linux versions)
> shows the address on the wire for source addresses of IP packets, but
> the destination address is displayed with NAT applied, which is
> quit confusing.
Yes, this was fixed in later kernels.
Thanks!
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
prev parent reply other threads:[~2002-01-30 4:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-29 19:57 Linux 2.4 and iptables: output includes NAT Florian Weimer
2002-01-30 4:20 ` Rusty Russell [this message]
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=20020130152045.345e3288.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=fw@deneb.enyo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tcpdump-workers@tcpdump.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