Date: Sun, 10 Mar 2002 21:47:04 +0100 From: "Leif Neland" <leifn@neland.dk> To: "Marcel de Vries" <mdevries@haveityourway.nl>, <freebsd-net@FreeBSD.ORG>, "Rogier R. Mulhuijzen" <drwilco@drwilco.net> Subject: Re: Changing MTU via dhcp (OT: how to see it in windows) Message-ID: <001d01c1c874$bd11b3a0$6d05a8c0@neland.dk> References: <003f01c1c862$31308c60$6d05a8c0@neland.dk> <5.1.0.14.0.20020310213335.01c3dbc8@mail.drwilco.net>
index | next in thread | previous in thread | raw e-mail
----- Original Message ----- From: "Rogier R. Mulhuijzen" <drwilco@drwilco.net> To: "Marcel de Vries" <mdevries@haveityourway.nl>; "Leif Neland" <leifn@neland.dk>; <freebsd-net@FreeBSD.ORG> Sent: Sunday, March 10, 2002 9:35 PM Subject: Re: Changing MTU via dhcp (OT: how to see it in windows) > With windows this would be a bit dodgy though. Even if it is stored in the > registry, I doubt it reflects runtime values. And thus you still don't know > whether or not the MTU setting is accepted from the DHCP server. > > I would suggest using tcpdump or some other sniffing tool to see how large > the packets on the wire are. > Windows ping can set the "don't fragment" bit, and then determine the mtu that way by trial and error / binary search. fpsd ping doesn't have that option. However, if I ping the win-box with packets of 10000 bytes, I see the ping gets fragmented in pieces of 1480. So it appears that win98 doesn't obey the mtu size dhcp sets. Damn... Leifhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001d01c1c874$bd11b3a0$6d05a8c0>