Strange DHCP behaviour on high InterfaceInitialise timeout

miclam wrote on Thursday, June 22, 2017:


during testing with my three Interfaces (Ethernet, Powerline, Bridge) I found a strange
behaviour of the DHCP which I found hard to figure out.

What happend, was that I did not connect a Cable to my Eth Interface, thus the PHY
Autonegotiation failed. But it’s timeout was set to 5s, whereas the IP stack sends
NetworkDown Events every 3 seconds (for all interfaces). So multiple DHCP requests where
send and the Transaction ID always missmatched.

Maybe it’s noteworthy that the NetworkInterfaceInitialise methods should finish in <1s, especially
with multiple interfaces.