-
Notifications
You must be signed in to change notification settings - Fork 41
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
[TASK] add WireGuard #198
[TASK] add WireGuard #198
Conversation
Originally posted by @genofire in #187 (comment) |
We spoke about this yesterday in hackint#ffhb: |
Update: |
This PR is currently not explicitly reflecting gluon-mesh-vpn-wireguards statistics-provider. It basically wraps {
"peers": {
"sn03": false,
"sn02": false,
"sn01": false,
"sn10": false,
"sn04": false,
"sn09": false,
"sn06": false,
"sn07": false,
"sn08": false,
"sn05": {
"established": 2635
}
}
} Which in turn is put below Line 51 in 4a9089b
As the wireguard-statistics-struct mimics the fastd-response, this should be fine. |
@lemoer and I just agreed, this looks about right. |
@genofire Please let me know when you find time to look over this; preferably before Wednesday noon, then I'll be gone for a week. |
On first look, there is missing |
open issue for it #206 - @AiyionPrime maybe you could make an PR for this too |
Description
This implements basic support for WireGuard in accordance of the fastd-related paragraphs in code.
Motivation and Context
We, @freifunkh are currently building up our WireGuard infrastructure;
and giving back something to yanic after using it for years seemed appropriate.
Furthermore this resolves #183 and could bring new momentum to the discussion of #66.
Checklist:
I do not think fastd is documented either; so I'm unsure whether this is matter to document, or not.
replaces #187 in order to use correct branches