-
Notifications
You must be signed in to change notification settings - Fork 24
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
Looking for some docs #8
Comments
Hi @tjjh89017, I am currently working on a new version (though it's just a hobby and I do not know when it's production ready, yet). I'm not sure what you mean by design. The software roughly works like this:
|
So wg-p2p will act as a proxy between the wg port and really port? If you are busy, plz ignore my questions. |
Exactly, I could not find a design where this forwarding is not required. Though I might replace it with a eBPF program one day ;) |
I'm not sure |
Not sure how this should help. I use STUN for that. |
Use hole punch, we can connect wireguard without proxy |
@manuels I want to implement a similar approach using BPF or eBPF (new C++ or Golang project)
and i don't think "pubkey exchange" will be necessary. (if i'm wrong, please correct me) [1] https://github.com/WireGuard/WireGuard/tree/master/contrib/examples/nat-hole-punching |
Hi, I'm also interested in Docs. A simple readme with an example configuration would be enough. Just hard to use without any info. |
Hi,
I'm very interested in this project.
But I found less docs about the design.
Could you tell us more about this? (master branch)
Thanks a lot
The text was updated successfully, but these errors were encountered: