<?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[Internal network routing with a public interface&#x2F;IP address]]></title><description><![CDATA[<p dir="auto">Simple diagram of my net work.  I have two ISP accounts one in each location.<br />
The two locations are connected by a private 10GB link.<br />
I am in the process of setting up an internet facing server in one location, using one of the public facing static IP addresses in the /29 provided by that ISP.  (I need the host on a public IP not relevant to this routing issue.)<br />
At present, I can access any system in any wired 192.168.0.0 address space behind either pfsense from any other.  To do this I set up static routes on each pfsense box  to routes.<br />
192.168.10.0 routes to 192.168.20.0 via 192.168.30.0 interfaces on each pfsense.</p>
<p dir="auto">Works fine, although DNS is slow.<br />
(Rather than manually duplicate the resolver space I just have each client use the local pfsense as first DNS server, the other pfsense as second.  If a resolution isn't found locally you can detect a sizable delay as the query fails and gets redirected.)</p>
<p dir="auto">When I set up the new server, everything works as expected.  So long as the public interface is down, routing works fine.  Access from both internal networks is fine.<br />
I bring up the public interface and I can the only access the server from the local private network (And the public IP of course).<br />
I have included a somewhat simple diagram of the setup.</p>
<p dir="auto">I have set the IP adress on the server internally both via dhcp and statically and tried adding a route to the 10 and 30 network, but nothing seems to be working.</p>
<p dir="auto">the route table for internal networking (route -n) doesn't appear to change when bringing up the public interface, but access to anything other than the .20 network immediatetly drops.</p>
<p dir="auto">I am missing something here blindingly easy, I know it ...</p>
<p dir="auto"><img src="/assets/uploads/files/1644076999395-559dbc3d-5eb9-4cef-a378-8c0c5683840c-image.png" alt="559dbc3d-5eb9-4cef-a378-8c0c5683840c-image.png" class=" img-fluid img-markdown" /></p>
<p dir="auto">Edit:<br />
I have setup a bare linux VM, using the simplest network configuration I can.</p>
<p dir="auto">dhcp from the local pfsense works exactly as expected -- so long as there are no other interfaces.</p>
<p dir="auto">I set both interfaces in the affected VM like this to play around with the client side routing:</p>
<p dir="auto">The primary/first nic configured network interface<br />
auto eth0<br />
iface eth0 inet static<br />
address 172.nnn.nnn.nn/29<br />
gateway  172.nnn.nnn.54</p>
<p dir="auto">auto eth1<br />
iface eth1 inet static<br />
address 192.168.20.13/24<br />
gateway 192.168.20.1</p>
<p dir="auto">Adding this route gets a ping response from 10.1 but no other IPs on that subnet and doesn't allow inbound traffic from any host on 192.168.10.0/24.</p>
<p dir="auto">route add -net 192.168.10.0/24 gw 192.168.20.1 eth1</p>
<p dir="auto">Downing the eth0 interface, and things work as expected.</p>
<p dir="auto">Since each pfsense has the routing table to direct traffic between the subnets, why -- so long as the traffic makes it to pfsense - is the traffic being dropped?</p>
<p dir="auto">Would changing the static public IP address to the second interface change this behavior?<br />
I'm assuming doing that would cause all outbound traffic to run across the pfsense gateway, but I need this server to send all internet bound/sourced traffic over the public IP.</p>
]]></description><link>https://forum.netgate.com/topic/169649/internal-network-routing-with-a-public-interface-ip-address</link><generator>RSS for Node</generator><lastBuildDate>Tue, 18 Aug 2026 17:59:13 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/169649.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 05 Feb 2022 16:07:21 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Internal network routing with a public interface&#x2F;IP address on Sat, 05 Feb 2022 21:14:51 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/makowner">@<bdi>makowner</bdi></a><br />
Possibly the server sends packets out to the internal interface with its public source IP?<br />
Sniff the traffic to check that out.</p>
]]></description><link>https://forum.netgate.com/post/1023763</link><guid isPermaLink="true">https://forum.netgate.com/post/1023763</guid><dc:creator><![CDATA[viragomann]]></dc:creator><pubDate>Sat, 05 Feb 2022 21:14:51 GMT</pubDate></item></channel></rss>