![]() EVPN routes (type-2/type-5) are imported from default bgp instance (where they are learnt) to non-default vrf instance. When a bgp instance (default) is deleted, unimport evpn routes from vrfs. In absence of unimport, the imported routes in vrf has parent path info points to default instance's path info which is no longer valid (if instance is deleted). When accessing parent path info leads to a crash in non-default vrf instance. The bgp instance is not cleaned up when 'no router bgp ASN' is performed, the instance's reference count remains for evpn imported routes. Ticket:CM-24484 Reviewed By: Testing Done: Validated via learning EVPN type-2/type-5 routes in symmetric routing scenario. The routes are imported to VRFs based on corresponding L3VNI. When the default instance is removed, the evpn routes are cleaned up from the VRF instance. TURTLE(config)# do show bgp vrf vrf3 ipv4 unicast Network Next Hop Metric LocPrf Weight Path *> 70.1.0.0/16 0.0.0.0 32768 i s 70.1.1.24/32 110.0.0.2 0 65100 65002 i s> 110.0.0.2 0 65100 65002 i s 70.1.1.43/32 110.0.0.4 0 65100 65004 i s> 110.0.0.4 0 65100 65004 i TURTLE(config)# no router bgp 65050 TURTLE(config)# do show bgp vrf vrf3 ipv4 unicast No BGP prefixes displayed, 0 exist Signed-off-by: Chirag Shah <chirag@cumulusnetworks.com> |
||
---|---|---|
.github | ||
alpine | ||
babeld | ||
bfdd | ||
bgpd | ||
debian | ||
doc | ||
docker | ||
eigrpd | ||
fpm | ||
gdb | ||
include | ||
isisd | ||
ldpd | ||
lib | ||
m4 | ||
nhrpd | ||
ospf6d | ||
ospfclient | ||
ospfd | ||
pbrd | ||
pimd | ||
pkgsrc | ||
ports | ||
python | ||
qpb | ||
redhat | ||
ripd | ||
ripngd | ||
sharpd | ||
snapcraft | ||
solaris | ||
staticd | ||
tests | ||
tools | ||
vtysh | ||
watchfrr | ||
yang | ||
zebra | ||
.clang-format | ||
.dir-locals.el | ||
.dockerignore | ||
.gitignore | ||
bootstrap.sh | ||
buildtest.sh | ||
changelog-auto.in | ||
config.version.in | ||
configure.ac | ||
COPYING | ||
COPYING-LGPLv2.1 | ||
defaults.h | ||
Makefile.am | ||
README.md | ||
stamp-h.in |
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 as well as Solaris 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
- EIGRP (alpha)
- NHRP (alpha)
Installation & Use
Packages are available for various distributions on our releases page.
Snaps are also available here.
Instructions on building and installing from source for supported platforms may be found here.
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