From: Thomas Zeitlhofer <thomas.zeitlhofer@nt.tuwien.ac.at>
To: Patrick McHardy <kaber@trash.net>
Cc: linux-kernel@vger.kernel.org,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>,
netdev@vger.kernel.org, Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: bridge+netfilter broken for IP fragments in 2.6.16?
Date: Mon, 3 Apr 2006 01:36:53 +0200 [thread overview]
Message-ID: <20060402233653.GA30271@swan.nt.tuwien.ac.at> (raw)
In-Reply-To: <44305A32.1010109@trash.net>
On Mon, Apr 03, 2006 at 01:11:46AM +0200, Patrick McHardy wrote:
> Thomas Zeitlhofer wrote:
> > On Sun, Apr 02, 2006 at 09:19:30PM +0200, Patrick McHardy wrote:
> >
> >>>Doing the same on 2.6.15.x shows:
> >>>
> >>> 1) on tap1: fragmented packets
> >>> 2) on br0: the defragmented packet (connection tracking)
> >>> 3) on eth1: fragmented packets
> >>
> >>Are you sure this is correct? I think in 2.6.15 you should see
> >>the fragments on br0 already.
> >
> >
> > Just verified it, at least in 2.6.15.6 tcpdump shows the defragmented
> > packet on br0.
>
> I'm probably missing something, but that still seems stange.
> Are you also seeing the defragmented packet on br0 with my
> patch?
Yes, here is the tcpdump output on all interfaces:
1) on tap1
23:22:51.830046 IP (tos 0x0, ttl 64, id 21174, offset 0, flags [+], proto: UDP (17), length: 1500) 192.168.10.1.500 > 192.168.20.1.500: isakmp 1.0 msgid : phase 1 I ident[E]: [encrypted id] (len mismatch: isakmp 2572/ip 1472)
23:22:51.830084 IP (tos 0x0, ttl 64, id 21174, offset 1480, flags [none], proto: UDP (17), length: 1120) 192.168.10.1 > 192.168.20.1: udp
2) on br0
23:22:51.830084 IP (tos 0x0, ttl 64, id 21174, offset 0, flags [none], proto: UDP (17), length: 2600) 192.168.10.1.500 > 192.168.20.1.500: isakmp 1.0 msgid : phase 1 I ident[E]: [encrypted id]
3) on eth1
23:22:51.830120 IP (tos 0x0, ttl 64, id 21174, offset 0, flags [+], proto: UDP (17), length: 1500) 192.168.10.1.500 > 192.168.20.1.500: isakmp 1.0 msgid : phase 1 I ident[E]: [encrypted id] (len mismatch: isakmp 2572/ip 1472)
23:22:51.830133 IP (tos 0x0, ttl 64, id 21174, offset 1480, flags [none], proto: UDP (17), length: 1120) 192.168.10.1 > 192.168.20.1: udp
--
Thomas
prev parent reply other threads:[~2006-04-02 23:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-01 14:30 Thomas Zeitlhofer
2006-04-02 19:19 ` Patrick McHardy
2006-04-02 22:56 ` Thomas Zeitlhofer
2006-04-02 23:11 ` Patrick McHardy
2006-04-02 23:36 ` Thomas Zeitlhofer [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=20060402233653.GA30271@swan.nt.tuwien.ac.at \
--to=thomas.zeitlhofer@nt.tuwien.ac.at \
--cc=herbert@gondor.apana.org.au \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®