• 2

HINET的IPv6連美國壞了?

好像是這一兩天開始,連 http://test-ipv6.com 都說我沒IPv6

測了一下發現,很多都過gateway後再過一個node就掛了


>tracert -6 ds.test-ipv6.com

在上限 30 個躍點上
追蹤 ds.test-ipv6.com [2001:470:1:18::119] 的路由:

2 2 ms 2 ms 2 ms 2001:b000:e0:5:22:2633:141:2
3 * 目的地網路無法連線。

追蹤完成。




>tracert -6 www.sprint.net

在上限 30 個躍點上
追蹤 www.sprint.net [2600::] 的路由:


2 <1 ms 2 ms 2 ms 2001:b000:e0:5:21:2633:121:2
3 * * * 要求等候逾時。
4 * * 目的地網路無法連線。

追蹤完成。




>tracert -6 www.berkeley.edu

在上限 30 個躍點上
追蹤 www.w3.berkeley.edu [2607:f140:0:81::f] 的路由:

2 2 ms 2 ms 2 ms 2001:b000:e0:5:21:2633:121:2
3 * * * 要求等候逾時。
4 * 目的地網路無法連線。

追蹤完成。



>tracert -6 support.att.com

在上限 30 個躍點上
追蹤 info.att.com [2001:1890:1c00:3113::f:3015] 的路由:

2 1 ms 2 ms 2 ms 2001:b000:e0:5:22:2633:141:2
3 * * * 要求等候逾時。
4 * * * 要求等候逾時。
5 * * * 要求等候逾時。


這還繞了幾圈才掛掉

>tracert -6 www.v6.facebook.com

在上限 30 個躍點上
追蹤 v6.vvv.facebook.com [2a03:2880:20:8f08:face:b00c:0:1] 的路由:

2 3 ms 2 ms 2 ms 2001:b000:e0:5:22:2633:141:2
3 2 ms 3 ms 3 ms 2001:b000:e0:4:3012:3316:1:a
4 13 ms 11 ms 11 ms 2001:b000:80:3:80:e0:22:a
5 7 ms 5 ms 6 ms 2001:b000:80:4:3012:3311:11:b
6 7 ms 6 ms 6 ms 2001:b000:80:7:0:3:2934:101
7 * * * 要求等候逾時。
8 * * * 要求等候逾時。
9 * * * 要求等候逾時。
10 * * * 要求等候逾時。
11 * * * 要求等候逾時。
12 * * * 要求等候逾時。




國內或是從國內連接上其他網路的就正常

>tracert -6 dns.hinet.net

在上限 30 個躍點上
追蹤 dns.hinet.net [2001:b000:168::2] 的路由:

2 6 ms 3 ms 2 ms 2001:b000:e0:5:21:2633:121:2
3 <1 ms 3 ms 3 ms 2001:b000:e0:4:3012:3315:3:a
4 9 ms 11 ms 11 ms 2001:b000:80:3:80:e0:22:a
5 5 ms 6 ms 6 ms 2001:b000:80:4:3012:3311:11:b
6 6 ms 5 ms 5 ms 2001:b000:80:6:3311:0:3:1
7 5 ms 5 ms 5 ms dns.hinet.net [2001:b000:168::2]

追蹤完成。



>tracert -6 www.post.gov.tw

在上限 30 個躍點上
追蹤 www.post.gov.tw [2404:0:5002:0:1:0:2:167] 的路由:

2 1 ms 2 ms 2 ms 2001:b000:e0:5:22:2633:141:2
3 5 ms 3 ms 3 ms 2001:b000:e0:4:3012:3316:4:a
4 8 ms 11 ms 11 ms 2001:b000:80:3:80:e0:22:a
5 7 ms 6 ms 6 ms 2001:b000:80:4:3012:4207:1:1
6 5 ms 5 ms 6 ms 2001:7fa:1:7481::46
7 7 ms 6 ms 9 ms 2404:0:10ff::5:76
8 7 ms 8 ms 5 ms 2404:0:10ff:1:7709:0:5e5a:601
9 8 ms 5 ms 6 ms 2404:0:5000:fffe::1
10 10 ms 11 ms 12 ms 2404:0:5000:fffe::102
11 9 ms 9 ms 9 ms 2404:0:5000:ffff::ff3
12 8 ms 8 ms 8 ms 2404:0:5002:0:1:0:2:167

