bonienl

See Though personally I would stay on 6.6 and not downgrade

When you switch to XML view. How does the interface section look like? <interface type='bridge'> <mac address='52:54:00:c0:5f:69'/> <source bridge='br0.4'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <interface type='bridge'> <mac address='52:54:00:89:67:08'/> <source bridge='br0.5'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </interface>

The picture above says "Asus Prime H370M-plus"

Indeed no problem for the array, but no guarantees for Docker & VM. Unraid 6.4 uses outdated versions of Docker and Libvirt.

Without VLANs all can work as expected, but server and containers will be in the same network, no segregation. VLANs (or more physical interfaces) are required when more isolation between server and containers is preferred (security) or server to container communication is required. The observed call traces happen when a broadcast frame is received on a macvlan interface, not everybody is experiencing this issue (like myself). Difficult to tell if/when this will be solved in the linux kernel. The VLAN solution / workaround works for a number of users.

Try disabling of bonding for both eth1 and eth2 and leave only bridging enabled. See if that makes a difference.

Just tested. Can add a second or third bridge interface without problem. Are your first and second MAC address different (MAC addresses must be unique)?

Not sure which plugins you had installed before, but I don't think any plugin puts your system at risk. As the creator of the dynamix plugins, I am 100% sure these plugins are safe.

When VLANs are used on the Unraid server, these must be supported on your switch as a trunk connection (if a switch is present) and your router needs to be configured too to use VLANs (sub-interfaces).

Which part isn't working? Your picture shows both br1 and br2 assigned to the VM.

Most (all) plugins do not access the array, because they are used to expand GUI functionality. Applications which need to access the array are highly preferred to run as Docker container. Docker allows explicit access rules for protection.

It was fixed in an earlier version, but to force the fix it requires a manual update.

When the array starts cache_dirs will scan automatically the directories which are configured to be included.

All popup windows have the same separate styling which is based on the white theme. In other words these windows do not change when selecting a different theme.

See (you can take any disk to do the update)