<?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[Don't access WAN Interface when set IP for LAN Interface]]></title><description><![CDATA[<p dir="auto">Hi all<br />
I have a question. When I installed pfSense in vmware workstation with 2 card WAN(bridge) and LAN(host-only). First I set IP for WAN Interface with 192.168.1.253 and don't set IP for LAN Interface. My PC have IP 192.168.1.2 can access web configurator of pfSense over WAN Interface. Next I set IP for LAN Interface 172.16.0.1. Then My PC cann't access web configurator over WAN Interface. Can you help me to fix this issue. Thanks for all.</p>
]]></description><link>https://forum.netgate.com/topic/39983/don-t-access-wan-interface-when-set-ip-for-lan-interface</link><generator>RSS for Node</generator><lastBuildDate>Sat, 14 Nov 2026 05:48:43 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/39983.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 14 Dec 2011 07:52:09 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Don't access WAN Interface when set IP for LAN Interface on Thu, 15 Dec 2011 08:59:33 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/metu69salemi" aria-label="Profile: Metu69salemi">@<bdi>Metu69salemi</bdi></a>:</p>
<blockquote>
<p dir="auto">JIMP already said the solution, but as i expected your wan rules isn't allowing even a thing to happen.<br />
You could add there a rule that allows management for that pfsense.</p>
<p dir="auto">You should do this before creation of lan, if you really don't want to have management access only in lan side.</p>
<pre><code>
Action: pass
Disabled: unchecked
Interface: WAN
Protocol: TCP
Source: you should determine your wanted ip or any
Source port: leave it as is
Destination: wan ip
Destination port: management port #(could be 80, 443 or what ever you have set)
Log: unchecked(usually this would be good trafic to log)
Description: something descritive, like firewall management

</code></pre>
<p dir="auto">And click save.</p>
</blockquote>
<p dir="auto">thanks all. I got it</p>
]]></description><link>https://forum.netgate.com/post/308810</link><guid isPermaLink="true">https://forum.netgate.com/post/308810</guid><dc:creator><![CDATA[ltrgiang]]></dc:creator><pubDate>Thu, 15 Dec 2011 08:59:33 GMT</pubDate></item><item><title><![CDATA[Reply to Don't access WAN Interface when set IP for LAN Interface on Thu, 15 Dec 2011 05:23:13 GMT]]></title><description><![CDATA[<p dir="auto">JIMP already said the solution, but as i expected your wan rules isn't allowing even a thing to happen.<br />
You could add there a rule that allows management for that pfsense.</p>
<p dir="auto">You should do this before creation of lan, if you really don't want to have management access only in lan side.</p>
<pre><code>
Action: pass
Disabled: unchecked
Interface: WAN
Protocol: TCP
Source: you should determine your wanted ip or any
Source port: leave it as is
Destination: wan ip
Destination port: management port #(could be 80, 443 or what ever you have set)
Log: unchecked(usually this would be good trafic to log)
Description: something descritive, like firewall management

</code></pre>
<p dir="auto">And click save.</p>
]]></description><link>https://forum.netgate.com/post/308782</link><guid isPermaLink="true">https://forum.netgate.com/post/308782</guid><dc:creator><![CDATA[Metu69salemi]]></dc:creator><pubDate>Thu, 15 Dec 2011 05:23:13 GMT</pubDate></item><item><title><![CDATA[Reply to Don't access WAN Interface when set IP for LAN Interface on Thu, 15 Dec 2011 01:28:04 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/metu69salemi" aria-label="Profile: Metu69salemi">@<bdi>Metu69salemi</bdi></a>:</p>
<blockquote>
<p dir="auto">What is your firewall rules on WAN?</p>
</blockquote>
<p dir="auto">Here is WAN rule in my firewall<br />
<img src="http://i630.photobucket.com/albums/uu26/ltrgiang/1-2.png" alt="" class="img-markdown  img-fluid" /></p>
]]></description><link>https://forum.netgate.com/post/308767</link><guid isPermaLink="true">https://forum.netgate.com/post/308767</guid><dc:creator><![CDATA[ltrgiang]]></dc:creator><pubDate>Thu, 15 Dec 2011 01:28:04 GMT</pubDate></item><item><title><![CDATA[Reply to Don't access WAN Interface when set IP for LAN Interface on Wed, 14 Dec 2011 17:16:33 GMT]]></title><description><![CDATA[<p dir="auto">If you only setup one interface, it would have put an anti-lockout rule on WAN to let you in. when you activated the LAN, it cut off that access thinking you wanted to get to it from the inside instead.</p>
<p dir="auto">You can get around this two ways:</p>
<p dir="auto">1. Setup a VM in the LAN and access it from there<br />
2. From the console, go to the shell and run:</p>
<pre><code>pfSsh.php playback enableallowallwan
</code></pre>
<p dir="auto">And then get into the GUI, add a proper rule to let you back in, and remove the 'allow all' rule that the previous command just added.</p>
]]></description><link>https://forum.netgate.com/post/308700</link><guid isPermaLink="true">https://forum.netgate.com/post/308700</guid><dc:creator><![CDATA[jimp]]></dc:creator><pubDate>Wed, 14 Dec 2011 17:16:33 GMT</pubDate></item><item><title><![CDATA[Reply to Don't access WAN Interface when set IP for LAN Interface on Wed, 14 Dec 2011 11:44:04 GMT]]></title><description><![CDATA[<p dir="auto">What is your firewall rules on WAN?</p>
]]></description><link>https://forum.netgate.com/post/308630</link><guid isPermaLink="true">https://forum.netgate.com/post/308630</guid><dc:creator><![CDATA[Metu69salemi]]></dc:creator><pubDate>Wed, 14 Dec 2011 11:44:04 GMT</pubDate></item></channel></rss>