Date: Sat, 3 Feb 2001 22:10:48 -0500 From: Andrew BOGECHO <andrewb@cs.mcgill.ca> To: cjclark@alum.mit.edu Cc: questions@FreeBSD.ORG Subject: Re: mtu not set with dhcp options Message-ID: <20010203221048.A18345@cs.mcgill.ca> In-Reply-To: <20010203182433.N91447@rfx-216-196-73-168.users.reflex>; from cjclark@reflexnet.net on Sat, Feb 03, 2001 at 06:24:33PM -0800 References: <20010203163437.A16076@cs.mcgill.ca> <20010203191302.A53923@solveinteractive.com> <20010203170850.M91447@rfx-216-196-73-168.users.reflex> <20010203205825.B17997@cs.mcgill.ca> <20010203182433.N91447@rfx-216-196-73-168.users.reflex>
next in thread | previous in thread | raw e-mail | index | archive | help
Sat Feb 3 21:44:37 EST 2001 On Sat, Feb 03, 2001 at 06:24:33PM -0800, Crist J. Clark wrote: > On Sat, Feb 03, 2001 at 08:58:25PM -0500, Andrew BOGECHO wrote: > > Sat Feb 3 20:47:46 EST 2001 > > > > Hi Chris, > > > > Thank you for your reply. The tcpdump was a good idea. Here are the > > results. It does look like the client requests the info, and that the > > server sends the info. However, I am not sure what base the number > > returned is in. I definitely put in 1492, but it seems to send out > > 54277. Any clues? > > 1492 = 0x05d4 > 54277 = 0xd405 > Good one. I was trying all bases to get from one to another. Now I feel silly :) Another thing I noticed, is that there is no entry at all for mtu in: /sbin/dhclient-script Could this be the reason that the mtu does not get set? It seems that all other values get set there: medium, netmask, IP , etc.. Thanks for all you help. Andrew. > Clearly a host versus network byte order issue. No idea whether it is > being sent out on the wire the wrong way or if tcpdump(8) is > erroniously reporting the value. > -- > Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010203221048.A18345>