-
Notifications
You must be signed in to change notification settings - Fork 105
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
#31 Relay servers #32
base: master
Are you sure you want to change the base?
Conversation
I think that the entire peer should be removed rather than just the routes. You also probably want to make this change so that the I've been making my own fork over here for personal use: https://github.com/mwt/wg-meshconf/ It contains a modified version of @rudolfbyker's code which hides the entire peer when a direct connection is not possible. It is worth noting that this config is only useful if you want all NATed peers to route through the same "lighthouse". If you want peers to route through their nearest lighthouse (e.g. peers in Singapore connect to each other through Singapore and peers in Germany connect to each other through Germany) then you need to have asymmetric AllowedIPs values. This setup does not work for that. Though, I think this is still useful. Edit: To clarify, this will not maximize the speed of NAT -> NAT connections, but it will "just work" and I think it's a useful feature. |
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.
You should remove , "Endpoint"
in line 101
Why? Sorry, it's been a long time since I made these changes, so the code is not fresh in my memory. |
That part checks to make sure that endpoint is not Because this PR makes |
f579c2c
to
cd5b1d3
Compare
I rebased my branch on the latest master! Please review :) |
… them to connect indirectly.
cd5b1d3
to
5a9f1c1
Compare
@mwt wrote:
Quite right, and I only realized this now. For anyone wondering why, see the docs at https://github.com/pirate/wireguard-docs#how-public-relay-servers-work . I updated the PR. |
In addition, we can mark one peer as relay (flag in config) and add subnets that are not directly accessible to it |
Good idea for the next PR after we get this merged! :) |
What prevents this from being merged? It's a valuable feature, and works properly. |
For your consideration :)
Closes #31