Wacky DHCP values that work in windows but not in FreeBSD
Michael K. Smith - Adhost
mksmith at adhost.com
Mon Oct 12 23:14:09 UTC 2009
> -----Original Message-----
> From: owner-freebsd-net at freebsd.org [mailto:owner-freebsd-
> net at freebsd.org] On Behalf Of Julian Elischer
> Sent: Monday, October 12, 2009 4:00 PM
> To: Doug Barton
> Cc: freebsd-net at freebsd.org
> Subject: Re: Wacky DHCP values that work in windows but not in FreeBSD
>
> 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
>
> huh?
>
> 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
More information about the freebsd-net
mailing list