bonienl

Under Network Settings --> Interface Rules --> Exclude listening interfaces You can enter the name of the interface(s) which get excluded from service binding (e.g. your dmz interface).

Your static IPv6 configuration is wrong for eth0. Stop the array Go to Settings -> Network Settings -> Eth0 Change the prefix to 64 (see example below) Start the array Docker should now be able to properly create the custom network.

If you still have an issue in 7.1.4 and know how to reproduce, that will help a lot. Docker doesn't allow /128 subnets, because this is a single host address and prevent other hosts (containers) from joining this subnet.

For most users this issue is resolved in 7.1.3 and 7.1.4 If you still encounter issues in 7.1.4, please open a bug report and provide diagnostics for further investigations.

With bridging disabled Unraid uses macvtap interface for VMs (in this case bond0.10). This is correctly configured. For nested VMs it is advised to let the host VM pass the interface as a 'regular' interface (pass thru) to them.

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.

Small correction: macvlan is used when bridging is disabled. This is due to the underlying macvtap interface instead of bridging.

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.

At the moment I am very much time constraint to look into this, but keep it on my todo list.

A better approach is to assign your Pihole container to custom network eth0 (or br0) and assign a static IP address for the container on the custom network. I am using Unbound as DNS server. Here is an example of assigning static addresses to the container (running on br0)

See my answer here

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.

You can enable the option "Permit exclusive shares" (see Settings -> Global Share Settings) This will bypass the fuse system and operates the same as accessing /mnt/disk*. This will work for shares residing only on a pool device.

See

In my tests this is working as should. Can you do a forced update by changing ipvlan to macvlan and back to ipvlan (see docker settings).

Can you make a dummy change in the Docker settings to force a settings update and see if that resolves the issue? Please try the latest version 7.1.0

Click on the wifi icon of the network and select "Forget this network"

Do something like this It runs a parity check on the first Sunday every three months.

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).

The original help text was never updated, which we should. I tested it many years ago, but don’t need/use it myself.

Correct, but personally I would connect your PC directly to the UDM Pro, unless you are running out of ports on it.

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).

For wireless to run properly, you need to use DHCP for both wired and wireless connections. Setting a static IP address for the wired interface interferes with wireless (even when the wired port is down).

Thanks, I see what is happening, will make a fix for the next release.

Can you post the content of rc.ssl.input cat /etc/rc.d/rc.ssl.input