On Fri, 4 Feb 2005, Hans-Peter Jansen wrote: > On Thursday 03 February 2005 05:47, Shane Hathaway wrote: > > The attached patch enhances the kernel's DHCP client support (in > > net/ipv4/ipconfig.c) to set the interface MTU if provided by the > > DHCP server. Without this patch, it's difficult to netboot on a > > network that uses jumbo frames. The patch is based on 2.6.10, but > > I'll update it to the latest testing kernel if that would expedite > > its inclusion in the kernel.
What will this code do at the (increasingly common) misconfigured sites - many places (hotels, airports, etc) return a MTU of 64... to which the DHCP3 client faithfully attempts to set, only to receive: SIOCSIFMTU: Invalid argument And is one of the easiest issues I've had during my travels - thankfully I don't do it all that often; trying to tell the helpdesk folk that their DHCP server is handing out bogus DNS servers, MTU, even networks is an exercise in futility. -- Rick Nelson "Absolutely nothing should be concluded from these figures except that no conclusion can be drawn from them." (By Joseph L. Brothers, Linux/PowerPC Project) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/