From: Athanasius <link@gurus.tf>
To: Rudmer van Dijk <rvandijk@science.uva.nl>
Cc: Bruce Cran <bruce@cran.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: wrong mtu value in /proc/net/route
Date: Fri, 26 Jul 2002 13:11:09 +0100 [thread overview]
Message-ID: <20020726121109.GA8043@miggy.org.uk> (raw)
In-Reply-To: <20020725220557Z316579-685+18235@vger.kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1349 bytes --]
On Fri, Jul 26, 2002 at 12:14:30AM +0200, Rudmer van Dijk wrote:
> On Thursday 25 July 2002 23:34, Bruce Cran wrote:
> > I've found something strange going on in 2.4 kernels - when I run
> > 'netstat -r' I get the routing table from /proc/net/route. The MSS
> > value reported is only 40 bytes, and when I run 'cat
> > /proc/net/route I'm told that the _MTU_ is 40 bytes. I thought the MSS
[snip]
>
> I see the same values on 2.4.19-rc3-ac3 with two Winbond Electronics Corp
> W89C940 NIC's. no idea what is causing it.
Same here with:
Kernel 2.4.18-pre8
eth0: NE2000 found at 0x240, using IRQ 10.
eth1: 3c5x9 at 0x320, 10baseT port, address 00 60 97 ad 3f 84, IRQ 5.
eth2: RealTek RTL8139 Fast Ethernet at 0xd8855000, 00:50:bf:ea:0f:41, IRQ 9
Kernel 2.4.18
Ethernet controller: 3Com Corporation 3c905C-TX [Fast Etherlink]
Kernel 2.4.19-rc1
eth0: RealTek RTL8139 Fast Ethernet at 0xe0863f00, 00:20:ed:1d:fe:2a, IRQ 5
Again, ifconfig on both machines shows the correct values.
I've not gotten around to trying 2.4.19-rc3 yet.
-Ath
--
- Athanasius = Athanasius(at)miggy.org.uk / http://www.clan-lovely.org/~athan/
Finger athan(at)fysh.org for PGP key
"And it's me who is my enemy. Me who beats me up.
Me who makes the monsters. Me who strips my confidence." Paula Cole - ME
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
prev parent reply other threads:[~2002-07-26 12:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-25 21:34 wrong mtu value in /proc/net/route Bruce Cran
2002-07-25 22:14 ` Rudmer van Dijk
2002-07-26 12:11 ` Athanasius [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=20020726121109.GA8043@miggy.org.uk \
--to=link@gurus.tf \
--cc=bruce@cran.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rvandijk@science.uva.nl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.