4 ms·
I've noticed that dhcpcd always gets the lease, then broadcasts on the network to see if anybody else has that address, waits for a timeout, and then proceeds.
by frezik 13y ago
I've noticed that dhcpcd always gets the lease, then broadcasts on the network to see if anybody else has that address, waits for a timeout, and then proceeds. This seems like an unnecessary waste of boot time when you're on uncomplicated home networks; the DHCP server can be trusted to give a fresh address almost always. Doubly so if you've set your AP to static MAC address mappings.
Is there a way to shut that off, or a Linux DHCP client that doesn't do that?
- rake 13y agoWhy just not use static IP addresses instead?
- simcop2387 13y agoSwitching to dhclient instead of dhcpcd will usually help that. Once it has an address it will go into the background during that check if the ip address is actually available. You can stop that by running it with -d if you're debugging a bad network.
- malone 13y agoThat check is actually recommended by the RFC, but using the --noarp switch should disable it.