https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162021-03-14T04:07:42ZpfSense bugtrackerpfSense - Bug #11599: Modifying static routes results in a logged error, changes are not reflected in routing tablehttps://redmine.pfsense.org/issues/11599?journal_id=523612021-03-14T04:07:42ZViktor Gurov
<ul><li><strong>Affected Version</strong> changed from <i>2.5.x</i> to <i>2.5.0</i></li></ul><p>see also <a class="issue tracker-1 status-3 priority-4 priority-default closed" title="Bug: Static routes using aliases are not automatically updated when alias content changes (Resolved)" href="https://redmine.pfsense.org/issues/7547">#7547</a><br />we need to keep a cache of the currently applied static routes to compare against when editing/updating</p> pfSense - Bug #11599: Modifying static routes results in a logged error, changes are not reflected in routing tablehttps://redmine.pfsense.org/issues/11599?journal_id=557382021-08-14T11:46:54ZViktor Gurov
<ul></ul><p><a class="external" href="https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/342">https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/342</a></p> pfSense - Bug #11599: Modifying static routes results in a logged error, changes are not reflected in routing tablehttps://redmine.pfsense.org/issues/11599?journal_id=557502021-08-16T07:35:58ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Pull Request Review</i></li><li><strong>Target version</strong> set to <i>CE-Next</i></li><li><strong>Plus Target Version</strong> set to <i>Plus-Next</i></li></ul> pfSense - Bug #11599: Modifying static routes results in a logged error, changes are not reflected in routing tablehttps://redmine.pfsense.org/issues/11599?journal_id=574972021-11-21T11:58:52ZMarcos M
<ul></ul>Tested this on <code>22.01.a.20211108.0600</code>.
<ul>
<li>Deleting a static route does not prompt for an "Apply Changes" confirmation.</li>
<li>Deleting a static route entry does not remove it from the route table.</li>
<li>Removing an entry from a network IP alias being used in a static route entry does not remove it from the route table.</li>
<li>Changing an entry from a network IP alias being used in a static route entry adds the new route but does not delete the old one.</li>
</ul>
<p>Related issues:<br /><a class="issue tracker-1 status-3 priority-4 priority-default closed" title="Bug: Modifying static routes results in a logged error, changes are not reflected in routing table (Resolved)" href="https://redmine.pfsense.org/issues/11599">#11599</a> <a class="issue tracker-2 status-3 priority-4 priority-default closed" title="Feature: Require user to manually apply changes after altering static route entries (Resolved)" href="https://redmine.pfsense.org/issues/11895">#11895</a> <a class="issue tracker-1 status-3 priority-4 priority-default closed" title="Bug: Static routes using aliases are not automatically updated when alias content changes (Resolved)" href="https://redmine.pfsense.org/issues/7547">#7547</a></p> pfSense - Bug #11599: Modifying static routes results in a logged error, changes are not reflected in routing tablehttps://redmine.pfsense.org/issues/11599?journal_id=575562021-11-29T13:05:09ZViktor Gurov
<ul><li><strong>Status</strong> changed from <i>Pull Request Review</i> to <i>Feedback</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Applied in changeset <a class="changeset" title="Static routes handling update. Fixes #11599 #11895 #7547 * Confirmation box to apply static rout..." href="https://redmine.pfsense.org/projects/pfsense/repository/2/revisions/332052b8bd2a5d35662be2dba773b7a9f0d50681">332052b8bd2a5d35662be2dba773b7a9f0d50681</a>.</p> pfSense - Bug #11599: Modifying static routes results in a logged error, changes are not reflected in routing tablehttps://redmine.pfsense.org/issues/11599?journal_id=575772021-12-01T22:34:37ZAlhusein Zawi
<ul></ul><p>I added a static route 192.168.254.0/24 ,the route is added to routing table.</p>
<p>after modifying it to be 192.0.0.0/8 the new route is added to routing table and old one has not been removed .</p>
<p>192.0.0.0/8 10.100.100.1 UGS 0 1500 em1 <br />192.168.254.0/24 10.100.100.1 UGS 0 1500 em1</p>
<p>22.01.a.20211130.0600</p> pfSense - Bug #11599: Modifying static routes results in a logged error, changes are not reflected in routing tablehttps://redmine.pfsense.org/issues/11599?journal_id=575782021-12-01T23:38:19ZViktor Gurov
<ul></ul><p>Alhusein Zawi wrote in <a href="#note-6">#note-6</a>:</p>
<blockquote>
<p>I added a static route 192.168.254.0/24 ,the route is added to routing table.</p>
<p>after modifying it to be 192.0.0.0/8 the new route is added to routing table and old one has not been removed .</p>
<p>192.0.0.0/8 10.100.100.1 UGS 0 1500 em1 <br />192.168.254.0/24 10.100.100.1 UGS 0 1500 em1</p>
<p>22.01.a.20211130.0600</p>
</blockquote>
<p>This fix is still not merged to 22.01</p> pfSense - Bug #11599: Modifying static routes results in a logged error, changes are not reflected in routing tablehttps://redmine.pfsense.org/issues/11599?journal_id=576842021-12-06T07:53:53ZJim Pingle
<ul><li><strong>Subject</strong> changed from <i>Error on updating routing table after modifying static routes</i> to <i>Modifying static routes results in a logged error, changes are not reflected in routing table</i></li><li><strong>Target version</strong> changed from <i>CE-Next</i> to <i>2.6.0</i></li><li><strong>Plus Target Version</strong> changed from <i>Plus-Next</i> to <i>22.01</i></li></ul><p>Updating subject for release notes and fixing targets.</p> pfSense - Bug #11599: Modifying static routes results in a logged error, changes are not reflected in routing tablehttps://redmine.pfsense.org/issues/11599?journal_id=585862022-01-25T12:41:55ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>Working as expected on current 22.01 RC and 2.6.0 RC snapshots.</p>