nrohluap
November 17th, 2012, 08:48 PM
Question on networking and initramfs interaction.
Installing Ubuntu 12.10 Server, 64 bit, on some new hardware. Working on using dropbear / ssh to remotely unlock LUKS volumes at boot.
The install is very basic at this point: an SSH server, apt-get update/upgrade complete, and a static IP address set for eth0 in /etc/network/interfaces.
After installing dropbear, initramfs starts networking on bootup. By default, it uses DHCP. It is also possible to set a static IP. That much I have working, and can remotely ssh in when the server starts and is waiting for the luks passphrase.
What I can't figure out, and haven't found a post anywhere that addresses this, is that once this process completes and the server continues to boot, the network remains somehow under "control" of initramfs. Boot process stops for several minutes "waiting for network configuration." Once it finally starts, any settings in /etc/network/interfaces are ignored.
service networking restart changes nothing.
"ifdown eth0" says that eth0 is not configured.
"ifup eth0" reports RTNETLINK answers: File exists. Failed to bring up eth0.
/run/network has only the loopback entries. There are no longer entries for eth0 or the static network directory.
Am I missing a script in the /scripts/init-bottom or local-bottom where dropbear shuts down? Or is this expected when initramfs uses the network at boot?
Installing Ubuntu 12.10 Server, 64 bit, on some new hardware. Working on using dropbear / ssh to remotely unlock LUKS volumes at boot.
The install is very basic at this point: an SSH server, apt-get update/upgrade complete, and a static IP address set for eth0 in /etc/network/interfaces.
After installing dropbear, initramfs starts networking on bootup. By default, it uses DHCP. It is also possible to set a static IP. That much I have working, and can remotely ssh in when the server starts and is waiting for the luks passphrase.
What I can't figure out, and haven't found a post anywhere that addresses this, is that once this process completes and the server continues to boot, the network remains somehow under "control" of initramfs. Boot process stops for several minutes "waiting for network configuration." Once it finally starts, any settings in /etc/network/interfaces are ignored.
service networking restart changes nothing.
"ifdown eth0" says that eth0 is not configured.
"ifup eth0" reports RTNETLINK answers: File exists. Failed to bring up eth0.
/run/network has only the loopback entries. There are no longer entries for eth0 or the static network directory.
Am I missing a script in the /scripts/init-bottom or local-bottom where dropbear shuts down? Or is this expected when initramfs uses the network at boot?