<?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[Forward webconfigurator interface from one machine to another one]]></title><description><![CDATA[<p dir="auto">So,</p>
<p dir="auto">in my network set up i have two pfsense machines chained in series to eachother. We'll call them pf1 and pf2</p>
<p dir="auto">PF1 has two WAN connections: WAN1 and WAN2, and a LAN connection with ip 192.168.3.1. (LAN1) This machine serves as failover/balancer.</p>
<p dir="auto">PF2 has 2 WAN connections : WAN3, and WAN4 with ip 192.168.3.2 (this last one being hooked to the LAN of the PF1 thus as a gateway using 192.168.3.1), and 2 LANs. (LAN2 and LAN3) One of them mapped with firewall rules to go on WAN3 and the other on WAN4.</p>
<p dir="auto">My failover/balancing works fine and everyone has access and is happy.</p>
<p dir="auto">Here lies my problem.</p>
<p dir="auto">I have the webconfigurator of one machine , pf1 on the LAN1 address say port 1111<br />
and the webconfigurator of pf2 on LAN2 address port 1111.</p>
<p dir="auto">Since i myself am on LAN2 i wanted to be able to monitor access both panels from lan 2.</p>
<p dir="auto">SO my logic was to start NAT'ing.</p>
<p dir="auto">in PF1 NAT port 1111 of 192.168.3.2 (which is the pf2 WAN, and is pingable from PF1) to the port 1111 of 192.168.3.1</p>
<p dir="auto">and then on the second machine PF2 NAT port 1111 of 192.168.3.2 on port 1112 of my lan2 address.</p>
<p dir="auto">This way from my LAN2 network i could navigate to :</p>
<p dir="auto">PF2 : 1111 and get my pf2 panel<br />
PF2 : 1112 and get my pf1 panel</p>
<p dir="auto">this, is not working. Not only the whole thing is not applying, but even on my PF1 box where is set up the following rule:</p>
<p dir="auto">If Proto Src. addr Src. ports Dest. addr   Dest. ports NAT IP NAT Ports Description</p>
<p dir="auto">LAN TCP/UDP * *        192.168.3.2    1111       192.168.3.1 1111</p>
<p dir="auto">Why would my nat'ing within the same machine/network/class not work?</p>
<p dir="auto">I hope the explanation was not too confusing.</p>
<p dir="auto">thank you in advance</p>
]]></description><link>https://forum.netgate.com/topic/45758/forward-webconfigurator-interface-from-one-machine-to-another-one</link><generator>RSS for Node</generator><lastBuildDate>Wed, 22 Apr 2026 14:30:38 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/45758.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 09 Jun 2012 10:47:28 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Forward webconfigurator interface from one machine to another one on Sat, 09 Jun 2012 11:15:47 GMT]]></title><description><![CDATA[<p dir="auto">Solved. I was overthinking it.<br />
On nat rule sufficed. ON PF2 mapping port 1112 of the LAN2 on 192.168.3.1:1111.</p>
<p dir="auto">Done.</p>
]]></description><link>https://forum.netgate.com/post/340971</link><guid isPermaLink="true">https://forum.netgate.com/post/340971</guid><dc:creator><![CDATA[sidis405]]></dc:creator><pubDate>Sat, 09 Jun 2012 11:15:47 GMT</pubDate></item></channel></rss>