Bridge vmbr0 entered blocking state

S

scottrus71

New Member
Sep 7, 2023
9
0
1
Is this common with Proxmox bridge? See below for a log of frequent blocking/forwarding state changes.
A basic description my network is:
  • Unify Dream Machine Pro with latest GA OS and Network stack
  • Unify 48 Port Switch Pro
  • Default VLAN is "LAN1" (192.168.1.0/24)
  • Configured a second VLAN of "PVE Network" with TAG 200 (192.168.200.0/24)
  • On ports 2, 4, and 6 of the switch, set with "PVE Network (200)" as the "Primary Network" on the port
  • 3 x Intel NUC connected to ports 2, 4, and 6 of the switch.
Config of /etc/network/interfaces. This is the same on all three Proxmox hosts.

Code: 
auto lo
iface lo inet loopback

iface enp89s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.200.103/24
        gateway 192.168.200.1
        bridge-ports enp89s0
        bridge-stp off
        bridge-fd 0


Output of journalctl | grep vmbr0 showing the bridge blocking/forwarding. I see this on all three Proxmox hosts. The timestamps across all three hosts do not indicated they all have the issue at the same time.

Code: 
Sep 12 08:18:14 pve-node-01 kernel: vmbr0: port 4(veth113i0) entered disabled state
Sep 12 08:18:14 pve-node-01 kernel: vmbr0: port 4(veth113i0) entered disabled state
Sep 12 08:18:17 pve-node-01 kernel: vmbr0: port 4(veth113i0) entered blocking state
Sep 12 08:18:17 pve-node-01 kernel: vmbr0: port 4(veth113i0) entered disabled state
Sep 12 08:18:17 pve-node-01 kernel: vmbr0: port 4(veth113i0) entered blocking state
Sep 12 08:18:17 pve-node-01 kernel: vmbr0: port 4(veth113i0) entered forwarding state
Sep 12 10:02:38 pve-node-01 kernel: vmbr0: port 2(veth108i0) entered disabled state
Sep 12 10:02:38 pve-node-01 kernel: vmbr0: port 2(veth108i0) entered disabled state
Sep 12 10:02:39 pve-node-01 kernel: vmbr0: port 3(veth110i0) entered disabled state
Sep 12 10:02:39 pve-node-01 kernel: vmbr0: port 3(veth110i0) entered disabled state
Sep 12 10:02:39 pve-node-01 kernel: vmbr0: port 6(veth114i0) entered disabled state
Sep 12 10:02:39 pve-node-01 kernel: vmbr0: port 6(veth114i0) entered disabled state
Sep 12 10:02:39 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered disabled state
Sep 12 10:02:39 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered disabled state
Sep 12 10:02:39 pve-node-01 kernel: vmbr0v1: port 2(veth115i1) entered disabled state
Sep 12 10:02:39 pve-node-01 kernel: vmbr0v1: port 2(veth115i1) entered disabled state
Sep 12 10:02:41 pve-node-01 kernel: vmbr0: port 5(fwpr101p0) entered disabled state
Sep 12 10:02:41 pve-node-01 kernel: vmbr0: port 5(fwpr101p0) entered disabled state
Sep 12 10:02:45 pve-node-01 kernel: vmbr0: port 4(veth113i0) entered disabled state
Sep 12 10:02:45 pve-node-01 kernel: vmbr0: port 4(veth113i0) entered disabled state
Sep 12 10:03:36 pve-node-01 kernel: vmbr0: port 1(enp89s0) entered blocking state
Sep 12 10:03:36 pve-node-01 kernel: vmbr0: port 1(enp89s0) entered disabled state
Sep 12 10:03:39 pve-node-01 kernel: vmbr0: port 1(enp89s0) entered blocking state
Sep 12 10:03:39 pve-node-01 kernel: vmbr0: port 1(enp89s0) entered forwarding state
Sep 12 10:03:39 pve-node-01 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vmbr0: link becomes ready
Sep 12 10:03:48 pve-node-01 kernel: vmbr0: port 2(fwpr101p0) entered blocking state
Sep 12 10:03:48 pve-node-01 kernel: vmbr0: port 2(fwpr101p0) entered disabled state
Sep 12 10:03:48 pve-node-01 kernel: vmbr0: port 2(fwpr101p0) entered blocking state
Sep 12 10:03:48 pve-node-01 kernel: vmbr0: port 2(fwpr101p0) entered forwarding state
Sep 12 10:03:50 pve-node-01 kernel: vmbr0: port 3(veth108i0) entered blocking state
Sep 12 10:03:50 pve-node-01 kernel: vmbr0: port 3(veth108i0) entered disabled state
Sep 12 10:03:50 pve-node-01 kernel: vmbr0: port 3(veth108i0) entered blocking state
Sep 12 10:03:50 pve-node-01 kernel: vmbr0: port 3(veth108i0) entered forwarding state
Sep 12 10:03:52 pve-node-01 kernel: vmbr0: port 4(veth110i0) entered blocking state
Sep 12 10:03:52 pve-node-01 kernel: vmbr0: port 4(veth110i0) entered disabled state
Sep 12 10:03:52 pve-node-01 kernel: vmbr0: port 4(veth110i0) entered blocking state
Sep 12 10:03:52 pve-node-01 kernel: vmbr0: port 4(veth110i0) entered forwarding state
Sep 12 10:03:54 pve-node-01 kernel: vmbr0: port 5(veth113i0) entered blocking state
Sep 12 10:03:54 pve-node-01 kernel: vmbr0: port 5(veth113i0) entered disabled state
Sep 12 10:03:54 pve-node-01 kernel: vmbr0: port 5(veth113i0) entered blocking state
Sep 12 10:03:54 pve-node-01 kernel: vmbr0: port 5(veth113i0) entered forwarding state
Sep 12 10:03:56 pve-node-01 kernel: vmbr0: port 6(veth114i0) entered blocking state
Sep 12 10:03:56 pve-node-01 kernel: vmbr0: port 6(veth114i0) entered disabled state
Sep 12 10:03:56 pve-node-01 kernel: vmbr0: port 6(veth114i0) entered blocking state
Sep 12 10:03:56 pve-node-01 kernel: vmbr0: port 6(veth114i0) entered forwarding state
Sep 12 10:03:58 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered blocking state
Sep 12 10:03:58 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered disabled state
Sep 12 10:03:58 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered blocking state
Sep 12 10:03:58 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered disabled state
Sep 12 10:03:58 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered blocking state
Sep 12 10:03:58 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered forwarding state
Sep 12 10:03:59 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered disabled state
Sep 12 10:03:59 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered blocking state
Sep 12 10:03:59 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered forwarding state
Sep 12 10:03:59 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered blocking state
Sep 12 10:03:59 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered forwarding state
Sep 12 10:08:30 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered disabled state
Sep 12 10:08:30 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered blocking state
Sep 12 10:08:30 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered disabled state
Sep 12 10:08:30 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered blocking state
Sep 12 10:08:30 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered forwarding state
Sep 12 10:08:39 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered disabled state
Sep 12 10:08:39 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered disabled state
Sep 12 10:08:39 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered disabled state
Sep 12 10:08:39 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered disabled state
Sep 12 10:08:41 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered blocking state
Sep 12 10:08:41 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered disabled state
Sep 12 10:08:42 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered blocking state
Sep 12 10:08:42 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered disabled state
Sep 12 10:08:42 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered blocking state
Sep 12 10:08:42 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered forwarding state
Sep 12 10:08:42 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered disabled state
Sep 12 10:08:42 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered blocking state
Sep 12 10:08:42 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered forwarding state
Sep 12 10:08:42 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered blocking state
Sep 12 10:08:42 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered forwarding state
Sep 12 10:09:22 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered disabled state
Sep 12 10:09:22 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered blocking state
Sep 12 10:09:22 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered disabled state
Sep 12 10:09:22 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered blocking state
Sep 12 10:09:22 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered forwarding state
Sep 12 10:09:49 pve-node-01 kernel: vmbr0: port 3(veth108i0) entered disabled state
Sep 12 10:09:49 pve-node-01 kernel: vmbr0: port 3(veth108i0) entered disabled state
Sep 12 10:09:49 pve-node-01 kernel: vmbr0: port 6(veth114i0) entered disabled state
Sep 12 10:09:49 pve-node-01 kernel: vmbr0: port 6(veth114i0) entered disabled state
Sep 12 10:09:49 pve-node-01 kernel: vmbr0: port 4(veth110i0) entered disabled state
Sep 12 10:09:49 pve-node-01 kernel: vmbr0: port 4(veth110i0) entered disabled state
Sep 12 10:09:51 pve-node-01 kernel: vmbr0: port 2(fwpr101p0) entered disabled state
Sep 12 10:09:51 pve-node-01 kernel: vmbr0: port 2(fwpr101p0) entered disabled state
Sep 12 10:09:51 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered disabled state
Sep 12 10:09:51 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered disabled state
Sep 12 10:09:51 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered disabled state
Sep 12 10:09:51 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered disabled state
Sep 12 10:09:56 pve-node-01 kernel: vmbr0: port 5(veth113i0) entered disabled state
Sep 12 10:09:56 pve-node-01 kernel: vmbr0: port 5(veth113i0) entered disabled state
Sep 12 10:10:35 pve-node-01 kernel: vmbr0: port 1(enp89s0) entered blocking state
Sep 12 10:10:35 pve-node-01 kernel: vmbr0: port 1(enp89s0) entered disabled state
Sep 12 10:10:38 pve-node-01 kernel: vmbr0: port 1(enp89s0) entered blocking state
Sep 12 10:10:38 pve-node-01 kernel: vmbr0: port 1(enp89s0) entered forwarding state
Sep 12 10:10:38 pve-node-01 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vmbr0: link becomes ready
Sep 12 10:10:47 pve-node-01 kernel: vmbr0: port 2(fwpr101p0) entered blocking state
Sep 12 10:10:47 pve-node-01 kernel: vmbr0: port 2(fwpr101p0) entered disabled state
Sep 12 10:10:47 pve-node-01 kernel: vmbr0: port 2(fwpr101p0) entered blocking state
Sep 12 10:10:47 pve-node-01 kernel: vmbr0: port 2(fwpr101p0) entered forwarding state
Sep 12 10:10:49 pve-node-01 kernel: vmbr0: port 3(veth108i0) entered blocking state
Sep 12 10:10:49 pve-node-01 kernel: vmbr0: port 3(veth108i0) entered disabled state
Sep 12 10:10:49 pve-node-01 kernel: vmbr0: port 3(veth108i0) entered blocking state
Sep 12 10:10:49 pve-node-01 kernel: vmbr0: port 3(veth108i0) entered forwarding state
Sep 12 10:10:51 pve-node-01 kernel: vmbr0: port 4(veth110i0) entered blocking state
Sep 12 10:10:51 pve-node-01 kernel: vmbr0: port 4(veth110i0) entered disabled state
Sep 12 10:10:52 pve-node-01 kernel: vmbr0: port 4(veth110i0) entered blocking state
Sep 12 10:10:52 pve-node-01 kernel: vmbr0: port 4(veth110i0) entered forwarding state
Sep 12 10:10:53 pve-node-01 kernel: vmbr0: port 5(veth113i0) entered blocking state
Sep 12 10:10:53 pve-node-01 kernel: vmbr0: port 5(veth113i0) entered disabled state
Sep 12 10:10:54 pve-node-01 kernel: vmbr0: port 5(veth113i0) entered blocking state
Sep 12 10:10:54 pve-node-01 kernel: vmbr0: port 5(veth113i0) entered forwarding state
Sep 12 10:10:55 pve-node-01 kernel: vmbr0: port 6(veth114i0) entered blocking state
Sep 12 10:10:55 pve-node-01 kernel: vmbr0: port 6(veth114i0) entered disabled state
Sep 12 10:10:55 pve-node-01 kernel: vmbr0: port 6(veth114i0) entered blocking state
Sep 12 10:10:55 pve-node-01 kernel: vmbr0: port 6(veth114i0) entered forwarding state
Sep 12 10:10:57 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered blocking state
Sep 12 10:10:57 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered disabled state
Sep 12 10:10:57 pve-node-01 kernel: vmbr0v1: port 1(enp89s0.1) entered blocking state
Sep 12 10:10:57 pve-node-01 kernel: vmbr0v1: port 1(enp89s0.1) entered disabled state
Sep 12 10:10:57 pve-node-01 kernel: vmbr0v1: port 1(enp89s0.1) entered blocking state
Sep 12 10:10:57 pve-node-01 kernel: vmbr0v1: port 1(enp89s0.1) entered forwarding state
Sep 12 10:10:57 pve-node-01 kernel: vmbr0v1: port 2(veth115i1) entered blocking state
Sep 12 10:10:57 pve-node-01 kernel: vmbr0v1: port 2(veth115i1) entered disabled state
Sep 12 10:10:57 pve-node-01 kernel: vmbr0v1: port 2(veth115i1) entered blocking state
Sep 12 10:10:57 pve-node-01 kernel: vmbr0v1: port 2(veth115i1) entered forwarding state
Sep 12 10:10:58 pve-node-01 kernel: vmbr0v1: port 2(veth115i1) entered disabled state
Sep 12 10:10:58 pve-node-01 kernel: vmbr0v1: port 2(veth115i1) entered blocking state
Sep 12 10:10:58 pve-node-01 kernel: vmbr0v1: port 2(veth115i1) entered forwarding state
Sep 12 10:10:58 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered blocking state
Sep 12 10:10:58 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered forwarding state


