Replies: 1 comment 7 replies
-
Netmaker sets up peer to peer networks, disregarding gateways for the moment. Once the peers have recieved their configuration the server is not involved in peer to peer communications, so there is no way for the server to block comms. If as you said, someone modified their allowed ips to add a node it would work temporarily. Netmaker sends updates to the peers periodically, so the change made to get around the acl would have to be reapplied everytime the server sends a periodic peer update |
Beta Was this translation helpful? Give feedback.
7 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I am interested in netmaker because auf the ACLs (Access Control Lists).
At the moment I am not sure if the communication permissions are configured client-side or serverside so it would be great if someone give some clarification.
I have this question because in the normal wireguard confs there is a "Allowed IPs" entry which can be changed client side. (my setup is not using netmaker yet).
So does netmaker only change this "allowed ips" settings for every client and the netmaker client pull these settings?
This would be bad because then someone could manually change the setting client-side and still reach devices which were denied in the netmaker UI.
I hope my explanation was understandable. :)
Just wanted to be sure that netmaker restricts connections serverside independet of configurations on the client side.
Beta Was this translation helpful? Give feedback.
All reactions