On 2018-04-19 08:35, Mathias Homann wrote:
Am Donnerstag, 19. April 2018, 00:44:16 CEST schrieb David C. Rankin:
All,
As I sort out the 42.3 install, I'm down my checklist to "Why does wicked create a 30s delay in the boot process?"
As far as i know it's a bad interpretation of the DHCP protocol. The standard defines that a DHCP client shall insert a RANDOM delay of UP TO 30 seconds after start. The idea is that when an adminitrator wakes up a whole client network with tons of clients to install updates at night they don't all start hitting the DHCP server at the same time and break it.
Some dhcp clients "misunderstood" that line and forgot the random part, doing a full 30 second delay.
That's what I've been told. I have to admit that I haven't actually looked up the RFC yself so far...
I use fixed IPs, no dhcp. The delay is 20 seconds, fixed, not random. This is a home, nobody else is loading the network. Two interfaces, one of them unused and unconfigured. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)