Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264373AbVBDTzc (ORCPT ); Fri, 4 Feb 2005 14:55:32 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261708AbVBDTyy (ORCPT ); Fri, 4 Feb 2005 14:54:54 -0500 Received: from moutng.kundenserver.de ([212.227.126.188]:28666 "EHLO moutng.kundenserver.de") by vger.kernel.org with ESMTP id S266414AbVBDTyN (ORCPT ); Fri, 4 Feb 2005 14:54:13 -0500 From: Hans-Peter Jansen To: Richard A Nelson Subject: Re: [PATCH] Configure MTU via kernel DHCP Date: Fri, 4 Feb 2005 20:54:02 +0100 User-Agent: KMail/1.5.4 Cc: Shane Hathaway , Kernel Mailing List References: <200502022148.00045.shane@hathawaymix.org> <200502041755.41288.hpj@urpla.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200502042054.02375.hpj@urpla.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:18d01dd0a2a377f0376b761557b5e99a Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 798 Lines: 20 On Friday 04 February 2005 19:22, Richard A Nelson wrote: > > 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 Well, the ip auto configuration is mainly intended for diskless setups, not something, one will use in an uncontrolled environment. I doubt, it will behave different, as well as usual distribution kernels will never enable this by default.. Pete - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/