Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - jmdomini

#1
About ready to throw in the towel on this project. Just when I think I have things working, another issue pops up. In short trying to work around my ISP not being willing to provide a static IP by using a tunneled static IP via Wireguard. I feel like one needs to be an expert in network engineering to get this working on Opnsense/Pfsense however.

Followed the below to a "T" and get my primary unfiltered internet going on 192.168.1.1 and the VLAN traffic on VLAN2 subnet 192.168.2.1.
https://docs.opnsense.org/manual/how-tos/wireguard-selective-routing.html

At first all seems to be good and working as it should. After a while however, I am unable to access certain (random) sites from the primary subnet. Subnet that is going over Wireguard continues to work fine. I noticed for example google.com works fine, fedex.com does not. Doing a tracert to google.com is normal, fedex.com dies at my ISP's gateway. Shutdown the Wireguard tunnel everything returns to normal on the primary subnet.

Thinking perhaps some traffic from the primary subnet is "leaking" to the Wireguard gateway, I try adding an explicit rule for the LAN subnet to send all outgoing traffic direct to the WAN interface. No change in behaviour, the only thing that corrects the problem is stopping Wireguard.

Is there something critical missing from the linked instructions that could be causing this undesired behaviour?
#2
Never mind, problem solved by following the instructions in this post....
https://forum.opnsense.org/index.php?topic=33213.0
#3
It shouldn't be this hard, but I've spent more hours trying to figure this out than I want to admit. I followed these instructions to complete the basic Wireguard configuration (https://www.ivpn.net/setup/router/opnsense-wireguard/) and they work perfectly if one wants to route all traffic over the VPN. However, I wish to route my primary subnet 192.168.1.0/24 out over the WAN untouched and only send 192.168.2.0/24 out over the Wireguard VPN.

Seemed like in theory it should be simple, just add two different outgoing NAT rules. One for each subnet. Traffic routes just fine for the primary subnet. However nothing routes for the secondary (I can't even ping the gateway 192.168.2.1). I tried adding a firewall rule on the interface the secondary subnet is connected to (OPT3) to allow all traffic in and out which fixes not being able to ping the gateway, but still no traffic goes to the Wireguard tunnel (or anywhere outside of the LAN). What am I missing here?