Skip to content

v055u: Intermittent Original IPv6 IP Leaks in NextDNS Logs with WireGuard - Always-On/Lockdown, and System DNS on Android 16  #2411

@L-3-m-o-n

Description

@L-3-m-o-n

This is a summary of all the errors (other than already mentioned issues) I encountered while using Rethink on latest version and a fix for these is much appreciated .

Description:
Device/OS: OnePlus device running Oxygen OS 16 (first stable build, based on Android 16). Non-rooted. Using mobile data only (ISP forces IPv4+IPv6; forcing IPv4-only APN breaks internet entirely). No WiFi testing possible.

Setup Overview:

Using Rethink as always-on VPN with lockdown mode enabled in Rethink settings and in Android Settings > VPN > Block connections without VPN + Always ON are enabled .
Proxy: WireGuard configs from Proton VPN :
Tested in both cases :
i> Original .conf files [Only supporting ipv4 , rethink set to ipv4 only]
ii> As per https://gist.github.com/mikaeldui/12127c91ccece42ea375c9f42d94aa8a
Enabled IPv6 manually but default settings did not work for me , So used fd54:20a4:d33b:b10c:0:2:0:2 as per one of the comments + Rethink set to ipv4+ipv6 mode .
(IPv4+IPv6 dual-stack in this case; AllowedIPs in both cases= 0.0.0.0/0, ::/0 confirmed optimal)
In wireguard : Tried changing dns to next dns + also tested with default and as as well as per https://gist.github.com/mikaeldui/12127c91ccece42ea375c9f42d94aa8a
So , All cases were tested and with same issue .

Tested with both single proxy ON or with Multiple endpoints : Mainly NL,NO,JP free servers but IP leak tests (ipleak.net, dnsleaktest.com) always show system DNS (NextDNS) as provider, which is desired even though when testing ipv4+ipv6 , Dns was set to Proton in wireguard .conf files .
Rethink's DNS: Forwarded to System DNS (NextDNS). Type: System DNS. Fallback DNS: Off (but set to System DNS despite being off; previously on, but Rethink fell back often which it still does but DNS tests still showed NextDNS (desired) ).
Advanced DNS Settings (all on, per update; IPv6 works with them enabled but rarely fails (Still an issue) ):
Never Proxy DNS: On - previously off to avoid limiting to IPv4 [occasionally causes IPv6 proxy failures (e.g., connections drop to IPv4-only), so please investigate/fix.], Also same result when Off .
Prevent DNS Leaks: On (Same as never proxy dns) , Also same result when off .
Use Fallback DNS as Bypass: On (Also same) , Same result when Off .
All Other settings in DNS section : (except blocklists) : ON .

Firewall Settings (Universal):
Block When Source App is Unknown: On , Rest : Off .
Block UDP Except DNS and NTP: Temporarily enabled for testing, but leaks persisted so disabled.
Block When DNS is Bypassed: Off (enabling blocks all internet; always been the case, even when proxies were IPv4-only) - Hoping for a fix here ...
Block Port 80 (Insecure HTTP Traffic): Temporarily enabled for testing, but leaks persisted so disabled.

Network Settings :
Enable Network Visibility: Off.
Stall on Network Loss: On.
Do Not Route Private IPs (Experimental): Off .
Use All Available Networks (Experimental): On.
Always Metered: Off.
Meter Mobile Networks: Off.
Loopback (Experimental): On.
Choose Fallback DNS: Set to System DNS (but fallback off overall).
Connection Change Policy: Auto.
Proxy > Loopback Proxy for Forwarder Apps: Off.
Do Not Randomize WireGuard Listen Port: On [Turning ON - Breaks internet for me - Hoping for a fix here]
TCP/IP: Shorter TCP Keep Alive: On. Endpoint-Independent Mapping: Off. Idle Timeout: 20m. Bandwidth Booster: Off. Choose IP Version: IPv4 & IPv6 , Tested with ipv4 only too on ipv4 proxies (same result) .

Issue Details:

Original IPv6 (non-WireGuard) leaks in NextDNS logs once every 15-40 mins at random, despite no DNS leak (tests show NextDNS as provider). Leaks mostly on telemetry domains , google domains (90% blocked by NextDNS blocklists): gstatic.com, improving.duckduckgo.com, favicons for NextDNS, Rethink's telemetry, youtubei.googleapis.com, other Google domains (even non telemetry essentials such as youtube or www.google.com) , Rarely on app calls (e.g., Instagram Google APIs, YouTube when not blocked).
Persists across setups: Previously IPv4-only WireGuard (Rethink set to IPv4 only; same leaks. Now dual-stack IPv4+IPv6 still leaks .

Partial Workaround: Use IPv6-only WireGuard for apps like YouTube (closes some leak surface - now in this case YouTube domains show only wireguard's ipv6), but Instagram/etc. fail without IPv4 (app and other limitations) , Only workaround is forcing ipv6 proxies wherever possible .

Proxy Inconsistencies: Endpoints sometimes fail or drop speed after heavy usage (despite Proton's no-limits claim).
No IPv4 leaks - only IPv6. Happens on mobile data; can't disable IPv6 systemwide for already mentioned reasons .

Steps to Reproduce:

Set up as above.
Use apps like YouTube/Instagram for 15-40 mins.
Check NextDNS logs (my.nextdns.io) for original IPv6 on telemetry domains.
Run IP/DNS leak tests - DNS shows NextDNS, but IP leaks in logs sometimes especially on ipv4 only proxies or when ipv6 isn't forced .

Expected: No original IP exposures with always-on/lockdown. Actual: Intermittent IPv6 leaks on specific domains/calls.

IMG_20251120_191229.jpg

Additional details :
1)Many times though using system dns (NextDNS) , It many times uses fallback (also set to system) despite it is turned off in settings .
2)Concerns over IP , Since this has shown that Rethink's always on + lockdown mode could still leak . While switching between proxies , Please make sure this does not leaks IP .

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions