IPv4.method manual prevents connections IPv4.method auto gives causes dual IP
I'm running Fedora Server 34, on a with motherboard has dual Intel nics, one is dedicated to a TrueNAS VM and the other acts as a bridging device for my remaining VM's and the host itself. The bridge has a static IP address and I created thus:
nmcli con add type bridge autoconnect yes ifname br0 con-name br0 ipv4.address 192.168.1.10 ipv4.gateway 192.168.1.1 ipv4.method manual ipv4.dns 192.168.1.1 ipv6.method disabled
Added the slave interface:
nmcli conn add type bridge-slave ifname enp35s0 master br0
I bring the interface up and it appears to be working, I can ping any machine on my network, I can ping the gateway, I can ping google.com for example. If I ping the server from another machine on the network it responds. If I then try to access it via SSH or Cockpit the connections time out, if I try to access the VM's they are also similarly not available and those can't be ping'd either.
If I set ipv4.method auto then the bridge will get an IP address from DHCP, the problem with this is that br0 now has a static IP address and a DHCP address at the same time. I am able to connect to the server using either IP addresses so that's 192.168.1.10 and whatever DHCP has assigned. Another quirk is the VM's have to be restarted when I switch between auto and manual otherwise they're unable to reconnect but more often than not they're unable to connect at all.
I should also add NetworkManager spends a long time starting on boot up. I'm at a loss with this problem
NetworkManager version: 1.30.6-1.fc34 nmcli version: 1.30.6-1.fc34