Repository navigation
feat: add optional WireGuard client for repeater MQTT - #18
Open
Misheldeep wants to merge 2 commits into
Open
Misheldeep wants to merge 2 commits into
Misheldeep wants to merge 2 commits into
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Adds an optional WireGuard client for ESP32 repeater MQTT builds.
The feature is disabled by default and enabled with a dedicated
heltec_v4_repeater_mqtt_wireguardPlatformIO environment. WireGuard settings are stored in NVS and managed through the existing CLI.What it adds
get wg.statuswith peer/session/RX/TX age diagnosticsWireGuard-ESP32-Arduino0.1.5 with its BSD-3-Clause license retainedCLI
The peer public key, endpoint and tunnel address are intentionally not hard-coded.
Routing behavior
The WireGuard interface receives only its configured tunnel subnet. After interface creation, the Wi-Fi STA interface is restored as the lwIP default route, so MQTT/NTP/general Internet traffic continues to use the existing Wi-Fi uplink.
WireGuard failure therefore does not make the repeater depend on the tunnel for normal operation.
Validation
Built successfully on the current
mainbase:heltec_v4_repeater_mqttheltec_v4_repeater_mqtt_wireguardThe implementation has also been exercised on a Heltec V4.3 repeater with remote web/CLI access through WireGuard while MQTT remained on the normal Internet path.
This PR deliberately does not include the separate experimental web-server socket-count change.