Add optional client isolation feature for blocking traffic between devices #134
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
…vices Until now there was absolutely no firewall between all online devices. While this is not problem (and often even wanted behaviour) for single-user setups, it can be useful for multi-user situations.
DasSkelett
added
enhancement
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.
Motivation
Until now there was absolutely no firewall between all online devices.
While this is not problem (and often even wanted behaviour) for single-user setups,
it can be useful for multi-user situations.
Changes
A new option
WG_VPN_CLIENT_ISOLATION/--vpn-client-isolation/vpn.clientIsolationis added.It defaults to false, and if set to true it will
REJECT(port unreachable) all packets coming from one client device IP address to another.We do not need to explicitly allow traffic to the server, as that one goes through the
INPUTtable, notFORWARD.Note that this does not affect incoming traffic from outside the VPN. This one can and should still be configured externally, wg-access-server does not drop incoming traffic (yet).