Andrew Pollock wrote: > On Fri, Feb 12, 2010 at 07:20:12AM +0100, Andrzej Adam Filip wrote: >> Andrew Pollock wrote: >>> On Wed, Feb 10, 2010 at 07:33:07PM +0100, Andrzej Adam Filip wrote: >>>> Andrew Pollock wrote: >>>>> On Wed, Feb 10, 2010 at 01:04:32PM +0100, Andrzej Filip wrote: >>>>>> [...] >>>>>> Background: currently debian completly ignores inteface-mtu equal 576 >>>>>> received from cable router (single crossover ethernet cable "network"). >>>> I will check later this week if the MTU is set by the provider itself or >>>> needlessly by "a crazy router". Anyway the reasoning behind the patch >>>> you have mentioned makes me think (as for now) that ignoring of too low >>>> MTU should be configurable instead of being hard coded. >>>> [ Very preliminary searches suggest "crazy route/ISP" in my case. ] >>>> >>>> I reserve right to change my opinion :-) >>> >>> I have some longer term plans to completely rewrite dhclient-script, and >>> split out a lot of the functionality to the hooks. At this point the MTU >>> sanitiser could be a hook, which could be disabled. >> It has been "a crazy router/ISP" in my case. "tracepath" program >> reported no problems with MTU higher than interface-mtu of 576 provided >> by DHCP. > > So that makes this "working as intended"?
In this particular case dhcp3-client has done good choice by ignoring interface-mtu equal to 576 - my faith in the ISP [and its choice of cable modem (?)] has been "reduced" :-) So my submission is no longer "a bug". It may be treated as *low* priority "style improvement suggestion" *if you wish* to replace "the hard coded decision" by "a configuration option". -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org