[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[linux-tr] Routing between two TR with Madge cards

To: linux-tr@emissary.aus-etc.com
Subject: [linux-tr] Routing between two TR with Madge cards
From: Paul Norton <pnorton@ccnusa.com>
Date: Thu, 15 Apr 1999 21:13:20 +0200 (DST)
In-reply-to: <C7A323A0D854D011AD950001FA37236505F20727@iaea-m1.iaea.or.at>
References: <C7A323A0D854D011AD950001FA37236505F20727@iaea-m1.iaea.or.at>
Reply-to: linux-tr@emissary.aus-etc.com
Sender: owner-linux-tr@emissary.aus-etc.com

Interesting.  If it were a driver issue one would hardly expect to see 
the same behavior in both the Madge driver and the ibmtr driver.  

I would suggest trying a 2.2.x kernel if it's supported by the Madge
drivers.  The 2000 byte MTU limitation no longer exists (at least for
the ibmtr driver) and I've personally verified the payload size
matches the specified MTU without fragmentation.

References:
- [linux-tr] Routing between two TR with Madge cards
  - From: P.Gillingwater@iaea.org

Prev by Date: [linux-tr] Routing between two TR with Madge cards
Next by Date: RE: [linux-tr] Routing between two TR with Madge cards
Previous by thread: [linux-tr] Routing between two TR with Madge cards
Next by thread: RE: [linux-tr] Routing between two TR with Madge cards
Index(es):
- Date
- Thread