FRRouting / frr

The FRRouting Protocol Suite
https://frrouting.org/
Other
3.21k stars 1.24k forks source link

OSPFv3 NSSA: redistributed kernel route wrongly shows as directly connected #11738

Open karelvanhecke opened 2 years ago

karelvanhecke commented 2 years ago

Describe the bug

To Reproduce

Expected behavior

Versions

donaldsharp commented 2 years ago

Please provide config and show output to show what you think is wrong.

karelvanhecke commented 2 years ago

router1 & router2 configuration:

interface eth0
 ip ospf area 1
 ipv6 ospf6 area 1
exit
!
router ospf
 redistribute kernel
 area 1 nssa
exit
!
router ospf6
 redistribute kernel
 area 1 nssa
exit
!
end

router1 routing table:

# sh ipv6 route
Codes: K - kernel route, C - connected, S - static, R - RIPng,
       O - OSPFv3, I - IS-IS, B - BGP, N - NHRP, T - Table,
       A - Babel, F - PBR, f - OpenFabric,
       > - selected route, * - FIB route, q - queued, r - rejected, b - backup
       t - trapped, o - offload failure

O   ::/0 [110/2] via fe80::4, eth0, weight 1, 00:02:26
K>* ::/0 [0/100] via fe80::4, eth0, 00:03:46
O   <prefix_redacted>:8e04::/64 [110/1] is directly connected, eth0, weight 1, 00:02:17
C>* <prefix_redacted>:8e04::/64 is directly connected, eth0, 00:03:46
C>* <prefix_redacted>:8e04::5/128 is directly connected, cilium_host, 00:03:46
K>* <prefix_redacted>:8e40::/64 [0/1024] via <prefix_redacted>:8e40::f558, cilium_host, src <prefix_redacted>:8e04::5, 00:00:25
K>* <prefix_redacted>:8e40::f558/128 [0/1024] is directly connected, cilium_host, 00:00:25
O>* <prefix_redacted>:8e41::/64 [110/20] is directly connected, eth0, weight 1, 00:01:42 ### Received from router2, should be: <prefix_redacted>:8e41::/64 [110/20] via <prefix_redacted>:8e04::a ###
O>* <prefix_redacted>:8e41::4f34/128 [110/20] is directly connected, eth0, weight 1, 00:01:42 ### Received from router2, should be: <prefix_redacted>:8e41::4f34/128 [110/20] via <prefix_redacted>:8e04::a ###
C * fe80::/64 is directly connected, lxcda272c180790, 00:03:46
C * fe80::/64 is directly connected, lxc_health, 00:03:46
C * fe80::/64 is directly connected, cilium_host, 00:03:46
C * fe80::/64 is directly connected, cilium_net, 00:03:46
C>* fe80::/64 is directly connected, eth0, 00:03:46

router2 routing table

# sh ipv6 route
Codes: K - kernel route, C - connected, S - static, R - RIPng,
       O - OSPFv3, I - IS-IS, B - BGP, N - NHRP, T - Table,
       A - Babel, F - PBR, f - OpenFabric,
       > - selected route, * - FIB route, q - queued, r - rejected, b - backup
       t - trapped, o - offload failure

O   ::/0 [110/2] via fe80::4, eth0, weight 1, 00:02:49
K>* ::/0 [0/100] via fe80::4, eth0, 00:04:17
O   <prefix_redacted>:8e04::/64 [110/1] is directly connected, eth0, weight 1, 00:02:49
C>* <prefix_redacted>:8e04::/64 is directly connected, eth0, 00:04:17
C>* <prefix_redacted>:8e04::a/128 is directly connected, cilium_host, 00:04:17
O>* <prefix_redacted>:8e40::/64 [110/20] is directly connected, eth0, weight 1, 00:02:03 ### Received from router1, should be: <prefix_redacted>:8e40::/64 [110/20] via <prefix_redacted>:8e04::5 ###
O>* <prefix_redacted>:8e40::f558/128 [110/20] is directly connected, eth0, weight 1, 00:02:03 ### Received from router1, should be: <prefix_redacted>:8e40::f558/128 [110/20] via <prefix_redacted>:8e04::5 ###
K>* <prefix_redacted>:8e41::/64 [0/1024] via <prefix_redacted>:8e41::4f34, cilium_host, src <prefix_redacted>:8e04::a, 00:00:02
K>* <prefix_redacted>:8e41::4f34/128 [0/1024] is directly connected, cilium_host, 00:00:02
C * fe80::/64 is directly connected, lxc7fdca77a36cc, 00:04:17
C * fe80::/64 is directly connected, lxc_health, 00:04:17
C * fe80::/64 is directly connected, cilium_host, 00:04:17
C * fe80::/64 is directly connected, cilium_net, 00:04:17
C>* fe80::/64 is directly connected, eth0, 00:04:17

I added comments to the routes that are incorrectly marked as directly connected. Expected result is achieved when the area is not a NSSA. Also works as expected for OSPFv2 NSSA's.

github-actions[bot] commented 1 year ago

This issue is stale because it has been open 180 days with no activity. Comment or remove the autoclose label in order to avoid having this issue closed.

frrbot[bot] commented 1 year ago

This issue will be automatically closed in the specified period unless there is further activity.