NetworkConfiguration
Sends an exit code before succesfully acquiring an IP
Initially reported against 10.1.0.
In its current form, dhcpcd apparently sends an exit code before it has succesfully acquired an IP (presumably, at the step where it backgrounds itself). This breaks the expected behavior for ifupdown. Other DHCP clients supported by ifupdown don't produce an exit code until an IP has been acquired. The above Debian bug provides more info.
This is likeley working as documented, see dhcpcd(1) --waitip. Our (Debian's) ifupdown integration is just broken.
This is likeley working as documented, see dhcpcd(1)
--waitip. Our (Debian's) ifupdown integration is just broken.
Adding --waitip to ifupdown's recipe might fix things. Then again, given how dhcpcd is designed to flip back and forth between LL and DHCP as needed, I'm not even sure why the reporter is getting that exit code.
The flipping between configuration protocols has nothing to do with anything here. The waitip option is to ensure a reasonable environment for system boot, what happens later is up to programs to handle correctly.