IPv6 support?

[djdarcy]

Discussed in #8

^{Originally posted by zbugrkx June 17, 2026}
Hi,

I just found this tool after tons of google searching for a solution to my particular issue and wondering if this could help?

NCSI does not want to consider a nat66 ipv6 address as "internet" despite it working just fine and will set the netconncetionprofile for ipv6 to localnetwork . This causes everything to prefer ipv4

Does this tool also changes the values etc for ipv6 or is it ipv4 only?

Thanks!

[djdarcy]

@zbugrkx

update: I built an experimental IPv6 path on a branch for you to test. If you have a chance I'd appreciate your help testing it since you have an actual NAT66 setup with the "no internet, secured" issue which I can't as easily repro on my own.

Important: this is experimental and reversible (one --uninstall should undo everything; it writes a registry .reg backup before touching anything). It's also self-gating. If your machine has no global IPv6 address, it refuses and changes nothing, because that case is router-side and not something this tool can fix.

The first thing the new experimental functionality does is tell us which case you're in. Could you grab the branch and run just Step 1 (no admin needed)?

git clone -b feature-ipv6 https://github.com/DazzleTools/Windows-No-Internet-Secured-BUGFIX.git

cd Windows-No-Internet-Secured-BUGFIX

python installer.py --diagnose-ipv6

and, in an admin PowerShell:

Get-NetConnectionProfile | Format-List Name, IPv4Connectivity, IPv6Connectivity, NetworkCategory

Paste both outputs here. The result tells us:

1. NoGlobalAddress (only a ULA fd.. address) -- meaning the redirect can't help; the fix is router-side (a global IPv6 prefix / NPTv6). We'd stop there, but at least you'll know it requires a change in your router to properly address.

2. ProbeBlocked (you have a global address but Windows still says no IPv6 internet) -- that's the case this new software aims to address/fix with the redirect, and then we'd continue to the apply / measure / undo steps.

If you're in the ProbeBlocked (scenario 2) case and are willing to go further, the full step-by-step (install dual-stack service -> apply redirect -> check if Windows flips IPv6 to "Internet" -> confirm it holds -> uninstall) is in the repo here: tests/checklists/v0.7.14__Phase2__ipv6-redirect-reporter-protocol.md. Every step is reversible.

No pressure, no rush; even just sharing the Step 1 output should tell us something useful.

Hope this helps!