Currently I'm setting up a VPN Tunnel on my home network. Mullvad with WireGuard. This works perfectly fine and I get a handshake.
My Synology NAS needs to be reachable from outside so I thought the best idea was to avoid the VPN for my NAS and leave it on my public IP.
I moved my NAS to a new seperated VLAN. I managed to update the local IP from xxx.xxx.1.x to xxx.xxx.10.x but now some stacks/containers also need an update is my guess. If I switch the VPN to ON I can't reach RustDesk anymore for example.
The NAS here is on a separate VLAN "br10". At home, I use a part of the Synology NAS, for example, RustDesk runs as a docker to give someone remote access to a server that I host. I also use RustDesk to remotely access my devices.
If I enable the VPN Tunnel over my UDM Pro I will no longer have access to these stacks, and if I do not add "br10" to the line FORCED_SOURCE_INTERFACE="br0 br......." in my VPN config this is also the case..
Hello
Currently I'm setting up a VPN Tunnel on my home network. Mullvad with WireGuard. This works perfectly fine and I get a handshake.
My Synology NAS needs to be reachable from outside so I thought the best idea was to avoid the VPN for my NAS and leave it on my public IP. I moved my NAS to a new seperated VLAN. I managed to update the local IP from xxx.xxx.1.x to xxx.xxx.10.x but now some stacks/containers also need an update is my guess. If I switch the VPN to ON I can't reach RustDesk anymore for example.
The NAS here is on a separate VLAN "br10". At home, I use a part of the Synology NAS, for example, RustDesk runs as a docker to give someone remote access to a server that I host. I also use RustDesk to remotely access my devices.
If I enable the VPN Tunnel over my UDM Pro I will no longer have access to these stacks, and if I do not add "br10" to the line FORCED_SOURCE_INTERFACE="br0 br......." in my VPN config this is also the case..
Thanks in advance.