wgautomesh vs innernet #6

Closed
opened 2023-06-07 10:23:06 +00:00 by hernad · 1 comment

Hello, have you look at innernet project?
It seems to me that innernet covers peering like wgautomesh, plus access control between peers.

Hello, have you look at [innernet](https://github.com/tonarino/innernet) project? It seems to me that innernet covers peering like wgautomesh, plus access control between peers.
Owner

Thanks for your comment! Innernet and wgautomesh are two different tools for different scenarios. We have built wgautomesh as the most minimal tool that would allow us to do what we wanted. Here are some of the most important differences between the two:

  • Innernet uses a coordination server, which is a single point of failure in such a deployment. The reason we built wgautomesh is specifically to avoid the need for such a coordination server, as we are trying to build a horizontal architecture where all nodes are equivalent. In the case of our Wireguard meshing protocol, all nodes are able to help other nodes to establish connections.

  • We have not addressed access control in wgautomesh, as the list of authorized peers is distributed statically in the wgautomesh configuration file (it might be possible to restrict access between nodes by having different config files at each node, but in all cases handling this is explicitly outside the scope of wgautomesh).

Thanks for your comment! Innernet and wgautomesh are two different tools for different scenarios. We have built wgautomesh as the most minimal tool that would allow us to do what we wanted. Here are some of the most important differences between the two: - Innernet uses a coordination server, which is a single point of failure in such a deployment. The reason we built wgautomesh is specifically to avoid the need for such a coordination server, as we are trying to build a horizontal architecture where all nodes are equivalent. In the case of our Wireguard meshing protocol, all nodes are able to help other nodes to establish connections. - We have not addressed access control in wgautomesh, as the list of authorized peers is distributed statically in the wgautomesh configuration file (it might be possible to restrict access between nodes by having different config files at each node, but in all cases handling this is explicitly outside the scope of wgautomesh).
lx closed this issue 2023-06-07 10:49:54 +00:00
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Deuxfleurs/wgautomesh#6
No description provided.