openwrt-passwall
openwrt-passwall copied to clipboard
xiaorouji
[Bug]: 使用 ss-rust 节点不能正常访问谷歌
描述您遇到的bug
我用几个 ss-rust 节点开启负载均衡，谷歌不能访问（tg 可以，youtube、v2ex、GitHub 等不行），谷歌连接测试显示 “连接失败”。 单独使用 ss-rust 节点可以正常访问谷歌（youtube、v2ex、tg 、GitHub可以），但有时不能正常访问，谷歌连接偶尔测试显示 “连接失败”。 TCP 节点日志里出现了错误，我截取相关日志（对 IP 进行了打码）。 TCP/UDP 默认代理模式：中国列表以外
复现此Bug的步骤
1.负载均衡添加 ss-rust 节点。 2.开启负载均衡。 3.添加负载均衡节点。 4.使用 ss-rust 负载均衡节点开启passwall。
您想要实现的目的
解决这个问题，或者指出我的错误操作。
日志信息
[shadowsocks_service::local::net::udp::association] 2333:45004 -> 8.8.4.4:53 (proxied) sending 29 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:24.525848701+00:00 DEBUG [21867:140153589500704] [shadowsocks_service::local::net::udp::association] 2333:37408 -> 8.8.4.4:53 (proxied) sending 29 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:24.525945982+00:00 DEBUG [21867:140153593719584] [shadowsocks_service::local::net::udp::association] 2333:55372 -> 8.8.4.4:53 (proxied) sending 29 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:24.572870244+00:00 DEBUG [21867:140153589500704] [shadowsocks_service::local::net::udp::association] 2333:33979 -> 8.8.4.4:53 (proxied) sending 33 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:24.863564015+00:00 DEBUG [21867:140153595829024] [shadowsocks_service::local::net::udp::association] 2333:33979 -> 8.8.4.4:53 (proxied) sending 35 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:25.517171189+00:00 DEBUG [21867:140153589500704] [shadowsocks_service::local::net::udp::association] 2333:49585 -> 8.8.4.4:53 (proxied) sending 28 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:25.517439928+00:00 DEBUG [21867:140153589500704] [shadowsocks_service::local::net::udp::association] 2333:35540 -> 8.8.4.4:53 (proxied) sending 28 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:25.517610414+00:00 DEBUG [21867:140153595829024] [shadowsocks_service::local::net::udp::association] 2333:54174 -> 8.8.4.4:53 (proxied) sending 28 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:26.892706156+00:00 DEBUG [21867:140153593719584] [shadowsocks_service::local::net::udp::association] 2333:33979 -> 8.8.4.4:53 (proxied) sending 35 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:26.893046549+00:00 DEBUG [21867:140153593719584] [shadowsocks_service::local::net::udp::association] 2333:33979 -> 8.8.4.4:53 (proxied) sending 35 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:27.150097832+00:00 DEBUG [21867:140153593719584] [shadowsocks_service::local::net::udp::association] 2333:33979 -> 8.8.4.4:53 (proxied) sending 32 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:28.590763929+00:00 DEBUG [21867:140153589500704] [shadowsocks_service::local::net::udp::association] 2333:55372 -> 8.8.4.4:53 (proxied) sending 29 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:28.590959621+00:00 DEBUG [21867:140153589500704] [shadowsocks_service::local::net::udp::association] 2333:45004 -> 8.8.4.4:53 (proxied) sending 29 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:28.611984532+00:00 DEBUG [21867:140153589500704] [shadowsocks_service::local::net::udp::association] 2333:33979 -> 8.8.4.4:53 (proxied) sending 33 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:28.684407359+00:00 DEBUG [21867:140153593719584] [shadowsocks_service::local::net::udp::association] 2333:33979 -> 8.8.4.4:53 (proxied) sending 33 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:28.923622332+00:00 DEBUG [21867:140153595829024] [shadowsocks_service::local::net::udp::association] 2333:33979 -> 8.8.4.4:53 (proxied) sending 35 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:29.001595633+00:00 DEBUG [21867:140153589500704] [shadowsocks_service::local::net::udp::association] 2333:33979 -> 8.8.4.4:53 (proxied) sending 35 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:29.573533809+00:00 DEBUG [21867:140153589500704] [shadowsocks_service::local::net::udp::association] 2333:54174 -> 8.8.4.4:53 (proxied) sending 28 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:29.573702624+00:00 DEBUG [21867:140153593719584] [shadowsocks_service::local::net::udp::association] 2333:49585 -> 8.8.4.4:53 (proxied) sending 28 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:29.652092009+00:00 DEBUG [21867:140153589500704] [shadowsocks_service::local::net::udp::association] 2333:55372 -> 8.8.4.4:53 (proxied) sending 29 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:29.652342240+00:00 DEBUG [21867:140153589500704] [shadowsocks_service::local::net::udp::association] 2333:45004 -> 8.8.4.4:53 (proxied) sending 29 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:29.652637666+00:00 DEBUG [21867:140153589500704] [shadowsocks_service::local::net::udp::association] 2333:33979 -> 8.8.4.4:53 (proxied) sending 32 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:29.652957741+00:00 DEBUG [21867:140153589500704] [shadowsocks_service::local::net::udp::association] 2333:33979 -> 8.8.4.4:53 (proxied) sending 32 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:29.684348978+00:00 DEBUG [21867:140153595829024] [shadowsocks_service::local::net::udp::association] 2333:33979 -> 8.8.4.4:53 (proxied) sending 33 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:30.001546154+00:00 DEBUG [21867:140153589500704] [shadowsocks_service::local::net::udp::association] 2333:33979 -> 8.8.4.4:53 (proxied) sending 35 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:30.648162881+00:00 DEBUG [21867:140153595829024] [shadowsocks_service::local::net::udp::association] 2333:54174 -> 8.8.4.4:53 (proxied) sending 28 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:30.648329014+00:00 DEBUG [21867:140153589500704] [shadowsocks_service::local::net::udp::association] 2333:49585 -> 8.8.4.4:53 (proxied) sending 28 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:31.667840566+00:00 DEBUG [21867:140153593719584] [shadowsocks_service::local::net::udp::association] 2333:45004 -> 8.8.4.4:53 (proxied) sending 29 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:31.668028776+00:00 DEBUG [21867:140153589500704] [shadowsocks_service::local::net::udp::association] 2333:55372 -> 8.8.4.4:53 (proxied) sending 29 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:31.699534229+00:00 DEBUG [21867:140153595829024] [shadowsocks_service::local::net::udp::association] 2333:33979 -> 8.8.4.4:53 (proxied) sending 33 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:31.699886470+00:00 DEBUG [21867:140153595829024] [shadowsocks_service::local::net::udp::association] 2333:33979 -> 8.8.4.4:53 (proxied) sending 33 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:32.017041329+00:00 DEBUG [21867:140153595829024] [shadowsocks_service::local::net::udp::association] 2333:33979 -> 8.8.4.4:53 (proxied) sending 35 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:32.017481238+00:00 DEBUG [21867:140153595829024] [shadowsocks_service::local::net::udp::association] 2333:33979 -> 8.8.4.4:53 (proxied) sending 35 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:32.295211663+00:00 DEBUG [21867:140153595829024] [shadowsocks_service::local::net::udp::association] 2333:33979 -> 8.8.4.4:53 (proxied) sending 32 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:32.295431703+00:00 DEBUG [21867:140153595829024] [shadowsocks_service::local::net::udp::association] 2333:33979 -> 8.8.4.4:53 (proxied) sending 32 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:32.654774610+00:00 DEBUG [21867:140153589500704] [shadowsocks_service::local::net::udp::association] 2333:54174 -> 8.8.4.4:53 (proxied) sending 28 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:32.654945200+00:00 DEBUG [21867:140153593719584] [shadowsocks_service::local::net::udp::association] 2333:49585 -> 8.8.4.4:53 (proxied) sending 28 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:34.797295480+00:00 DEBUG [21867:140153595829024] [shadowsocks_service::local::net::udp::association] 2333:33979 -> 8.8.4.4:53 (proxied) sending 32 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:34.797529289+00:00 DEBUG [21867:140153595829024] [shadowsocks_service::local::net::udp::association] 2333:33979 -> 8.8.4.4:53 (proxied) sending 32 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:35.681636809+00:00 DEBUG [21867:140153593719584] [shadowsocks_service::local::net::udp::association] 2333:55372 -> 8.8.4.4:53 (proxied) sending 29 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:35.681838986+00:00 DEBUG [21867:140153595829024] [shadowsocks_service::local::net::udp::association] 2333:45004 -> 8.8.4.4:53 (proxied) sending 29 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:35.688933297+00:00 DEBUG [21867:140153589500704] [shadowsocks_service::local::net::udp::association] created udp association for 2333:35787 2023-04-12T12:55:35.713037065+00:00 DEBUG [21867:140153589500704] [shadowsocks_service::local::net::udp::association] 2333:33979 -> 8.8.4.4:53 (proxied) sending 33 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:35.713448069+00:00 DEBUG [21867:140153589500704] [shadowsocks_service::local::net::udp::association] 2333:33979 -> 8.8.4.4:53 (proxied) sending 33 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:36.027196813+00:00 DEBUG [21867:140153589500704] [shadowsocks_service::local::net::udp::association] 2333:33979 -> 8.8.4.4:53 (proxied) sending 35 bytes failed, error: Connection refused (os error 111) 2023-04-12T12:55:36.027593528+00:00 DEBUG [21867:140153589500704] [shadowsocks_service::local::net::udp::association] 2333:33979 -> 8.8.4.4:53 (proxied) sending 35 bytes failed, error: Connection refused (os error 111)
2023-04-12T13:23:11.048295254+00:00 DEBUG [29697:140159268498208] [shadowsocks_service::local::net::udp::association] udp association for 2333:43949 is closed 2023-04-12T13:23:22.682607312+00:00 DEBUG [29697:140159262169888] [shadowsocks_service::local::utils] established tcp tunnel 2333:52644 <-> 5666:80 through sever 7888:10004 (outbound: 120.241.255.171:10004) 2023-04-12T13:23:24.134196396+00:00 DEBUG [29697:140159262169888] [shadowsocks_service::local::net::udp::association] created udp association for 2333:35280 2023-04-12T13:23:24.134884485+00:00 DEBUG [29697:140159262169888] [shadowsocks_service::local::net::udp::association] created udp association for 2333:35940 2023-04-12T13:23:24.135007140+00:00 DEBUG [29697:140159262169888] [shadowsocks_service::local::net::udp::association] created udp association for 2333:59419
2023-04-12T13:24:31.264771433+00:00 DEBUG [29697:140159266388768] [shadowsocks_service::local::net::udp::association] udp association for 2333:60090 is closed 2023-04-12T13:24:31.264952080+00:00 DEBUG [29697:140159262169888] [shadowsocks_service::local::net::udp::association] udp association for 2333:33880 is closed 2023-04-12T13:24:38.215174012+00:00 DEBUG [29697:140159266388768] [shadowsocks_service::local::net::udp::association] udp association for 2333:35443 is closed 2023-04-12T13:24:38.469040492+00:00 DEBUG [29697:140159268498208] [shadowsocks_service::local::net::udp::association] created udp association for 2333:40788
截图
系统相关信息
-passwall 版本：4.63-1（commits ef58085999b55636339f0b60556ea35ba4a06960） -浏览器：chrome 111.0.5563.147（正式版本） （64 位）
其他信息
No response
使用 trojan 节点做负载均衡或者单独使用 trojan 节点的时候访问外网也会不正常。使用的是（trojan-plus）
日志： Trojan Plus v10.0.3 starts. [2023-04-12 22:40:23] [FATAL] trojan plus service (nat) started at 0.0.0.0:1041
我今天重新进行了测试。使用 TCP 去请求 DNS，结果还是一样。现在负载均衡运行不了了，重启也一样。 节点日志如下： 2023-04-18T12:49:29.083675765+00:00 DEBUG [24513:140413818653472] [shadowsocks_service::local::redir::tcprelay] TCP redirect client, error: Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" } 2023-04-18T12:49:29.265239117+00:00 DEBUG [24513:140413818653472] [shadowsocks_service::local::utils] established tcp tunnel 192.168.99.172:46300 <-> 手工打码:443 through sever 120.241.255.171:10004 (outbound: 120.241.255.171:10004) 2023-04-18T12:49:29.501625764+00:00 DEBUG [24513:140413816544032] [shadowsocks_service::local::net::udp::association] created udp association for 192.168.99.206:51118 2023-04-18T12:49:29.501730935+00:00 DEBUG [24513:140413816544032] [shadowsocks_service::local::net::udp::association] created udp association for 192.168.99.206:51119 2023-04-18T12:49:29.615226617+00:00 DEBUG [24513:140413812325152] [shadowsocks_service::local::utils] established tcp tunnel 192.168.99.206:63076 <-> 手工打码:443 through sever 120.241.255.171:10004 (outbound: 120.241.255.171:10004) 2023-04-18T12:49:29.615477733+00:00 DEBUG [24513:140413814434592] [shadowsocks_service::local::utils] established tcp tunnel 192.168.99.206:63079 <-> 手工打码:80 through sever 120.241.255.171:10004 (outbound: 120.241.255.171:10004) 2023-04-18T12:49:29.616811442+00:00 DEBUG [24513:140413818653472] [shadowsocks_service::local::utils] established tcp tunnel 192.168.99.206:63078 <-> 手工打码:80 through sever 120.241.255.171:10004 (outbound: 120.241.255.171:10004) 2023-04-18T12:49:29.619028153+00:00 DEBUG [24513:140413818653472] [shadowsocks_service::local::utils] established tcp tunnel 192.168.99.206:63077 <-> 手工打码:443 through sever 120.241.255.171:10004 (outbound: 120.241.255.171:10004) 2023-04-18T12:49:29.827466578+00:00 DEBUG [24513:140413814434592] [shadowsocks_service::local::utils] established tcp tunnel 192.168.99.206:63082 <-> 手工打码:443 through sever 120.241.255.171:10004 (outbound: 120.241.255.171:10004) 2023-04-18T12:49:29.827715915+00:00 DEBUG [24513:140413814434592] [shadowsocks_service::local::utils] established tcp tunnel 192.168.99.172:46302 <-> 手工打码:443 through sever 120.241.255.171:10004 (outbound: 120.241.255.171:10004) 2023-04-18T12:49:29.828800029+00:00 DEBUG [24513:140413814434592] [shadowsocks_service::local::utils] established tcp tunnel 192.168.99.206:63083 <-> 手工打码:80 through sever 120.241.255.171:10004 (outbound: 120.241.255.171:10004) 2023-04-18T12:49:30.306115402+00:00 DEBUG [24513:140413818653472] [shadowsocks_service::local::net::udp::association] created udp association for 手工打码:38687 2023-04-18T12:49:30.515713011+00:00 DEBUG [24513:140413814434592] [shadowsocks_service::local::net::udp::association] created udp association for 192.168.99.206:54924 2023-04-18T12:49:30.837182257+00:00 DEBUG [24513:140413814434592] [shadowsocks_service::local::utils] established tcp tunnel 手工打码:56508 <-> 手工打码:80 through sever 120.241.255.171:10004 (outbound: 120.241.255.171:10004) 2023-04-18T12:49:30.837449+00:00 DEBUG [24513:140413814434592] [shadowsocks_service::local::redir::tcprelay] TCP redirect client, error: Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" } 2023-04-18T12:49:30.838651469+00:00 DEBUG [24513:140413814434592] [shadowsocks_service::local::utils] established tcp tunnel 手工打码:51154 <-> 手工打码:80 through sever 120.241.255.171:10004 (outbound: 120.241.255.171:10004) 2023-04-18T12:49:30.838838671+00:00 DEBUG [24513:140413814434592] [shadowsocks_service::local::redir::tcprelay] TCP redirect client, error: Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" } 2023-04-18T12:49:30.839302251+00:00 DEBUG [24513:140413818653472] [shadowsocks_service::local::utils] established tcp tunnel 手工打码:34566 <-> 手工打码:80 through sever 120.241.255.171:10004 (outbound: 120.241.255.171:10004) 2023-04-18T12:49:30.839636899+00:00 DEBUG [24513:140413818653472] [shadowsocks_service::local::redir::tcprelay] TCP redirect client, error: Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" } 2023-04-18T12:49:32.387081135+00:00 DEBUG [24513:140413814434592] [shadowsocks_service::local::utils] established tcp tunnel 192.168.99.206:63108 <-> 手工打码:443 through sever 120.241.255.171:10004 (outbound: 120.241.255.171:10004) 2023-04-18T12:49:32.661758221+00:00 DEBUG [24513:140413818653472] [shadowsocks_service::local::utils] established tcp tunnel 192.168.99.172:46304 <-> 手工打码:443 through sever 120.241.255.171:10004 (outbound: 120.241.255.171:10004)
emmmmm.这个东西很久之前我提过，不过没被关注，之前我以为是ss-local的问题（我以为复用了shadowsocks的ss-loca），后来发现是服务商的问题......你试试看开xray的分流套这个是不是就没有问题了。
我重写编译固件，负载均衡能正常运行，其他的还是一样。节点是 ss，使用 ss-rust，几个 ss 节点进行负载均衡，使用 ssrp 跑负载均衡节点倒是正常。
使用 ssrp 代理一次之后，passwal 现在貌似正常了。 日志如下（节点地址和域名已打码）： 2023-04-24 16:26:03: 执行启动延时 1 秒后再启动! 2023-04-24 16:26:07: 清空并关闭相关程序和缓存完成。 2023-04-24 16:26:07: HAPROXY 负载均衡... 2023-04-24 16:26:07: + 入口 0.0.0.0:1181... 2023-04-24 16:26:07: | - 出口节点：110.23.21.31:10001，权重：5 2023-04-24 16:26:07: | - 出口节点：110.23.21.31:10002，权重：5 2023-04-24 16:26:07: | - 出口节点：110.23.21.31:10003，权重：5 2023-04-24 16:26:07: | - 出口节点：110.23.21.31:10004，权重：5 2023-04-24 16:26:07: | - 出口节点：110.23.21.31:10005，权重：5 2023-04-24 16:26:07: | - 出口节点：110.23.21.31:10006，权重：5 2023-04-24 16:26:07: | - 出口节点：150.123.201.131:10007，权重：5 2023-04-24 16:26:07: | - 出口节点：150.123.201.131:10008，权重：5 2023-04-24 16:26:07: | - 出口节点：150.123.201.131:10009，权重：5 2023-04-24 16:26:07: | - 出口节点：150.123.201.131:10010，权重：5 2023-04-24 16:26:07: + 入口 0.0.0.0:1182... 2023-04-24 16:26:07: | - 出口节点：www.xxoo.com:10021，权重：5 2023-04-24 16:26:07: | - 出口节点：www.xxoo.com:10022，权重：5 2023-04-24 16:26:07: | - 出口节点：www.xxoo.com:10023，权重：5 2023-04-24 16:26:07: | - 出口节点：www.xxoo.com:10024，权重：5 2023-04-24 16:26:07: | - 出口节点：www.xxoo.com:10025，权重：5 2023-04-24 16:26:07: + 入口 0.0.0.0:1183... 2023-04-24 16:26:07: | - 出口节点：js.xxoo.com:10031，权重：5 2023-04-24 16:26:07: | - 出口节点：js.xxoo.com:10032，权重：5 2023-04-24 16:26:07: | - 出口节点：js.xxoo.com:10033，权重：5 2023-04-24 16:26:07: | - 出口节点：js.xxoo.com:10034，权重：5 2023-04-24 16:26:07: | - 出口节点：js.xxoo.com:10035，权重：5 2023-04-24 16:26:07: + 入口 0.0.0.0:1184... 2023-04-24 16:26:07: | - 出口节点：js.xxoo.com:10051，权重：5 2023-04-24 16:26:07: | - 出口节点：js.xxoo.com:10052，权重：5 2023-04-24 16:26:07: | - 出口节点：js.xxoo.com:10053，权重：5 2023-04-24 16:26:07: | - 出口节点：js.xxoo.com:10054，权重：5 2023-04-24 16:26:07: | - 出口节点：js.xxoo.com:10055，权重：5 2023-04-24 16:26:07: * 控制台端口：1188 2023-04-24 16:26:07: 运行完成！
2023-04-24 16:27:23: 清空并关闭相关程序和缓存完成。 2023-04-24 16:27:23: HAPROXY 负载均衡... 2023-04-24 16:27:23: + 入口 0.0.0.0:1181... 2023-04-24 16:27:23: | - 出口节点：110.23.21.31:10001，权重：5 2023-04-24 16:27:23: | - 出口节点：110.23.21.31:10002，权重：5 2023-04-24 16:27:23: | - 出口节点：110.23.21.31:10003，权重：5 2023-04-24 16:27:23: | - 出口节点：110.23.21.31:10004，权重：5 2023-04-24 16:27:23: | - 出口节点：110.23.21.31:10005，权重：5 2023-04-24 16:27:23: | - 出口节点：110.23.21.31:10006，权重：5 2023-04-24 16:27:23: | - 出口节点：150.123.201.131:10007，权重：5 2023-04-24 16:27:23: | - 出口节点：150.123.201.131:10008，权重：5 2023-04-24 16:27:23: | - 出口节点：150.123.201.131:10009，权重：5 2023-04-24 16:27:23: | - 出口节点：150.123.201.131:10010，权重：5 2023-04-24 16:27:23: + 入口 0.0.0.0:1182... 2023-04-24 16:27:23: | - 出口节点：www.xxoo.com:10021，权重：5 2023-04-24 16:27:23: | - 出口节点：www.xxoo.com:10022，权重：5 2023-04-24 16:27:23: | - 出口节点：www.xxoo.com:10023，权重：5 2023-04-24 16:27:23: | - 出口节点：www.xxoo.com:10024，权重：5 2023-04-24 16:27:23: | - 出口节点：www.xxoo.com:10025，权重：5 2023-04-24 16:27:23: + 入口 0.0.0.0:1183... 2023-04-24 16:27:23: | - 出口节点：js.xxoo.com:10031，权重：5 2023-04-24 16:27:23: | - 出口节点：js.xxoo.com:10032，权重：5 2023-04-24 16:27:23: | - 出口节点：js.xxoo.com:10033，权重：5 2023-04-24 16:27:23: | - 出口节点：js.xxoo.com:10034，权重：5 2023-04-24 16:27:23: | - 出口节点：js.xxoo.com:10035，权重：5 2023-04-24 16:27:23: + 入口 0.0.0.0:1184... 2023-04-24 16:27:23: | - 出口节点：js.xxoo.com:10051，权重：5 2023-04-24 16:27:23: | - 出口节点：js.xxoo.com:10052，权重：5 2023-04-24 16:27:23: | - 出口节点：js.xxoo.com:10053，权重：5 2023-04-24 16:27:23: | - 出口节点：js.xxoo.com:10054，权重：5 2023-04-24 16:27:23: | - 出口节点：js.xxoo.com:10055，权重：5 2023-04-24 16:27:23: * 控制台端口：1188 2023-04-24 16:27:23: TCP节点：[xsus-负载均衡-香港]，监听端口：1041 2023-04-24 16:27:24: 过滤服务配置：准备接管域名解析... 2023-04-24 16:27:24: - 域名解析：dns2tcp + 使用(TCP节点)解析域名... 2023-04-24 16:27:24: * 请确认上游 DNS 支持 TCP 查询，如非直连地址，确保 TCP 代理打开，并且已经正确转发！ 2023-04-24 16:27:24: | - (chinadns-ng) 最高支持4级域名过滤... 2023-04-24 16:27:24: + 过滤服务：ChinaDNS-NG(:15354)：国内DNS：120.196.165.7，可信DNS：127.0.0.1#15353 2023-04-24 16:27:24: - 节点列表中的域名(vpsiplist)：120.196.165.7 2023-04-24 16:27:24: - 域名白名单(whitelist)：120.196.165.7 2023-04-24 16:27:24: - 代理域名表(blacklist)：127.0.0.1#15353 2023-04-24 16:27:24: - 防火墙域名表(gfwlist)：默认 2023-04-24 16:27:24: - 中国域名表(chnroute)：默认 2023-04-24 16:27:24: - 以上所列以外及默认：127.0.0.1#15354 2023-04-24 16:27:24: - PassWall必须依赖于Dnsmasq，如果你自行配置了错误的DNS流程，将会导致域名(直连/代理域名)分流失效！！！ 2023-04-24 16:27:24: 开始加载防火墙规则... 2023-04-24 16:27:24: 加入负载均衡的节点到ipset[vpsiplist]直连完成 2023-04-24 16:27:24: 加入所有节点到ipset[vpsiplist]直连完成 2023-04-24 16:27:25: 加载路由器自身 TCP 代理... 2023-04-24 16:27:25: - [0]将上游 DNS 服务器 8.8.4.4:53 加入到路由器自身代理的 TCP 转发链 2023-04-24 16:27:25: - [0]，屏蔽代理UDP 端口：80,443 2023-04-24 16:27:25: 加载路由器自身 UDP 代理... 2023-04-24 16:27:25: TCP默认代理：使用TCP节点[xsus-负载均衡-香港] 中国列表以外代理所有端口 2023-04-24 16:27:25: UDP默认代理：使用UDP节点[xsus-负载均衡-香港] 中国列表以外代理所有端口 2023-04-24 16:27:25: 防火墙规则加载完成！ 2023-04-24 16:27:28: 重启 dnsmasq 服务 2023-04-24 16:27:28: 配置定时任务：自动更新【xsus】订阅。 2023-04-24 16:27:28: 运行完成！
节点日志里还是出现错误。 2023-04-24T11:39:50.047509782+00:00 DEBUG [10142:140214920043296] [shadowsocks_service::local::redir::tcprelay] TCP redirect client, error: Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" } 2023-04-24T11:39:50.047629381+00:00 DEBUG [10142:140214917933856] [shadowsocks_service::local::utils] established tcp tunnel 10.97.19.34:48028 <-> 140.82.114.26:80 through sever 127.0.0.1:1181 (outbound: 127.0.0.1:1181)
现在是 Passwall 能正常使用（大概？）。如果我使用 AdguardHome 则会不能正常访问谷歌（重定向端口模式，谷歌访问测试能通过，浏览器不能访问谷歌。Dnsmasq 上游模式，谷歌访问测试不通过，浏览器能访问谷歌），AdguardHome 的上游是 Smartdns，Smartdns 的上游是几个国内的 DNS 和几个国外的 DNS，这个模式在之前的版本能用。难道是 AdguardHome 的问题？
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
我现在4.66也还是有这个问题。。主要是提示证书安全问题 类似：https://www.right.com.cn/forum/thread-3772992-1-1.html
