mirror of
https://git.proxmox.com/git/mirror_frr
synced 2025-08-11 16:39:33 +00:00
doc: update VRF support description
Signed-off-by: Igor Ryzhov <iryzhov@nfware.com>
This commit is contained in:
parent
60070c3d02
commit
75b8d48236
@ -56,7 +56,4 @@ net.ipv6.neigh.default.base_reachable_time_ms=14400000
|
|||||||
|
|
||||||
# Use neigh information on selection of nexthop for multipath hops
|
# Use neigh information on selection of nexthop for multipath hops
|
||||||
net.ipv4.fib_multipath_use_neigh=1
|
net.ipv4.fib_multipath_use_neigh=1
|
||||||
|
|
||||||
# Allows Apps to Work with VRF
|
|
||||||
net.ipv4.tcp_l3mdev_accept=1
|
|
||||||
```
|
```
|
||||||
|
@ -541,20 +541,15 @@ Additional kernel modules are also needed to support MPLS forwarding.
|
|||||||
|
|
||||||
:makevar:`VRF forwarding`
|
:makevar:`VRF forwarding`
|
||||||
General information on Linux VRF support can be found in
|
General information on Linux VRF support can be found in
|
||||||
https://www.kernel.org/doc/Documentation/networking/vrf.txt. Kernel
|
https://www.kernel.org/doc/Documentation/networking/vrf.txt.
|
||||||
support for VRFs was introduced in 4.3 and improved upon through
|
|
||||||
4.13, which is the version most used in FRR testing (as of June
|
|
||||||
2018). Additional background on using Linux VRFs and kernel specific
|
|
||||||
features can be found in
|
|
||||||
http://schd.ws/hosted_files/ossna2017/fe/vrf-tutorial-oss.pdf.
|
|
||||||
|
|
||||||
A separate BGP TCP socket is opened per VRF.
|
Kernel support for VRFs was introduced in 4.3, but there are known issues
|
||||||
|
in versions up to 4.15 (for IPv4) and 5.0 (for IPv6). The FRR CI system
|
||||||
|
doesn't perform VRF tests on older kernel versions, and VRFs may not work
|
||||||
|
on them. If you experience issues with VRF support, you should upgrade your
|
||||||
|
kernel version.
|
||||||
|
|
||||||
**Important note** as of June 2018, Kernel versions 4.14-4.18 have a
|
.. seealso:: :ref:`zebra-vrf`
|
||||||
known bug where VRF-specific TCP sockets are not properly handled. When
|
|
||||||
running these kernel versions, if unable to establish any VRF BGP
|
|
||||||
adjacencies, downgrade to 4.13. The issue was fixed in 4.14.57, 4.17.9
|
|
||||||
and more recent kernel versions.
|
|
||||||
|
|
||||||
Building
|
Building
|
||||||
^^^^^^^^
|
^^^^^^^^
|
||||||
|
@ -261,8 +261,6 @@ Link Parameters Commands
|
|||||||
Allows nexthop tracking to resolve via the default route. This is useful
|
Allows nexthop tracking to resolve via the default route. This is useful
|
||||||
when e.g. you want to allow BGP to peer across the default route.
|
when e.g. you want to allow BGP to peer across the default route.
|
||||||
|
|
||||||
.. _zebra-vrf:
|
|
||||||
|
|
||||||
Administrative Distance
|
Administrative Distance
|
||||||
=======================
|
=======================
|
||||||
|
|
||||||
@ -338,6 +336,8 @@ work FRR must use the same metric when issuing the replace command.
|
|||||||
Currently FRR only supports Route Replace semantics using the Linux
|
Currently FRR only supports Route Replace semantics using the Linux
|
||||||
Kernel.
|
Kernel.
|
||||||
|
|
||||||
|
.. _zebra-vrf:
|
||||||
|
|
||||||
Virtual Routing and Forwarding
|
Virtual Routing and Forwarding
|
||||||
==============================
|
==============================
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user