Insights
No IPv6 connection: check service, addresses and routes
Check IPv6 service, Windows adapter addresses and routes without changing settings, then narrow the issue to your provider, router or device.
On this page
No IPv6 (Internet Protocol version 6) connection doesn't always mean your internet is broken. Your service or router may not provide IPv6, while IPv4 (Internet Protocol version 4) still works.
In short:
- IPv4 can still work. Missing IPv6 may reflect your service or router's limits.
- Check addresses and routes. Inspect your active adapter before changing settings.
- Don't disable IPv6. Locate the affected network layer first.
Check whether your network offers IPv6
Start by checking whether your provider, plan and router support IPv6Opens in a new tab. Also check whether you can still reach sites over IPv4. If IPv6 isn't supplied and IPv4 works, the missing IPv6 connection isn't by itself a device fault.
A browser test at test-ipv6.com can show the path used for that test at that time. It won't identify the cause of a failure or show that the problem is permanent. One failing app doesn't prove an IPv6 fault, and working IPv4 doesn't rule out an IPv6-related app problem.
If your service should provide IPv6, collect your device's addresses and routes next. Treat Windows' IPv6 connectivity label as an observation, not a diagnosis.
Find the address on your active Windows adapter
This documentation-based Windows inspection uses Microsoft's ipconfig commandOpens in a new tab to view adapter addresses and gateways. Inspect only a device you own or administer. These commands don't change settings, so no rollback is needed.
1. Open Windows Command Prompt and run ipconfig.
ipconfig
Find the connected Wi-Fi or Ethernet adapter you're using. Skip disconnected adapters and unrelated virtual interfaces. Record the adapter name, IPv4 address, IPv6 or Link-local IPv6 Address entries, and Default Gateway.
You should see the adapter's configured addresses and gateway entries, where present. That shows what Windows has configured, not whether the internet is reachable. If an entry is missing, record that result instead of assuming it exists.
2. Get the full adapter configuration if you need more detail.
ipconfig /all
From the same adapter, record the Domain Name System (DNS) servers. DNS turns names into addresses. The full output includes physical and logical adapters, so keep your interface selection consistent.
3. Check which type of IPv6 address you found.
An address starting with fe80: is link-localOpens in a new tab. It supports communication on the local link, not proof of public IPv6 access.
An address starting with FC or FD is a unique local address, which may work inside a home or company network. Neither address type proves public IPv6 access. Don't assume every other IPv6 address is publicly usable.
Check where Windows sends IPv6 traffic
Microsoft's Get-NetRoute commandOpens in a new tab reads the routing table, which holds Windows' choices for where traffic goes. Run these documentation-based, read-only checks only on a Windows device you own or administer. They don't change settings, so no rollback is needed.
1. Open Windows PowerShell and list IPv6 routes.
Get-NetRoute -AddressFamily IPv6
When routes exist, expect entries with destination prefixes, next-hop addresses and route metrics. Match InterfaceAlias or InterfaceIndex to the adapter you're inspecting. If the displayed output doesn't show enough detail, use the next command.
2. Show all route properties if needed.
Get-NetRoute -AddressFamily IPv6 | Format-List -Property *
Read these fields:
DestinationPrefixis the destination address range covered by the route.NextHopis the next router address, or::when the destination is on the local subnet.RouteMetricis a cost used in route selection.InterfaceAliasandInterfaceIndexidentify the interface used by the route.
3. Look for a default route and any more specific routes.
::/0 is the IPv6 default route, used when no more specific route matches. Check specific routes too, especially when tunnel or virtual interfaces are present. If the default route is absent, record it. More specific routes may still allow access to some IPv6 destinations.
A default gateway starting with fe80: can be normal because the next router is on the same local link. That's different from your device having only a link-local address. A route entry shows a configured forwarding choice, not proof that its gateway or the internet is reachable.
Work out whether the problem is upstream or on your device
Use your results to choose the next layer, following OPNsense's router-first troubleshooting approachOpens in a new tab.
| Collected result | What it suggests | Next investigation |
|---|---|---|
| IPv4 works, IPv6 isn't supplied | Expected IPv4-only access | Confirm account and equipment support |
| Router's upstream IPv6 check fails | Possible provider or router issue | Check upstream service and router configuration |
| Router IPv6 works, clients lack addresses or routes | Possible client configuration or delivery issue | Check how the router supplies IPv6 to clients |
| One device fails, an authorized peer works | Device setup or policy may differ | Compare active interfaces, addresses and routes |
On OPNsense, use its documented router diagnostics to check upstream IPv6 connectivity and the default route before troubleshooting clients. If the upstream path fails, investigate the provider or router side first. For other routers, use that model's documented diagnostics instead of copying OPNsense commands.
Compare several clients on the same network. When you're authorized and it's practical, check the affected device on another IPv6-capable network. A working peer proves that its path and configuration work, not that every device has the same policy.
If addresses and routes exist but access fails, investigate actual IPv6 reachability and DNS separately. DNS can return an IPv6 address record, called an AAAA record, over either IP version. A successful lookup doesn't prove that the query used IPv6 or that the returned address is reachable.
Keep IPv6 enabled while you collect the evidence
Microsoft advises against disabling IPv6 or unbinding it from interfacesOpens in a new tab, because some Windows components might stop working. Don't start with blanket disabling, registry edits, network resets or Windows reinstallation.
An adapter checkbox alone doesn't show the effective IPv6 configuration. Microsoft notes that the checkbox can stay selected even when a registry setting disables IPv6. Before any later configuration change, get authorization and save the original settings so you can restore them.
Send support the expected service, active interface, address types, route results, router's upstream result and comparison-device result. This evidence lets you ask your provider or administrator to investigate IPv6 service, router delivery or the affected device's configuration.