diff options
| author | Lee Clements <lclements0@gmail.com> | 2026-07-25 20:00:20 -0400 |
|---|---|---|
| committer | Lee Clements <lclements0@gmail.com> | 2026-07-27 03:07:24 -0400 |
| commit | c031fd07a098b958cbcac681e3431e33a435da3c (patch) | |
| tree | 69bd6563879c3483a2a71a7691e2aa2ec006a1c0 /scripts | |
| parent | d50098cd3023fb7307c2612caf9b02bac275f46b (diff) | |
| download | vyos-1x-c031fd07a098b958cbcac681e3431e33a435da3c.tar.gz vyos-1x-c031fd07a098b958cbcac681e3431e33a435da3c.zip | |
nhrp: T9128: fix duplicate nftables meter name for multiple redirect tunnels
Committing a second NHRP tunnel with "redirect" enabled failed with
"Failed to apply NHRP tunnel firewall rules". The redirect chain in
nhrpd_nftables.conf.j2 is rendered in a per-tunnel loop but hardcoded the
nftables meter name "loglimit-0". With two redirect-enabled tunnels the
loop declared the named set "loglimit-0" twice in table vyos_nhrp_redirect,
which nft rejects, aborting the atomic ruleset load so the commit failed.
Derive the meter name from the loop index (loglimit-0, loglimit-1, ...) so
every redirect-enabled tunnel gets a unique meter. The first tunnel keeps
the name "loglimit-0", leaving single-tunnel setups unchanged.
Add a smoketest that configures two tunnels with redirect + multicast and
verifies the commit succeeds and both meters are present. Also clear the
"vpn ipsec" tree in tearDown so the IPsec profile created by the existing
test does not leak into the new one.
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions
