<?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[PfSense clients access private network]]></title><description><![CDATA[<p dir="auto">Hi.</p>
<p dir="auto">I have a private network (192.168.1.xxx) and pfSense network (10.10.10.xxx) connected to the same router/modem ADSL (192.168.1.1), and the clients from pfSense have access to my private network. Is it possible to block them from the pfSense firewall? But I still want to access pfSense network from my private.</p>
<p dir="auto">Thank you :)</p>
]]></description><link>https://forum.netgate.com/topic/5523/pfsense-clients-access-private-network</link><generator>RSS for Node</generator><lastBuildDate>Wed, 15 Jul 2026 06:58:32 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/5523.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 16 Aug 2007 20:18:13 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to PfSense clients access private network on Sun, 19 Aug 2007 02:34:15 GMT]]></title><description><![CDATA[<p dir="auto">Excelent :)</p>
<p dir="auto">It worked<br />
Thanks a lot!!</p>
]]></description><link>https://forum.netgate.com/post/158808</link><guid isPermaLink="true">https://forum.netgate.com/post/158808</guid><dc:creator><![CDATA[KaYs3r]]></dc:creator><pubDate>Sun, 19 Aug 2007 02:34:15 GMT</pubDate></item><item><title><![CDATA[Reply to PfSense clients access private network on Sat, 18 Aug 2007 18:30:24 GMT]]></title><description><![CDATA[<p dir="auto">That rule says, block the LAN interface from accessing anything except the ADSL gateway.</p>
<p dir="auto">First off, you'll need to create an alias, say PRIVATE, that contains the following networks:</p>
<p dir="auto">192.168.1.2/31<br />
192.168.1.4/30<br />
192.168.1.8/29<br />
192.168.1.16/28<br />
192.168.1.32/27<br />
192.168.1.64/26<br />
192.168.1.128/25</p>
<p dir="auto">(This is a list that effectively lists every host EXCEPT 192.168.1.1)</p>
<p dir="auto">Now create a rule that blocks access from the LAN SUBNET to this alias.</p>
]]></description><link>https://forum.netgate.com/post/158804</link><guid isPermaLink="true">https://forum.netgate.com/post/158804</guid><dc:creator><![CDATA[Cry Havok]]></dc:creator><pubDate>Sat, 18 Aug 2007 18:30:24 GMT</pubDate></item><item><title><![CDATA[Reply to PfSense clients access private network on Sat, 18 Aug 2007 13:24:55 GMT]]></title><description><![CDATA[<p dir="auto">Just tested this, but it's not working :(</p>
<p dir="auto">Could you please check if the rulle is correct?</p>
<p dir="auto"><img src="/public/_imported_attachments_/1/printscreen.JPG" alt="printscreen.JPG" class=" img-fluid img-markdown" /><br />
<img src="/public/_imported_attachments_/1/printscreen.JPG_thumb" alt="printscreen.JPG_thumb" class=" img-fluid img-markdown" /></p>
]]></description><link>https://forum.netgate.com/post/158799</link><guid isPermaLink="true">https://forum.netgate.com/post/158799</guid><dc:creator><![CDATA[KaYs3r]]></dc:creator><pubDate>Sat, 18 Aug 2007 13:24:55 GMT</pubDate></item><item><title><![CDATA[Reply to PfSense clients access private network on Fri, 17 Aug 2007 11:07:41 GMT]]></title><description><![CDATA[<p dir="auto">So, as I said in my first post - your basic problem is that you've got your design backwards.  Your pfSense host is connected, via it's WAN interface, to the network you want to protect.  That's just wrong.</p>
<p dir="auto">You can "fix" this by putting in a deny rule on the LAN interface of the pfSense host, denying access to 192.168.1.0/24, except for 192.168.1.1.  However, given what you've said so far, it would be far more sensible to switch the 2 networks around, putting the "Private" network behind the pfSense host's LAN interface and the 10.10.10.x network between the ADSL router and the pfSense host:</p>
<p dir="auto">| 10.10.10.0/24<br />
  ADSL    |<br />
