I'm also seeing that d-i hangs after DHCP setup.
But only in Jessie Beta 2 - debian-jessie-DI-b2-amd64-netinst.iso. Not
with Beta 1. The OP also used debian-jessie-DI-b2-amd64-netinst.iso.
While it hangs, if I go to another terminal with ALT-F2, and issue:
> kill-all-dhcp
Then d-i continues past the hang.
This occurs in in our work environment in VMware Workstation and
Proxmox when using bridged eth0, but not when using NAT. In my home
network, the exact same procedure goes through without any hangs for
both bridged and NAT.
I've put a wireshark capture of everything from the virtual machine's
MAC address and /var/log/syslog from the installation up until after
running kill-all-dhcp at http://ge.tt/7b1wK872?c and also attached.
It seems that in our network, IPv6 reverse DNS lookups fail. It is a
likely suspect to why it hangs, but I can't be sure. Misconfigured
IPv6 networks are probably not uncommon! ;-)
The release announcement: "Debian Installer Jessie Beta 2 release" at
https://www.debian.org/devel/debian-installer/News/2014/20141005
says:
netcfg: Do not kill_dhcp_client after setting the hostname and domain,
otherwise Linux udhcpc will stop renewing its lease, and on other
platforms dhclient will de-configure the network interface (#757711,
#757988).
This comes from a fix to:
#757711 - netcfg: promptly kills dhclient, deconfigures interface -
Debian Bug report logs
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757711
which is:
Don't kill_dhcp_client without reason (Closes: #757711, #757988)
http://anonscm.debian.org/cgit/d-i/netcfg.git/commit/?id=48f1de7076f8d17a9bf4d11cb05968cb9d8987f7
that essentially is this diff:
diff --git a/dhcp.c b/dhcp.c
index aa37bd0..5ef0dbc 100644
--- a/dhcp.c
+++ b/dhcp.c
@@ -614,7 +614,6 @@ int netcfg_activate_dhcp (struct debconfclient
*client, struct netcfg_interface
netcfg_write_loopback();
netcfg_write_interface(interface);
netcfg_write_resolv(domain, interface);
- kill_dhcp_client();
stop_rdnssd();
return 0;
Since killing the dhcp client makes it continue for me, I'm pretty
sure the introduction of this fix for #757711 introduced in Jessie
Beta2 is the reason we're now seeing this.
Sincerely,
Peter
Attachment:
jessieInstallerDHCPProblems.pcapng
Description: application/pcapng
Attachment:
jessieInstallerDHCPProblems.syslog
Description: Binary data