Source
r/PFSENSE•
WickedColdfront

Possible bug with WireGuard

I’m not sure if this is actually a bug or if it is indicative of a problem with my configuration. I figured I’d post here to see if anyone can confirm this behavior.

I created a WireGuard tunnel and configured all traffic from a specific VLAN to use the tunnel. I set the “Monitor IP” of the WireGuard gateway to use 1.1.1.1. All traffic to 1.1.1.1, even traffic originating from VLANs which should not be using the tunnel, goes over the WireGuard tunnel.

I worked around the issue by setting the Monitor IP to an IP that I would never use.

Posted Dec 23, 2021, 7:20 PM UTC

14
DutchOfBurdockpfSense+OpenWRT+Mikrotik•

I set the “Monitor IP” of the WireGuard gateway to use 1.1.1.1. All traffic to 1.1.1.1, even traffic originating from VLANs which should not be using the tunnel, goes over the WireGuard tunnel.

If you set a Monitor IP for a link, a static route to that IP is made over that link, so all traffic to that IP will go over that link.

6
cmcdonald-netgateNetgate•

Yes this is correct. Not unique to WireGuard

6
Constrained_Entropy•

Check the pfsense DNS resolver settings

-1
WickedColdfrontOP•

Thanks for your reply. I have the DNS resolver disabled. I don’t think it’s an issue related to DNS, as pings to the monitor IP use the tunnel as well.

0