-
Notifications
You must be signed in to change notification settings - Fork 45
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
Implement an option to specify VPNProtocols #70
Conversation
@herbetom, does this suit you as well? |
Tested on one of our supernodes as well; |
Looks okay, i'm testing it later 👍 |
Thanks |
btw, what protocol are you using instead of fastd? |
see here: #66 (comment) I only checked if #66 is solved with it. It seems that way. What i couldn't easily test is the actual output. What i tested:
|
Well this is worse than before; the list produces |
And ready again. It's getting quite a massacre by now, but @freifunkh runs mesh-announce upstream/master with #63, #64, #69, #70 as well as #71 merged concurrently without problems. example: https://hannover.freifunk.net/karte/#/en/map/88e640ba7014 |
I think the 3 commits should be squashed. They currently contradict each other. That makes applying them a pain. |
@herbetom yeah, good idea. |
'fastd' is the only valid option, for now, anything else results in fastd hidden under software and not called for its version, therefore this resolves ffnord#66
5a9adf8
to
8e13ffe
Compare
8e13ffe
to
2543479
Compare
This gets rid of fastd for those who don't want it anymore, while letting it be as the default for any current users.