Our Balance 20 froze last weekend, and required a power cycle to get it working this morning. Perhaps it’s a coincidence, but it was about the same time that our provider, Comcast Business Internet, switched our IPv6 address. Could this have been the cause?
Hi Steven,
No idea whether this is related to your ISP. Anyway I suggest to upgrade to latest firmware version since we do have similiar cases on v6.1.2. This has been resolved since v6.2.0.
I just upgraded to 6.2.1. Now I have a different IPv6 issue.
I’m trying to connect to http://ipv6.whatismyv6.com, which times out.
On Windows, I can ping it:
C:\Windows\system32>ping ipv6.whatismyv6.com
Pinging ipv6.whatismyv6.com [2001:4810::110] with 32 by
Reply from 2001:4810::110: time=91ms
Reply from 2001:4810::110: time=94ms
Reply from 2001:4810::110: time=101ms
Reply from 2001:4810::110: time=124ms
Ping statistics for 2001:4810::110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 91ms, Maximum = 124ms, Average = 102ms
But connecting from the browser times out. (It worked last week.) While connecting, it is in this state:
C:\Windows\system32>netstat -n
Active Connections
Proto Local Address Foreign Address State
TCP [2601:647:4901:4e00:2969:3080:9a7e:4942]:50154 [2001:4810::110]:80 SYN_SENT
Connecting from a machine on the WAN side of the router (i.e. directly on the Comcast modem, not passing through the Peplink) works.
Also, IPv6 TCP connections to other hosts on the LAN works.