Skip to content
New issue

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

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

Already on GitHub? # to your account

RIP: distribute-list not applied to correct VRF #18141

Closed
2 tasks done
alesuiss opened this issue Feb 13, 2025 · 3 comments
Closed
2 tasks done

RIP: distribute-list not applied to correct VRF #18141

alesuiss opened this issue Feb 13, 2025 · 3 comments
Labels
triage Needs further investigation

Comments

@alesuiss
Copy link

Description

Hello,

I have an issue where, when RIP is configured on multiple VRFs, and a distribute-list is configured for RIP in one of the VRFs, it actually applies to the wrong VRF. Example:

router rip vrf VRF1
  timers basic 5 10 5
  distance 19
!

router rip vrf VRF2
 distance 19
 network svi-vlan14
 passive-interface svi-vlan14
 timers basic 5 10 5
 distribute-list vlan14svcip in svi-vlan14
!

Output of show running-config after applying the above:

router rip vrf VRF1
 distance 19
 timers basic 5 10 5
 distribute-list vlan14svcip in svi-vlan14
exit
!
router rip vrf VRF2
 distance 19
 network svi-vlan14
 passive-interface svi-vlan14
 timers basic 5 10 5
exit
!

As you can see, the distribute-list configured on VRF2 is actually applied on VRF1 (and is indeed not effective on VRF2). As it is, I can't find any way to configure the distribute-list on VRF2 as long as the RIP config for VRF1 exists.

OS is Proxmox 8 (based on Debian "bookworm"); frr version is 8.5.2-1+pve1. The daemons in use are zebra, bgpd, ripd, bfdd and staticd.

Version

FRRouting 8.5.2 (cmmi06) on Linux(6.8.12-3-pve).
Copyright 1996-2005 Kunihiro Ishiguro, et al.
configured with:
    '--build=x86_64-linux-gnu' '--prefix=/usr' '--includedir=${prefix}/include' '--mandir=${prefix}/share/man' '--infodir=${prefix}/share/info' '--sysconfdir=/etc' '--localstatedir=/var' '--disable-option-checking' '--disable-silent-rules' '--libdir=${prefix}/lib/x86_64-linux-gnu' '--runstatedir=/run' '--disable-maintainer-mode' '--localstatedir=/var/run/frr' '--sbindir=/usr/lib/frr' '--sysconfdir=/etc/frr' '--with-vtysh-pager=/usr/bin/pager' '--libdir=/usr/lib/x86_64-linux-gnu/frr' '--with-moduledir=/usr/lib/x86_64-linux-gnu/frr/modules' '--disable-dependency-tracking' '--disable-rpki' '--disable-scripting' '--enable-pim6d' '--with-libpam' '--enable-doc' '--enable-doc-html' '--enable-snmp' '--enable-fpm' '--disable-protobuf' '--disable-zeromq' '--enable-ospfapi' '--enable-bgp-vnc' '--enable-multipath=256' '--enable-user=frr' '--enable-group=frr' '--enable-vty-group=frrvty' '--enable-configfile-mask=0640' '--enable-logfile-mask=0640' 'build_alias=x86_64-linux-gnu' 'PYTHON=python3'

How to reproduce

Configure RIP on 2 VRFs, and set a distribute-list on the second VRF.

Expected behavior

distribute-list configured on the second VRF.

Actual behavior

distribute-list configured on the first VRF and not the second one.

Additional context

No response

Checklist

  • I have searched the open issues for this bug.
  • I have not included sensitive information in this report.
@alesuiss alesuiss added the triage Needs further investigation label Feb 13, 2025
@ton31337
Copy link
Member

@alesuiss any chance to test with at least 10.x releases?

@alesuiss
Copy link
Author

@ton31337 Ah, it does seem to work properly with 10.2; apologies for the noise.

@ton31337
Copy link
Member

No worries, closing.

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

No branches or pull requests

2 participants