Implement an option to specify VPNProtocols

[AiyionPrime]

This gets rid of fastd for those who don't want it anymore, while letting it be as the default for any current users.

'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 #66

[AiyionPrime]

@herbetom, does this suit you as well?

[AiyionPrime]

Tested on one of our supernodes as well; works as intended, if no option, a valid or an invalid one is given.

[herbetom]

Looks okay, i'm testing it later :+1:

[AiyionPrime]

Thanks

[AiyionPrime]

btw, what protocol are you using instead of fastd?

[herbetom]

btw, what protocol are you using instead of fastd?

see here: https://github.com/ffnord/mesh-announce/issues/66#issuecomment-779409783

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:

• no config set
• VPNProtocol: fastd (as the Default Setting)
• VPNProtocol: None (as the Default Setting)

[AiyionPrime]

Well this is worse than before; the list produces TypeError: unhashable type: 'list'

[AiyionPrime]

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

[herbetom]

I think the 3 commits should be squashed. They currently contradict each other. That makes applying them a pain.

[AiyionPrime]

@herbetom yeah, good idea. Thoug I think I'll leave them unsquashed until one of Kiels members acked the proposed changes and make less commits of it right before the merge.