dhcp at system boot on a bridged connection takes over a minute
Sam Varshavchik
mrsam at courier-mta.com
Sat Nov 16 20:38:48 UTC 2013
[root at monster ~]# systemd-analyze blame
1min 20.456s network.service
…
>From watching boot messages, it appears that DHCP takes over a minute. It
doesn't fail, eventually it acquires the assigned IP address, and the server
finishes booting normally.
This started happening after I bridged eth0 in order to assign LAN IP
addresses to VMs on the server.
Interestingly enough, doing ifdown vnet0/ifup vnet0 after booting does not
experience the same delay. ifup vnet0 acquires IP from DHCP in a few seconds.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/users/attachments/20131116/d6247fbe/attachment.sig>
More information about the users
mailing list