<?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[OpenVPN Firewalling]]></title><description><![CDATA[<p dir="auto">I'm sorry to ask a question thats probably been asked 1000 times before.</p>
<p dir="auto">I am trying to do some best-practises firewalling between me and my friends site-to-site openVPN tunnel.<br />
Lets say the network looks like this:</p>
<p dir="auto">Local(My) network: 192.168.1.0/24<br />
Remote site-to-site network: 192.168.2.0/24<br />
Local tunnel endpoint 192.168.10.1<br />
Remote tunnel endpoint: 192.168.10.2</p>
<p dir="auto">I have no idea what kind of people that might connect on his network, so I will try to be alittle strict with that I will let pass through the tunnel.<br />
So I guess the best way to go, is probably to specify what IS allowed through, instead of specifying everything that is NOT allowed.</p>
<p dir="auto">Now my question is about how to specify the source when filtering the traffic. If I understand correctly, the filtering is happening on the OpenVPN-tab. Can I set the source to be that whole subnet on his end (192.168.2.0/24) and thats good? Or can I specify the tunnel-IP as a source, and in that way block/allow from that particular tunnel to him, no matter what subnet he has? (I have more VPN tunnels to other people). In other words, can I use source 192.168.10.2?</p>
<p dir="auto">He may have other VPN-tunnels on his end to other people, and I would like to restrict access for them (but maybe still allow him(his subnet) access, so they don't just "bridge" theire way onto my home network. How can this be avoided?</p>
<p dir="auto">Regards</p>
]]></description><link>https://forum.netgate.com/topic/81635/openvpn-firewalling</link><generator>RSS for Node</generator><lastBuildDate>Sun, 15 Mar 2026 05:50:14 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/81635.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 22 Mar 2015 21:27:56 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to OpenVPN Firewalling on Mon, 23 Mar 2015 00:02:42 GMT]]></title><description><![CDATA[<p dir="auto">Pass the specific traffic you want to come through.  Everything else will be blocked.</p>
<p dir="auto">The traffic will be coming from the 192.168.2.0/24 network unless he is natting it, in which case it will come from his tunnel IP.</p>
<p dir="auto">So, say you want anyone on his LAN to be able to connect to a web server at 192.168.1.100:80.  You could put this on the OpenVPN Tab:</p>
<p dir="auto"><em>Pass IPv4 TCP any any dest 192.168.1.100 port 80</em></p>
<p dir="auto">That's all pfSense will allow in through that OpenVPN tunnel.  Everything else will be blocked,  just like any other interface.</p>
]]></description><link>https://forum.netgate.com/post/530095</link><guid isPermaLink="true">https://forum.netgate.com/post/530095</guid><dc:creator><![CDATA[Derelict]]></dc:creator><pubDate>Mon, 23 Mar 2015 00:02:42 GMT</pubDate></item></channel></rss>