追蹤完成。





>tracert -6 www.google.com

在上限 30 個躍點上
追蹤 www.google.com [2404:6800:4005:803::2004] 的路由:

2 3 ms 2 ms 2 ms 2001:b000:e0:5:22:2633:141:2
3 4 ms 3 ms 3 ms 2001:b000:e0:4:3011:3316:2:a
4 6 ms 9 ms 9 ms 2001:b000:81:3:81:e0:3:a
5 8 ms 9 ms 9 ms 2001:b000:81:4:3201:3302:11:b
6 7 ms 9 ms 9 ms 2001:4860:1:1:0:d86:0:1
7 13 ms 11 ms 12 ms 2001:4860::1:0:73ac
8 24 ms 24 ms 24 ms 2001:4860::8:0:a432
9 25 ms 24 ms 24 ms 2001:4860::8:0:8f46
10 24 ms 24 ms 25 ms 2001:4860::1:0:ca31
11 23 ms 24 ms 24 ms 2001:4860:0:e05::1
12 25 ms 24 ms 24 ms 2001:4860:0:1::f
13 24 ms 24 ms 24 ms hkg07s22-in-x04.1e100.net [2404:6800:4005:803::2
004]

追蹤完成。



>tracert -6 www.facebook.com

在上限 30 個躍點上
追蹤 star-mini.c10r.facebook.com [2a03:2880:f017:1e:face:b00c:0:25de] 的路由:

2 27 ms 3 ms 2 ms 2001:b000:e0:5:21:2633:121:2
3 2 ms 3 ms 3 ms 2001:b000:e0:4:3012:3315:2:a
4 18 ms 11 ms 12 ms 2001:b000:80:3:80:e0:22:a
5 6 ms 6 ms 5 ms 2001:b000:80:4:3012:3311:11:b
6 7 ms 6 ms 6 ms 2001:b000:80:7:0:3:2934:101
7 8 ms 8 ms 9 ms psw01c.tpe1.tfbnw.net [2620:0:1cff:dead:beef:fff
f:ffff:fd53]
8 8 ms 8 ms 9 ms msw1aj.01.tpe1.tfbnw.net [2620:0:1cff:dead:bef0:
ffff:ffff:fdfd]
9 7 ms 6 ms 6 ms edge-star-mini6-shv-01-tpe1.facebook.com [2a03:2
880:f017:1e:face:b00c:0:25de]

追蹤完成。



到日本也OK

>tracert -6 www.kddi.com

在上限 30 個躍點上
追蹤 www.kddi.com [2001:268:fa03:500:106:162:242:107] 的路由:

2 1 ms 2 ms 2 ms 2001:b000:e0:5:22:2633:141:2
3 5 ms 3 ms 3 ms 2001:b000:e0:4:3012:3316:1:a
4 17 ms 11 ms 11 ms 2001:b000:80:3:80:e0:22:a
5 5 ms 5 ms 6 ms 2001:b000:80:4:3012:4103:7:b
6 7 ms 6 ms 6 ms 2001:b000:80:4:4103:4003:8:b
7 39 ms 39 ms 42 ms 2001:268:fc02:11::1
8 38 ms 45 ms 40 ms 6otejbb206.int-gw.kddi.ne.jp [2001:268:fb02:11b:
:1]
9 48 ms 47 ms 48 ms tm4BBAC02.v6.kddi.ne.jp [2001:268:fa00:ff0e::2]

10 40 ms 44 ms 40 ms tm4BBML64.v6.kddi.ne.jp [2001:268:fa03:305::2]
11 38 ms 46 ms 41 ms tm4BBML63.v6.kddi.ne.jp [2001:268:fa03:300::1]
12 37 ms 41 ms 40 ms 2001:268:fa03:217::2
13 40 ms 41 ms 45 ms www.kddi.com [2001:268:fa03:500:106:162:242:107]


