bearattack

I'm having a strange issue with FileBot mounting CIFS shares to /storage. It seems on a fresh reboot of Unraid, FileBot decides not to mount the CIFS share. I see the log line: [filebot-info] STORAGE: btrfs [/] @ 16 GB | fuse.shfs [/config] @ 1.9 TB | btrfs [/output] @ 16 GB | btrfs [/watch] @ 16 GB Simply restarting the container fixes the issue, and I see the log line: [filebot-info] STORAGE: btrfs [/] @ 16 GB | cifs [/storage] @ 398 GB | fuse.shfs [/config] @ 1.9 TB | btrfs [/watch] @ 16 GB | btrfs [/output] @ 16 GB Note that there is a "cifs [/storage]" item mounted now. I am also using the MKVToolNix docker which works flawlessly on fresh restarts and also uses CIFS mounts. Is this a strange bug or am I missing something?

That seems to have fixed it! Thank you!

I tried reverting back to MTU 1500 and rebooted. Getting the same error. wg-quick up wg0 (autostart) [#] ip link add wg0 type wireguard [#] wg setconf wg0 /dev/fd/63 [#] ip -4 address add 10.253.0.1 dev wg0 [#] ip -6 address add fc00:253:0:0::1 dev wg0 [#] ip link set mtu 1420 up dev wg0 [#] ip -6 route add fc00:253::3/128 dev wg0 [#] ip -6 route add fc00:253::2/128 dev wg0 [#] ip -4 route add 10.253.0.3/32 dev wg0 [#] ip -4 route add 10.253.0.2/32 dev wg0 [#] logger -t wireguard 'Tunnel WireGuard-wg0 started' [#] iptables -t nat -A POSTROUTING -s 10.253.0.0/24 -o br0 -j MASQUERADE;ip6tables -t nat -A POSTROUTING -s fc00:253:0:0::/64 -o br0 -j MASQUERADE [#] ip -4 route flush table 200 [#] ip -4 route add default via 10.253.0.1 table 200 [#] ip -4 route add 192.168.1.0/24 via 192.168.1.1 table 200 Error: Nexthop has invalid gateway. [#] ip link delete dev wg0

I did the update and got this from the log: wg-quick up wg0 (autostart) [#] ip link add wg0 type wireguard [#] wg setconf wg0 /dev/fd/63 [#] ip -4 address add 10.253.0.1 dev wg0 [#] ip -6 address add fc00:253:0:0::1 dev wg0 [#] ip link set mtu 1420 up dev wg0 [#] ip -6 route add fc00:253::3/128 dev wg0 [#] ip -6 route add fc00:253::2/128 dev wg0 [#] ip -4 route add 10.253.0.3/32 dev wg0 [#] ip -4 route add 10.253.0.2/32 dev wg0 [#] logger -t wireguard 'Tunnel WireGuard-wg0 started' [#] iptables -t nat -A POSTROUTING -s 10.253.0.0/24 -o br0 -j MASQUERADE;ip6tables -t nat -A POSTROUTING -s fc00:253:0:0::/64 -o br0 -j MASQUERADE [#] ip -4 route flush table 200 [#] ip -4 route add default via 10.253.0.1 table 200 [#] ip -4 route add 192.168.1.0/24 via 192.168.1.1 table 200 Error: Nexthop has invalid gateway. [#] ip link delete dev wg0 Manually starting the WireGuard server adds this and all is working fine: wg-quick up wg0 [#] ip link add wg0 type wireguard [#] wg setconf wg0 /dev/fd/63 [#] ip -4 address add 10.253.0.1 dev wg0 [#] ip -6 address add fc00:253:0:0::1 dev wg0 [#] ip link set mtu 8920 up dev wg0 [#] ip -6 route add fc00:253::3/128 dev wg0 [#] ip -6 route add fc00:253::2/128 dev wg0 [#] ip -4 route add 10.253.0.3/32 dev wg0 [#] ip -4 route add 10.253.0.2/32 dev wg0 [#] logger -t wireguard 'Tunnel WireGuard-wg0 started' [#] iptables -t nat -A POSTROUTING -s 10.253.0.0/24 -o br0 -j MASQUERADE;ip6tables -t nat -A POSTROUTING -s fc00:253:0:0::/64 -o br0 -j MASQUERADE [#] ip -4 route flush table 200 [#] ip -4 route add default via 10.253.0.1 table 200 [#] ip -4 route add 192.168.1.0/24 via 192.168.1.1 table 200 Any ideas?

Hmm that's really strange. I ran your command and they just execute normally. I don't see any errors, and the tunnel starts up normally too. It seems like the tunnel just don't want to autostart on a reboot. Is there any other logs files I can retrieve related to boot up?

I'm also having issues when enabling VLANs on my Unraid setup. I have 2 VLANS on my network: 192.168.1.0/24 (LAN) 192.168.2.0/24 (IoT VLAN) I have WireGuard setup as a "Remote tunneled access". When I DON'T have VLANs setup on Unraid, my WireGuard peers can connect to the internet and connect to anything on both the LAN / IoT VLAN. ex. WG peer > 192.168.1.X OK WG peer > 192.168.3.X OK When I DO have VLANs setup on Unraid, my WireGuard peers can connect to the internet but can only access the LAN. Anything on the IoT VLAN has no response. ex. WG peer > 192.168.1.X OK WG peer > 192.168.3.X NO ACCESS Is this a bug in the WireGuard plugin?

I wasn’t able to disable SSL - I can access via HTTPS which throws certificate errors. Also the default admin/adminadmin credentials aren’t working… anyone find a workaround for this?

Hi, I'm trying to setup a remote tunneled access server using IPv4 + IPv6 and a local DNS (pihole) server. I run through the advanced configuration and my clients are successfully tunneling through IPv4, but it seems there is no IPv6 access through the tunnel. Is this a bug or am I misconfiguring something? My config is almost all default settings: