fix: WireGuard handshake (51820, keepalive, IPv6 off) - #25
Open
dfosterj wants to merge 4 commits into
Open
Conversation
NM activates proton0 with no handshake when the peer is :443. Prefer 51820 when the server list includes it. Co-authored-by: Cursor <cursoragent@cursor.com>
Match exported Proton nmcli profiles so NAT mappings stay open. Co-authored-by: Cursor <cursoragent@cursor.com>
IPv6 DNS 2a07:b944::2:1 is routed via the kill-switch dummy. Match working exported profiles that leave IPv6 off. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
5 tasks
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
1 participant
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
udp[0]is 443; NetworkManager marksproton0activated with no handshake, Local Agent times out, and the GTK app cycles.2a07:b944::2:1follows the kill-switch dummy default and blackholes Local Agent.Verified on Arch / Proton VPN Flatpak 4.18.1 (
python-proton-vpn-api-core5.6.10):can(…:51820, IPv6 off, keepalive 25) pings10.2.0.1.…:443+ IPv6) is 100% loss to10.2.0.1while NM shows activated.This belongs here, not in
proton-vpn-gtk-app(UI only) or Flathub packaging.Test plan
nmcli connection show "ProtonVPN …"shows endpoint:51820,ipv6.method: disabled, keepalive 25ping -c 2 -W 2 10.2.0.1replies while Connectedudp[0]Made with Cursor