Messages

Yeah, that IP is the Nord endpoint. So you are not setting a local gateway IP. Might update the guide to allow for this

Might actually be a good idea to share your configuration info that you have from your VPN provider to ensure that I have that straight. Otherwise the assumptions I am making may be totally wrong

I see you are using NordVPN. They make it trickier to get config info due to their preference that users use their NordLynx application (at least they used to)

Several things (making some assumptions about tunnel IPs based on what you have currently):

- Gateway config - IP address should be 10.5.0.1. Remove the monitor IP for the time being (once the tunnel is working you can run a traceroute to figure out what the VPN tunnel IP is at the VPN provider's end, unless you already know that)

- OPNsense local config - Tunnel address should be 10.5.0.2/32 - I am assuming this is what your VPN provider has said should be set as the tunnel IP at your end

- OPNsense endpoint config - Allowed IPs should just be 0.0.0.0/0

Neither.

It's the local IPs of the particular machines/VMs etc that you want to use the tunnel.

Eg you have a PC on 192.168.1.10 in your network. Include that.

Or you have an entire VLAN subnet like 10.0.1.10/24 that you want anything on that subnet to use the tunnel. Include that.

You're missing some of the most important info - your WG configs and the gateway, for example.

Can I suggest that you show what you have set up for each step of the wiki how-to?

I'd guess remove the duplicate from config.xml

It would probably be more productive for you to post screenshots of all your configs (masking private keys), as your situation will be different to others.

Sounds like you want to implement selective routing: https://docs.opnsense.org/manual/how-tos/wireguard-selective-routing.html

You can do it without a VPS, but you still need another endpoint with a different public IP to tunnel through. That's what commercial VPN providers like Mullvad are commonly used for, if you don't want to roll your own solution with a VPS

Hopefully you didn't do everything exactly the same, as you will have conflicting subnets, ports, keys etc. xD Post configs?

Those rules are not new to the update and won't be causing your issues

This may help you: https://forum.opnsense.org/index.php?topic=18745.msg97953#msg97953

Not sure what json you are referring to. OPNsense's primary configuration file is /conf/config.xml

Back a few versions ago the underlying code was similar enough that a direct import was possible. That's not the case now

You should be able to achieve this by firewall rules (policy based routing) and allowed IPs in WG