https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162011-08-22T18:01:37ZpfSense bugtrackerpfSense - Bug #1813: Static routes on WAN interfaces overridden by route-to for firewall-initiated traffichttps://redmine.pfsense.org/issues/1813?journal_id=68132011-08-22T18:01:37ZChris Buechlercbuechler@gmail.com
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li></ul> pfSense - Bug #1813: Static routes on WAN interfaces overridden by route-to for firewall-initiated traffichttps://redmine.pfsense.org/issues/1813?journal_id=68142011-08-22T18:11:23ZChris Buechlercbuechler@gmail.com
<ul></ul><p>floating rules can work around this</p> pfSense - Bug #1813: Static routes on WAN interfaces overridden by route-to for firewall-initiated traffichttps://redmine.pfsense.org/issues/1813?journal_id=293032016-11-06T01:03:07ZJim Thompsonjim@netgate.com
<ul><li><strong>Assignee</strong> set to <i>Jim Pingle</i></li><li><strong>Priority</strong> changed from <i>High</i> to <i>Normal</i></li></ul><p>Can't be "high", it's five years old.</p>
<p>JimP, please reeval to see if this is still and issue.</p> pfSense - Bug #1813: Static routes on WAN interfaces overridden by route-to for firewall-initiated traffichttps://redmine.pfsense.org/issues/1813?journal_id=293502016-11-09T14:06:16ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Confirmed</i></li><li><strong>Assignee</strong> deleted (<del><i>Jim Pingle</i></del>)</li><li><strong>Affected Version</strong> changed from <i>2.0</i> to <i>All</i></li></ul><p>It is still an issue but it can be easily worked around by adding a floating rule to pass outbound to the destination network.</p>
<p>We could automatically add rules behind the scenes for static route destinations on WAN-type interfaces that do not use the interface gateway if we wanted, but given that the situation is so rare, we may just want to document the quirk and let the user choose to add the workaround if they need it.</p>