James Carlson wrote:
Dave Miner wrote:
Ken Powell wrote:
Should Solaris support automatically configuring to a network
that works this way?
I ran into this at a hotel about 3 years ago and amazingly haven't since
despite the number of hotels I visit. I could swear we filed a bug
somewhere about it, but I can't find it now. I'd put it in the "liberal
in what you accept" bucket and hence we ought to make it work.
I remember that, too. I don't remember it ever making it into a CR --
at least I can't find it externally.
The two places I can think of where this ought to be handled are in
configure_v4_lease(): we should be able to detect and ignore "obviously"
bogus netmasks, and we should check dsm_pil[] before attempting to use
CD_SUBNETMASK.
The latter would make it possible for you to set PARAM_IGNORE_LIST so
that the DHCP client would not use that option. (It's not a fix, but
it'd be a useful work-around, just in case there's someone out there
with a DHCP server that gives out bogus netmasks that aren't "obvious.")
Just ignoring the netmask would still fail at the hotel I was at.
The default netmask for address 192.168.7.216 is 255.255.255.0.
I needed a netmask of 255.255.252.0 to reach the router.
Ken
_______________________________________________
networking-discuss mailing list
[email protected]
