lkml.org 
[lkml]   [1996]   [Jun]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: MTU ?
Date
In article <Pine.LNX.3.91.960606234136.13276B-100000@audio.apana.org.au>,
Keith Owens <kaos@audio.apana.org.au> wrote:
>On Thu, 6 Jun 1996, Mikael Abrahamsson wrote:
>
>> 1.99.12 (has been there for a few versions)
>>
>> Jun 6 01:05:15 uplift kernel: 4.2BSD based fragmenting router between
>> here and 204.174.243.49, mtu corrected from 1500 to 1480
>>
>> I get A LOT of these... I guess I can hack them out, but still... What
>> good does it do?
>
>1.99.11 added a fix for path MTU over paths that include broken 4.2BSD based
>routers. The syslog message is just to indicate that at least this path MTU
>bug has been detected, in case there are any other path MTU problems still in
>the system. I'll remove the debugging messages when 2.0 is out.

Ehm.. on our news server:

4.2BSD based fragmenting router between here and 194.235.77.135, mtu corrected f
rom 1500 to 1480
4.2BSD based fragmenting router between here and 194.235.77.130, mtu corrected f
rom 1068 to 1048
[repeat hunderds of times]

These are dynamic IP adresses of dialin customers. Between them and the
newsserver is just a linux 1.2.13-based terminal server. Most of the
customers are running Trumpet 2.0b (yup, the old one).

Does Linux 1.2.13 or Trumpet have the same 4.2 bug?

Mike.
--
Miquel van | Cistron Internet Services -- Alphen aan den Rijn.
Smoorenburg, | mailto:info@cistron.nl http://www.cistron.nl/
miquels@het.net | Tel: +31-172-419445 (Voice) 430979 (Fax) 442580 (Data)


\
 
 \ /
  Last update: 2005-03-22 13:37    [W:0.054 / U:9.904 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site