1cbbc94e55
On a L3VPN setup, an aggretated prefix can not be exported and selected. The below example illustrates the 172.31.0.0/24 aggregated prefix, which is valid as a VRF prefix, but invalid as a VPN prefix: > r1# show bgp ipv4 vpn 172.31.0.0/24 > BGP routing table entry for 444:1:172.31.0.0/24, version 0 > not allocated > Paths: (1 available, no best path) > Not advertised to any peer > Local, (aggregated by 65500 192.0.2.1) > 0.0.0.0 from 0.0.0.0 (192.0.2.1) vrf vrf1(4) announce-nh-self > Origin incomplete, metric 0, weight 32768, invalid, sourced, local, atomic-aggregate > Extended Community: RT:52:100 > Originator: 192.0.2.1 > Remote label: 101 > Last update: Mon Mar 3 14:35:04 2025 > r1# show bgp vrf vrf1 ipv4 172.31.0.0/24 > BGP routing table entry for 172.31.0.0/24, version 1 > Paths: (1 available, best #1, vrf vrf1) > Not advertised to any peer > Local, (aggregated by 65500 192.0.2.1) > 0.0.0.0 from 0.0.0.0 (192.0.2.1) > Origin incomplete, metric 0, weight 32768, valid, aggregated, local, atomic-aggregate, best (First path received) > Last update: Mon Mar 3 14:35:03 2025 > r1# Actually, the aggregated prefix nexthop is considered, and 0.0.0.0 is an invalid nexthop. > r1# show bgp vrf vrf1 nexthop > Current BGP nexthop cache: > 0.0.0.0 invalid, #paths 1 > Is not Registered > Last update: Thu Feb 13 18:33:43 2025 Fix this by considering the L3VPN prefix selected, if the VRF prefix is selected too. Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com> |
||
|---|---|---|
| .github | ||
| alpine | ||
| babeld | ||
| bfdd | ||
| bgpd | ||
| debian | ||
| doc | ||
| docker | ||
| eigrpd | ||
| fpm | ||
| gdb | ||
| grpc | ||
| include | ||
| isisd | ||
| ldpd | ||
| lib | ||
| m4 | ||
| mgmtd | ||
| mlag | ||
| nhrpd | ||
| ospf6d | ||
| ospfclient | ||
| ospfd | ||
| pathd | ||
| pbrd | ||
| pceplib | ||
| pimd | ||
| pkgsrc | ||
| python | ||
| qpb | ||
| redhat | ||
| ripd | ||
| ripngd | ||
| sharpd | ||
| snapcraft | ||
| staticd | ||
| tests | ||
| tools | ||
| vrrpd | ||
| vtysh | ||
| watchfrr | ||
| yang | ||
| zebra | ||
| .clang-format | ||
| .dockerignore | ||
| .flake8 | ||
| .git-blame-ignore-revs | ||
| .gitignore | ||
| .isort.cfg | ||
| .pylintrc | ||
| .travis.yml | ||
| bootstrap.sh | ||
| buildtest.sh | ||
| config.version.in | ||
| configure.ac | ||
| COPYING | ||
| Makefile.am | ||
| README.md | ||
| stamp-h.in | ||
| version.h | ||
FRRouting
FRR is free software that implements and manages various IPv4 and IPv6 routing protocols. It runs on nearly all distributions of Linux and BSD and supports all modern CPU architectures.
FRR currently supports the following protocols:
- BGP
- OSPFv2
- OSPFv3
- RIPv1
- RIPv2
- RIPng
- IS-IS
- PIM-SM/MSDP
- LDP
- BFD
- Babel
- PBR
- OpenFabric
- VRRP
- EIGRP (alpha)
- NHRP (alpha)
Installation & Use
For source tarballs, see the releases page.
For Debian and its derivatives, use the APT repository at https://deb.frrouting.org/.
Instructions on building and installing from source for supported platforms may be found in the developer docs.
Once installed, please refer to the user guide for instructions on use.
Community
The FRRouting email list server is located here and offers the following public lists:
| Topic | List |
|---|---|
| Development | dev@lists.frrouting.org |
| Users & Operators | frog@lists.frrouting.org |
| Announcements | announce@lists.frrouting.org |
For chat, we currently use Slack. You can join by clicking the "Slack" link under the Participate section of our website.
Contributing
FRR maintains developer's documentation which contains the project workflow and expectations for contributors. Some technical documentation on project internals is also available.
We welcome and appreciate all contributions, no matter how small!
Security
To report security issues, please use our security mailing list:
security [at] lists.frrouting.org