retitle 407336 dhclient3: adopts dhcp server's settings despite them not being
"request"ed
thanks
I have cut down the settings I want to accept from the server to a bare
minimum:
request subnet-mask, broadcast-address, time-offset, routers, interface-mtu,
domain-name-servers;
As well as trying to give me ntp servers to use, which prompted this bug,
it is now giving me a domain name search list too, which resolvconf is
appending to my own list. I'm not on the network now, so can't show the
debug behaviour, but it gives this strange looking lease with wacky expire
dates:
lease {
interface "bond0";
fixed-address 192.168.2.4;
option subnet-mask 255.255.255.0;
option routers 192.168.2.1;
option dhcp-lease-time 4294967295;
option dhcp-message-type 5;
option domain-name-servers 150.203.92.5;
option dhcp-server-identifier 192.168.2.1;
option interface-mtu 1492;
option domain-name "Belkin";
renew 1 2076/03/16 05:47:04;
rebind 1 2127/03/31 14:12:33;
expire 6 2144/04/04 09:01:11;
}
"Belkin" ended up being appended to the search list, but I presume it came
from a pushed domain-search rather than "domain-name" option from the
server (I assume not everything sent by the server ends up in
/var/lib/dhcp3/dhclient.leases ?).
Since it is evident that dhcp servers are pushing setting not being
requested of them, perhaps it is time for the dhcp client to ignore
anything it didn't request.
--
TimC
Skywalker> You are either with me, or you are my enemy.
Only a Sith deals in absolutes. -- Obi Wan Kenobi on George Bush Jnr
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
