Repository navigation
docs: LAN hosts behind a downstream NDP relay share the delegated /64 - #180
Merged
Merged
Conversation
…ted /64 (odhcpd relay, pinholes by interface identifier, relay MAC for MAC-based features, RA guard)
…ion; odhcpd relay on both interfaces; RA MTU note (review)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Docs only (net.md + one comment in fw.md): how hosts behind a downstream router/hypervisor segment get public IPv6 from the single delegated /64 with a standard NDP/RA relay (odhcpd relay mode) on the LAN, and what the router does and does not need.
Why
Real deployment: AIS gives one /64; PVE guests behind RouterOS need public IPv6 with inbound pinholes, no NAT66. Checking mini-router showed no code change is needed: the /64 is on-link on br-lan,
firewall.ipv6_allowmatches by interface identifier (independent of the relay's MAC and of prefix changes). The caveats worth documenting: all relayed traffic carries the relay's MAC (MAC-based features see one device), anat6policy on a non-PD line would NPT the relayed hosts, and RA guard is needed on the downstream bridge when other routers there accept RAs.Verification
Docs only; checked against mod_fw_nft.go (v6in pinholes), the nat6 policy rules and the live router ruleset.