From: Patrick McHardy <kaber@trash.net>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: bridge@osdl.org, nfs@lists.sourceforge.net,
Chris Rankin <rankincj@yahoo.com>
Subject: Re: [Bridge] Re: No UDP NFS over bridges in Linux 2.6.16.x?
Date: Mon, 17 Apr 2006 20:00:34 +0200 [thread overview]
Message-ID: <4443D7C2.7030901@trash.net> (raw)
In-Reply-To: <44408207.1070404@osdl.org>
Stephen Hemminger wrote:
> Then get a packet trace of a failing session with tcpdump. You may need
> to get two, one
> one the client and one on the server to be able to see which packet
> isn't getting past the
> bridge.
I only saw half of this thread (Chris' mails haven't made it to the list
yet), but in case you're using bridge-netfilter and conntrack, its most
likely because of conntrack fragmentation changes in 2.6.16. Conntrack
defragments packets, but relies on the IP layer to do the
refragmentation now. With purely bridged traffic, the packets don't go
through the IP layer, so they exceed the MTU of the outgoing bridge
port. 2.6.16.6 will include a fix for this problem:
[patch 06/22] NETFILTER: Fix fragmentation issues with bridge netfilter
next prev parent reply other threads:[~2006-04-17 18:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060414235008.66335.qmail@web52913.mail.yahoo.com>
2006-04-15 5:17 ` [Bridge] Re: No UDP NFS over bridges in Linux 2.6.16.x? Stephen Hemminger
2006-04-17 18:00 ` Patrick McHardy [this message]
[not found] <20060417181727.43038.qmail@web52902.mail.yahoo.com>
2006-04-17 18:24 ` Patrick McHardy
2006-04-14 13:42 [Bridge] " Chris Rankin
2006-04-14 16:40 ` [Bridge] " Stephen Hemminger
[not found] ` <20060414192656.870.qmail@web52914.mail.yahoo.com>
2006-04-14 20:53 ` Stephen Hemminger
[not found] ` <20060414205815.15338.qmail@web52911.mail.yahoo.com>
2006-04-14 21:00 ` Stephen Hemminger
[not found] ` <20060414221312.64298.qmail@web52901.mail.yahoo.com>
2006-04-14 22:17 ` Stephen Hemminger
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=4443D7C2.7030901@trash.net \
--to=kaber@trash.net \
--cc=bridge@osdl.org \
--cc=nfs@lists.sourceforge.net \
--cc=rankincj@yahoo.com \
--cc=shemminger@osdl.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