最近搬瓦工机场中断很严重?

2022-06-20 18:51:43 +08:00
 idblife
感觉基本没法用了啊。。。
7395 次点击
所在节点    VPS
41 条回复
Xusually
2022-06-21 08:26:36 +08:00
gia 没感觉
demoshengxw
2022-06-21 08:41:13 +08:00
买的两年的砖瓦工,自己搭建的还是不如机场爽。机场节点多,随便切
Ne
2022-06-21 09:14:37 +08:00
半年之前的 2.88 也没续,感觉不爽。还不如机场。
VeryZero
2022-06-21 09:15:38 +08:00
原来不是我一个人,换成 3 也不稳。
datocp
2022-06-21 09:30:39 +08:00
用的最最普通的黑色星期 5 主机。自从换到一个 144 开头的 ip 就安稳了,至少 3 年了。。。
至于 dns 问题,啊,想想 socks5 软件一直就支持远端 dns 解析。也不知道大家用的那些旁门左道软件竟然还有 DNS 污染这种问题。

stunnel 的证书链验证过程,更是让中间人无可奈何。
datocp
2022-06-21 09:35:29 +08:00
中国电信也是个烂 ISP 。路由每天换一次新 IP ,有时候遇到问题的时候换 IP 无效,还是以为 VPS 的服务进程又挂了,一通折腾无效,然后估计前后换了了次 pppoe 拔号 IP 才解决。。。也就是有时候实际是家里的 ip 就自带墙属性。

# cat redial.sh
#!/bin/sh
ip1=`ifconfig eth0.2 | grep addr|cut -d":" -f2|awk '{ print $1}'`;while true;do
echo "`(date +"%m/%d/%Y %T")` pppoe-wan_ipaddr_old_$ip1 dropped_ redial_ " >> /tmp/log1;
killall pppd;sleep 8
ip2=`ifconfig eth0.2 | grep addr|cut -d":" -f2|awk '{ print $1}'`;
echo $ip2|grep ^101
if [ $? -eq 0 ];then
echo "`(date +"%m/%d/%Y %T")` pppoe-wan_ipaddr_new_101 redial_" >> /tmp/log1;
elif [ $ip1 != $ip2 ];then
echo "`(date +"%m/%d/%Y %T")` pppoe-wan_ipaddr_new_$ip2 successfully_" >> /tmp/log1;break;fi;done;
/da/ddns.sh
zanxj
2022-06-21 10:01:10 +08:00
传家宝还行。搬瓦工的同学可进群交流 t.me/bandwagonvps
FakNoCNName
2022-06-21 10:13:18 +08:00
原有的域名也还能用,现在出问题是因为:
1. ip 封禁
今年机场的 IP 被封的厉害。所以他家的 IP 解析更新格外频繁,最近几个月 1~2 周就会换一批。
2. dns 污染
端午节期间排查了下,Just My Socks 的域名解析在国内全部被指向了黑洞 IP ,国内的 DNS 服务商全军覆没,国外的 DNS 又有抢答。
每次机场更新 IP 解析以后的头一天还能用,随后域名又会被污染。

