gtun客户端无法实现快速断线重连 #12
Description
cat /etc/gtund.yml
enable_auth: true
auths:
- access_token: "xxxxxxxxxxx"
expired_ath: 0
trace: ":3003"
server:
- listen: ":3002"
scheme: "kcp"
- listen: ":3002"
scheme: "mux"
- listen: ":4002"
scheme: "quic"
log:
days: 1
level: "debug"
path: "/tmp/gtund.log"
cat /etc/gtun.yaml
access_token: "xxxxxxxxxxx"
accelerator:
DATA1:
routes:
- scheme: "kcp"
server: "172.18.99.12:3002"
trace: "172.18.99.12:3003"
- scheme: "mux"
server: "172.18.99.12:3002"
trace: "172.18.99.12:3003"
- scheme: "quic"
server: "172.18.99.12:4002"
trace: "172.18.99.12:3003"
proxy:
tproxy_tcp: |
{
"read_timeout": 30,
"write_timeout": 30,
"listen_addr": ":8524"
}
tproxy_udp: |
{
"read_timeout": 30,
"write_timeout": 30,
"session_timeout": 30,
"listen_addr": ":8524"
}
log:
days: 1
level: debug
path: /root/gtun.log
把服务端kill掉之后 客户端断线，再把服务端起来之后，客户端还是断线状态，10分钟过去了还是一样
2024/09/04 13:34:25.008022 [W] [route.go:67] no best node for region[DATA1]
2024/09/04 13:34:25.008078 [W] [route.go:70] region[DATA1] use random hop
2024/09/04 13:34:25.008092 [D] [tproxy_tcp.go:141] 172.18.99.11:59380=>172.18.99.17:7931
2024/09/04 13:34:25.008111 [E] [tproxy_tcp.go:144] open stream fail: timeout: no recent network activity
2024/09/04 13:35:25.007885 [W] [route.go:67] no best node for region[DATA1]
2024/09/04 13:35:25.007956 [W] [route.go:70] region[DATA1] use random hop
2024/09/04 13:35:25.007965 [D] [tproxy_tcp.go:141] 172.18.99.11:60892=>172.18.99.17:7931
2024/09/04 13:35:25.007981 [E] [tproxy_tcp.go:144] open stream fail: timeout: no recent network activity
2024/09/04 13:35:59.802819 [D] [trace.go:128] region[DATA1] {172.18.99.12:3003 172.18.99.12:3002 kcp} loss 0 rtt 1 lossRank 50.0000 delayRank 50.0000 score 100.0000
2024/09/04 13:35:59.816353 [D] [trace.go:128] region[DATA1] {172.18.99.12:3003 172.18.99.12:3002 mux} loss 0 rtt 0 lossRank 50.0000 delayRank 0.0000 score 50.0000
2024/09/04 13:35:59.828266 [D] [trace.go:128] region[DATA1] {172.18.99.12:3003 172.18.99.12:4002 quic} loss 0 rtt 9223372036854775807 lossRank 50.0000 delayRank -12297829382472990.0000 score -12297829382472940.0000
2024/09/04 13:36:25.008042 [D] [route.go:60] region[DATA1] best node match kcp://172.18.99.12:3002
2024/09/04 13:36:25.008118 [D] [tproxy_tcp.go:141] 172.18.99.11:40780=>172.18.99.17:7931
2024/09/04 13:37:25.008204 [D] [route.go:60] region[DATA1] best node match kcp://172.18.99.12:3002
2024/09/04 13:37:25.008266 [D] [tproxy_tcp.go:141] 172.18.99.11:35776=>172.18.99.17:7931
2024/09/04 13:37:59.800208 [D] [trace.go:128] region[DATA1] {172.18.99.12:3003 172.18.99.12:3002 kcp} loss 0 rtt 9223372036854775807 lossRank 50.0000 delayRank -12297829382472990.0000 score -12297829382472940.0000
2024/09/04 13:37:59.811406 [D] [trace.go:128] region[DATA1] {172.18.99.12:3003 172.18.99.12:3002 mux} loss 0 rtt 9223372036854775807 lossRank 50.0000 delayRank -12297829382472990.0000 score -12297829382472940.0000
2024/09/04 13:37:59.822759 [D] [trace.go:128] region[DATA1] {172.18.99.12:3003 172.18.99.12:4002 quic} loss 0 rtt 9223372036854775807 lossRank 50.0000 delayRank -12297829382472990.0000 score -12297829382472940.0000
2024/09/04 13:38:25.007983 [W] [route.go:67] no best node for region[DATA1]
2024/09/04 13:38:25.008034 [W] [route.go:70] region[DATA1] use random hop
2024/09/04 13:38:25.008042 [D] [tproxy_tcp.go:141] 172.18.99.11:42950=>172.18.99.17:7931
2024/09/04 13:38:25.008061 [E] [tproxy_tcp.go:144] open stream fail: timeout: no recent network activity