This repository has been archived by the owner on Jun 21, 2018. It is now read-only.
Add network namespaces for users #103
Open
Conversation
This file contains 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
Todo: - add DHCP and NAT setup for IPv4 - add pam_network_namespace to actually make the user enter the namespace
RD/RA should take care of it
- Avoid non-POSIX keywords (function, source) - Use proper quoting - Do not return strings - Avoid [ X -a Y ], as it isn't well-defined
|
@lrvick Rebased this on the IPv6 branch, so that we can see more easily how it fits with the example config. |
|
Drive by observation: if outgoing connections are bound to a user's IP (or range? I don't know much about IPv6), the IRC network operators will no longer care about |
Users still NAT to the ipv4 internet via the server's main ip. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Do not merge, there are some important parts missing:
resolv.conf, as Unbound doesn't listen on 127.0.0.1 in the user's netns;Moreover, this probably breaks our current
identdsetup.