From: Rolf Fokkens <fokkensr@linux06.vertis.nl>
To: "David S. Miller" <davem@redhat.com>, rusty@rustcorp.com.au
Cc: fokkensr@linux06.vertis.nl, linux-kernel@vger.kernel.org,
kuznet@ms2.inr.ac.ru
Subject: Re: iptables and tcpdump
Date: Tue, 30 Oct 2001 21:45:24 -0800 [thread overview]
Message-ID: <01103021452400.03241@home01> (raw)
In-Reply-To: <01102817104101.01788@home01> <20011030152812.2e9ba8ee.rusty@rustcorp.com.au> <20011029.213157.39157336.davem@redhat.com>
In-Reply-To: <20011029.213157.39157336.davem@redhat.com>
Hi!
I may have missed something, but I'm not on the maillists which would explain
why. And the archives dont contain the email messages (yet) between my
initial question and this part of the discussion.
Apparently my question triggered a discussion about some deep NAT details at
the skb level. As much as I understand it, something goes wrong with the skb
cloning in the NAT layer, NAT changes read-only copies.
Is this the cause of the weird data that shows up with tcpdump?
Or in other words: does tcpdump show something buggy?
Rolf
On Tuesday 30 October 2001 09:31, you wrote:
> Hello!
>
> > Alexey, should the NAT layer be doing skb_unshare() before altering the
> > packet?
>
> MUST. Cloned skbs are read-only.
>
> I did not expect such question from you. :-)
>
> Alexey
next prev parent reply other threads:[~2001-10-30 20:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-29 1:10 iptables and tcpdump Rolf Fokkens
2001-10-30 4:28 ` Rusty Russell
2001-10-30 5:31 ` David S. Miller
2001-10-31 5:45 ` Rolf Fokkens [this message]
2001-10-31 6:28 ` Rusty Russell
2001-10-31 13:34 ` kuznet
2001-11-06 23:40 ` David S. Miller
2001-10-30 17:31 ` kuznet
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=01103021452400.03241@home01 \
--to=fokkensr@linux06.vertis.nl \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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