追蹤完成。



香港也OK

>tracert -6 www.netvigator.com

在上限 30 個躍點上
追蹤 www.netvigator.com [2404:c800:8000:13::1001] 的路由:

2 1 ms 2 ms 2 ms 2001:b000:e0:5:21:2633:121:2
3 5 ms 3 ms 3 ms 2001:b000:e0:4:3011:3315:3:a
4 18 ms 11 ms 11 ms 2001:b000:80:3:80:e0:21:a
5 5 ms 5 ms 6 ms 2001:b000:80:4:3011:4103:6:b
6 6 ms 5 ms 6 ms 2001:b000:80:4:4103:4003:9:b
7 34 ms 34 ms 34 ms 2001:b000:80:7::3491:40b
8 34 ms 33 ms 34 ms 2400:8800:1f01:25::2
9 35 ms 34 ms 33 ms 2404c8008002001d0000000000000002.netvigator.com
[2404:c800:8002:1d::2]
10 179 ms 211 ms 69 ms 2404c800800200290000000000000002.netvigator.com
[2404:c800:8002:29::2]
11 38 ms 34 ms 34 ms 2404c800800200040000000000000001.netvigator.com
[2404:c800:8002:4::1]
12 30 ms 35 ms 34 ms 2404c800800200330000000000000002.netvigator.com
[2404:c800:8002:33::2]
13 27 ms 32 ms 29 ms 2404c800800000130000000000001001.netvigator.com
[2404:c800:8000:13::1001]

追蹤完成。





似乎HINET IPv6連美國(?)壞掉了?


2016-05-29 9:39 發佈
文章關鍵字 Hinet IPV6 美國
Snow wrote:
好像是這一兩天開始...(恕刪)


應該不是連美國掛了,應該是真的掛了,我連http://test-ipv6.com和http://ipv6-test.com這2個都說沒IPV6

FACEBOOK有支援IPV6連線,也不知是AC88U新韌體還HINET的問題造成IPV6的不穩定而斷線

昨天我剛好更新AC88U的韌體,IPV6是設在AC88U裡,88U後端的所有的設備一開始都能正常連上IPV6,但過一小段時間IPV6就會斷線變成無網際網路,我原本以為是88U新版韌體造成
真的全掛了
包含我自己日本的伺服器用IPv6也連不過去
只要是經過美國就會掛,再說往香港到印度孟買之後消失了

C:\Windows\system32>tracert ix.br

在上限 30 個躍點上
追蹤 ix.br [2001:12ff:0:6192::220] 的路由:

1 <1 ms <1 ms <1 ms 2001:b011:a406:1945::1
2 3 ms 2 ms 2 ms ipv6.dynamic.hinet.net [2001:b010:ffff::1]
3 1 ms 2 ms 2 ms 2001:b000:c5:5:21:2203:1:2
4 3 ms 2 ms 2 ms 2001:b000:c5:4:3012:3301:2:2
5 * 目的地網路無法連線。

追蹤完成。

C:\Windows\system32>tracert www.yandex.com

在上限 30 個躍點上
追蹤 www.yandex.com [2a02:6b8::11:11] 的路由:

