Files
ykxmz/_build/check_try_cloudflare.sh
T
xmz7891 b705216e4a ykxmz 1.5.0锛氫慨澶嶆墜琛ㄧ TLS 璇佷功鏍¢獙 + MTU 淇缃戠粶绋冲畾鎬?
琚帶绔?- 淇 MTU 闂锛氬す MSS + 璺緞 MTU 鎺㈡祴锛堝叕缃戝彲鐢ㄧ巼 48% -> 100%锛?- 澶嶇敤 HTTP 杩炴帴锛堝厤鎺夋瘡娆℃柊寤?TLS 鐨?30% 鎻℃墜澶辫触锛?- 姣忓垎閽熷洖澶存壘灞€鍩熺綉锛岃嚜鍔ㄥ垏鍥炲揩 400 鍊嶇殑璺緞
- 鐢婚潰蹇冭烦甯э細闈欐鏃剁渷娴侀噺锛屽鎴风浠嶇煡閬撴祦鏄椿鐨?- 閿佸睆鏃剁粰鍑哄彲鎿嶄綔鐨勬彁绀?
鎵嬭〃绔?- 鍐呯疆 GTS Root R4 / GlobalSign Root CA锛屼慨 SSLHandshakeException
- 杩炴帴閿欒缈昏瘧鎴愪汉璇濓紙璇佷功/鏃堕棿/瑙f瀽/瓒呮椂鍒嗗埆鎻愮ず锛?- 缁忎腑杞繛涓婂悗鐢ㄦ湇鍔″櫒鎶ョ殑鍦板潃鍒锋柊宸查厤瀵硅褰?- 鏂板灞€鍩熺綉杩炴帴椤甸潰銆佹湇鍔″櫒寤惰繜妫€娴?
鏈嶅姟鍣ㄧ
- 鏀寔 chunked 璇锋眰浣擄紙淇瘡 16 绉掍竴娆$殑杩炴帴閿欎贡涓庡ぇ闈㈢Н 502锛?- 缃戠粶璋冧紭鑴氭湰 net-tune.sh锛堝紑鏈鸿嚜鍔ㄥ簲鐢級
- 绠$悊椤碉細鎵归噺鍒犻櫎銆佺綉缁滀綋妫€銆佷笅杞藉尯
- 闅ч亾鏀?HTTP/2 + 鍙岃繛鎺?
鏂囨。
- 璁稿彲鍗忚 / 瀹夎鍓嶅繀璇?/ 瀹夎鍚庨』鐭ワ紙浣滆€咃細灏忛害瀛愶級
2026-10-06 19:01:05 +08:00

87 lines
3.2 KiB
Bash

#!/bin/bash
# 查 api.trycloudflare.com 是不是也被 DNS 劫持了。
#
# 隧道一直在报:
# Post "https://api.trycloudflare.com/tunnel": context deadline exceeded
# 而我们刚刚才发现 api.cloudflare.com 被劫持到 141.193.154.210。
# 很可能同一个劫持设备把 trycloudflare 也劫了 —— 那才是隧道时好时坏的真正原因。
set -u
echo "===== 1. 解析结果 ====="
for host in api.trycloudflare.com trycloudflare.com api.cloudflare.com; do
V4=$(getent ahostsv4 "$host" 2>/dev/null | awk 'NR==1{print $1}')
printf " %-26s -> %s\n" "$host" "${V4:-解析不出来}"
done
echo
echo "===== 2. 这个 IP 是不是 Cloudflare 的 ====="
check_ip() {
case "$1" in
104.16.*|104.17.*|104.18.*|104.19.*|104.20.*|104.21.*|172.64.*|172.66.*|172.67.*|162.159.*|188.114.*|141.193.*)
if [ "${1#141.193.}" != "$1" ]; then
echo " ✗ $1 是 141.193 网段 —— 疑似运营商劫持设备"
else
echo " ✓ $1 是 Cloudflare 网段"
fi
;;
*) echo " ? $1 不属于已知的 Cloudflare 网段" ;;
esac
}
for host in api.trycloudflare.com api.cloudflare.com; do
V4=$(getent ahostsv4 "$host" 2>/dev/null | awk 'NR==1{print $1}')
echo " $host:"
[ -n "$V4" ] && check_ip "$V4"
done
echo
echo "===== 3. 实测连不连得上 ====="
for host in api.trycloudflare.com api.cloudflare.com; do
echo " --- $host ---"
timeout 15 curl -4 -v -o /dev/null "https://$host" 2>&1 \
| grep -E 'Trying|Connected|self-signed|SSL certificate|HTTP/' \
| head -4 | sed 's/^/ /'
done
echo
echo "===== 4. 找 api.trycloudflare.com 的真实 IP ====="
echo " 用公共 DNS 查(绕开本地劫持):"
for dns in 1.1.1.1 8.8.8.8; do
echo " 经 $dns:"
timeout 8 nslookup api.trycloudflare.com "$dns" 2>/dev/null \
| grep -A6 'Name:' | grep -E 'Address' | head -4 | sed 's/^/ /'
done
echo
echo "===== 5. 用真实 IP 试着连 ====="
# trycloudflare 和 cloudflare 走同一套边缘,用已知真实 IP 试
for ip in 104.16.132.229 104.17.0.1; do
C=$(timeout 10 curl -4 -s -o /dev/null -w '%{http_code}' \
--resolve "api.trycloudflare.com:443:$ip" \
https://api.trycloudflare.com/ 2>/dev/null)
printf " 经 %-16s -> %s\n" "$ip" "${C:-超时}"
done
echo
echo "===== 6. 结论 ====="
TRY_IP=$(getent ahostsv4 api.trycloudflare.com 2>/dev/null | awk 'NR==1{print $1}')
case "$TRY_IP" in
141.193.*)
echo " ✗ api.trycloudflare.com 也被劫持到 $TRY_IP"
echo " → 这就是隧道一直 context deadline exceeded 的真正原因"
echo " → 修法:同样的 hosts 钉 IP"
;;
"")
echo " ✗ 解析不出来"
;;
*)
echo " api.trycloudflare.com 解析到 $TRY_IP"
C=$(timeout 10 curl -4 -s -o /dev/null -w '%{http_code}' https://api.trycloudflare.com/ 2>/dev/null)
echo " 实测 HTTP ${C:-超时}"
if [ "${C:-000}" = "000" ]; then
echo " → 连不上。可能也是劫持,或者被限流"
else
echo " → 能连上,那隧道失败是 Cloudflare 侧限流"
fi
;;
esac