From: "David S. Miller" <davem@redhat.com>
To: 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: Mon, 29 Oct 2001 21:31:57 -0800 (PST) [thread overview]
Message-ID: <20011029.213157.39157336.davem@redhat.com> (raw)
In-Reply-To: <20011030152812.2e9ba8ee.rusty@rustcorp.com.au>
In-Reply-To: <01102817104101.01788@home01> <20011030152812.2e9ba8ee.rusty@rustcorp.com.au>
From: Rusty Russell <rusty@rustcorp.com.au>
Date: Tue, 30 Oct 2001 15:28:12 +1100
should the NAT layer be doing skb_unshare() before altering the packet?
I think it should.
Look, if you are messing with packets before they go back out, and
tcpdump could have sniffed it on the way in, you can't change it's
contents blindly.
Franks a lot,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2001-10-30 5:31 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 [this message]
2001-10-31 5:45 ` Rolf Fokkens
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=20011029.213157.39157336.davem@redhat.com \
--to=davem@redhat.com \
--cc=fokkensr@linux06.vertis.nl \
--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