<?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[No access Web Interface when set ip on lan]]></title><description><![CDATA[<p dir="auto">I am running PFSense 2.0 on VirtualBox in Ubuntu.<br />
The interface Wan with IP via DHCP.<br />
When I set the ip on the Lan interface can no longer access PFSense via the web interface.<br />
Where am I wrong?</p>
]]></description><link>https://forum.netgate.com/topic/29128/no-access-web-interface-when-set-ip-on-lan</link><generator>RSS for Node</generator><lastBuildDate>Thu, 18 Jun 2026 02:31:13 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/29128.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 27 Dec 2010 11:02:24 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to No access Web Interface when set ip on lan on Thu, 30 Dec 2010 16:04:03 GMT]]></title><description><![CDATA[<p dir="auto">PJ2 Thank you!</p>
<p dir="auto">It Worked!</p>
<p dir="auto">I create the rule accepting everything in the wan interface<br />
After I enabled Lan Interface I remove "Anti-Lockout Rule" in the Lan Interface!</p>
]]></description><link>https://forum.netgate.com/post/258599</link><guid isPermaLink="true">https://forum.netgate.com/post/258599</guid><dc:creator><![CDATA[cleriston]]></dc:creator><pubDate>Thu, 30 Dec 2010 16:04:03 GMT</pubDate></item><item><title><![CDATA[Reply to No access Web Interface when set ip on lan on Wed, 29 Dec 2010 18:20:57 GMT]]></title><description><![CDATA[<p dir="auto">Yes - that rule moves to the LAN interface when the LAN is enabled.  You will need to create a manual rule on the WAN interface if you want it to apply after you enable the LAN.</p>
]]></description><link>https://forum.netgate.com/post/258503</link><guid isPermaLink="true">https://forum.netgate.com/post/258503</guid><dc:creator><![CDATA[FisherKing]]></dc:creator><pubDate>Wed, 29 Dec 2010 18:20:57 GMT</pubDate></item><item><title><![CDATA[Reply to No access Web Interface when set ip on lan on Wed, 29 Dec 2010 01:35:37 GMT]]></title><description><![CDATA[<p dir="auto">PJ2 thanks for your help, but by default the rule already exists with description "Anti-Lockout Rule"</p>
]]></description><link>https://forum.netgate.com/post/258430</link><guid isPermaLink="true">https://forum.netgate.com/post/258430</guid><dc:creator><![CDATA[cleriston]]></dc:creator><pubDate>Wed, 29 Dec 2010 01:35:37 GMT</pubDate></item><item><title><![CDATA[Reply to No access Web Interface when set ip on lan on Tue, 28 Dec 2010 18:05:31 GMT]]></title><description><![CDATA[<p dir="auto">I believe that once you enable the LAN interface management traffic is blocked on the WAN interface.</p>
<p dir="auto">If you don't have a computer on the LAN network that you can manage pfSense from, you will need to create a firewall rule on the WAN interface <em>before</em> you enable your LAN that will accept TCP traffic on ports 443 (or 80 or 22 depending on how you manage your firewall).</p>
]]></description><link>https://forum.netgate.com/post/258373</link><guid isPermaLink="true">https://forum.netgate.com/post/258373</guid><dc:creator><![CDATA[FisherKing]]></dc:creator><pubDate>Tue, 28 Dec 2010 18:05:31 GMT</pubDate></item><item><title><![CDATA[Reply to No access Web Interface when set ip on lan on Tue, 28 Dec 2010 16:29:24 GMT]]></title><description><![CDATA[<blockquote>
<p dir="auto">How did you access the pfSense web interface BEFORE you set the LAN IP address? Through which interface and using what IP address?</p>
</blockquote>
<p dir="auto">Yes! I can access Web Interface Throug which wan interface with Wan Ip 192.168.56.101 (Given by VirtualBox via DHCP)</p>
<blockquote>
<p dir="auto">How did you attempt to access the pfSense web interface AFTER you set the LAN IP address? Through which interface and using what IP address</p>
</blockquote>
<p dir="auto">Through of both address. Wan 192.168.56.101 and Lan 192.168.5.1</p>
<blockquote>
<p dir="auto">It is often (maybe even always) necessary to restart the webconfigurator (menu item 11 in the console menu) after changing the LAN IP address.</p>
</blockquote>
<p dir="auto">I tried using the option 11 but continued with the same problem.</p>
<p dir="auto">I do not have this network 192.168.5.255.<br />
I just wanted to test the options pfsense II and with this I need to set a Lan.</p>
<p dir="auto">For now thanks for help</p>
]]></description><link>https://forum.netgate.com/post/258344</link><guid isPermaLink="true">https://forum.netgate.com/post/258344</guid><dc:creator><![CDATA[cleriston]]></dc:creator><pubDate>Tue, 28 Dec 2010 16:29:24 GMT</pubDate></item><item><title><![CDATA[Reply to No access Web Interface when set ip on lan on Mon, 27 Dec 2010 14:52:36 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/cleriston">@<bdi>cleriston</bdi></a>:</p>
<blockquote>
<p dir="auto">When I set the ip on the Lan interface can no longer access PFSense via the web interface.</p>
</blockquote>
<p dir="auto">How did you access the pfSense web interface BEFORE you set the LAN IP address? Through which interface and using what IP address?</p>
<p dir="auto">How did you attempt to access the pfSense web interface AFTER you set the LAN IP address? Through which interface and using what IP address?</p>
<p dir="auto">It is often (maybe even always) necessary to restart the webconfigurator (menu item 11 in the console menu) after changing the LAN IP address.</p>
]]></description><link>https://forum.netgate.com/post/258105</link><guid isPermaLink="true">https://forum.netgate.com/post/258105</guid><dc:creator><![CDATA[wallabybob]]></dc:creator><pubDate>Mon, 27 Dec 2010 14:52:36 GMT</pubDate></item></channel></rss>