1 <1 ms <1 ms <1 ms 2001:b011:a406:1945::1
2 4 ms 2 ms 2 ms ipv6.dynamic.hinet.net [2001:b010:ffff::1]
3 1 ms 2 ms 2 ms 2001:b000:c5:5:21:2203:1:2
4 4 ms 2 ms 2 ms 2001:b000:c5:4:3011:3301:3:2
5 9 ms 6 ms 6 ms 2001:b000:80:3:80:c5:3:2
6 5 ms 6 ms 6 ms 2001:b000:80:4:3011:4104:2:b
7 112 ms 5 ms 6 ms 2001:b000:80:4:4104:4004:8:b
8 28 ms 27 ms 28 ms ix-so-3-2-2-0.thar1.HK2-Hong-Kong.ipv6.as6453.ne
t [2405:2000:400:100::1]
9 30 ms 31 ms 30 ms if-ae-2-2.tcore2.HK2-Hong-Kong.ipv6.as6453.net [
2405:2000:400:100::12]
10 62 ms 63 ms 68 ms if-ae-16-2.tcore2.SVW-Singapore.ipv6.as6453.net
[2405:2000:400:300::e]
11 59 ms 59 ms 63 ms if-ae-2-2.tcore1.SVW-Singapore.ipv6.as6453.net [
2405:2000:ffa0:100::1]
12 124 ms 124 ms 123 ms if-ae-5-2.tcore1.CXR-Chennai.ipv6.as6453.net [24
05:2000:ffa0:100::2e]
13 123 ms 129 ms 133 ms if-ae-7-2.tcore1.MLV-Mumbai.ipv6.as6453.net [240
5:2000:ff10:100::1e]
14 123 ms 124 ms 120 ms if-ae-2-2.tcore2.MLV-Mumbai.ipv6.as6453.net [200
1:5a0:2300:200::2]
15 * * * 要求等候逾時。
16 * * * 要求等候逾時。
17 * * * 要求等候逾時。
18 * * * 要求等候逾時。
19 * * * 要求等候逾時。
20 * ^C
露天表示:www.ruten.xxx
Snow wrote:
>tracert -6 www.v6.facebook.com
在上限 30 個躍點上
追蹤 v6.vvv.facebook.com [2a03:2880:20:8f08:face:b00c:0:1] 的路由:
2 3 ms 2 ms 2 ms 2001:b000:e0:5:22:2633:141:2
3 2 ms 3 ms 3 ms 2001:b000:e0:4:3012:3316:1:a
4 13 ms 11 ms 11 ms 2001:b000:80:3:80:e0:22:a
5 7 ms 5 ms 6 ms 2001:b000:80:4:3012:3311:11:b
6 7 ms 6 ms 6 ms 2001:b000:80:7:0:3:2934:101
7 * * * 要求等候逾時。
8 * * * 要求等候逾時。
9 * * * 要求等候逾時。
10 * * * 要求等候逾時。
11 * * * 要求等候逾時。
12 * * * 要求等候逾時。...(恕刪)


我的也是這樣,如果連到tpe1的server就正常了,連 https://ipv6.google.com/ 到澳洲也正常

騎狗去撞車 wrote:
昨天我剛好更新AC88U的韌體,IPV6是設在AC88U裡,88U後端的所有的設備一開始都能正常連上IPV6,但過一小段時間IPV6就會斷線變成無網際網路,我原本以為是88U新版韌體造成
...(恕刪)


我的AC55U韌體拖很久還沒更新,這三天IPv6應該沒斷過

