[Solved] unRAID Slow or Unresponsive due to bridge mode?

Version:

6.2-beta23

virtio-win-0.1.118

Goal:

I'm trying to setup a network bridge for my VMs so I can access them on my LAN. You can't do this with virtbr0, as it essentially works as a NAT and allows internet connectivity but not RDP access or network share access outside the virtual network.

Issue:

I created a bridge (br0) to accomplish this and it works, but I keep getting hung, frozen, and laggy VNC or RDP sessions. This is even experienced when I SSH into the Unraid server--typing will freeze for a few seconds.

root@Tower:~# ifconfiWrite failed: Broken pipe

After a few days of dealing with this, I stumbled upon a log message that I believe is the culprit. I've tried for a few hours now to figure out what this is and how to work around it. Here's the output from Unraid GUI Log Information:

Jul 7 09:59:20 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 10:01:26 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 10:03:31 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 10:05:36 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 10:07:41 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 10:09:46 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 10:11:51 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 10:13:56 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 10:16:01 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 10:18:06 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 10:20:11 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 10:22:16 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 10:24:21 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 10:26:25 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 10:28:31 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 10:30:36 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 10:32:41 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 10:34:46 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 10:36:51 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 10:38:56 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 10:41:01 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 10:43:05 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 10:45:11 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 10:47:16 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 10:49:21 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 10:51:26 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 10:53:31 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 10:55:36 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 10:57:41 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 10:59:46 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 11:01:51 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 11:03:56 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 11:06:01 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 11:08:06 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 11:10:11 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 11:12:16 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 11:14:21 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 11:16:26 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 11:18:31 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 11:20:36 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 11:22:42 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 11:24:46 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 11:26:51 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 11:28:56 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 11:31:01 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 11:33:06 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 11:35:11 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 11:37:16 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 11:39:21 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 11:41:26 Tower kernel: br0: received packet on eth0 with own address as source address
Jul 7 11:43:31 Tower kernel: br0: received packet on eth0 with own address as source address

I found this existing post on the subject-->https://lime-technology.com/forum/index.php?topic=46516.msg444453#msg444453, but it didn't seem to apply in my situation. This occurs whether or not I have a bond configured (and I only have a single ethernet port anyway).

This occurs whether or not I have VMs running or VMs enabled. Rebooting doesn't resolve the issue.

Is this an Unraid configuration problem or something else? I ran this command via SSH into Unraid to turn STP on, as initially it shows STP is off, but that didn't change anything:

brctl br0 stp on

Request:

I'm not a networking guru, so I don't understand the behavior, but from what I've read, it may be related to a faulty switch or STP. I'm seeking guidance on how to troubleshoot. The Unraid server is physically connected to a Netgear R6300v2 with latest firmware in AP mode, which is connected to a Zyxel FR1000Z. I'm not seeing options for STP in either device, but I gather that most modern routers have it enabled by default.

Thanks in advance for the help.

Removed my WiFi Access point that the unRAID server was physically connected to and the messages went away.