SOLVED Cannot create a bridge - how to diagnose?

[vmoriaux]

I try to add a bridge so that I can access my TrueNas services/apps from my VM.

I'm following the official instructions: https://www.truenas.com/docs/scale/scaletutorials/virtualization/accessingnasfromvm/

But when I get to the point where I test the changes, it spins for a while (60 secs, also tried with 180s) and reverts back all the changes. And I can't pinpoint what's wrong, there are not feedback. Are there any logs showing the test progress and failures? During the test I monitor the ping to the Truenas box and the IP doesn't respond until the revert happens.

I'm using an alias on the bridge to set the static IP. Should I use DHCP instead like I do for the physical NIC (before trying to setup the bridge)? I have a static lease setup but I'm not sure the bridge will expose the same MAC address.

I'm using TrueNAS-SCALE-23.10.1 with only one NIC. The NIC is currently set to get the IP over DHCP, and I configured a static lease.
I have running apps (I didn't see anywhere advise to shut them down) and two VMs (the one that needs the bridge is currently shutdown, again, should I turn off the other one?).

To get the logs I changed the test timeout to 30secs

log messages

Code:

Dec 27 23:27:44 truenas kernel: br0: port 1(eno1) entered blocking state
Dec 27 23:27:44 truenas kernel: br0: port 1(eno1) entered disabled state
Dec 27 23:28:14 truenas kernel: e1000e 0000:00:1f.6 eno1: NIC Link is Down
Dec 27 23:28:18 truenas kernel: e1000e 0000:00:1f.6 eno1: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Dec 27 23:28:18 truenas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes

Syslog

Code:

Dec 27 23:27:44 truenas avahi-daemon[3759]: Withdrawing address record for 192.168.120.3 on eno1.
Dec 27 23:27:44 truenas avahi-daemon[3759]: Leaving mDNS multicast group on interface eno1.IPv4 with address 192.168.120.3.
Dec 27 23:27:44 truenas avahi-daemon[3759]: Interface eno1.IPv4 no longer relevant for mDNS.
Dec 27 23:27:44 truenas avahi-daemon[3759]: Withdrawing address record for 2a01:e0a:3a6:1200:f639:9ff:fe07:dd29 on eno1.
Dec 27 23:27:44 truenas avahi-daemon[3759]: Leaving mDNS multicast group on interface eno1.IPv6 with address 2a01:e0a:3a6:1200:f639:9ff:fe07:dd29.
Dec 27 23:27:44 truenas avahi-daemon[3759]: Joining mDNS multicast group on interface eno1.IPv6 with address fe80::f639:9ff:fe07:dd29.
Dec 27 23:27:44 truenas avahi-daemon[3759]: Registering new address record for fe80::f639:9ff:fe07:dd29 on eno1.*.
Dec 27 23:27:44 truenas avahi-daemon[3759]: Withdrawing address record for fe80::f639:9ff:fe07:dd29 on eno1.
Dec 27 23:27:44 truenas avahi-daemon[3759]: Leaving mDNS multicast group on interface eno1.IPv6 with address fe80::f639:9ff:fe07:dd29.
Dec 27 23:27:44 truenas avahi-daemon[3759]: Interface eno1.IPv6 no longer relevant for mDNS.
Dec 27 23:27:44 truenas kernel: br0: port 1(eno1) entered blocking state
Dec 27 23:27:44 truenas kernel: br0: port 1(eno1) entered disabled state
Dec 27 23:27:44 truenas nscd[2724]: 2724 monitored file `/etc/resolv.conf` was written to
Dec 27 23:28:14 truenas kernel: e1000e 0000:00:1f.6 eno1: NIC Link is Down
Dec 27 23:28:15 truenas dhclient[73844]: DHCPREQUEST for 192.168.120.3 on eno1 to 255.255.255.255 port 67
Dec 27 23:28:15 truenas nscd[2724]: 2724 monitored file `/etc/resolv.conf` was written to
Dec 27 23:28:18 truenas kernel: e1000e 0000:00:1f.6 eno1: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Dec 27 23:28:18 truenas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
Dec 27 23:28:20 truenas avahi-daemon[3759]: Joining mDNS multicast group on interface eno1.IPv6 with address fe80::f639:9ff:fe07:dd29.
Dec 27 23:28:20 truenas avahi-daemon[3759]: New relevant interface eno1.IPv6 for mDNS.
Dec 27 23:28:20 truenas avahi-daemon[3759]: Registering new address record for fe80::f639:9ff:fe07:dd29 on eno1.*.
Dec 27 23:28:20 truenas dhclient[73844]: DHCPREQUEST for 192.168.120.3 on eno1 to 255.255.255.255 port 67
Dec 27 23:28:20 truenas dhclient[73844]: DHCPACK of 192.168.120.3 from 192.168.120.1
Dec 27 23:28:20 truenas avahi-daemon[3759]: Joining mDNS multicast group on interface eno1.IPv4 with address 192.168.120.3.
Dec 27 23:28:20 truenas avahi-daemon[3759]: New relevant interface eno1.IPv4 for mDNS.
Dec 27 23:28:20 truenas avahi-daemon[3759]: Registering new address record for 192.168.120.3 on eno1.IPv4.
Dec 27 23:28:20 truenas dhclient[73844]: bound to 192.168.120.3 -- renewal in 18913 seconds.
Dec 27 23:28:21 truenas avahi-daemon[3759]: Leaving mDNS multicast group on interface eno1.IPv6 with address fe80::f639:9ff:fe07:dd29.
Dec 27 23:28:21 truenas avahi-daemon[3759]: Joining mDNS multicast group on interface eno1.IPv6 with address 2a01:e0a:3a6:1200:f639:9ff:fe07:dd29.
Dec 27 23:28:21 truenas avahi-daemon[3759]: Registering new address record for 2a01:e0a:3a6:1200:f639:9ff:fe07:dd29 on eno1.*.
Dec 27 23:28:21 truenas avahi-daemon[3759]: Withdrawing address record for fe80::f639:9ff:fe07:dd29 on eno1.

 

[sretalla]

I have running apps (I didn't see anywhere advise to shut them down) and two VMs (the one that needs the bridge is currently shutdown, again, should I turn off the other one?).

This will be the problem. You need to stop all apps and VMs or the network changes will stall.

I'm using an alias on the bridge to set the static IP. Should I use DHCP instead like I do for the physical NIC (before trying to setup the bridge)?

No, don't do that.

I have a static lease setup but I'm not sure the bridge will expose the same MAC address.

Again, don't do that, but it uses a different MAC address.

 

[vmoriaux]

Thanks ! That worked immediately