https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162022-02-22T01:12:35ZpfSense bugtrackerpfSense - Bug #12847: On startup "No routing address with matching address" might appearhttps://redmine.pfsense.org/issues/12847?journal_id=592022022-02-22T01:12:35ZViktor Gurov
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Confirmed</i></li><li><strong>Assignee</strong> set to <i>Viktor Gurov</i></li></ul><p>incorrect dynamic resolution of IPv6 gateway address if IPv6 address is not obtained:<br /><pre>
# Gateways
GWWAN_DHCP = " route-to ( vtnet1 192.168.89.3 ) "
GWWAN_DHCP6 = " route-to ( vtnet1 192.168.89.3 ) "
GWMain6 = " route-to { ( vtnet1 192.168.89.3 ) } "
</pre></p>
<p>fix:<br /><a class="external" href="https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/634">https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/634</a></p> pfSense - Bug #12847: On startup "No routing address with matching address" might appearhttps://redmine.pfsense.org/issues/12847?journal_id=592182022-02-22T07:48:11ZFlole Systems
<ul></ul><p>I am also seeing on reloading of the rules <code>all pool addresses must be in the same address family</code>, probably related/the same issue and also fixed now?</p> pfSense - Bug #12847: On startup "No routing address with matching address" might appearhttps://redmine.pfsense.org/issues/12847?journal_id=592222022-02-22T07:51:46ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>Confirmed</i> to <i>Pull Request Review</i></li><li><strong>Plus Target Version</strong> set to <i>22.05</i></li></ul> pfSense - Bug #12847: On startup "No routing address with matching address" might appearhttps://redmine.pfsense.org/issues/12847?journal_id=592492022-02-22T10:12:09ZViktor Gurov
<ul><li><strong>Status</strong> changed from <i>Pull Request Review</i> to <i>Feedback</i></li></ul><p>Merged:<br /><a class="external" href="https://github.com/pfsense/pfsense/commit/90f21a78c81778ccd9150ec0d6789efa19b66702">https://github.com/pfsense/pfsense/commit/90f21a78c81778ccd9150ec0d6789efa19b66702</a></p> pfSense - Bug #12847: On startup "No routing address with matching address" might appearhttps://redmine.pfsense.org/issues/12847?journal_id=616892022-06-03T13:08:47ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>No sign of these errors on anything I'm seeing here, static or dynamic, with or without working IPv6 when configured to obtain it. If anyone else can reproduce now we'll need to know more details about how, but as far as I can see it looks OK.</p> pfSense - Bug #12847: On startup "No routing address with matching address" might appearhttps://redmine.pfsense.org/issues/12847?journal_id=616942022-06-03T13:50:39ZDanilo Zrenjanin
<ul></ul><p>Replicated the issue on:<br /><pre>
22.01-RELEASE (amd64)
built on Mon Feb 07 16:37:59 UTC 2022
FreeBSD 12.3-STABLE
</pre></p>
<pre>
There were error(s) loading the rules: /tmp/rules.debug:182: no routing address with matching address family found. - The line in question reads [182]: pass in quick on $LAN $GWWAN_DHCP6 inet6 proto tcp from any to any ridentifier 1654279960 flags S/SA keep state label "USER_RULE"
@ 2022-06-03 20:35:38
</pre>
<p>Retested on:<br /><pre>
2.7.0-DEVELOPMENT (amd64)
built on Fri Jun 03 14:45:06 UTC 2022
FreeBSD 12.3-STABLE
</pre></p>
<p>It works fine. No errors after reboot.</p>