Package: dhcp3
Version: 3.0.4-10
Tags: patch

The default dhcp3 client configuration is unnecessarily and harmfully
limiting the DHCP options the server is sending.

The "request" statement in dhclient.conf changes the list of DHCP
options that the client allows the server to send back.  The list of
options sent by the server is the intersection of what the server
knows to send and what the client has requested to receive.  (Note
that the client's requesting options serves only to limit the received
options, never to expand them.)

Since dhclient has no problems ignoring options it doesn't understand,
there is no harm in allowing all the options the server feels like
sending.

Furthermore, dhclient cannot know about all the other packages that
may wish to insert a hook script to handle some option.  For example,
the Etch NTP daemon knows how to use the "ntp-servers" option, if
dhclient.conf doesn't suppress it.

The appended patch puts "request;" in the default dhclient.conf file;
this empty request list prevents limiting the options the server
sends.

I would suggest to the upstream developers that this be shown in their
sample conf file, too, or that dhclient's default should be not to
send a parameter request list at all.

 < Stephen


--- dhcp3-3.0.4/debian/dhclient.conf    2006-10-17 22:08:54 -0700
+++ debian/dhclient.conf        2006-11-12 20:12:02 -0500
@@ -16,10 +16,8 @@
 #send dhcp-lease-time 3600;
 #supersede domain-name "fugue.com home.vix.com";
 #prepend domain-name-servers 127.0.0.1;
-request subnet-mask, broadcast-address, time-offset, routers,
-       domain-name, domain-name-servers, host-name,
-       netbios-name-servers, netbios-scope, interface-mtu;
-#require subnet-mask, domain-name-servers;
+# request nothing: let the server send all the parameters it knows
+request;
 #timeout 60;
 #retry 60;
 #reboot 10;


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to