解决方案:
1. 把 IP 、域名的解析配置到自建 DNS server
1.1 通过 just my socks 官网查询最新 ip
1.2 或者用国外 VPS 自建一个 dns server ,只做自建 DNS 的上游 DNS server
2. 找一个新的机场备用,在 clash 上配置成故障转移,避免彻底不能用
Akitora
2022-06-21 10:29:58 +08:00
今早被莫名重启了,淦
datocp
2022-06-21 11:33:21 +08:00
2022.06.21 11:31:17 LOG6[main]: Initializing inetd mode configuration
2022.06.21 11:31:17 LOG5[main]: stunnel 5.64 on x64-pc-mingw32-gnu platform
2022.06.21 11:31:17 LOG5[main]: Compiled/running with OpenSSL 3.0.3 3 May 2022
2022.06.21 11:31:17 LOG5[main]: Threading:WIN32 Sockets:SELECT,IPv6 TLS:ENGINE,OCSP,PSK,SNI
2022.06.21 11:31:17 LOG6[main]: Initializing inetd mode configuration
2022.06.21 11:31:17 LOG5[main]: Reading configuration from file D:\stunnel\config\stunnel.conf
2022.06.21 11:31:17 LOG5[main]: UTF-8 byte order mark detected
2022.06.21 11:31:17 LOG5[main]: FIPS mode disabled
2022.06.21 11:31:17 LOG6[main]: Compression enabled: 0 methods
2022.06.21 11:31:17 LOG6[main]: Initializing service [server4]
2022.06.21 11:31:17 LOG6[main]: stunnel default security level set: 2
2022.06.21 11:31:17 LOG6[main]: Session resumption enabled
2022.06.21 11:31:17 LOG6[main]: Loading certificate from file: 1.pem
2022.06.21 11:31:17 LOG6[main]: Certificate loaded from file: 1.pem
2022.06.21 11:31:17 LOG6[main]: Loading private key from file: 1.pem
2022.06.21 11:31:17 LOG6[main]: Private key loaded from file: 1.pem
2022.06.21 11:31:17 LOG6[main]: DH initialization skipped: client section
2022.06.21 11:31:17 LOG6[main]: Initializing service [server7]
2022.06.21 11:31:17 LOG6[main]: PSKsecrets line 1: 30-byte ASCII key configured for identity "test1"
2022.06.21 11:31:17 LOG6[main]: PSK identities: 1 retrieved
2022.06.21 11:31:17 LOG6[main]: stunnel default security level set: 2
2022.06.21 11:31:17 LOG6[main]: Session resumption enabled
2022.06.21 11:31:17 LOG6[main]: Loading certificate from file: 1.pem
2022.06.21 11:31:17 LOG6[main]: Certificate loaded from file: 1.pem
2022.06.21 11:31:17 LOG6[main]: Loading private key from file: 1.pem
2022.06.21 11:31:17 LOG6[main]: Private key loaded from file: 1.pem
2022.06.21 11:31:17 LOG6[main]: DH initialization skipped: client section
2022.06.21 11:31:17 LOG6[main]: Initializing service [gmail-smtp]
2022.06.21 11:31:17 LOG6[main]: stunnel default security level set: 2
2022.06.21 11:31:17 LOG6[main]: Session resumption enabled
2022.06.21 11:31:17 LOG6[main]: Loading certificate from file: 1.pem
2022.06.21 11:31:17 LOG6[main]: Certificate loaded from file: 1.pem
2022.06.21 11:31:17 LOG6[main]: Loading private key from file: 1.pem
2022.06.21 11:31:17 LOG6[main]: Private key loaded from file: 1.pem
2022.06.21 11:31:18 LOG6[main]: DH initialization skipped: client section
2022.06.21 11:31:18 LOG5[main]: Configuration successful
2022.06.21 11:31:18 LOG6[main]: Service [server4] (FD=712) bound to 127.0.0.1:1084
2022.06.21 11:31:18 LOG6[main]: Service [server7] (FD=716) bound to 127.0.0.1:1087
2022.06.21 11:31:18 LOG6[main]: Service [gmail-smtp] (FD=720) bound to 127.0.0.1:10025
2022.06.21 11:31:18 LOG6[cron]: Executing cron jobs
2022.06.21 11:31:18 LOG6[cron]: Cron jobs completed in 0 seconds
2022.06.21 11:31:22 LOG5[0]: Service [server4] accepted connection from 127.0.0.1:62451
2022.06.21 11:31:22 LOG6[0]: failover: priority, starting at entry #0
2022.06.21 11:31:22 LOG6[0]: s_connect: connecting ip.ip.ip.ip:80
2022.06.21 11:31:23 LOG5[0]: s_connect: connected ip.ip.ip.ip:80
2022.06.21 11:31:23 LOG5[0]: Service [server4] connected remote server from 192.168.1.100:62452
2022.06.21 11:31:23 LOG6[0]: SNI: sending servername: ip.ip.ip.ip
2022.06.21 11:31:23 LOG6[0]: Peer certificate required
2022.06.21 11:31:23 LOG6[0]: No client CA list
2022.06.21 11:31:23 LOG6[0]: Certificate accepted at depth=1: C=US, O=Symantec Corporation, OU=Symantec Trust Network, CN=Symantec Class 3 EV SSL CA - G3
2022.06.21 11:31:23 LOG6[0]: CERT: Host name "www.symantec.com" matched with "www.symantec.com"
2022.06.21 11:31:23 LOG5[0]: Certificate accepted at depth=0: C=US, ST=California, L=Mountain View, O=Symantec Corporation, OU=Corp Mktg & Comms - Online Exp, CN=www.symantec.com, SN=20220621
2022.06.21 11:31:23 LOG6[0]: TLS connected: new session negotiated
2022.06.21 11:31:23 LOG6[0]: TLSv1.3 ciphersuite: TLS_AES_256_GCM_SHA384 (256-bit encryption)
2022.06.21 11:31:23 LOG6[0]: Peer temporary key: X25519, 253 bits
2022.06.21 11:31:23 LOG6[0]: Session id: F098A4AEC33D35EE3571665029E41457BE5493D5C129C8F0F544248A68A66B47
2022.06.21 11:31:23 LOG6[0]: Session id: E1907AABD1160855B124CD2639E371277A504FD2292EA01CB4AB9EE6F414DDE8
2022.06.21 11:31:23 LOG5[1]: Service [server4] accepted connection from 127.0.0.1:62453
2022.06.21 11:31:23 LOG6[1]: failover: priority, starting at entry #0
2022.06.21 11:31:23 LOG6[1]: s_connect: connecting ip.ip.ip.ip:80
2022.06.21 11:31:23 LOG5[2]: Service [server4] accepted connection from 127.0.0.1:62455
2022.06.21 11:31:23 LOG6[2]: failover: priority, starting at entry #0
2022.06.21 11:31:23 LOG6[2]: s_connect: connecting ip.ip.ip.ip:80
2022.06.21 11:31:23 LOG5[1]: s_connect: connected ip.ip.ip.ip:80
2022.06.21 11:31:23 LOG5[1]: Service [server4] connected remote server from 192.168.1.100:62454
2022.06.21 11:31:23 LOG6[1]: SNI: sending servername: ip.ip.ip.ip
2022.06.21 11:31:23 LOG6[1]: Peer certificate required
2022.06.21 11:31:24 LOG5[2]: s_connect: connected ip.ip.ip.ip:80
2022.06.21 11:31:24 LOG5[2]: Service [server4] connected remote server from 192.168.1.100:62456
2022.06.21 11:31:24 LOG6[2]: SNI: sending servername: ip.ip.ip.ip
2022.06.21 11:31:24 LOG6[2]: Peer certificate required
2022.06.21 11:31:24 LOG6[1]: TLS connected: previous session reused
2022.06.21 11:31:24 LOG6[1]: TLSv1.3 ciphersuite: TLS_AES_256_GCM_SHA384 (256-bit encryption)
2022.06.21 11:31:24 LOG6[1]: Peer temporary key: X25519, 253 bits
2022.06.21 11:31:24 LOG6[1]: Session id: E1907AABD1160855B124CD2639E371277A504FD2292EA01CB4AB9EE6F414DDE8
2022.06.21 11:31:24 LOG6[1]: Read socket closed (readsocket)
2022.06.21 11:31:24 LOG6[1]: SSL_shutdown successfully sent close_notify alert
2022.06.21 11:31:24 LOG6[2]: TLS connected: previous session reused
2022.06.21 11:31:24 LOG6[2]: TLSv1.3 ciphersuite: TLS_AES_256_GCM_SHA384 (256-bit encryption)
2022.06.21 11:31:24 LOG6[2]: Peer temporary key: X25519, 253 bits
2022.06.21 11:31:24 LOG6[2]: Session id: E1907AABD1160855B124CD2639E371277A504FD2292EA01CB4AB9EE6F414DDE8
2022.06.21 11:31:24 LOG6[1]: Session id: 662356847A6AC360543E6B85687A11984354CD08CCD4945D0126775FEE5A786F
2022.06.21 11:31:24 LOG3[1]: SSL_read: ssl/record/rec_layer_s3.c:308: error:0A000126:SSL routines::unexpected eof while reading
2022.06.21 11:31:24 LOG5[1]: Connection reset: 3 byte(s) sent to TLS, 2 byte(s) sent to socket
2022.06.21 11:31:24 LOG6[2]: Session id: C669039CF828A7087E3AE5DFD9F84FBABEB39E89D0BE8F2B1313F5B478C3E003
2022.06.21 11:31:34 LOG6[2]: TLS closed (SSL_read)
keepeye
2022-06-21 11:38:03 +08:00
在用搬瓦工日本 gia ,比机场快还稳定,找 3 个人合租差不多也能打平机场价格
idblife
2022-06-21 11:59:10 +08:00
@datocp
看不懂,啥意思
wwqm2
2022-06-21 12:19:31 +08:00
JMS 我在两年前就几乎用不了了,后来买 VPS 自建,这两年一直很稳。
sadfQED2
2022-06-21 12:26:28 +08:00
传家宝 gia ,稳如老狗
liveoppo
2022-06-21 12:39:17 +08:00
非常有同感,非常不稳
wengang285
2022-06-23 14:56:13 +08:00
挂了啊,官网都上不去
FloatLost
2022-07-09 17:33:15 +08:00
@idblife 我也是,今年买了那个 HK 专线的,6 月开始就出问题,我观察了下,每次域名的 IP 好像是会变的,有部分 IP 是封了,所以导致时好时坏...
smallboy19991231
122 天前
@idblife 老哥你還在用 JMS 嗎合租嗎
idblife
122 天前
@smallboy19991231
还在用,不合租
smallboy19991231
122 天前
@keepeye 还在用 JMS 吗合租吗

这是一个专为移动设备优化的页面(即为了让你能够在 Google 搜索结果里秒开这个页面),如果你希望参与 V2EX 社区的讨论,你可以继续到 V2EX 上打开本讨论主题的完整版本。

https://www.v2ex.com/t/860945

V2EX 是创意工作者们的社区,是一个分享自己正在做的有趣事物、交流想法,可以遇见新朋友甚至新机会的地方。

V2EX is a community of developers, designers and creative people.

© 2021 V2EX