[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#682342: netcfg DHCP information handling regression between Lenny and Squeeze



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Package: netcfg
Version: 1.59

I'm using PXE boot with network preseeding to perform automated Debian
installations with Lenny, Squeeze and Wheezy.

With Lenny, netcfg used the DHCP options domain-name,
domain-name-servers, and ntp-servers. With Squeeze and Wheezy, these
options seem to be ignored.

I have the following in my DHCP configuration file, dhcpd.conf:

option domain-name "training.nta-monitor.com";
option domain-name-servers ns0.training.nta-monitor.com;
option ntp-servers ntp0.training.nta-monitor.com;

And I'm using the following boot parameters in the PXE configuration file:

append vga=normal initrd=debian/lenny/i386/initrd.gz
hostname=unassigned domain=unassigned netcfg/no_default_route=true
auto=true url=http://10.0.57.1/debian/d-i/lenny/preseed.cfg
DEBCONF_DEBUG=5

For Lenny, this works fine. In particular the domain name gets set
from the DHCP "domain-name" option, the DNS servers get set from
"domain-name-servers", and the system sets the time from the NTP
server specified by the "ntp-servers" option.

For Squeeze, these boot parameters (appropriately changed to use the
Squeeze preseed URL) result in the domain name getting set to
"unassigned", the installer prompting for the DNS servers, and the
system trying to use the default Debian NTP servers (and failing
because I'm behind a proxy with no direct Internet access).

Wheezy shows the same behaviour as Squeeze.

I can specify these parameters by adding the appropriate additional
parameters to the boot options, but this is not ideal as I'd like to
store the information in the DHCP configuration so it's just in one place.

I think this is a regression in netcfg some time between Lenny and
Squeeze.

I notice the following changelog entry for netcfg 1.48:

* Refactor dhcp configuration code.

Could that be the culprit I wonder?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlALDrQACgkQy4enOlZ7nzpw6QCeOyTYnCafj0eIpkSB+dnBhKWB
k80An34LxUlU599Sxprp1395LPgUyTVm
=6HUK
-----END PGP SIGNATURE-----


Reply to: