mirror of
https://git.proxmox.com/git/mirror_frr
synced 2025-08-14 04:26:12 +00:00
c9b416cbd1
The label allocation per nexthop mode requires to use a nexthop tracking context. For redistributed routes, a nexthop tracking context is created, and the resolution helps to know the real nexthop ip address used. The below configuration example has been used: > vrf vrf1 > ip route 172.31.0.14/32 192.0.2.14 > ip route 172.31.0.15/32 192.0.2.12 > ip route 172.31.0.30/32 192.0.2.30 > exit > router bgp 65500 vrf vrf1 > address-family ipv4 unicast > redistribute static > label vpn export per-nexthop > [..] The static routes are correctly imported in the BGP IPv4 RIB. Contrary to label allocation per vrf mode, some nexthop tracking are created/or reused: > # show bgp vrf vrf1 nexthop > 192.0.2.12 valid [IGP metric 0], #paths 3, peer 192.0.2.12 > if r1-eth1 > Last update: Fri Jan 13 15:49:42 2023 > 192.0.2.14 valid [IGP metric 0], #paths 1 > if r1-eth1 > Last update: Fri Jan 13 15:49:42 2023 > 192.0.2.30 valid [IGP metric 0], #paths 1 > if r1-eth1 > Last update: Fri Jan 13 15:49:51 2023 > [..] This results in having a BGP VPN route for each of the static routes: > # show bgp ipv4 vpn > [..] > Route Distinguisher: 444:1 > *> 172.31.0.14/32 192.0.2.14@9< 0 32768 ? > *> 172.31.0.15/32 192.0.2.12@9< 0 32768 ? > *> 172.31.0.30/32 192.0.2.30@9< 0 32768 ? > [..] Without that patch, only the redistributed routes that rely on a pre-existing nexthop tracking context could be exported. Also, a command in the code about redistributed routes is modified accordingly, to explain that redistribute routes may be submitted to nexthop tracking in the case label allocation per next-hop is used. note: VNC routes have been removed from the redistribution, because of a test failure in the bgp_l3vpn_to_bgp_direct test. 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 | ||
| 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 | ||
| .dir-locals.el | ||
| .dockerignore | ||
| .git-blame-ignore-revs | ||
| .gitignore | ||
| .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