Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NPTv6 does not work with Track Interface #8371

Open
2 tasks done
STRUBartacus opened this issue Feb 22, 2025 · 1 comment
Open
2 tasks done

NPTv6 does not work with Track Interface #8371

STRUBartacus opened this issue Feb 22, 2025 · 1 comment

Comments

@STRUBartacus
Copy link

Important notices

Before you add a new report, we ask you kindly to acknowledge the following:

Describe the bug

If NPTv6 is configured with a ULA prefix that is statically configured on a LAN interface with a GUA prefix via the “Track Interface” function, no translation takes place. If the same GUA prefix is configured manually, a correct translation takes place.

To Reproduce

  • Firewall - NAT - NPTv6
  • Change Track Interface from LAN to None
  • Manually enter the LAN GUA prefix under “External IPv6 Prefix (target)”
  • Save

Expected behavior

NPTv6 works correctly with the “Track Interface” function, so that the translation is automatically adjusted when the prefix is changed.

Environment

Software version used and hardware type if relevant, e.g.:

OPNsense 25.1.1-amd64
FreeBSD 14.2-RELEASE-p1
OpenSSL 3.0.16
Supermicro A2SDi-4C-HLN4F
Intel Atom Processor C3558

@funtowne
Copy link

Are you using the LAN as your NPTv6 translation target or WAN? I’ve used WAN without issue on a similar setup, for example.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants