Created attachment 1652495 [details]
Description of problem:
Even if ipv4.dhcp-timeout is set to infinity, the connection is deactivated if the DHCP server does not respond on renewal.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Setup bridge with dhcp and ipv4.dhcp-timeout=infinity
2. Activate the bridge, bridge will get an IP address via DHCP
3. Kill the dhcp server
NetworkManager deactivates the connection and removes the bridge.
NetworkManager keeps the connection active and the bridge can still work on layer 2.
Hi, it seems to work fine here:
# nmcli connection modify veth0+ ipv4.dhcp-timeout infinity
# nmcli connection up veth0+ &
# journalctl -u NetworkManager -e
Feb 04 10:46:11 fedora NetworkManager: <info> [1580809571.7718] device (veth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Feb 04 10:46:11 fedora NetworkManager: <info> [1580809571.7721] dhcp4 (veth0): activation: beginning transaction (no timeout)
# nmcli --version
nmcli tool, version 1.22.6
Are you sure the connection was reactivated after you changed the timeout?
It is working fine when specified on connection profile. It does not work in /etc/NetworkManager/conf.d/*.conf but int32 max is doing so this is fine by me.
> It is working fine when specified on connection profile. It does not work in /etc/NetworkManager/conf.d/*.conf but int32 max is doing so this is fine by me.
Please share the exact configuration file that you used. Did you reload the configuration after editing the file? Did you leave the corresponding setting in the profile at "0", so that the default can take effect?
We might need a level=TRACE log to understand this issue.
covered by bridge_down_to_l2_only
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.