bonienl

When you start up the system it will try to find any of the known wireless networks, with the last connected network preferred.
 
Once the system is operational, only manual switching of wireless networks is supported.
 

These messages indicate that the NTP client on Unraid can not reach this NTP server.
By itself not a problem if other NTP servers are reachable, otherwise you could define a different server under Date and Time settings.
 

Officially use of secondary addresses is not supported, because some services may not work properly with it, be aware.
 
I made an update for the next release to exclude secondary addresses from binding.
 

See
 

The log shows this message
May 4 09:02:51 Unraid kernel: wlan0: driver doesn't support chan-switch with channel contexts  
Disable channel switching on your access point (router).
 

In the past bridging was needed for VMs and give them external access.
In the latest versions 6.12.x and 7.0.x of Unraid both Docker and VMs can work without bridging enabled.
I would recommend to disable it, unless you have a specific requirement to let your Unraid server act as a physical bridge between your router and PC (see picture).
 

Thanks for the recommendations.
 
I made some updates for Unraid 6.13.
 

For upcoming version 6.12.4 I added a new option to specify the life time of notifications. Default is 3 seconds.
 

These error messages come from 'netbios'
I recommend to disable netbios and use WSD instead for host discovery. See Settings -> SMB settings
 

Can you test with "IPv4 only" setting on br0 and see if that makes a differrence?
Please provide diagnostics of the new test.
Thx
 

You need to check your router configuration, it has issues with IPv6.
Jul 10 22:15:50 xxxx dhcpcd[1697]: br0: expired address fda2:612d:c297:4585:265e:beff:fe43:dc4d/64 Jul 10 22:15:50 xxxx dhcpcd[1697]: br0: part of a Router Advertisement expired  
Alternatively set "IPv4 only".
 

You can use the plugin “Dynamix Factory Reset”
 

If using macvlan in docker settings, change it to ipvlan
 

This will be solved in the upcoming version 6.12.2
 

ssh is restarted because your system looses network connection halfway.
 
Jun 25 17:36:33 narvi kernel: bond0: (slave eth0): link status definitely down, disabling slave Jun 25 17:36:33 narvi kernel: device eth0 left promiscuous mode Jun 25 17:36:33 narvi kernel: bond0: now running without any active interface! Jun 25 17:36:33 narvi kernel: br0: port 1(bond0) entered disabled state Jun 25 17:36:33 narvi dhcpcd[1345]: br0: carrier lost Jun 25 17:36:33 narvi dhcpcd[1345]: br0: deleting route to 192.168.1.0/24 Jun 25 17:36:33 narvi dhcpcd[1345]: br0: deleting default route via 192.168.1.1  
Disable bonding in the network configuration and see if that solves the issue.
It might also be that the plugin "tips and tweaks" interferes. Uninstall this plugin and retest.
 

I have created a new plugin, called Dynamix Factory Reset
 

 
This plugin allows to return your system to default settings and start like a new installation.
 
Docker and VM images are not removed, the plugin does not touch any data on the array or pool(s).
You can recreate your VM by adding a new VM and point to the existing image for the primary vdisk location.
 

Normally I don't recommend this, because people tend to forget this in the future, but you can add the disable line in the 'go' file on your USB device.
Put the line before starting the GUI (emhttp).
 
 
The all setting is not used because you should enable or disable IPv6 per individual interface, it is allowed to mix between ipv4 and ipv6 depending on requirements

You deleted the interface section (and perhaps more) in the XML file.
I suggest you start fresh with a new VM.
 

When no explicit gateway address is given for the subnet, then docker will assign the first address as gateway address. This is the conflict you see.
 
Under docker settings you need to set the specific subnet assignment for each VLAN, see example below
 

Remark: the upcoming Unraid version 6.10-rc5 has a new setting to enable or disable SMB multi-channel (it is disabled by default).
 

In 6.10 the read/write speeds are updated every 2 seconds.
 

If you don't want to capitalize device names, you can change the setting
 
Settings --> Display Settings --> Display device name = Raw
 

Getting a 169.254.xxx.xxx address means the system could not get an IP address from your router.
This suggests you have some network issue.
Try replacing cables and. moving ports on your switch or router.
You mentioned the message about interface eth0 down, this is another indicator that there is a network issue.
This interface should never go down, otherwise you loose connectivity.
 

The original check works fine for me, do you have SSL enabled for GUI access?
 
I tested your modification on my systems, there is no regression.
Made a change to use https instead of http for checking both plugins and docker.
Thx
 

The message about the share means the share is located on a disk (disk5), which is not part of the included disks / excluded disks list.
You need to update the included or excluded list if you want disk5 to be a member of the share.
Note: everything keeps working even with the mismatch in place (content is never touched)
 
This is the general setting to check
 Settings -> Global Share Settings -> Included/Excluded disks
 
This is the per share setting to check
 Shares -> <share name> -> Included/Excluded disks