10.10.10.1-|<br />
          |    192.168.1.1<br />
          |–- pfSense ---- 192.168.1.0/24<br />
            10.10.10.2</p>
<p dir="auto">(Hint - firewalls are generally designed to protect the network on the LAN side from the network on the WAN side, not the other way around ;) )</p>
]]></description><link>https://forum.netgate.com/post/158771</link><guid isPermaLink="true">https://forum.netgate.com/post/158771</guid><dc:creator><![CDATA[Cry Havok]]></dc:creator><pubDate>Fri, 17 Aug 2007 11:07:41 GMT</pubDate></item><item><title><![CDATA[Reply to PfSense clients access private network on Fri, 17 Aug 2007 10:24:08 GMT]]></title><description><![CDATA[<p dir="auto">Exactly</p>
<p dir="auto">| Private network (192.168.1.x)<br />
ADSL Router    |<br />
(192.168.1.1)  | pfSense Box (192.168.1.15) (10.10.10.1)</p>
<p dir="auto">I think it's complete now :P</p>
]]></description><link>https://forum.netgate.com/post/158770</link><guid isPermaLink="true">https://forum.netgate.com/post/158770</guid><dc:creator><![CDATA[KaYs3r]]></dc:creator><pubDate>Fri, 17 Aug 2007 10:24:08 GMT</pubDate></item><item><title><![CDATA[Reply to PfSense clients access private network on Fri, 17 Aug 2007 10:17:56 GMT]]></title><description><![CDATA[<p dir="auto">Yes, but what you're saying is that the pfSense box has an interface on the 192.168.1.x network:</p>
<p dir="auto" style="text-align:left"> clients<br />
  ADSL      |<br />
192.168.1.1-|<br />
            |<br />
            |- pfSense - 10.10.10.x</p>
<p dir="auto">Is that correct?</p>
]]></description><link>https://forum.netgate.com/post/158769</link><guid isPermaLink="true">https://forum.netgate.com/post/158769</guid><dc:creator><![CDATA[Cry Havok]]></dc:creator><pubDate>Fri, 17 Aug 2007 10:17:56 GMT</pubDate></item><item><title><![CDATA[Reply to PfSense clients access private network on Thu, 16 Aug 2007 23:54:38 GMT]]></title><description><![CDATA[<p dir="auto">Sorry, you're right, but the diagram is not like that, is more something like this</p>
<p dir="auto">192.168.1.x<br />
ADSL &lt;<br />
            pfSense – 10.10.10.x</p>
]]></description><link>https://forum.netgate.com/post/158764</link><guid isPermaLink="true">https://forum.netgate.com/post/158764</guid><dc:creator><![CDATA[KaYs3r]]></dc:creator><pubDate>Thu, 16 Aug 2007 23:54:38 GMT</pubDate></item><item><title><![CDATA[Reply to PfSense clients access private network on Thu, 16 Aug 2007 22:30:44 GMT]]></title><description><![CDATA[<p dir="auto">A diagram would help.  It sounds like you've got:</p>
<p dir="auto">ADSL –- 192.168.1.x --- pfSense --- 10.10.10.x</p>
<p dir="auto">If that's the case, you could simply create a firewall rule to deny access from the 10.10.10.x network to the 192.168.1.x network, except for 192.168.1.1 (otherwise you'll never get to the Internet).  Of course, if that's the case you've got your networks back to front - you should put the more protected network behind the pfSense box, not in front of it :)</p>
]]></description><link>https://forum.netgate.com/post/158760</link><guid isPermaLink="true">https://forum.netgate.com/post/158760</guid><dc:creator><![CDATA[Cry Havok]]></dc:creator><pubDate>Thu, 16 Aug 2007 22:30:44 GMT</pubDate></item></channel></rss>