Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Weird inactive interface in route table on frr-10.2 #17550

Open
2 tasks done
bocmanpy opened this issue Dec 3, 2024 · 3 comments
Open
2 tasks done

Weird inactive interface in route table on frr-10.2 #17550

bocmanpy opened this issue Dec 3, 2024 · 3 comments
Labels
triage Needs further investigation

Comments

@bocmanpy
Copy link

bocmanpy commented Dec 3, 2024

Description

On new version frr-10.2 i getting weird case.
Interface po1 is UP and you can see it from ip link and show interface command.
But in show ip route routes belonging that interface saying it's linkdown/inactive.
frr_10 2_weird_status
I'm downgraded to frr-10.1 and that problem won't reproducing.
Restarting frr-10.2 helping interface become normal in route table.

Version

FRRouting 10.2 (hostname) on Linux(4.18.0-532.el8.x86_64).
Copyright 1996-2005 Kunihiro Ishiguro, et al.
configured with:
    '--prefix=/usr' '--sbindir=/usr/sbin' '--sysconfdir=/etc' '--localstatedir=/run' '--libdir=/usr/lib64/frr' '--libexecdir=/usr/libexec/frr' '--with-moduledir=/usr/lib64/frr/modules' '--with-crypto=openssl' '--with-libpam' '--enable-multipath=256' '--enable-user=frr' '--enable-group=frr' '--enable-vty-group=frrvty' '--enable-configfile-mask=0640' '--enable-logfile-mask=0640' '--enable-config-rollbacks' '--enable-pcre2posix' '--enable-rpki' '--enable-fpm' '--disable-babeld' '--disable-pimd' '--disable-pim6d' '--disable-isisd' '--disable-ripd' '--disable-ripngd' '--disable-ldpd' '--disable-nhrpd' '--disable-eigrpd' 'runstatedir=/run' '--disable-static' 'PKG_CONFIG_PATH=:/usr/lib64/pkgconfig:/usr/share/pkgconfig'

How to reproduce

  1. On frr 10.2 use similar frr.conf
frr.conf
!
ip route 10.10.0.0/16 10.10.3.254 po1
ip route 10.24.0.0/16 10.24.3.254 vlan24
ip route 10.25.0.0/16 10.25.3.254 vlan25
!
interface po1
 pbr-policy po1
exit
!
interface vlan24
 pbr-policy vlan24
exit
!
interface vlan25
 pbr-policy vlan25
exit
!
pbr-map po1 seq 5
 match src-ip 10.10.3.24/32
 set nexthop-group po1
exit
!
pbr-map vlan24 seq 5
 match src-ip 10.24.3.24/32
 set nexthop-group vlan24
exit
!
pbr-map vlan25 seq 5
 match src-ip 10.25.3.16/32
 set nexthop-group vlan25
exit
!
nexthop-group po1
 nexthop 10.10.3.254 po1
exit
!
nexthop-group vlan24
 nexthop 10.24.3.254 vlan24
exit
!
nexthop-group vlan25
 nexthop 10.25.3.254 vlan25
exit
!
access-list vty remark Disable connections to vtysh from non localhost
access-list vty seq 5 permit 127.0.0.1/8
access-list vty seq 10 deny any
!
line vty
 access-class vty
exit
!
Expected behavior

Interface should be active in route table and related routes was added.

Actual behavior

Interface in route table marked as linkdown/inactive and related routes doesn't adding to route table.
Here is debug logs from 10.1 and 10.2 versions.
frr_10.1_debug.log
frr_10.2_debug.log

Additional context

The main problem is that is not 100% reproducible.
I have a same(only subnets different) configuration that is working fine with frr-10.2

Checklist

  • I have searched the open issues for this bug.
  • I have not included sensitive information in this report.
@bocmanpy bocmanpy added the triage Needs further investigation label Dec 3, 2024
@k0ste
Copy link
Contributor

k0ste commented Dec 4, 2024

@anlancs can be #17544 or #17403 is fix this issue? Or is another bug? Thanks

@ton31337
Copy link
Member

@anlancs is this familiar to you?

@anlancs
Copy link
Contributor

anlancs commented Dec 16, 2024

No, this is different with my two PRs.
In this issue, the nexthop seems wrongly inactive and not 100%. I haven’t met this issue. :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Needs further investigation
Projects
None yet
Development

No branches or pull requests

4 participants