- Joined
- Mar 5, 2013
- Messages
- 1,824
I have a TrueNAS Core 13.0 machine at 192.168.50.10. On it, there is a Nextcloud plug-in. I also run the built-in Wireguard VPN network on the TrueNAS machine at 10.0.0.0/24 subnet.
Now here's the interesting issue. If I run the Nextcloud plug-in through normal DHCP from my router on the 192.168.50.0/24 network, it works fine and Wireguard VPN clients can access it normally. But if I set it up as NAT forwarded to a port on the NAS IP (the default plugin setup: i.e. 192.168.50.10:8384), LAN clients can still access it, but Wireguard clients can no longer access it. Wireguard clients can ping any machine on the LAN including the TrueNAS machine itself. SSH and all other services also work, so that leads me to believe that there is nothing wrong with the network setup aside from the port forwarding.
Any ideas why?
Now here's the interesting issue. If I run the Nextcloud plug-in through normal DHCP from my router on the 192.168.50.0/24 network, it works fine and Wireguard VPN clients can access it normally. But if I set it up as NAT forwarded to a port on the NAS IP (the default plugin setup: i.e. 192.168.50.10:8384), LAN clients can still access it, but Wireguard clients can no longer access it. Wireguard clients can ping any machine on the LAN including the TrueNAS machine itself. SSH and all other services also work, so that leads me to believe that there is nothing wrong with the network setup aside from the port forwarding.
Any ideas why?