May 26 03:15:09 dnsmasq[719]: ignoring nameserver 192.168.1.1 - local interface
May 26 03:15:09 rdnssd[4241]: Child process hung up unexpectedly, aborting
May 26 03:15:09 radvd[4297]: Exiting, sigterm or sigint received.
May 26 03:15:09 dhcp6c[4285]: client6_send: transmit failed: Network is unreachable
May 26 03:15:10 dhcp6c[4285]: client6_send: transmit failed: Network is unreachable
May 26 03:15:11 dnsmasq[719]: ignoring nameserver 192.168.1.1 - local interface
May 26 03:15:11 WAN Connection: Fail to connect with some issues.
May 26 03:15:11 stop_nat_rules: apply the redirect_rules!
May 26 03:15:12 pppd[867]: Connection terminated.
May 26 03:15:12 pppd[867]: Modem hangup
May 26 03:15:22 pppd[867]: Connected to 00:02:3b:10:92:89 via interface vlan2
May 26 03:15:22 pppd[867]: Connect: ppp0 <--> vlan2
May 26 03:15:23 pppd[867]: PAP authentication succeeded
May 26 03:15:23 pppd[867]: peer from calling number 00:02:3B:10:92:89 authorized
May 26 03:15:23 pppd[867]: local LL address fe80::85ce:19a5:11b5:5f5c
May 26 03:15:23 pppd[867]: remote LL address fe80::d2f0:dbff:fe65:7000
May 26 03:15:23 pppd[867]: local IP address 61.223.82.129
May 26 03:15:23 pppd[867]: remote IP address 168.95.98.254
May 26 03:15:23 pppd[867]: primary DNS address 168.95.1.1
May 26 03:15:23 pppd[867]: secondary DNS address 168.95.192.1
May 26 03:15:23 kernel: ra_sw_nat_hook_wifi: 1
May 26 03:15:23 syslog: module ip6t_ROUTE not found in modules.dep
May 26 03:15:23 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_vlan2)!
May 26 03:15:23 rc_service: ip-up 4851:notify_rc stop_upnp
May 26 03:15:23 rc_service: ip-up 4851:notify_rc start_upnp
May 26 03:15:23 rc_service: waitting "stop_upnp" via ip-up ...
May 26 03:15:23 miniupnpd[4288]: received signal 15, good-bye
May 26 03:15:23 rdnssd[4855]: Get IPv6 address from RA & DNS from DHCPv6
May 26 03:15:24 miniupnpd[4902]: HTTP listening on port 58211
May 26 03:15:24 miniupnpd[4902]: Listening for NAT-PMP traffic on port 5351
May 26 03:15:24 ddns update: ez-ipupdate: starting...
May 26 03:15:24 ddns update: connected to ns1.asuscomm.com (103.10.4.108) on port 80.
May 26 03:15:24 ddns update: Asus update entry:: return: HTTP/1.1 200 OK^M Date: Wed, 25 May 2016 19:15:24 GMT^M Server: Apache^M Content-Length: 0^M Connection: close^M Content-Type: text/html^M ^M
May 26 03:15:24 ddns update: retval= 0, ddns_return_code (,200)
May 26 03:15:24 ddns update: asusddns_update: 0
May 26 03:15:24 ddns: ddns update ok
May 26 03:15:26 WAN Connection: WAN was restored.
May 26 03:15:27 ntp: start NTP update
May 26 07:06:46 kernel: rt2860v2:ASSOC - Assign AID=2 to STA 80:01:84:13:33:8a
May 26 15:15:25 ntp: start NTP update
May 26 17:46:01 kernel: rt2860v2:ASSOC - Assign AID=2 to STA 80:01:84:13:33:8a
May 26 17:46:29 kernel: MT7610ap:ASSOC - Assign AID=1 to STA 80:01:84:13:33:8a
May 26 17:59:58 kernel: rt2860v2:ASSOC - Assign AID=2 to STA 00:1e:64:77:2d:c4
May 26 21:08:26 kernel: rt2860v2:ASSOC - Assign AID=2 to STA 5c:ff:35:74:d5:e5
May 26 21:08:26 kernel: MT7610ap:ASSOC - Assign AID=2 to STA 5c:ff:35:74:d5:e5
May 27 03:15:23 ntp: start NTP update
May 27 09:41:00 kernel: MT7610ap:ASSOC - Assign AID=1 to STA c0:bd:d1:21:ef:a9
May 27 09:41:06 kernel: MT7610ap:WPARetryExec::MSG1 timeout, pEntry->ReTryCounter = 4, STA c0:bd:d1:21:ef:a9
May 27 15:15:20 ntp: start NTP update
May 27 18:13:59 kernel: rt2860v2:ASSOC - Assign AID=2 to STA 00:1e:64:77:2d:c4
May 27 18:36:27 kernel: MT7610ap:ASSOC - Assign AID=1 to STA 80:01:84:13:33:8a
May 27 21:16:13 kernel: rt2860v2:ASSOC - Assign AID=2 to STA 00:1e:64:77:2d:c4
May 27 21:22:49 kernel: rt2860v2:ASSOC - Assign AID=3 to STA 80:01:84:13:33:8a
May 27 21:22:55 kernel: MT7610ap:ASSOC - Assign AID=1 to STA 80:01:84:13:33:8a
May 27 21:31:04 kernel: rt2860v2:ASSOC - Assign AID=3 to STA 80:01:84:13:33:8a
May 27 21:31:48 kernel: MT7610ap:ASSOC - Assign AID=1 to STA 80:01:84:13:33:8a
May 27 21:41:33 kernel: rt2860v2:ASSOC - Assign AID=3 to STA 80:01:84:13:33:8a
May 27 21:48:01 kernel: MT7610ap:ASSOC - Assign AID=1 to STA 80:01:84:13:33:8a
May 27 22:47:51 kernel: rt2860v2:ASSOC - Assign AID=3 to STA 80:01:84:13:33:8a
May 27 22:48:10 kernel: MT7610ap:ASSOC - Assign AID=1 to STA 80:01:84:13:33:8a
May 28 00:01:28 kernel: rt2860v2:ASSOC - Assign AID=2 to STA 80:01:84:13:33:8a
May 28 00:01:52 kernel: MT7610ap:ASSOC - Assign AID=1 to STA 80:01:84:13:33:8a
May 28 03:15:18 ntp: start NTP update
May 28 07:14:59 kernel: rt2860v2:ASSOC - Assign AID=2 to STA 80:01:84:13:33:8a
May 28 07:15:36 kernel: MT7610ap:ASSOC - Assign AID=1 to STA 80:01:84:13:33:8a
May 28 07:15:37 kernel: MT7610ap:Replay Counter Different in pairwise msg 2 of 4-way handshake!
May 28 07:30:29 kernel: MT7610ap:ASSOC - Assign AID=1 to STA 80:01:84:13:33:8a
May 28 08:23:25 kernel: rt2860v2:ASSOC - Assign AID=2 to STA 00:1e:64:77:2d:c4
May 28 12:16:34 kernel: rt2860v2:ASSOC - Assign AID=2 to STA 80:01:84:13:33:8a
May 28 12:17:38 kernel: MT7610ap:ASSOC - Assign AID=1 to STA 80:01:84:13:33:8a
May 28 12:28:14 kernel: MT7610ap:ASSOC - Assign AID=1 to STA 80:01:84:13:33:8a
May 28 15:15:15 ntp: start NTP update
May 28 16:03:28 kernel: rt2860v2:ASSOC - Assign AID=2 to STA 80:01:84:13:33:8a
May 28 16:03:40 kernel: MT7610ap:ASSOC - Assign AID=1 to STA 80:01:84:13:33:8a
May 28 20:54:28 kernel: rt2860v2:ASSOC - Assign AID=2 to STA 00:1e:64:77:2d:c4
May 29 01:25:42 kernel: rt2860v2:ASSOC - Assign AID=2 to STA 80:01:84:13:33:8a
May 29 01:26:05 kernel: MT7610ap:ASSOC - Assign AID=1 to STA 80:01:84:13:33:8a
May 29 03:15:13 ntp: start NTP update
May 29 04:23:39 dnsmasq[719]: ignoring nameserver 192.168.1.1 - local interface
May 29 04:23:39 rdnssd[4854]: Child process hung up unexpectedly, aborting
May 29 04:23:39 radvd[4910]: Exiting, sigterm or sigint received.
May 29 04:23:39 dhcp6c[4898]: client6_send: transmit failed: Network is unreachable
May 29 04:23:40 dhcp6c[4898]: client6_send: transmit failed: Network is unreachable
May 29 04:23:40 dnsmasq[719]: ignoring nameserver 192.168.1.1 - local interface
May 29 04:23:42 pppd[867]: Connection terminated.
May 29 04:23:42 pppd[867]: Modem hangup
May 29 04:23:43 WAN Connection: Fail to connect with some issues.
May 29 04:23:43 stop_nat_rules: apply the redirect_rules!
May 29 04:23:52 pppd[867]: Connected to 00:02:3b:10:92:89 via interface vlan2
May 29 04:23:52 pppd[867]: Connect: ppp0 <--> vlan2
May 29 04:23:53 pppd[867]: PAP authentication succeeded
May 29 04:23:53 pppd[867]: peer from calling number 00:02:3B:10:92:89 authorized
May 29 04:23:53 pppd[867]: local LL address fe80::b1b2:3ea1:f5db:9798
May 29 04:23:53 pppd[867]: remote LL address fe80::d2f0:dbff:fe65:7000
May 29 04:23:53 pppd[867]: local IP address 61.223.84.59
May 29 04:23:53 pppd[867]: remote IP address 168.95.98.254
May 29 04:23:53 pppd[867]: primary DNS address 168.95.1.1
May 29 04:23:53 pppd[867]: secondary DNS address 168.95.192.1
May 29 04:23:53 kernel: ra_sw_nat_hook_wifi: 1
May 29 04:23:53 syslog: module ip6t_ROUTE not found in modules.dep
May 29 04:23:53 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_vlan2)!
May 29 04:23:53 rc_service: ip-up 5313:notify_rc stop_upnp
May 29 04:23:53 rc_service: ip-up 5313:notify_rc start_upnp
May 29 04:23:53 rc_service: waitting "stop_upnp" via ip-up ...
May 29 04:23:53 miniupnpd[4902]: received signal 15, good-bye
May 29 04:23:53 WAN Connection: WAN was restored.
May 29 04:23:54 rdnssd[5317]: Get IPv6 address from RA & DNS from DHCPv6
May 29 04:23:54 miniupnpd[5363]: HTTP listening on port 50299
May 29 04:23:54 miniupnpd[5363]: Listening for NAT-PMP traffic on port 5351
May 29 04:23:54 ddns update: ez-ipupdate: starting...
May 29 04:23:57 ddns update: connected to ns1.asuscomm.com (103.10.4.108) on port 80.
May 29 04:23:58 ddns update: Asus update entry:: return: HTTP/1.1 200 OK^M Date: Sat, 28 May 2016 20:23:57 GMT^M Server: Apache^M Content-Length: 0^M Connection: close^M Content-Type: text/html^M ^M
May 29 04:23:58 ddns update: retval= 0, ddns_return_code (,200)
May 29 04:23:58 ddns update: asusddns_update: 0
May 29 04:23:58 ddns: ddns update ok
May 29 04:23:58 ntp: start NTP update
May 29 04:54:13 kernel: rt2860v2:ASSOC - Assign AID=2 to STA 80:01:84:13:33:8a
May 29 04:54:25 kernel: MT7610ap:ASSOC - Assign AID=1 to STA 80:01:84:13:33:8a
May 29 04:56:54 kernel: rt2860v2:ASSOC - Assign AID=2 to STA 80:01:84:13:33:8a
May 29 04:57:19 kernel: MT7610ap:ASSOC - Assign AID=1 to STA 80:01:84:13:33:8a
May 29 07:24:10 kernel: rt2860v2:ASSOC - Assign AID=2 to STA 80:01:84:13:33:8a
May 29 07:24:16 kernel: rt2860v2:WPARetryExec::MSG1 timeout, pEntry->ReTryCounter = 4, STA 80:01:84:13:33:8a



notebook18k wrote:
我的也是這樣,如果...(恕刪)


因為剛好是昨天更新AC88U韌體,也剛好我昨天注意到網卡連線資訊裡的IPV6狀態,會突然變成IPV6的IP不見了,只剩IPV6的DNS,加上測了http://test-ipv6.com和http://ipv6-test.com這2個網站都說沒IPV6,才會懷疑是不是88U的新版韌體造成的
maodou8886 wrote:
可能是因為這個吧:因...(恕刪)

海底纜線問題跟IP6沒直接關係=..=
HINet 有問題 已聯絡365 星期一會回電看是否解決
Hinet 已經快速修復 通知有效
  • 2
內文搜尋
X
評分
評分
複製連結
Mobile01提醒您
您目前瀏覽的是行動版網頁
是否切換到電腦版網頁呢?