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
nixos/nat: support IPv6 NAT #104836
nixos/nat: support IPv6 NAT #104836
Conversation
(I guess I should ping @edolstra @valeriangalliat @volth @ryantrinkle) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other than the one comment, this looks good to me!
Done! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, now I think squashing the commits is the only thing needed.
Feel free to squash on merge. |
I'd appreciate for PR authors to squash the commits themselves because:
While this may not all apply to this specific PR, I think it's still valuable to be comfortable with |
Noted, and done! EDIT: actually, I'm not sure what you mean by "it maintains the original SHA1". Squashing more than one commit together creates a new commit with a new SHA1. |
It does create a new commit on master, but the PR still shows the original git hashes. So if you wanted to cherry-pick a PR by copying a git hash from the PR's commits, that wouldn't work when it was squashed. |
Ah, I see, thanks. |
Motivation for this change
This is a revival of half of #6208, because I need to use NAT with IPv6 (yes, there are edge cases).
I tested the module manually on my server (including
forwardPorts
andloopbackIPs
, both v4 and v6), everything seems to work fine.I didn't add an IPv6 version of
dmzHost
, but it would be trivial to add if needed.Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)