I have just noticed an issue in my environment with DHCP/IPv4LL. I'm using an ethernet interface plugged directly into a router switch port, and every time my router reboots, I end up getting an IPv4LL address. I have to physically unplug the cable and re-plug before I can get a DHCP address. This appears to be caused by the router turning on the switch ports too soon before the DHCP server is started. I can also verify this issue by plugging the ethernet cable into an isolated switch (with no DHCP server), and then plugging that switch into the router later. In both cases I am stuck with the IPv4LL address.
So, what *should* happen here? Seems to me that connman should continue sending occasional DHCP discover requests even while it has an IPv4LL address, so that it can switch over once a DHCP server comes online. -Justin _______________________________________________ connman mailing list [email protected] http://lists.connman.net/listinfo/connman
