LeeLou

走得有点慢了啊, 是不着急上班吗? 每天坚持还是很难的吧

这是太保的保险吗,还是就是在燃气营业厅买的保险?

原来燃气险还能赔这个? 仅限厨房的吗

好吧,看来还是打网约车吧

西城商务纪 不正经?

@datocp https://tcp.ping.pe/ 可以去这个网站测一下,是不是全球各地都无法访问

Query: tcp s.networkplanner.xyz:443 [104.21.96.1]

Location ISP TCP port check result
Canada, BC, Vancouver Telus Connection to 104.21.96.1:443 successful
Canada, BC, Vancouver Shaw Connection to 104.21.96.1:443 successful
USA, CA, Fremont Hurricane Connection to 104.21.96.1:443 successful
USA, CA, Fremont IT7 FMT2 Connection to 104.21.96.1:443 successful
USA, CA, Fremont Linode Connection to 104.21.96.1:443 successful
USA, CA, San Francisco Digital Ocean Connection to 104.21.96.1:443 successful
USA, CA, Santa Clara Hurricane Connection to 104.21.96.1:443 successful
USA, CA, Los Angeles Hurricane Connection to 104.21.96.1:443 successful
USA, CA, Los Angeles DMIT Connection to 104.21.96.1:443 successful
USA, CA, Los Angeles Vultr Connection to 104.21.96.1:443 successful
USA, CA, Los Angeles RamNode Connection to 104.21.96.1:443 successful
USA, CA, Los Angeles NetActuate Connection to 104.21.96.1:443 successful
USA, WA, Seattle Google Connection to 104.21.96.1:443 successful
USA, WA, Seattle RamNode Connection to 104.21.96.1:443 successful
USA, CO, Denver Cogent Connection to 104.21.96.1:443 successful
USA, CO, Denver NetActuate Connection to 104.21.96.1:443 successful
USA, TX, Dallas NetActuate Connection to 104.21.96.1:443 successful
USA, IL, Chicago FDC/AS30058 Connection to 104.21.96.1:443 successful
USA, IL, Chicago NetActuate Connection to 104.21.96.1:443 successful
USA, GA, Atlanta RamNode Connection to 104.21.96.1:443 successful
USA, NY, Buffalo ColoCrossing Connection to 104.21.96.1:443 successful
USA, VA, Ashburn NetActuate Connection to 104.21.96.1:443 successful
USA, NY, New York Hurricane Connection to 104.21.96.1:443 successful
USA, NY, New York RamNode Connection to 104.21.96.1:443 successful
Canada, QC, Montreal OVH Connection to 104.21.96.1:443 successful
Chile, Santiago NetActuate Connection to 104.21.96.1:443 successful
Brazil, Sao Paulo NetActuate Connection to 104.21.96.1:443 successful
Morocco, Fez Hostoweb Connection to 104.21.96.1:443 successful
Spain, Madrid NetActuate Connection to 104.21.96.1:443 successful
UK, Manchester NetActuate Connection to 104.21.96.1:443 successful
UK, London FDC/AS30058 Connection to 104.21.96.1:443 successful
France, Paris Online.net Connection to 104.21.96.1:443 successful
France, Paris NetActuate Connection to 104.21.96.1:443 successful
Netherlands, Amsterdam Online.net Connection to 104.21.96.1:443 successful
Netherlands, Amsterdam Eranium Connection to 104.21.96.1:443 successful
Norway, Sandefjord Terrahost Connection to 104.21.96.1:443 successful
Switzerland, Zurich iFog Connection to 104.21.96.1:443 successful
Germany, Frankfurt ZetNet Connection to 104.21.96.1:443 successful
Germany, Nuremberg NetActuate Connection to 104.21.96.1:443 successful
Romania, Bucharest ZetNet Connection to 104.21.96.1:443 successful
Romania, Bucharest M247 Connection to 104.21.96.1:443 successful
Turkey, Bursa Oneprovider Connection to 104.21.96.1:443 successful
Cyprus, Limassol CL8 Connection to 104.21.96.1:443 successful
Israel, Tel Aviv Oneprovider Connection to 104.21.96.1:443 successful
UAE, Dubai Bamboozle Connection to 104.21.96.1:443 successful
UAE, Dubai Buzinessware Connection to 104.21.96.1:443 successful
UAE, Dubai NetActuate Connection to 104.21.96.1:443 successful
Iran, Tehran MHOST Connection to 104.21.96.1:443 successful
India, Mumbai Vultr Connection to 104.21.96.1:443 successful
India, Bengaluru Digital Ocean Connection to 104.21.96.1:443 successful
India, Chennai NetActuate Connection to 104.21.96.1:443 successful
Bangladesh, Dhaka Dot Internet Connection to 104.21.96.1:443 successful
Singapore Digital Ocean Connection to 104.21.96.1:443 successful
Japan, Tokyo DODO Connection to 104.21.96.1:443 successful
Japan, Tokyo Vultr Connection to 104.21.96.1:443 successful
Australia, Sydney Vultr Connection to 104.21.96.1:443 successful
Taiwan, Taichung Google Connection to 104.21.96.1:443 successful
China, Guiyang Huawei Connection to 104.21.96.1:443 failed
China, Beijing Huawei Connection to 104.21.96.1:443 failed
China, Shandong China Unicom Connection to 104.21.96.1:443 failed
China, Jiangsu China Telecom Connection to 104.21.96.1:443 failed
China, Jiangsu China Mobile Connection to 104.21.96.1:443 failed
China, Lishui China Telecom Connection to 104.21.96.1:443 failed
China, Lishui China Unicom Connection to 104.21.96.1:443 failed
China, Lishui China Mobile Connection to 104.21.96.1:443 successful
China, Qingdao Aliyun Connection to 104.21.96.1:443 failed
China, Shanghai Aliyun Connection to 104.21.96.1:443 failed
China, Shanghai Huawei Connection to 104.21.96.1:443 failed
China, Shanghai Tencent Connection to 104.21.96.1:443 failed


测了一下端口,发现国内大多不通,但国外都是好的

2024/12/31 19:38:13 [Warning] failed to handler mux client connection > v2ray.com/core/proxy/vmess/outbound: failed to find an available destination > v2ray.com/core/common/retry: [v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://s.networkplanner.xyz/network): > dial tcp 104.21.32.1:443: i/o timeout] > v2ray.com/core/common/retry: all retry attempts failed

2024/12/31 19:39:00 [Warning] failed to handler mux client connection > v2ray.com/core/proxy/vmess/outbound: failed to find an available destination >
v2ray.com/core/common/retry:

[v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://s.networkplanner.xyz/network): > dial tcp 104.21.32.1:443: i/o timeout] > v2ray.com/core/common/retry: all retry attempts failed


搜了一下,跟 https://github.com/233boy/v2ray/issues/1363 很像, 是域名问题 ?

图片好像不能放大,看着并没有明显环路,服务器是双网卡的吧

wifi 终端是不是 2.5G 内网, 应该跟 wifi 的 ap 有关, 跟中心的交换机 2.5G 不是很强的因果条件吧