forked from Mirror/frr
ef1fc25431
When acting as intermediate device for BGP signaling, and as transit device for data traffic, the device is not able to modify the label value from incoming MPLS VPN updates: - as BGP device, modifying the label value is necessary when redistributing VPN prefixes with its own next-hop. - as transit device that connects two ethernet segments on separate interfaces, the return MPLS traffic must be handled: the modified label value must be swapped with the original label value and sent back to the original next-hop. The border router use case can be taken as example, when it acts both as transit and as BGP device: - When receiving updates from a border router peer, and where interior traffic is expected to transit through the local border router. - When receiving updates from interior devices, and where exterior traffic will transit through the local border router. In those two situations, a new label is bound to the received entry, and the entry is advertised to a new peer with the new label. In the same time, an MPLS entry is created to handle return traffic with the new mpls label: the traffic would be swapped to the original MPLS label and the original next-hop. This is the first commit of a series of patches, that address the above mentioned issue. The first commit introduces a new per-interface command: > interface eth0 > [no] mpls bgp l3vpn-multi-domain-switching > exit This command will authorise mpls vpn updates to have a new label value bound to the mpls vpn routes received over that interface. Link: https://www.rfc-editor.org/rfc/rfc3107.html#section-3 > When a BGP speaker redistributes a route, the label(s) assigned to > that route must not be changed (except by omission), unless the > speaker changes the value of the Next Hop attribute of the route. Link: https://www.rfc-editor.org/rfc/rfc3031.html#section-4.6 Link: https://www.rfc-editor.org/rfc/rfc4364.html#section-10 sub-chapter b. Signed-off-by: Louis Scalbert <louis.scalbert@6wind.com> 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 | ||
| 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