Skip to content

feat: disconnect other VPNs, IPv4-only exit by default, no Blizzard probe - #5

Merged
Freecode100Year merged 4 commits into
mainfrom
feat/ipv4-exit
Oct 10, 2026
Merged

Freecode100Year merged 4 commits into
mainfrom
feat/ipv4-exit

Conversation

@Freecode100Year

Copy link
Copy Markdown
Owner

See commit message.

🤖 Generated with Claude Code

Freecode100Year and others added 4 commits October 9, 2026 22:18
…robe

- On start, disconnect the official WARP client (warp-cli), Windows'
  built-in VPN connections (rasdial) and WireGuard tunnel services.
  Anything else still holding a default route stops the program.
- -exit ipv4|ipv6|dual replaces -v6only; ipv4 is the default. IPv6 is
  routed into the tunnel and refused at once (TCP RST / ICMPv6
  unreachable); the tunnel gets no IPv6 default route or resolver so
  Windows hands out IPv4 addresses only.
- The diagnosis no longer probes Blizzard or compares WARP against it;
  it measures router and ISP, and recognises phone hotspots.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…out AAAA

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Freecode100Year
Freecode100Year merged commit 8e57032 into main Oct 10, 2026
1 check passed
@Freecode100Year
Freecode100Year deleted the feat/ipv4-exit branch October 10, 2026 02:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant