mirror of
https://git.proxmox.com/git/mirror_frr
synced 2025-08-14 08:50:26 +00:00
02e7a369b8
Route-maps contain a hash of hash's that contain the container type name ( say community or access list or whatever ) and then it has a hash of route-maps that this maps too Suppose you have this: ! frr version 7.3.1 frr defaults traditional hostname eva log stdout ! debug route-map ! router bgp 239 neighbor 192.168.161.2 remote-as external ! address-family ipv4 unicast neighbor 192.168.161.2 route-map foo in exit-address-family ! bgp community-list standard 7000:40002 permit 7000:40002 bgp community-list standard 7000:40002 permit 7000:40003 ! route-map foo deny 20 match community 7000:40002 ! route-map foo permit 10 ! line vty ! end You have a community hash which has an 7000:40002 entry This entry has a hash of routemaps that are referencing it. In this above example it would have `foo` as the single entry. Given the above config if you do this: eva# conf eva(config)# route-map foo deny 20 eva(config-route-map)# match community 7000:4003 eva(config-route-map)# We would expect the `7000:40002` community hash to no longer have a reference to the `foo` routemap. Instead we see the code doing this: 2020/12/18 13:47:12 BGP: bgpd 7.3.1 starting: vty@2605, bgp@<all>:179 2020/12/18 13:47:47 BGP: Add route-map foo 2020/12/18 13:47:47 BGP: Route-map foo add sequence 10, type: permit 2020/12/18 13:47:57 BGP: Route-map foo add sequence 20, type: deny 2020/12/18 13:48:05 BGP: Adding dependency for filter 7000:40002 in route-map foo 2020/12/18 13:48:05 BGP: route_map_print_dependency: Dependency for 7000:40002: foo 2020/12/18 13:48:41 BGP: bgp_update_receive: rcvd End-of-RIB for IPv4 Unicast from 192.168.161.2 in vrf default 2020/12/18 13:49:19 BGP: Deleting dependency for filter 7000:4003 in route-map foo 2020/12/18 13:49:19 BGP: Adding dependency for filter 7000:4003 in route-map foo 2020/12/18 13:49:19 BGP: route_map_print_dependency: Dependency for 7000:4003: foo Note how the code attempts to remove the dependency for `7000:4003` instead of the dependency for `7000:40002`. Then we create a new hash for `7000:4003` and then install the routemap name in it. This is wrong. We should remove the `7000:40002` dependency and then install a dependency for `7000:4003`. Fix the code to do the right thing. Signed-off-by: Donald Sharp <sharpd@nvidia.com> |
||
|---|---|---|
| .github | ||
| alpine | ||
| babeld | ||
| bfdd | ||
| bgpd | ||
| debian | ||
| doc | ||
| docker | ||
| eigrpd | ||
| fpm | ||
| gdb | ||
| grpc | ||
| include | ||
| isisd | ||
| ldpd | ||
| lib | ||
| m4 | ||
| mlag | ||
| nhrpd | ||
| ospf6d | ||
| ospfclient | ||
| ospfd | ||
| pbrd | ||
| 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 | ||
| bootstrap.sh | ||
| buildtest.sh | ||
| changelog-auto.in | ||
| config.version.in | ||
| configure.ac | ||
| COPYING | ||
| COPYING-LGPLv2.1 | ||
| 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 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