From: Cyker <cyker.lnx@gmail.com>
To: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Kernel bridge not passing some traffic (VNC, embedded webservers)
Date: Mon, 01 Sep 2008 21:03:14 +0100 [thread overview]
Message-ID: <48BC4A82.4000901@gmail.com> (raw)
In-Reply-To: <mailman.902.1220288669.22943.bridge@lists.linux-foundation.org>
Message-ID: <48B5D43E.9060909@gmail.com>
It turns out that the issue was caused by an MTU mismatch on the bridge.
For some reason, the bridge had an MTU of 1492, presumably something to
do with the DSL router it feeds.
Because it's impossible for bridges to fragment packets, the packets at
the full 1500 size were just being silently dropped.
It is odd that so few things on the network were being affected, but
that's computers for you :P
Sorry for the silly postings; I didn't even consider that it could be an
MTU issue since even multi-gigabyte SMB, SSH and FTP transfers were
going through!!
next parent reply other threads:[~2008-09-01 20:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.902.1220288669.22943.bridge@lists.linux-foundation.org>
2008-09-01 20:03 ` Cyker [this message]
2008-08-27 22:25 [Bridge] Kernel bridge not passing some traffic (VNC, embedded webservers) Cyker
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=48BC4A82.4000901@gmail.com \
--to=cyker.lnx@gmail.com \
--cc=bridge@lists.linux-foundation.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