62a452c47f
When 'no neighbor .. update-source' is issued for a regular peer, that peer is always reset. This is unnecessary if the peer is a member of a peer-group and it inherits an identical update-source, so let's skip the reset/Notification for that condition. Config: ------------ router bgp 1 neighbor PG peer-group neighbor PG remote-as internal neighbor PG update-source 100.64.0.3 neighbor 192.168.122.99 peer-group PG neighbor 192.168.122.99 update-source 100.64.0.3 Before: ------------ ub20-2(config-router)# do show ip bgp sum | include .99 192.168.122.99 4 1 36 34 0 0 0 00:00:17 0 0 N/A ub20-2(config-router)# do show ip bgp neighbors 192.168.122.99 | include Local host Local host: 100.64.0.3, Local port: 46083 ub20-2(config-router)# no neighbor 192.168.122.99 update-source ub20-2(config-router)# do show ip bgp sum | include .99 192.168.122.99 4 1 36 35 0 0 0 00:00:01 Idle 0 N/A ub20-2(config-router)# do show ip bgp neighbors 192.168.122.99 | include Local host Local host: 100.64.0.3, Local port: 39847 After: ------------ ub20-2(config-router)# do show ip bgp sum | include .99 192.168.122.99 4 1 3 3 0 0 0 00:00:20 0 0 N/A ub20-2(config-router)# do show ip bgp neighbors 192.168.122.99 | include Local host Local host: 100.64.0.3, Local port: 39415 ub20-2(config-router)# no neighbor 192.168.122.99 update-source ub20-2(config-router)# do show ip bgp sum | include .99 192.168.122.99 4 1 3 3 0 0 0 00:00:28 0 0 N/A ub20-2(config-router)# do show ip bgp neighbors 192.168.122.99 | include Local host Local host: 100.64.0.3, Local port: 39415 Signed-off-by: Trey Aspelund <taspelund@nvidia.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