I have an unexpected issue with Wireguard. Please see description below.
-I have a wireguard interface which connects to Mullvad VPN that acts as a secondary WAN for a Guest VLAN. This is 100% separate from my primary LAN (with regular WAN) with no issues.
Note: Mullvad allows port forwarding so users can privately host services on their public IP.
I want to host a WG server on my GUEST VLAN (192.168.100.0) through such a forwarded port.
How it is going:
-I can connect successfully to the GUEST VLAN WG peer hrough the forwarded port on the Mullvad public IP. Handshake occurs and I am inside tunnel 192.168.9.0.
The strange part....my client specifies the Mullvad IP, but upon connecting, instantly it shows "endpoint IP" as my regular WAN/ISP IP.
Has anybody seen this before or know where to begin as a troubleshoot?