Comment 0 for bug 1466790
Revision history for this message
| Stefan Bader (smb) wrote dhclient not started on boot | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Not sure whether this is a systemd or ifupdown issue. I just happened to notice today for a Wily VM (set up from server iso) that I failed to get a DNS resolution for a VM I started earlier the day. DNS updates in my case are related to DHCP updates. And on the DHCP/DNS server I noticed that the IP address had been removed at some point. Looking at the VM, I find no dhclient being started. When I manually run ifdown and ifup on the interface this does happen. But not whenever I boot.
Curious about this I also checked a Vivid VM (also server install) and this looks the same.
Network config in /etc/network/
auto eth0
iface eth0 inet dhcp
Expected result:
dhclient running for eth0
Actual result after boot:
No dhclient process is running.