Merge pull request #1281 from vyos/nht

T6001: add option to disable next-hop-tracking resolve-via-default
This commit is contained in:
Christian Breunig 2024-02-16 09:36:34 +01:00 committed by GitHub
commit ef69ba431c
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 45 additions and 0 deletions

View File

@ -43,6 +43,19 @@ can be used to filter which routes zebra will install in the kernel.
.. note:: If you choose any as the option that will cause all protocols that
are sending routes to zebra.
Nexthop Tracking
^^^^^^^^^^^^^^^^
Nexthop tracking resolve nexthops via the default route by default. This is enabled
by default for a traditional profile of FRR which we use. It and can be disabled if
you do not wan't to e.g. allow BGP to peer across the default route.
.. cfgcmd:: set system ip nht no-resolve-via-default
Do not allow IPv4 nexthop tracking to resolve via the default route. This
parameter is configured per-VRF, so the command is also available in the VRF
subnode.
Operational commands
--------------------

View File

@ -39,6 +39,19 @@ can be used to filter which routes zebra will install in the kernel.
.. note:: If you choose any as the option that will cause all protocols that
are sending routes to zebra.
Nexthop Tracking
^^^^^^^^^^^^^^^^
Nexthop tracking resolve nexthops via the default route by default. This is enabled
by default for a traditional profile of FRR which we use. It and can be disabled if
you do not wan't to e.g. allow BGP to peer across the default route.
.. cfgcmd:: set system ipv6 nht no-resolve-via-default
Do not allow IPv6 nexthop tracking to resolve via the default route. This
parameter is configured per-VRF, so the command is also available in the VRF
subnode.
Operational commands
--------------------

View File

@ -67,6 +67,25 @@ can be used to filter which routes zebra will install in the kernel.
.. note:: If you choose any as the option that will cause all protocols that
are sending routes to zebra.
Nexthop Tracking
----------------
Nexthop tracking resolve nexthops via the default route by default. This is enabled
by default for a traditional profile of FRR which we use. It and can be disabled if
you do not wan't to e.g. allow BGP to peer across the default route.
.. cfgcmd:: set vrf name <name> ip nht no-resolve-via-default
Do not allow IPv4 nexthop tracking to resolve via the default route. This
parameter is configured per-VRF, so the command is also available in the VRF
subnode.
.. cfgcmd:: set vrf name <name> ipv6 nht no-resolve-via-default
Do not allow IPv4 nexthop tracking to resolve via the default route. This
parameter is configured per-VRF, so the command is also available in the VRF
subnode.
Interfaces
----------