Screenshot of Port 2 Config. Ports 4 and 6 are the same.

Screenshot 2023-09-12 at 3.39.14 PM.png
 
I'm actually not sure if I have a invalid VLAN configuration between the Switch, Proxmox hosts, and LXC configs, or if I have a different problem such as RSTP issues.
 
scottrus71 said:
Is this common with Proxmox bridge? See below for a log of frequent blocking/forwarding state changes.
A basic description my network is:
  • Unify Dream Machine Pro with latest GA OS and Network stack
  • Unify 48 Port Switch Pro
  • Default VLAN is "LAN1" (192.168.1.0/24)
  • Configured a second VLAN of "PVE Network" with TAG 200 (192.168.200.0/24)
  • On ports 2, 4, and 6 of the switch, set with "PVE Network (200)" as the "Primary Network" on the port
  • 3 x Intel NUC connected to ports 2, 4, and 6 of the switch.
Config of /etc/network/interfaces. This is the same on all three Proxmox hosts.

Code: 
auto lo
iface lo inet loopback

iface enp89s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.200.103/24
        gateway 192.168.200.1
        bridge-ports enp89s0
        bridge-stp off
        bridge-fd 0


Output of journalctl | grep vmbr0 showing the bridge blocking/forwarding. I see this on all three Proxmox hosts. The timestamps across all three hosts do not indicated they all have the issue at the same time.

