chore: bump wireguard_lwip submodule to v1.0.1 - #46
Merged
Conversation
Picks up the TAI64N wall-clock handshake-timestamp fix (fugo101/wireguard-lwip#13, released as v1.0.1) for local/submodule builds. Registry-based builds already resolve it automatically via idf_component.yml's existing "^1.0.0" pin — no change needed there. Refs fugo101/wireguard-lwip#13 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
fudio101
added a commit
that referenced
this pull request
Aug 19, 2026
…t needed (#59) * docs(fork-prs): #34/#42 landed in wireguard_lwip submodule PR, #31 not needed Batched the wireguard_lwip-submodule candidates that had piled up across sessions 5-9 (#31, #34, #35's remaining piece, #42). - #34 (handshake retry throttle) and #42 (DERP-routing-flag preservation) are both small, independent, and entirely within wireguardif.c/.h -- adapted and opened as fugo101/wireguard-lwip#15. Rows stay open until that PR merges, a new submodule version releases, and the pointer here gets bumped (same two-step flow as issue #43's TAI64N fix / PR #46). - #31 (LOCK_TCPIP_CORE around netif_set_link_up/down) investigated and found not needed: LOCK_TCPIP_CORE()/UNLOCK_TCPIP_CORE() expand to nothing when LWIP_TCPIP_CORE_LOCKING is disabled (this fork's default), so it's a no-op here. Its ip_input()->tcpip_input() change duplicates what this fork already does independently (issue #30). The rest of the commit disables WireGuard's cryptokey-routing source-IP validation entirely plus scattered debug printf's -- a security-relevant scope change, not something to fold in silently. No port planned. #35's remaining submodule piece (backpressure/TCP_NODELAY/hot-spin fixes in wireguardif.c) not triaged this pass -- left for a future session. Co-authored-by: Adrian.Nguyen-Qualgo <nguyen.ndt@qualgo.net> Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com> * docs(fork-prs): fugo101/wireguard-lwip#15 merged, release-please PR open Update rows 15/#34 and 22/#42: the submodule PR merged shortly after this branch was opened. release-please auto-opened its usual release PR (fugo101/wireguard-lwip#16, "release 1.0.2") -- merging that is the next step, then a follow-up PR here bumps the submodule pointer. Co-authored-by: Adrian.Nguyen-Qualgo <nguyen.ndt@qualgo.net> Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com> --------- Co-authored-by: Adrian.Nguyen-Qualgo <nguyen.ndt@qualgo.net> Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
4 tasks
fudio101
added a commit
that referenced
this pull request
Aug 19, 2026
Bumps the components/wireguard_lwip git submodule pointer to the v1.0.2 release commit, which carries the handshake-retry-throttle and DERP-routing-flag fixes from fugo101/wireguard-lwip#15 (issues #34 and #42 here). No change to components/microlink/idf_component.yml -- its existing fugo101/wireguard_lwip: version: "^1.0.0" pin already covers 1.0.2 (verified live on the ESP Component Registry after the publish-component CI job ran: https://components.espressif.com/components/fugo101/wireguard_lwip/versions/1.0.2); only the local/submodule dev path needed this bump. Same reasoning as PR #46's 1.0.1 bump. Closes #34 Closes #42 Co-authored-by: Adrian.Nguyen-Qualgo <nguyen.ndt@qualgo.net> Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
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
2 participants
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
Bumps the
components/wireguard_lwipgit submodule pointer to thev1.0.1release commit, whichcarries the TAI64N wall-clock handshake-timestamp fix from
fugo101/wireguard-lwip#13.Follow-up to #44 — that PR absorbed the rest of the
bugfix/hardening subset of upstream
CamM2325/microlink#22, but the TAI64N fix lives in thissubmodule (a separate repo), so it couldn't land in the same PR. It needed its own PR there, merged,
then released (registry publish gated on release-please) before this pointer bump made sense.
No change to
components/microlink/idf_component.yml— its existingfugo101/wireguard_lwip: version: "^1.0.0"pin already covers1.0.1(registry-based builds pick this up automatically);only the local/submodule dev path needed this bump.
Related
Refs #43 (
FORK_PRS.mddj-oyu bundle — TAI64N item now fully superseded, both by source and by this landing)Refs
fugo101/wireguard-lwip#13Test plan
git submodule update --init --recursive && idf.py fullclean && idf.py buildforexamples/basic_connect(not runnable in this sandbox — please build before merging)idf_component.yml's^1.0.0pin already satisfies1.0.1, no edit needed🤖 Generated with Claude Code