Orcon IPv6 problem

Forums › LAN (ethernet/Wifi/routers/Bluetooth) › Orcon IPv6 problem

linw

2849 posts

Uber Geek

#303319 1-Feb-2023 08:29

My IPv6 doesn't seem to be working. I have a std NF18 acv router that hasn't been fiddled with. It shows 3 WAN interfaces with IPv6 enabled.

My windows comps have IPv6 addresses but when I "ping -6 google.com" I get Destination unreachable.

I also used to get the green IPv6 'flag' when logged into Geekzone but not now.

No big deal as nothing I do needs IPv6 but it would be nice to get it right.

Anything I should be looking at?

TIA.

OldGeek

893 posts

Ultimate Geek

ID Verified

Lifetime subscriber

#3030276 1-Feb-2023 12:31

I use a website to test connectivity: Test your IPv6. (test-ipv6.com)

I am using Sky Broadband (same Vocus network as Orcon) and the above website reported me as having IPv4 connectivity only. Rebooted (Windows 11 laptop) and now this website reports both IPv4 and IPv6 connectivity.

--

OldGeek.

Voyager referral code: https://refer.voyager.nz/6XQR2QG9Q

linw

2849 posts

Uber Geek

#3030355 1-Feb-2023 13:13

Thanks, but that site says no address detected.

linw

2849 posts

Uber Geek

#3030440 1-Feb-2023 15:35

OK, fixed now. I followed the instructions below.

I did it on one computer and was surprised to find it fixed all three of my computers. Suppose there is a good reason for that but wonder where the common data is stored. Perhaps an enlightened person can tell me?

And the little green 'flag' is showing!

Reset IPv6 settings from the command prompt (Windows). Here's how:
1. Type cmd in the Windows system search box.
2. Right-click the Command Prompt desktop app displayed, then choose Run as administrator.
3. Type netsh winsock reset catalog and then press the Enter key.
4. Type netsh int ipv6 reset reset.log and then press the Enter key.
5. Restart your system.

linw

2849 posts

Uber Geek

#3035383 12-Feb-2023 15:07

OK, got it wrong. It is the router that has the problem. The dropout affects all three computers here.

A router reboot fixes it for a short while then the problem recurs. The router system log doesn't show anything relevant at the time it fails.

Luckily it doesn't stop what I do but it is still annoying!