Actions
Bug #16493
closedStatic routes not withdrawn from FRR when deleted in pfSense
Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
FRR
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
Affected Architecture:
Description
Created a static route to the ospf neighbor:
somefirewall-vtysh# show ip route 172.25.17.0/24 Routing entry for 172.25.17.0/24 Known via "kernel", distance 0, metric 0, best Last update 00:00:58 ago * 172.25.16.4, via ix0.1001
Added that interface to the neighbor's OSPF process:
somefirewall-vtysh# show ip route 172.25.17.0/24 Routing entry for 172.25.17.0/24 Known via "ospf", distance 110, metric 20 Last update 00:00:22 ago 172.25.16.4, via ix0.1001, weight 1 Routing entry for 172.25.17.0/24 Known via "kernel", distance 0, metric 0, best Last update 00:02:50 ago * 172.25.16.4, via ix0.1001
pfSense routing table:
[25.07.1-RELEASE][root@somefirewall]/root: netstat -rnfinet Internet: Destination Gateway Flags Netif Expire [snip] 172.25.17.0/24 172.25.16.4 UGS ix0.1001
That's the static route...
Deleted static route from pfSense.
Routing table loses route:
[25.07.1-RELEASE][root@somefirewall]/root: netstat -rnfinet Internet: Destination Gateway Flags Netif Expire [snip] 172.25.16.0/29 link#30 U ix0.1001 172.25.16.5 link#10 UHS lo0 172.25.64.0/24 link#32 U ovpns2 172.25.64.1 link#10 UHS lo0
FRR still thinks the static route exists so it will not install the ospf route due to administrative distance:
somefirewall# show ip route 172.25.17.0/24 Routing entry for 172.25.17.0/24 Known via "ospf", distance 110, metric 20 Last update 00:03:47 ago 172.25.16.4, via ix0.1001, weight 1 Routing entry for 172.25.17.0/24 Known via "kernel", distance 0, metric 0, best <-- Last update 00:06:15 ago * 172.25.16.4, via ix0.1001
Should the static/kernel route drop from FRR so it knows to insert the OSPF route into the FIB? Yes. Does it? No.
Actions