Date: Mon, 12 Oct 2009 16:14:06 -0700 From: "Michael K. Smith - Adhost" <mksmith@adhost.com> To: "Julian Elischer" <julian@elischer.org>, "Doug Barton" <dougb@FreeBSD.org> Cc: freebsd-net@freebsd.org Subject: RE: Wacky DHCP values that work in windows but not in FreeBSD Message-ID: <17838240D9A5544AAA5FF95F8D52031606D020C7@ad-exh01.adhost.lan> In-Reply-To: <4AD3B4E3.2090406@elischer.org> References: <4AD3ABD0.7010603@FreeBSD.org> <4AD3B4E3.2090406@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: owner-freebsd-net@freebsd.org [mailto:owner-freebsd- > net@freebsd.org] On Behalf Of Julian Elischer > Sent: Monday, October 12, 2009 4:00 PM > To: Doug Barton > Cc: freebsd-net@freebsd.org > Subject: Re: Wacky DHCP values that work in windows but not in FreeBSD >=20 > Doug Barton wrote: > > Howdy, > > > > I usually have a wireless router connected directly to the AT&T/Yahoo > > DSL modem but last night I wanted to do some debugging so I plugged > my > > laptop directly into the modem (after powering off the modem, etc.). > > > > The values I got back from DHCP not only don't make sense, they > didn't > > work in FreeBSD at all. Dual-booting to Windows showed that the > values > > I saw from DHCP were "correct," and somehow they managed to work. > > Taking a closer look at the router after I plugged it back in showed > > the same. > > > > Dhcp Enabled. . . . . . . . . . . : Yes > > Autoconfiguration Enabled . . . . : Yes > > IP Address. . . . . . . . . . . . : 76.212.147.xxx > > Subnet Mask . . . . . . . . . . . : 255.255.0.0 > > Default Gateway . . . . . . . . . : 151.164.184.xxx >=20 > huh? >=20 > only way this could work would be if it was marked as "point to point" > I think.. That could be a primary IP address on an interface on which your 76 address is a sub interface. The interface will do proxy-arp when a traffic request comes in. Or something else! I'm not sure if this will work, but you could actually hard code your default gateway with a -hopcount 2 (or higher) and see if that works. I've not tried it on a live machine. Something like route add default 151.164.184.xxx -hopcount 5. You may have to delete the DHCP-assigned entry first. Regards, Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17838240D9A5544AAA5FF95F8D52031606D020C7>