-
Notifications
You must be signed in to change notification settings - Fork 104
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
Relay servers #31
Comments
I didn't add anything like this. This program, as its description suggests, generates configs for a The easier approach at that point would be to build some kind of a UI and you can drag a line between nodes to create a connection or remove a line to break that direct connection, but that's going to take a lot longer to write. |
I understand that The proposed logic is:
|
I wrote this on the PR, but I think that this sort of config is still useful. Without manual editing, NAT -> NAT routing will not be optimized, but it will work so long as you set allowedIPs on one connectable client to include the wg IPs of all NAT devices. For many people, this is likely fine. |
Here is an example config: example.zip
It has two nodes with public IPs, called
alpha
andbeta
, and two nodes without public IPs and behind NATs, calledgamma
anddelta
. In this configuration, the mesh works well, except for the connection betweengamma
anddelta
. (Note thatgamma
can talk toalpha
andbeta
and vice versa without issues. The same withdelta
.)I can tweak the generated config manually to get everything to work. The required changes are:
AllowedIPs
line under thedelta
peer in thegamma
config fileAllowedIPs
line under thegamma
peer in thedelta
config fileThis tells wireguard that gamma can't reach delta directly, so it uses
alpha
orbeta
as a relay server, which is exactly what I want.Can this be done in wg-meshconf without post-processing the generated config files?
The text was updated successfully, but these errors were encountered: