https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162021-02-17T11:36:49ZpfSense bugtrackerpfSense - Regression #11433: Gateways with "Use non-local gateway" set are not added to routing tablehttps://redmine.pfsense.org/issues/11433?journal_id=511582021-02-17T11:36:49ZJim Pingle
<ul><li><strong>Tracker</strong> changed from <i>Bug</i> to <i>Regression</i></li><li><strong>Target version</strong> set to <i>CE-Next</i></li></ul><p>Do you see any errors in the console output while it boots when that happens?</p>
<p>There were numerous changes to gateway handling on 2.5.0 but I'm not aware of anything that would have specifically broken this. It's not very widely used, however, so if the required syntax changed in some way it may have not been updated since nobody complained when using development snapshots.</p> pfSense - Regression #11433: Gateways with "Use non-local gateway" set are not added to routing tablehttps://redmine.pfsense.org/issues/11433?journal_id=511592021-02-17T11:54:42ZDaniel Berteauddani-pfs@lapiole.org
<ul><li><strong>File</strong> <a href="/attachments/3390">gateway_pfs_2_5_0_boot.png</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/3390/gateway_pfs_2_5_0_boot.png">gateway_pfs_2_5_0_boot.png</a> added</li></ul><p>Attached is a screenshot of my VM during boot. Not sure if it's a symptom or a consequence of the default route missing</p> pfSense - Regression #11433: Gateways with "Use non-local gateway" set are not added to routing tablehttps://redmine.pfsense.org/issues/11433?journal_id=511702021-02-18T07:17:03ZM Felden
<ul><li><strong>File</strong> <a href="/attachments/3394">pfsa-1.JPG</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/3394/pfsa-1.JPG">pfsa-1.JPG</a> added</li><li><strong>File</strong> <a href="/attachments/3395">pfsb-1.JPG</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/3395/pfsb-1.JPG">pfsb-1.JPG</a> added</li><li><strong>File</strong> <a href="/attachments/3396">pfsc-1.JPG</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/3396/pfsc-1.JPG">pfsc-1.JPG</a> added</li></ul><p>I can replicate this!</p>
<p>I was about to respond that this "works for me" because I have a pfSense demo VPS with a cloud provider who gives an IPv4 gateway of 172.31.1.1 when the public IP address is in a totally different subnet. I upgraded this to 2.5.0 today and have had no issues. Then I realized that this instance has WAN set to DHCP4. Perhaps the original report is all static.</p>
<p>Trying to replicate this issue I proceeded to spin up a new instance of 2.4.5 and set a static IPv4 of 95.217.5.253/32 (no need to censor this, its a throwaway) and the gateway as 172.31.1.1 with the option "Use non-local gateway through interface specific route" as reported by Daniel B.</p>
<p>Confirmed it worked in 2.4.5. Rebooted. Still good. Upgraded to 2.5.0-Release and rebooted: No gateway. Instance unreachable as described by the original report. netstat -r shows now IPv4 default route - see attached pfsc-1.JPG</p> pfSense - Regression #11433: Gateways with "Use non-local gateway" set are not added to routing tablehttps://redmine.pfsense.org/issues/11433?journal_id=511712021-02-18T07:19:08ZDaniel Berteauddani-pfs@lapiole.org
<ul></ul><p>Indeed, forgot to mention I'm assigning a static /32 IPv4 on my WAN interface, not with DHCP</p> pfSense - Regression #11433: Gateways with "Use non-local gateway" set are not added to routing tablehttps://redmine.pfsense.org/issues/11433?journal_id=512142021-02-18T10:19:09ZViktor Gurov
<ul></ul><p>fix:<br /><a class="external" href="https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/139">https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/139</a></p> pfSense - Regression #11433: Gateways with "Use non-local gateway" set are not added to routing tablehttps://redmine.pfsense.org/issues/11433?journal_id=512262021-02-18T10:31:23ZRenato Botelhorenato@netgate.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li><li><strong>Assignee</strong> set to <i>Viktor Gurov</i></li></ul><p>PR has been merged. Thanks!</p> pfSense - Regression #11433: Gateways with "Use non-local gateway" set are not added to routing tablehttps://redmine.pfsense.org/issues/11433?journal_id=512302021-02-18T11:21:51ZDaniel Berteauddani-pfs@lapiole.org
<ul></ul><p>Can confirm it fixes the issue for me :-)</p> pfSense - Regression #11433: Gateways with "Use non-local gateway" set are not added to routing tablehttps://redmine.pfsense.org/issues/11433?journal_id=512312021-02-18T11:29:35ZRenato Botelhorenato@netgate.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Waiting on Merge</i></li></ul> pfSense - Regression #11433: Gateways with "Use non-local gateway" set are not added to routing tablehttps://redmine.pfsense.org/issues/11433?journal_id=512512021-02-18T15:22:19ZJim Pingle
<ul></ul><p>This could also be related to <a class="issue tracker-1 status-6 priority-4 priority-default closed" title="Bug: Problem with IPv6 netmask /128 in WireGuard (Rejected)" href="https://redmine.pfsense.org/issues/11450">#11450</a> since it uses that function in this way</p> pfSense - Regression #11433: Gateways with "Use non-local gateway" set are not added to routing tablehttps://redmine.pfsense.org/issues/11433?journal_id=513572021-02-20T17:54:19ZTácio Andrade
<ul></ul><p>I am facing the same problem at OVH. After the migration some pfSense stopped the gateway.</p>
<p>I found it strange because I updated 3 pfSense and none of them had this problem, but I realized that it is because the other 3 instead of non-local gateway used the last IP of their network range as a gateway.</p> pfSense - Regression #11433: Gateways with "Use non-local gateway" set are not added to routing tablehttps://redmine.pfsense.org/issues/11433?journal_id=513832021-02-21T08:28:36ZRenato Botelhorenato@netgate.com
<ul><li><strong>Status</strong> changed from <i>Waiting on Merge</i> to <i>Feedback</i></li><li><strong>Target version</strong> changed from <i>CE-Next</i> to <i>2.5.1</i></li></ul><p>Cherry picked to 2.5.0</p> pfSense - Regression #11433: Gateways with "Use non-local gateway" set are not added to routing tablehttps://redmine.pfsense.org/issues/11433?journal_id=522872021-03-12T10:00:27ZJim Pingle
<ul><li><strong>Subject</strong> changed from <i>2.5.0 breaks non local gateways</i> to <i>Gateways with "Use non-local gateway" set are not added to routing table</i></li></ul><p>Updating subject for release notes.</p> pfSense - Regression #11433: Gateways with "Use non-local gateway" set are not added to routing tablehttps://redmine.pfsense.org/issues/11433?journal_id=524382021-03-16T10:57:04ZViktor Gurov
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>works as expected on 2.5.1.r.20210314.2256:<br /><pre>
Destination Gateway Flags Netif Expire
...
172.13.13.13 ea:f3:ba:7c:55:4a UHS vtnet0
</pre></p> pfSense - Regression #11433: Gateways with "Use non-local gateway" set are not added to routing tablehttps://redmine.pfsense.org/issues/11433?journal_id=525012021-03-18T01:59:38ZAndrew Murray
<ul></ul><p>Viktor Gurov wrote:</p>
<blockquote>
<p>works as expected on 2.5.1.r.20210314.2256:<br />[...]</p>
</blockquote>
<p>I tested this with 2.5.1.r.20210314.2256 and confirmed it does work with IP but DNS doesn't resolve even though remote DNS is configured for 1.1.1.1 and 1.0.0.1. I can access these without issue but trying with DNS on pfsense doesn't work.</p>
<p>EDIT: Setting the default gateway to a specific one instead of automatic, solved the problem.</p> pfSense - Regression #11433: Gateways with "Use non-local gateway" set are not added to routing tablehttps://redmine.pfsense.org/issues/11433?journal_id=528302021-04-03T03:21:46ZFrank Soyerfsoyer@systea.net
<ul></ul><p>Hi guys,<br />I'm just facing this bug after an update to 2.5.0. Unfortunatly, gitlab.netgate.com is actually OFF, I can't see the fix, and I not really want to fully re-install a RC. I can revert to 2.4.5 for the moment, no matter, but can someone tell me when a stable 2.5.1 (if it fix this) will be available ? Or point me to a roadmap, somewhere ? Thanks.</p> pfSense - Regression #11433: Gateways with "Use non-local gateway" set are not added to routing tablehttps://redmine.pfsense.org/issues/11433?journal_id=528402021-04-05T06:17:41ZRenato Botelhorenato@netgate.com
<ul></ul><p>Frank Soyer wrote:</p>
<blockquote>
<p>Hi guys,<br />I'm just facing this bug after an update to 2.5.0. Unfortunatly, gitlab.netgate.com is actually OFF, I can't see the fix, and I not really want to fully re-install a RC. I can revert to 2.4.5 for the moment, no matter, but can someone tell me when a stable 2.5.1 (if it fix this) will be available ? Or point me to a roadmap, somewhere ? Thanks.</p>
</blockquote>
<p>You can apply the patch <a class="external" href="https://github.com/pfsense/pfsense/commit/a97987a5d1df8219f40433270fce0e3ef49345dc">https://github.com/pfsense/pfsense/commit/a97987a5d1df8219f40433270fce0e3ef49345dc</a>, which fixed this issue, using System Patches package as described at <a class="external" href="https://docs.netgate.com/pfsense/en/latest/development/system-patches.html">https://docs.netgate.com/pfsense/en/latest/development/system-patches.html</a></p> pfSense - Regression #11433: Gateways with "Use non-local gateway" set are not added to routing tablehttps://redmine.pfsense.org/issues/11433?journal_id=528572021-04-06T06:44:07ZFrank Soyerfsoyer@systea.net
<ul></ul><p>Hi Renato,<br />the only patch (pfSense-pkg-System_Patches: 1.2_5) shown in the UI does not correct the problem. It seems that a "2.5.1" patch isn't yet available.<br />But modifying the line manually did the trick, thanks a lot.</p>