Date: Mon, 12 Oct 2009 16:25:59 -0700 From: Julian Elischer <julian@elischer.org> To: Doug Barton <dougb@FreeBSD.org> Cc: "Michael K. Smith - Adhost" <mksmith@adhost.com>, freebsd-net@freebsd.org Subject: Re: Wacky DHCP values that work in windows but not in FreeBSD Message-ID: <4AD3BB07.3070109@elischer.org> In-Reply-To: <4AD3B9FB.4010205@FreeBSD.org> References: <4AD3ABD0.7010603@FreeBSD.org> <4AD3B4E3.2090406@elischer.org> <17838240D9A5544AAA5FF95F8D52031606D020C7@ad-exh01.adhost.lan> <4AD3B9FB.4010205@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug Barton wrote: > Michael K. Smith - Adhost wrote: >>> -----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 >>> >>> 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. > > Can you specify what you mean by 'that'? > >> 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. > > Ah, I didn't know about -hopcount, thanks. There was no default route > installed at all when I booted. I tried 'route add default 151...' > even though I was sure it wouldn't work, and I was not disappointed. > > Doug > also not sure if you can add a -iface argument to make your default route include the correct interface .
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4AD3BB07.3070109>