回覆  evantkh
無錯,正常情況你啱~
但我驚佢係行緊IPV4 扮IPV6 所以先問WAN ...
a886 發表於 2017-1-18 21:49


我用開firefox,會用呢個套件check 吓係咪用緊IPv6 去連線。因為我個router/wifi adapter 唔知點解有時會自己由native ipv6 變返做tunneling。
Chrome 都應該會有類似套件。

TOP

From Netvigator homepage link
http://myspeedmeter.net/index.html
If you have IPv6, the test site will have option of IPv4 and IPv6
For IPv6, I mean native not tunnel in router
BTW, the Netvigator IPv6 is very unstable in recent 1 month, always out of service

TOP

本帖最後由 ed1 於 2017-1-19 02:49 編輯

回覆 12# AAA1


試下改用 Google IPv6 DNS
2001:4860:4860::8888
2001:4860:4860::8844
即係router 輸入
2001:4860:4860:0000:0000:0000:0000:8888
2001:4860:4860:0000:0000:0000:0000:8844

TOP

回覆  AAA1


試下改用 Google IPv6 DNS
2001:4860:4860::8888
2001:4860:4860::8844
即係router 輸入
20 ...
ed1 發表於 2017-1-19 02:45


華碩個UI 好似唔俾輸入IPv6 嘅DNS?
不過照睇個log,就應該用緊PCCW 嘅IPv6 DNS:
  1. DNS Servers: 2404:c800:8000:1a::1201 2404:c800:8000:8::1201
複製代碼
我應該遇到呢個IPv6 ping latency 問題:
  1. C:\Users\Fanolian>ping google.com -4

  2. Pinging google.com [216.58.200.14] with 32 bytes of data:
  3. Reply from 216.58.200.14: bytes=32 time=5ms TTL=54
  4. Reply from 216.58.200.14: bytes=32 time=5ms TTL=54
  5. Reply from 216.58.200.14: bytes=32 time=5ms TTL=54
  6. Reply from 216.58.200.14: bytes=32 time=5ms TTL=54

  7. Ping statistics for 216.58.200.14:
  8.     Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
  9. Approximate round trip times in milli-seconds:
  10.     Minimum = 5ms, Maximum = 5ms, Average = 5ms

  11. C:\Users\Fanolian>ping google.com -6

  12. Pinging google.com [2404:6800:4005:800::200e] with 32 bytes of data:
  13. Reply from 2404:6800:4005:800::200e: time=22ms
  14. Reply from 2404:6800:4005:800::200e: time=6ms
  15. Reply from 2404:6800:4005:800::200e: time=6ms
  16. Reply from 2404:6800:4005:800::200e: time=9ms

  17. Ping statistics for 2404:6800:4005:800::200e:
  18.     Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
  19. Approximate round trip times in milli-seconds:
  20.     Minimum = 6ms, Maximum = 22ms, Average = 10ms
複製代碼
如果隔大約30秒先再ping google.com -6,會再次出現單一次~22ms 嘅情況。

TOP

回覆 14# Fanolian

netgear r8000可set ipv6 dns


Asus rt-ac66u 都可set ipv6 dns
附件: 您需要登錄才可以下載或查看附件。沒有帳號?註冊

TOP

回覆 15# ed1

Thanks. 凌晨3點睇漏眼。去咗平時WAN 嗰一part 度搞。

TOP

回覆 16# Fanolian


    改後ping time 有無改善?

TOP

Have tried before using Google public ipv6 DNS
still in vain
As mentioned, the ipv6 failure just happens in recent 1 month
longest halt for 3 weeks
Recent one week is intermittent, sometimes need to wait for 10 to 15 min after router reboot
Also the wan address IP is changing after router reboot

TOP

回覆  Fanolian


    改後ping time 有無改善?
ed1 發表於 2017-1-19 04:23


都係一樣,每大約30秒第一下ping 會時間特別耐。
  1. C:\Users\Fanolian>ping google.com -6

  2. Pinging google.com [2404:6800:4005:806::200e] with 32 bytes of data:
  3. Reply from 2404:6800:4005:806::200e: time=22ms
  4. Reply from 2404:6800:4005:806::200e: time=6ms
  5. Reply from 2404:6800:4005:806::200e: time=6ms
  6. Reply from 2404:6800:4005:806::200e: time=5ms

  7. Ping statistics for 2404:6800:4005:806::200e:
  8.     Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
  9. Approximate round trip times in milli-seconds:
  10.     Minimum = 5ms, Maximum = 22ms, Average = 9ms
複製代碼

TOP

回覆 18# AAA1
netvigator 300MB
speed test ipv6 慢過ipv4 少少 用緊google ipv6 & ipv4 dns

附件: 您需要登錄才可以下載或查看附件。沒有帳號?註冊

TOP