-
-
Notifications
You must be signed in to change notification settings - Fork 307
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
Please explain AllowedIPs #87
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How does
AllowedIPs
behave on clients and what are the side effects?It's not very clear whether the client's behavior overrides the server's behavior in terms of allowing or refusing access to the network/subnet, and or IP address(es) specified in that field.
My understanding is that, even if you assign an IP, say of, 10.0.1.x/32, to a client Peer, it can specify its own IP with a different subnet, allowing it to receive other peers packets.
Is this the case? If so, how can one configure wireguard to only allow peers access the servers internet (pass-through) but without the peers having access to, or knowledge of other peers?
The text was updated successfully, but these errors were encountered: