bc09f3e6bb
During the database description exchange process, the slave releases the last dbdesc packet after router_dead_interval. This was not implemented in the code. I have written the function ospf6_neighbor_last_dbdesc_release, which releases the last dbdesc packet after router_dead_interval. This change was required as per the conformance test 13.11: In state Full reception of a Database Description packet from the master after this interval (RouterDeadInterval) will generate a SeqNumberMismatch neighbor event. Associated Parameters ICMPv6 Packet Listen Time ICMPv6 Packet Tolerance Factor ICMPv6 Packet Tolerance Time OSPFV3 DUT Interface Transmit Delay OSPF Reset Adjacencies Timeout Test Actions 1. 2. 3. ANVL: Establish full adjacency with DUT for neighbor Rtr-0-A on DIface-0, with DUT as slave. ANVL: Wait (for <RouterDeadInterval> seconds). ANVL: Send <OSPF-DD> packet from neighbor Rtr-0-A to DIface-0 con- taining: • • I-bit field not set M-bit field not set MS-bit field set DD sequence number same as the one last sent by ANVL. . ANVL: Listen (for upto 2 * <RxmtInterval> seconds) on DIface-0. 5. DUT: Trigger the event SeqNumberMismatch and set the neighbor state for neighbor Rtr-0-A to ExStart. 6. DUT: Send <OSPF-DD> packet. 7. ANVL: Verify that the received <OSPF-DD> packet contains: • I-bit field set • M-bit field set • MS-bit field set. Test Reference • RFC 5340, s4.2.1.2 p19 Sending Database Description Packets RFC 2328, s10.8 p104 Sending Database Description Packets. Signed-off-by: Yash Ranjan <ranjany@vmware.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 | ||
| .travis.yml | ||
| bootstrap.sh | ||
| buildtest.sh | ||
| changelog-auto.in | ||
| config.version.in | ||
| configure.ac | ||
| COPYING | ||
| COPYING-LGPLv2.1 | ||
| 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