Code: 
Sep 12 08:18:14 pve-node-01 kernel: vmbr0: port 4(veth113i0) entered disabled state
Sep 12 08:18:14 pve-node-01 kernel: vmbr0: port 4(veth113i0) entered disabled state
Sep 12 08:18:17 pve-node-01 kernel: vmbr0: port 4(veth113i0) entered blocking state
Sep 12 08:18:17 pve-node-01 kernel: vmbr0: port 4(veth113i0) entered disabled state
Sep 12 08:18:17 pve-node-01 kernel: vmbr0: port 4(veth113i0) entered blocking state
Sep 12 08:18:17 pve-node-01 kernel: vmbr0: port 4(veth113i0) entered forwarding state
Sep 12 10:02:38 pve-node-01 kernel: vmbr0: port 2(veth108i0) entered disabled state
Sep 12 10:02:38 pve-node-01 kernel: vmbr0: port 2(veth108i0) entered disabled state
Sep 12 10:02:39 pve-node-01 kernel: vmbr0: port 3(veth110i0) entered disabled state
Sep 12 10:02:39 pve-node-01 kernel: vmbr0: port 3(veth110i0) entered disabled state
Sep 12 10:02:39 pve-node-01 kernel: vmbr0: port 6(veth114i0) entered disabled state
Sep 12 10:02:39 pve-node-01 kernel: vmbr0: port 6(veth114i0) entered disabled state
Sep 12 10:02:39 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered disabled state
Sep 12 10:02:39 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered disabled state
Sep 12 10:02:39 pve-node-01 kernel: vmbr0v1: port 2(veth115i1) entered disabled state
Sep 12 10:02:39 pve-node-01 kernel: vmbr0v1: port 2(veth115i1) entered disabled state
Sep 12 10:02:41 pve-node-01 kernel: vmbr0: port 5(fwpr101p0) entered disabled state
Sep 12 10:02:41 pve-node-01 kernel: vmbr0: port 5(fwpr101p0) entered disabled state
Sep 12 10:02:45 pve-node-01 kernel: vmbr0: port 4(veth113i0) entered disabled state
Sep 12 10:02:45 pve-node-01 kernel: vmbr0: port 4(veth113i0) entered disabled state
Sep 12 10:03:36 pve-node-01 kernel: vmbr0: port 1(enp89s0) entered blocking state
Sep 12 10:03:36 pve-node-01 kernel: vmbr0: port 1(enp89s0) entered disabled state
Sep 12 10:03:39 pve-node-01 kernel: vmbr0: port 1(enp89s0) entered blocking state
Sep 12 10:03:39 pve-node-01 kernel: vmbr0: port 1(enp89s0) entered forwarding state
Sep 12 10:03:39 pve-node-01 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vmbr0: link becomes ready
Sep 12 10:03:48 pve-node-01 kernel: vmbr0: port 2(fwpr101p0) entered blocking state
Sep 12 10:03:48 pve-node-01 kernel: vmbr0: port 2(fwpr101p0) entered disabled state
Sep 12 10:03:48 pve-node-01 kernel: vmbr0: port 2(fwpr101p0) entered blocking state
Sep 12 10:03:48 pve-node-01 kernel: vmbr0: port 2(fwpr101p0) entered forwarding state
Sep 12 10:03:50 pve-node-01 kernel: vmbr0: port 3(veth108i0) entered blocking state
Sep 12 10:03:50 pve-node-01 kernel: vmbr0: port 3(veth108i0) entered disabled state
Sep 12 10:03:50 pve-node-01 kernel: vmbr0: port 3(veth108i0) entered blocking state
Sep 12 10:03:50 pve-node-01 kernel: vmbr0: port 3(veth108i0) entered forwarding state
Sep 12 10:03:52 pve-node-01 kernel: vmbr0: port 4(veth110i0) entered blocking state
Sep 12 10:03:52 pve-node-01 kernel: vmbr0: port 4(veth110i0) entered disabled state
Sep 12 10:03:52 pve-node-01 kernel: vmbr0: port 4(veth110i0) entered blocking state
Sep 12 10:03:52 pve-node-01 kernel: vmbr0: port 4(veth110i0) entered forwarding state
Sep 12 10:03:54 pve-node-01 kernel: vmbr0: port 5(veth113i0) entered blocking state
Sep 12 10:03:54 pve-node-01 kernel: vmbr0: port 5(veth113i0) entered disabled state
Sep 12 10:03:54 pve-node-01 kernel: vmbr0: port 5(veth113i0) entered blocking state
Sep 12 10:03:54 pve-node-01 kernel: vmbr0: port 5(veth113i0) entered forwarding state
Sep 12 10:03:56 pve-node-01 kernel: vmbr0: port 6(veth114i0) entered blocking state
Sep 12 10:03:56 pve-node-01 kernel: vmbr0: port 6(veth114i0) entered disabled state
Sep 12 10:03:56 pve-node-01 kernel: vmbr0: port 6(veth114i0) entered blocking state
Sep 12 10:03:56 pve-node-01 kernel: vmbr0: port 6(veth114i0) entered forwarding state
Sep 12 10:03:58 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered blocking state
Sep 12 10:03:58 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered disabled state
Sep 12 10:03:58 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered blocking state
Sep 12 10:03:58 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered disabled state
Sep 12 10:03:58 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered blocking state
Sep 12 10:03:58 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered forwarding state
Sep 12 10:03:59 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered disabled state
Sep 12 10:03:59 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered blocking state
Sep 12 10:03:59 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered forwarding state
Sep 12 10:03:59 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered blocking state
Sep 12 10:03:59 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered forwarding state
Sep 12 10:08:30 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered disabled state
Sep 12 10:08:30 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered blocking state
Sep 12 10:08:30 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered disabled state
Sep 12 10:08:30 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered blocking state
Sep 12 10:08:30 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered forwarding state
Sep 12 10:08:39 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered disabled state
Sep 12 10:08:39 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered disabled state
Sep 12 10:08:39 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered disabled state
Sep 12 10:08:39 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered disabled state
Sep 12 10:08:41 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered blocking state
Sep 12 10:08:41 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered disabled state
Sep 12 10:08:42 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered blocking state
Sep 12 10:08:42 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered disabled state
Sep 12 10:08:42 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered blocking state
Sep 12 10:08:42 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered forwarding state
Sep 12 10:08:42 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered disabled state
Sep 12 10:08:42 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered blocking state
Sep 12 10:08:42 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered forwarding state
Sep 12 10:08:42 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered blocking state
Sep 12 10:08:42 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered forwarding state
Sep 12 10:09:22 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered disabled state
Sep 12 10:09:22 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered blocking state
Sep 12 10:09:22 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered disabled state
Sep 12 10:09:22 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered blocking state
Sep 12 10:09:22 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered forwarding state
Sep 12 10:09:49 pve-node-01 kernel: vmbr0: port 3(veth108i0) entered disabled state
Sep 12 10:09:49 pve-node-01 kernel: vmbr0: port 3(veth108i0) entered disabled state
Sep 12 10:09:49 pve-node-01 kernel: vmbr0: port 6(veth114i0) entered disabled state
Sep 12 10:09:49 pve-node-01 kernel: vmbr0: port 6(veth114i0) entered disabled state
Sep 12 10:09:49 pve-node-01 kernel: vmbr0: port 4(veth110i0) entered disabled state
Sep 12 10:09:49 pve-node-01 kernel: vmbr0: port 4(veth110i0) entered disabled state
Sep 12 10:09:51 pve-node-01 kernel: vmbr0: port 2(fwpr101p0) entered disabled state
Sep 12 10:09:51 pve-node-01 kernel: vmbr0: port 2(fwpr101p0) entered disabled state
Sep 12 10:09:51 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered disabled state
Sep 12 10:09:51 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered disabled state
Sep 12 10:09:51 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered disabled state
Sep 12 10:09:51 pve-node-01 kernel: vmbr0: port 8(veth115i1) entered disabled state
Sep 12 10:09:56 pve-node-01 kernel: vmbr0: port 5(veth113i0) entered disabled state
Sep 12 10:09:56 pve-node-01 kernel: vmbr0: port 5(veth113i0) entered disabled state
Sep 12 10:10:35 pve-node-01 kernel: vmbr0: port 1(enp89s0) entered blocking state
Sep 12 10:10:35 pve-node-01 kernel: vmbr0: port 1(enp89s0) entered disabled state
Sep 12 10:10:38 pve-node-01 kernel: vmbr0: port 1(enp89s0) entered blocking state
Sep 12 10:10:38 pve-node-01 kernel: vmbr0: port 1(enp89s0) entered forwarding state
Sep 12 10:10:38 pve-node-01 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vmbr0: link becomes ready
Sep 12 10:10:47 pve-node-01 kernel: vmbr0: port 2(fwpr101p0) entered blocking state
Sep 12 10:10:47 pve-node-01 kernel: vmbr0: port 2(fwpr101p0) entered disabled state
Sep 12 10:10:47 pve-node-01 kernel: vmbr0: port 2(fwpr101p0) entered blocking state
Sep 12 10:10:47 pve-node-01 kernel: vmbr0: port 2(fwpr101p0) entered forwarding state
Sep 12 10:10:49 pve-node-01 kernel: vmbr0: port 3(veth108i0) entered blocking state
Sep 12 10:10:49 pve-node-01 kernel: vmbr0: port 3(veth108i0) entered disabled state
Sep 12 10:10:49 pve-node-01 kernel: vmbr0: port 3(veth108i0) entered blocking state
Sep 12 10:10:49 pve-node-01 kernel: vmbr0: port 3(veth108i0) entered forwarding state
Sep 12 10:10:51 pve-node-01 kernel: vmbr0: port 4(veth110i0) entered blocking state
Sep 12 10:10:51 pve-node-01 kernel: vmbr0: port 4(veth110i0) entered disabled state
Sep 12 10:10:52 pve-node-01 kernel: vmbr0: port 4(veth110i0) entered blocking state
Sep 12 10:10:52 pve-node-01 kernel: vmbr0: port 4(veth110i0) entered forwarding state
Sep 12 10:10:53 pve-node-01 kernel: vmbr0: port 5(veth113i0) entered blocking state
Sep 12 10:10:53 pve-node-01 kernel: vmbr0: port 5(veth113i0) entered disabled state
Sep 12 10:10:54 pve-node-01 kernel: vmbr0: port 5(veth113i0) entered blocking state
Sep 12 10:10:54 pve-node-01 kernel: vmbr0: port 5(veth113i0) entered forwarding state
Sep 12 10:10:55 pve-node-01 kernel: vmbr0: port 6(veth114i0) entered blocking state
Sep 12 10:10:55 pve-node-01 kernel: vmbr0: port 6(veth114i0) entered disabled state
Sep 12 10:10:55 pve-node-01 kernel: vmbr0: port 6(veth114i0) entered blocking state
Sep 12 10:10:55 pve-node-01 kernel: vmbr0: port 6(veth114i0) entered forwarding state
Sep 12 10:10:57 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered blocking state
Sep 12 10:10:57 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered disabled state
Sep 12 10:10:57 pve-node-01 kernel: vmbr0v1: port 1(enp89s0.1) entered blocking state
Sep 12 10:10:57 pve-node-01 kernel: vmbr0v1: port 1(enp89s0.1) entered disabled state
Sep 12 10:10:57 pve-node-01 kernel: vmbr0v1: port 1(enp89s0.1) entered blocking state
Sep 12 10:10:57 pve-node-01 kernel: vmbr0v1: port 1(enp89s0.1) entered forwarding state
Sep 12 10:10:57 pve-node-01 kernel: vmbr0v1: port 2(veth115i1) entered blocking state
Sep 12 10:10:57 pve-node-01 kernel: vmbr0v1: port 2(veth115i1) entered disabled state
Sep 12 10:10:57 pve-node-01 kernel: vmbr0v1: port 2(veth115i1) entered blocking state
Sep 12 10:10:57 pve-node-01 kernel: vmbr0v1: port 2(veth115i1) entered forwarding state
Sep 12 10:10:58 pve-node-01 kernel: vmbr0v1: port 2(veth115i1) entered disabled state
Sep 12 10:10:58 pve-node-01 kernel: vmbr0v1: port 2(veth115i1) entered blocking state
Sep 12 10:10:58 pve-node-01 kernel: vmbr0v1: port 2(veth115i1) entered forwarding state
Sep 12 10:10:58 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered blocking state
Sep 12 10:10:58 pve-node-01 kernel: vmbr0: port 7(veth115i0) entered forwarding state


Screenshot of Port 2 Config. Ports 4 and 6 are the same. uno online

View attachment 55345
Click to expand...
These are informational messages that your bridge is in blocking state (not forwarding packets), as long as the bridge goes to forwarding mode you should have no problem. The messages are generated by the bridge_stp setting, which controls whether the bridge checks for loops or not.
You can create a fake stp daemon and disable in-kernel stp handling to prevent the state changes. The result provides a code snippet to do this.
You can reference two posts.
https://forum.proxmox.com/threads/v...isabled-then-blocking-then-forwarding.124934/
https://forum.proxmox.com/threads/vmbr0-port-1-enp2s0-entered-blocking-state.36586/
 
I have similar issues, last I recall doing was messing with cables, messing with vmbr0 switch config, and messing with this:

#net.ipv6.conf.all.forwarding=1

line in
/etc/sysctl.conf

Should I have forwarding on =1 or =0 ?
I'm guessing =1

Sorry I mean ipv4
#net.ipv4.ip_forward=1
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back