networking: add support for WireGuard VPN #882
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ℹ️ This PR is based on other branches that are needed, and not merged in master yet - so it appears huge. In particular it's based on my experimental-esp-idf-build-workflow branch. However, only the last commit
networking: add support for WireGuard VPN
is the important part of this PR.This VPN allows your OVMS module to "connect" itself to your own private network, make it visible and reachable, whatever the connexion it is using (WiFi, Mobile, ...)
(Note: 3G untested at the moment)
It should also (unverified) be able to roam from one connexion to the other, or even among different WiFi networks, without any specific setting to do.
A documentation has been added. (Note: The schematics, drawn with draw.io is embedded in the resulting PNG file, so you can open the PNG file with the editor to edit the diagram. Please keep it that way (by checking the 'Include a copy of my diagram' check box))
Support for wireguard on ESP provided by https://github.com/trombik/esp_wireguard, cf https://github.com/trombik/esp_wireguard/blob/main/LICENSE
Cf #752