There doesnt appear to be an option to enable "ipv6 nht resolve-via-default". This is needed for bgp to work with providers such as vultr who require multihop sessions that must use an autoconfigured gateway.
Description
Details
- Version
- -
- Is it a breaking change?
- Unspecified (possibly destroys the router)
- Issue type
- Unspecified (please specify)
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | FEATURE REQUEST | c-po | T5788 frr: update to 9.1 release | ||
Resolved | c-po | T6001 Add option to enable resolve-via-default |
Event Timeline
this command was added by default in FRR , but it's supported on lasted version (9.1):
https://docs.frrouting.org/en/latest/zebra.html#clicmd-ip-nht-resolve-via-default
https://docs.frrouting.org/en/latest/zebra.html#clicmd-ipv6-nht-resolve-via-default
I was looking into the issue here on the forums for the user, i see the documentation says it should be enabled by default for the traditional profile which it appears to be set to use, but it does not work until i manually set that option through vtysh.
root@vyos:/home/vyos# vtysh
Hello, this is FRRouting (version 9.0.2).
Copyright 1996-2005 Kunihiro Ishiguro, et al.
root@vyos:/home/vyos# show version
Version: VyOS 1.4-rolling-202401280807
Release train: sagitta
Built by: kylem@serverforge.org
Built on: Sun 28 Jan 2024 08:07 UTC
Build UUID: 7b58c827-660e-467b-8fcc-bba021e4fb04
Build commit ID: 425029722042fa
Architecture: x86_64
Boot via: installed image
System type: Microsoft Hyper-V guest
Hardware vendor: Vultr
Hardware model: VC2
Hardware S/N: 71360910
Hardware UUID: 7e74c4c3-8264-4c8e-9ed0-b3ef55f708f9
Copyright: VyOS maintainers and contributors
as I mentioned , it was added in 9.1 as default behavior :
https://github.com/FRRouting/frr/releases/tag/frr-9.1
although , we've identified an issues that has not yet been fixed :
I recommend waiting until this version will be updated with our system, it will be cleaner than adding a new command.
Ahh, i misunderstood that as the command "ipv6 nht resolve-via-default" was still supported on 9.1, not that it was only the default in 9.1. I agree waiting on the update may be a cleaner solution.
As FRR 9.1 will be shipped in 1.5 - I will add knobs do disable this behavior
- set system ip nht no-resolve-via-default
- set system ipv6 nht no-resolve-via-default
- set vrf name <name> ip nht no-resolve-via-default
- set vrf name <name> ipv6 nht no-resolve-via-default
And some other knobs under nht provided by FRR