Moving Back To Higher Priority Connection Profile After Link-Local Fallback ?
Hello, I've been digging for a solution to this and hoping someone here can help determine if NetworkManager can handle this.
Question: Is it possible to configure an ethernet connection that will fall back to link-local, but also continue sending DHCP Discover requests so that an IP can be obtained and we can move back to the higher priority connection profile if a DHCP server eventually becomes available?
Additional Details: I'm trying to configure an ethernet device that would fall back to a link-local connection if a DHCP address cannot be initially obtained, but would also like to continue making DHCP Discover requests so that we can move back to the DHCP/auto connection if an address can eventually be obtained. For example, if the DHCP server was down when initially connected but comes back up at a later point.
My current configuration is that I have 2 connection profiles configured, one with ipv4.method set to auto, which has a higher priority and connection.autoconnect-retries set to 2. My other connection is set to ipv4.method of link-local. The fallback works fine but I'm running into a situation where I could end up in a link-local state and not move back to the DHCP configured connection.
Is it possible to accomplish what I'm trying to do via a NetworkManager configuration? Thank you.