bonienl

Can you disable the nginx proxy and test with a plain connection. Jul 16 01:28:17 NAS rc.docker: container Nginx-Proxy-Manager has an additional network that will be restored: none; There is also something wrong with your router and IPv6 assignment. You need to check router configuration. Jul 16 02:06:21 [1123]: br0: part of a Router Advertisement expired Jul 16 02:06:21 [1123]: route socket overflowed (rcvbuflen 106496) - learning interface state Jul 16 02:06:21 [1123]: drained 279 messages

I made an update which automatically resolves the issue when the shim interface is created. This should help anyone with static network settings and "host access" enabled.

I see what is happening When you create a static IP address + gateway without explicitely setting a metric value, then a default route with metric 0 is created for br0. This is indeed wrongly displayed in the GUI as value 1 (a display error). When creating the interface shim-br0, another default route with metric 0 is added, but this fails because two times the same metric is not allowed and hence there is a missing default route for the shim-br0 interface as a result, and this causes communication loss to the outside world whenever the shim-interface is used. The solution is indeed to set a metric value other then zero for the br0 gateway when a static IP assignment is used and "host access" is enabled. Btw this is not Unraid 6.12 specific but is true for earlier versions too. Need to think of a way to make this clear to the user and avoid this situation. Thanks for all the testing.

This is my routing table I use static routing with explicit settings for metrics. Docker uses ipvlan and has "host access" enabled, hence the shim interface Doesn't give any problems in my network set up.

To me this confirms your router is the source of the problem.

This information comes from your DHCP server macvlan / ipvlan setting is for docker, it doesn't change network settings. An incomplete ARP occurs when the target host (your router in this case) is no longer responding to arp requests from the server.

Do you have netbios enabled? Problem with netbios is twofold (1) it doesn't support ipv6 and (2) it wants to use a broadcast address, which doesn't exist on a tailscale tunnel. Netbios needs to be disabled and use WSD instead for host discovery.

It tells how many interfaces are present and need to be configured When this line is not present, it is assumed the network.cfg file holds a legacy configuration (pre V6) and it results in a basic network configuration without all the extras which is supported in V6 and later. When modifying the network settings using the GUI, it will automatically add the SYSNICS setting.

Keep in mind that Unraid completely runs from RAM, which is a different situation as Truenas.

One other thing. Do you change interface settings using the "Tips and Tweaks" plugin? If yes, disable this (or temporary uninstall the plugin) and retest.

Did you modify your "network.cfg" file manually? It is missing the last entry, which should be SYSNICS="1" Tip: since you are using a single interface, you can disable bonding.

Looks like your router gets confused by the shim-br0 interface. Test again with host acces to custom network disabled.

What is not working?

Just tested zerotier (again) and SMB works fine. Make sure you have correctly set up the zerotier address under Network Extra.

There are some unexplainable events in your log which prevents nfs to start. You should remove the packages from the folder /extra and restart the server without them installed and test again running in safe mode. In particular "llfuse-1.4.2-x86_64-1_SBo_nerdtools.txz" is suspicious (this one is no longer developed). Why is this installed?

Changed Status to Closed Changed Priority to Other

Please open a topic in the support thread of the vpn container.

Your diagnostics is AFTER reboot and does not contain anything relevant for troubleshooting. Information is required when the indicent happens, see syslog server setup to obtain the required info

The interface rules are only created when more than one ethernet interface are present in your system. Not a bug.

Please remove this line from your 'go' file sysctl -w net.ipv6.conf.all.disable_ipv6=1 This conflicts with the Unraid IPv6 assignments, you should let Unraid do the IPv6 selection instead.

It is possible to run Unbound containers too. This is what I actually do.

I have 6 DNS servers (PIHOLE) running as docker containers. An other DNS server alternative is ADGUARD. See the apps store.

Changed Priority to Minor

The wireguard log shows a duplicate network address in your wg0 configuration and it doesn't look complete wg-quick up wg0 (autostart) [#] ip link add wg0 type wireguard [#] wg setconf wg0 /dev/fd/63 [#] ip -4 address add 192.168.126.1 dev wg0 [#] ip link set mtu 1420 up dev wg0 [#] ip -4 route add 192.168.126.4/32 dev wg0 [#] ip -4 route add 192.168.126.3/32 dev wg0 [#] ip -4 route add 192.168.126.2/32 dev wg0 [#] ip -4 route add 192.168.128.0/24 dev wg0 RTNETLINK answers: File exists [#] ip link delete dev wg0 Can you delete the wg0 tunnel and re-create? wg1 is correct and has the expected entries wg-quick up wg1 (autostart) [#] ip link add wg1 type wireguard [#] wg setconf wg1 /dev/fd/63 [#] ip -4 address add 10.253.1.1 dev wg1 [#] ip link set mtu 1420 up dev wg1 [#] ip -4 route add 10.253.1.2/32 dev wg1 [#] logger -t wireguard 'Tunnel WireGuard-wg1 started';/usr/local/emhttp/webGui/scripts/update_services [#] iptables -t nat -A POSTROUTING -s 10.253.1.0/24 -o br0 -j MASQUERADE [#] ip -4 route flush table 201 [#] ip -4 route add default via 10.253.1.1 dev wg1 table 201 [#] ip -4 route add 192.168.128.0/24 via 192.168.128.1 dev br0 table 201

Thanks. Will be fixed in next version.