You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Installed FRR 10.2.1 on Rocky Linux 9.5, interfaces are configured with network manager. When running the ospfd, 3 of 4 ospf external routes is shown as duplicated.
Don't know if it helps, but i'm using multiple ospf instances: ospfd_instances="1,2" configured in /etc/frr/daemons.
dcvpnr001prphk2# sho ip route ospf 1
O[1]>* 10.0.0.0/20 [110/111] via 10.254.65.24, eno12409.208, weight 1, 20:51:54
via 10.254.65.24, eno12409.208, weight 1, 20:51:54
via 10.254.65.24, eno12409.208, weight 1, 20:51:54
via 10.254.65.24, eno12409.208, weight 1, 20:51:54
O[1]>* 10.0.16.0/20 [110/111] via 10.254.65.24, eno12409.208, weight 1, 20:51:54
via 10.254.65.24, eno12409.208, weight 1, 20:51:54
via 10.254.65.24, eno12409.208, weight 1, 20:51:54
via 10.254.65.24, eno12409.208, weight 1, 20:51:54
O[1]>* 10.1.0.0/16 [110/111] via 10.254.65.24, eno12409.208, weight 1, 20:51:54
via 10.254.65.24, eno12409.208, weight 1, 20:51:54
via 10.254.65.24, eno12409.208, weight 1, 20:51:54
via 10.254.65.24, eno12409.208, weight 1, 20:51:54
O[1]>* 10.2.0.0/16 [110/111] via 10.254.65.24, eno12409.208, weight 1, 20:51:54
via 10.254.65.24, eno12409.208, weight 1, 20:51:54
via 10.254.65.24, eno12409.208, weight 1, 20:51:54
via 10.254.65.24, eno12409.208, weight 1, 20:51:54
O[1]>* 10.3.0.0/16 [110/111] via 10.254.65.24, eno12409.208, weight 1, 20:51:54
via 10.254.65.24, eno12409.208, weight 1, 20:51:54
via 10.254.65.24, eno12409.208, weight 1, 20:51:54
via 10.254.65.24, eno12409.208, weight 1, 20:51:54
Its strange that only one interface is available eno12409.208, but show ip route shows all 4 routes, even only one is correct. Is this correct behaviour ?
ip route on Linux shows as correct and expected.
prod [root@dcvpnr001prphk2 ~]# ip route
10.1.0.0/16 nhid 62 via 10.254.65.24 dev eno12409.208 proto ospf metric 20
10.2.0.0/16 nhid 62 via 10.254.65.24 dev eno12409.208 proto ospf metric 20
10.3.0.0/16 nhid 62 via 10.254.65.24 dev eno12409.208 proto ospf metric 20
10.8.0.0/16 nhid 62 via 10.254.65.24 dev eno12409.208 proto ospf metric 20
10.11.0.0/16 nhid 62 via 10.254.65.24 dev eno12409.208 proto ospf metric 20
10.13.0.0/16 nhid 62 via 10.254.65.24 dev eno12409.208 proto ospf metric 20
10.21.0.0/16 nhid 62 via 10.254.65.24 dev eno12409.208 proto ospf metric 20
10.22.0.0/16 nhid 62 via 10.254.65.24 dev eno12409.208 proto ospf metric 20
10.33.0.0/16 nhid 62 via 10.254.65.24 dev eno12409.208 proto ospf metric 20
10.34.0.0/16 nhid 62 via 10.254.65.24 dev eno12409.208 proto ospf metric 20
10.64.32.0/19 nhid 62 via 10.254.65.24 dev eno12409.208 proto ospf metric 20
prod [root@dcvpnr001prphk2 ~]# ip route get 10.1.0.0
10.1.0.0 via 10.254.65.24 dev eno12409.208 src 10.254.65.25 uid 0
cache
prod [root@dcvpnr001prphk2 ~]# ip addr show eno12409.208
17: eno12409.208@eno12409: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 30:3e:a7:1c:9e:f1 brd ff:ff:ff:ff:ff:ff
inet 10.254.65.25/31 brd 255.255.255.255 scope global eno12409.208
valid_lft forever preferred_lft forever
prod [root@dcvpnr001prphk2 ~]#
Description
Installed FRR 10.2.1 on Rocky Linux 9.5, interfaces are configured with network manager. When running the ospfd, 3 of 4 ospf external routes is shown as duplicated.
Don't know if it helps, but i'm using multiple ospf instances: ospfd_instances="1,2" configured in /etc/frr/daemons.
Lets take the same route and see:
Its strange that only one interface is available
eno12409.208
, butshow ip route
shows all 4 routes, even only one is correct. Is this correct behaviour ?ip route
on Linux shows as correct and expected.Version
How to reproduce
Configure ospf neighbourship between Rocky Linux 9.5 and FRR. Look at ospf external routes.
Expected behavior
FRR should not(?) consider all external routes as duplicated ?
Actual behavior
FRR considers external routes as duplicated
Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: