Open Forrk opened 6 years ago
ipv6-status: Fail
teredo是否稳定?
ipv4-status: OK ipv6-status: Fail 你没有打开ipv6.
ipv6-status: Fail netsh interface ipv6 show teredo 贴结果
类型 : enterpriseclient (Group Policy) 服务器名称 : teredo.remlab.net (Group Policy) 客户端刷新间隔 : 30 秒 客户端端口 : unspecified 状态 : qualified 客户端类型 : teredo client 网络 : managed NAT : symmetric (address) NAT 特殊行为 : UPNP: 否,PortPreserving: 否 本地映射 : 192.168.1.8:59750 外部 NAT 映射 : 122.226.185.100:17685
貌似参数正常,试试改用PING不通的微软服务器或许更稳定
试试 use-ipv6: auto 改为force_ipv6
一樣fail
P.S:即使成功了還是沒有連接池..
刚才我的也ipv6-status: Fail,但参数正常,怎么刷新控制页或重启XX都无效,use-ipv6: auto 改为force_ipv6 后刷新ok 但你我有别:你是组策略开启的,我不是
沒看懂,是直接輸入他給出的兩個CMD命令還是怎樣?
你没看仔细,他xp系统,与win7命令有别 你参数貌似正常,use-ipv6: auto 改为force_ipv6 ,退出XX-Net再启动貌似行(本人今天都有3次这样的了——貌似因为use-ipv6: auto 或 force_ipv4)
哦,又忘了:你我有别,你是组策略开启的,我不是
确保系统服务IP Helper 为自动并已启动,先前修改的ipv6组策略退回到默认值的全部“未配置”,退出XX-Net,先disable_ipv6.bat,再enable_ipv6.bat即可正常——取消你我之区别
OK是OK了,但是連接池問題依然存在
怎么OK的? 連接池問題不就是时间的问题?
再不济换服务器?
現在又變回fail的狀態了,已經不指望IPV6了,之前可以的時候IPV4只有兩三個IP,但是連接池有一兩個也能完全正常運作
换服务器 netsh interface teredo set state server=teredo-debian.remlab.net 或 netsh interface teredo set state server=teredo.trex.fi 或 netsh interface teredo set state server=win10.ipv6.microsoft.com
win10系统,win1710.ipv6.microsoft.com 新:0 h1:86 h2:0
IP也像是死了一樣維持著一樣的數字——检查所有IP——运行
XX-Net Status:
sys-platform: AMD64, Windows-7-6.1.7601-SP1 os-system: Windows os-version: 6.1.7601 os-release: 7 os-detail: Version:6-1; Build:7601; Platform:2; CSD:Service Pack 1; ServicePack:1-0; Suite:256; ProductType:0 architecture: 32bit,WindowsPE browser: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36 xxnet-version: 3.8.2 python-version: 2.7.13 openssl-version: 16.0.0 TLSv1_2 h2:alpn use-ipv6: auto gws-ip-num: total:1260 ipv4:4 ipv6:1058 ipv4-status: OK ipv6-status: Fail connected-link: new:0 used:0 worker: h1:0 h2:0 scan-ip-thread-num: 50 ip-quality: 332 is-idle: 0 block-stat: OK proxy_state: OK ca_state: OK Appid_Working: true Appids_Out_Of_Quota: false Appids_Not_Exist: false Using_Public_Appid: false
Nov 22 16:53:43.898 - [DEBUG] connect 2607:f8b0:401d:1f::8 fail:timeout('timed out',) Nov 22 16:53:43.898 - [DEBUG] report_connect_fail network fail Nov 22 16:53:47.898 - [DEBUG] connect 2607:f8b0:401d:d::9 fail:timeout('timed out',) Nov 22 16:53:47.898 - [DEBUG] report_connect_fail network fail Nov 22 16:53:51.902 - [DEBUG] connect 2607:f8b0:401d:1f::8 fail:timeout('timed out',) Nov 22 16:53:51.902 - [DEBUG] report_connect_fail network fail Nov 22 16:53:55.910 - [DEBUG] connect 2607:f8b0:401d:d::9 fail:timeout('timed out',) Nov 22 16:53:55.910 - [DEBUG] report_connect_fail network fail Nov 22 16:53:57.560 - [DEBUG] POST http://www.twitter.com/xxnet Nov 22 16:53:57.591 - [DEBUG] POST http://www.twitter.com/xxnet Nov 22 16:53:59.910 - [DEBUG] connect 2607:f8b0:401d:1f::8 fail:timeout('timed out',) Nov 22 16:53:59.910 - [DEBUG] report_connect_fail network fail Nov 22 16:54:03.917 - [DEBUG] connect 2607:f8b0:401d:d::9 fail:timeout('timed out',) Nov 22 16:54:03.917 - [DEBUG] report_connect_fail network fail Nov 22 16:54:07.917 - [DEBUG] connect 2607:f8b0:401d:1f::8 fail:timeout('timed out',) Nov 22 16:54:07.917 - [DEBUG] report_connect_fail network fail Nov 22 16:54:11.918 - [DEBUG] connect 2607:f8b0:401d:d::9 fail:timeout('timed out',) Nov 22 16:54:11.918 - [DEBUG] report_connect_fail network fail Nov 22 16:54:15.921 - [DEBUG] connect 2607:f8b0:401d:1f::8 fail:timeout('timed out',) Nov 22 16:54:15.921 - [DEBUG] report_connect_fail network fail Nov 22 16:54:19.922 - [DEBUG] connect 2607:f8b0:401d:d::9 fail:timeout('timed out',) Nov 22 16:54:19.922 - [DEBUG] report_connect_fail network fail