From: Evgeniy Polyakov <zbr@ioremap.net>
To: "Joerg M. Sigle" <joerg.sigle@jsigle.com>
Cc: netdev@vger.kernel.org
Subject: Re: Problem: ip_forward in 2.6.27 via realtek 8169 and rt2500pci needs mtu 185 on machines in LAN
Date: Fri, 24 Oct 2008 10:28:20 +0400 [thread overview]
Message-ID: <20081024062820.GA9321@ioremap.net> (raw)
In-Reply-To: <490127D6.8080201@jsigle.com>
Hi Joerg.
On Fri, Oct 24, 2008 at 03:41:42AM +0200, Joerg M. Sigle (joerg.sigle@jsigle.com) wrote:
> Linux box1
> eth0:192.168.1.1 (3com Vortex or so)
> |
> | Linux Box2
> | eth0:192.168.1.4 (Ne2000 PCMCIA)
> | |
> SimpleSwitch
> |
> eth0:192.168.1.40 (Realtek 8169 onboard)
> Linux routerbox (Plain vanilla 2.6.27 SMP)
> wlan0:192.168.2.40 (Ralink rt2500 PCI)
> |
> USR8054 dedicated WLAN-Router
> |
> Internet (or so).
Let me clarify the problem. Traffic fom linux clients only goes through
above setup if mtu on the USR8054 lan device is 185 bytes, correct?
Can you run network traffic with big mtu (normal 1500 bytes) between
linux router and clients? Between clients?
--
Evgeniy Polyakov
next prev parent reply other threads:[~2008-10-24 6:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 1:41 Problem: ip_forward in 2.6.27 via realtek 8169 and rt2500pci needs mtu 185 on machines in LAN Joerg M. Sigle
2008-10-24 6:28 ` Evgeniy Polyakov [this message]
2008-10-24 12:54 ` Joerg M. Sigle
2008-10-24 14:30 ` Evgeniy Polyakov
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=20081024062820.GA9321@ioremap.net \
--to=zbr@ioremap.net \
--cc=joerg.sigle@jsigle.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).