<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[wireGuard point-to-point route internet traffic]]></title><description><![CDATA[<p dir="auto">I have the following network. Ru and RH being PFsense routers.<br />
<img src="/assets/uploads/files/1717518307428-wan-2024-06-04-17-12-resized.jpg" alt="WAN-2024-06-04-17-12.jpg" class=" img-fluid img-markdown" /><br />
Due to Ru being under double NAT i can't access my server that is in LAN u.<br />
For the past 3 years i have had a point-to-point OVPN tunnel between the sites that bridged the 2 lans. Since RH had access to LAN u it was a simple port forward in router RH and it could be accessed from the internet. Also if i needed to route plex since it checks the ip of the internet i just gave the plex container a different IP and made a rule in the LAN u interface to re-route traffic through the tunnel gateway which worked fine + port forward on RH.</p>
<p dir="auto">Now i have made a tunnel with wire guard with the following settings:<br />
<strong>Ru allowed ip:</strong><br />
192.168.255.0/31<br />
192.168.0.0/24<br />
<strong>RH allowed ip:</strong><br />
192.168.255.0/31<br />
192.168.1.0/24</p>
<p dir="auto">The 2 LANs can communicate with each other but port forwarding something on RH or routing internet traffic of  device through the gateway doesn't work. I think this is because of the allowed ips blocking traffic originating from the internet in RH.<br />
I have tried adding 0.0.0.0/1 to the allowed ips of both to enable this but it doesnt work.<br />
Is there a way to do this on WireGuard or should i just continue with OVPN?</p>
]]></description><link>https://forum.netgate.com/topic/188549/wireguard-point-to-point-route-internet-traffic</link><generator>RSS for Node</generator><lastBuildDate>Wed, 15 Jul 2026 01:09:51 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/188549.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 04 Jun 2024 16:44:00 GMT</pubDate><ttl>60</ttl></channel></rss>