<?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[Routing Issue]]></title><description><![CDATA[<p dir="auto">We currently have three WAN links and are going to get rid of two of them soon. All go through the PFSense box (v.2) and access works fine on the two that we will be taking down. On the remaining WAN link we have a Cisco 2901 router between the PFSense and the ISP Layer 2 device. The configuration is something like this:</p>
<p dir="auto">Internal network (192.168.0.0/24)<br />
      |<br />
      |<br />
192.168.0.x/24<br />
PFSense<br />
1.1.1.3/28<br />
      |<br />
      |<br />
      |<br />
1.1.1.4/28<br />
Cisco Router<br />
8.8.8.5/30<br />
      |<br />
      |<br />
      |<br />
8.8.8.6/30<br />
ISP Layer 2 Device<br />
Internet</p>
<p dir="auto">With the other two WAN links intact I can ping from the firewall through the router to the Internet. When I take the doomed WAN links down I can still ping from the firewall out to the Internet by FQDN and IP address.<br />
However, when I try from a PC within the internal network and the doomed WAN links are down, I cannot get out at all.<br />
It has to be something simple within the firewall and I am hoping somebody can steer me in the right direction off the bat. I am not that familiar with the PFSense firewall….but that is changing!<br />
Thank you!<br />
BanjoBoy</p>
]]></description><link>https://forum.netgate.com/topic/101036/routing-issue</link><generator>RSS for Node</generator><lastBuildDate>Tue, 15 Sep 2026 11:57:53 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/101036.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 05 Jun 2016 17:06:22 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Routing Issue on Fri, 08 Jul 2016 21:43:58 GMT]]></title><description><![CDATA[<p dir="auto">Issue resolved. I simply restored the PFsense to a saved configuration, then rebuilt my Cisco Router and it all came back.<br />
Thanks for the help!</p>
]]></description><link>https://forum.netgate.com/post/636526</link><guid isPermaLink="true">https://forum.netgate.com/post/636526</guid><dc:creator><![CDATA[BanjoBoy]]></dc:creator><pubDate>Fri, 08 Jul 2016 21:43:58 GMT</pubDate></item><item><title><![CDATA[Reply to Routing Issue on Wed, 22 Jun 2016 18:00:29 GMT]]></title><description><![CDATA[<p dir="auto">what are you firewall rules.. Guessing you were using some load balancing directing specific gateways?</p>
<p dir="auto">So need to see what firewall rules you have on interface your internal network talks to pfsense on.</p>
]]></description><link>https://forum.netgate.com/post/633537</link><guid isPermaLink="true">https://forum.netgate.com/post/633537</guid><dc:creator><![CDATA[johnpoz]]></dc:creator><pubDate>Wed, 22 Jun 2016 18:00:29 GMT</pubDate></item><item><title><![CDATA[Reply to Routing Issue on Wed, 22 Jun 2016 16:20:05 GMT]]></title><description><![CDATA[<p dir="auto">NAT rules are setup correctly (basically copied from one of the other working interfaces) and triple-checked for accuracy. But here is the weird thing: without changing anything, the new interface I setup suddenly began working! I cannot explain it (which causes me a little concern) but working it is! We'll monitor and continue troubleshooting but I think this issue is resolved. Thanks for your help!</p>
]]></description><link>https://forum.netgate.com/post/633491</link><guid isPermaLink="true">https://forum.netgate.com/post/633491</guid><dc:creator><![CDATA[BanjoBoy]]></dc:creator><pubDate>Wed, 22 Jun 2016 16:20:05 GMT</pubDate></item><item><title><![CDATA[Reply to Routing Issue on Thu, 09 Jun 2016 06:24:02 GMT]]></title><description><![CDATA[<p dir="auto">perhaps you are missing NAT rules for that wan interface?</p>
]]></description><link>https://forum.netgate.com/post/630446</link><guid isPermaLink="true">https://forum.netgate.com/post/630446</guid><dc:creator><![CDATA[heper]]></dc:creator><pubDate>Thu, 09 Jun 2016 06:24:02 GMT</pubDate></item></channel></rss>