"
Hello ludarkstar99,
Thank you for getting back to me so quickly. I tried the official documentation last week but without 2FA. I can try again.
The WAN interface is connected to a local network on which the Windows PC is also present [n.b. second NIC used to connect to OpnSense LAN [192.168.1.0/24]). This is the Use Case for the VPN connection but also avoids the need to worry about other routers.
Yes.
No router involved.
Not sure what other ports to test right now but the log (see first attached screenshot) seems to show port 1401 is open.
I've just created a firewall rule for the WAN allowing anything from anyone but can't ping the WAN port from the PC (see second attached screenshot). Does that make sense?
Thank you for getting back to me so quickly. I tried the official documentation last week but without 2FA. I can try again.
Quote- Verify that the Windows client is connecting from a WAN network (i.e., dialing in from outside your local network). You can simulate this by sharing your mobile broadband connection with your laptop.
- Based on the attached logs, I see the Windows 11 client is trying to connect to the address 192.168.3.16, which is an internal address. When exporting the profile (Client Export), ensure you set the hostname to your internet-routable address (e.g., your WAN IP if your firewall has a public IP, or the public IP of your modem if your firewall is behind it).
The WAN interface is connected to a local network on which the Windows PC is also present [n.b. second NIC used to connect to OpnSense LAN [192.168.1.0/24]). This is the Use Case for the VPN connection but also avoids the need to worry about other routers.
Quote- Have you created a firewall rule on your WAN interface to allow incoming connections on port 1401/udp?
Yes.
Quote- If your OPNsense WAN interface is behind a routed modem (not a bridge modem), have you configured your ISP modem to forward all ports (or at least port 1401) to your firewall's WAN IP address?
No router involved.
Quote- Can you open and redirect other ports on your firewall? To test, try connecting on a closed port and check the live logs for any activity. Avoid testing port 1401, as it uses UDP/TLS and will not respond unless the correct encryption key is provided.
Not sure what other ports to test right now but the log (see first attached screenshot) seems to show port 1401 is open.
I've just created a firewall rule for the WAN allowing anything from anyone but can't ping the WAN port from the PC (see second attached screenshot). Does that make sense?
