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

Bug#757711: netcfg: promptly kills dhclient, deconfigures interface



retitle 757711 netcfg: promptly kills dhclient, deconfigures interface
reassign 757711 src:netcfg
found 757711 netcfg/1.118
severity 757711 grave
user debian-bsd@lists.debian.org
usertags 757711 + kfreebsd
thanks

Hi,

On 11/08/14 08:18, Jan Henke wrote:
> [...] DHCP client terminating directly after network
> detection (after receiving signal 15), which interferes later with the
> mirror selection, as there is no Internet connection then.

More specifically, this is what I see happening:
* dhclient correctly gets a DHCP lease and correctly sets the IPv4
address on the interface
* if it doesn't know yet what hostname to use, netcfg prompts the user
to enter one (and the DNS search domain)
* right after entering those, dhclient receives SIGTERM, gives up the
DHCP lease and deconfigures the interface.

> Aug 11 11:12:09 netcfg[1872]: WARNING **: Started DHCP client; PID is 1919
> Aug 11 11:12:10 dhclient: DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 1
> Aug 11 11:12:10 dhclient: DHCPREQUEST on em0 to 255.255.255.255 port 67
> Aug 11 11:12:10 dhclient: DHCPOFFER from 10.0.2.2
> Aug 11 11:12:10 dhclient: DHCPACK from 10.0.2.2
> Aug 11 11:12:10 dhclient: bound to 10.0.2.15 -- renewal in 41223 seconds.
> Aug 11 11:12:12 netcfg[1872]: DEBUG: Reading domain name returned via DHCP
> Aug 11 11:12:12 netcfg[1872]: DEBUG: DHCP domain name is ''
> Aug 11 11:12:12 netcfg[1872]: DEBUG: Reading nameservers from /etc/resolv.conf
> Aug 11 11:12:12 netcfg[1872]: DEBUG: Read nameserver 10.0.2.3
> Aug 11 11:12:12 netcfg[1872]: DEBUG: State is now 1
> Aug 11 11:12:12 netcfg[1872]: DEBUG: State is now 2
> Aug 11 11:12:12 netcfg[1872]: DEBUG: State is now 5
> Aug 11 11:12:12 netcfg[1872]: DEBUG: Using DNS to try and obtain default hostname
> Aug 11 11:12:12 netcfg[1872]: DEBUG: Getting default hostname from rDNS lookup of autoconfigured address fe80::5054:ff:fe12:3456
> Aug 11 11:12:12 netcfg[1872]: DEBUG: getnameinfo() returned -2 (Name or service not known)
> Aug 11 11:12:12 netcfg[1872]: DEBUG: Getting default hostname from rDNS lookup of autoconfigured address 10.0.2.15
> Aug 11 11:12:12 netcfg[1872]: DEBUG: getnameinfo() returned -2 (Name or service not known)
...then hostname and domain are provided...
> Aug 11 11:12:22 netcfg[1872]: DEBUG: State is now 6
> Aug 11 11:12:23 netcfg[1872]: DEBUG: Network config complete
> Aug 11 11:12:23 netcfg[1872]: DEBUG: No interface given; clearing /etc/network/interfaces
> Aug 11 11:12:23 netcfg[1872]: DEBUG: Writing informative header
> Aug 11 11:12:23 netcfg[1872]: DEBUG: Success!
> Aug 11 11:12:23 netcfg[1872]: DEBUG: Writing loopback interface
> Aug 11 11:12:23 netcfg[1872]: DEBUG: Success!
> Aug 11 11:12:23 netcfg[1872]: DEBUG: Writing DHCP stanza for em0
> Aug 11 11:12:23 netcfg[1872]: INFO: No hotpluggable devices are present in the system.
> Aug 11 11:12:23 netcfg[1872]: DEBUG: Success!
> Aug 11 11:12:23 dhclient: Received signal 15, initiating shutdown.
> Aug 11 11:12:23 dhclient: DHCPRELEASE on em0 to 10.0.2.2 port 67

Incriminating code is at:
http://anonscm.debian.org/cgit/d-i/netcfg.git/tree/dhcp.c#n617

Is it really intended that kill_dhcp_client will deconfigure the
interface?  Why was this not a problem for wheezy d-i?  Is it supposed
to be brought back up again in a later step?

Regards,
-- 
Steven Chamberlain
steven@pyro.eu.org

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: