![]() Hopefully I'm just not looking in the right spot, or possibly it's something I can configure manually somehow. I feel like what is missing is the ability to be able to choose traffic from the Wireguard VPN connection instead of just Internet. When I look at the port forward rules for the device I have setup, it says the source is "Internet". On the VPS, running docker exec wireguard-home ping 192.168.1.1 should return a successful ping of my OPNsense router from inside my home LAN. However, when I try configure the incoming port forward rule for the device on my VPN connection, what happens is that Firewalla opens the port on the normal WAN interface and not the VPN connection. On the VPS, running docker exec wireguard-mullvad curl should return the Mullvad connection status. Configured an incoming port forward for a different LAN device unrelated to the VPN.Attached a device on my LAN to the VPN in Firewalla and confirmed that it works.Configured a forwarding port on my Mullvad account for the city I use. ![]() Configured 3rd party VPN Wireguard client to Mullvad. ![]() I am attempting to configure one of my devices on my LAN to use the Mullvad Wireguard VPN connection configured on my Firewalla Purple with an incoming forwarded port. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |