Useful or not, from you.
kcptun broken pipe的原因可能有哪些,这样大家都可以尽量避免

#tail -f /var/log/kcptun/server.log 2019/04/12 23:14:08 remote address: 223.xx.xx.xx:16127 2019/04/12 23:14:15 broken pipe 2019/04/12 23:14:15 broken pipe 2019/04/12 23:14:24 broken pipe 2019/04/12 23:14:24 broken pipe 2019/04/12 23:14:25 broken pipe 2019/04/12 23:14:38 broken pipe 2019/04/12 23:14:58 remote address: 223.xx.xx.xx:16293 2019/04/12 23:15:05 remote address: 223.xx.xx.xx:16316 2019/04/12 23:15:13 remote address: 223.xx.xx.xx:16329 2019/04/12 23:15:22 remote address: 223.xx.xx.xx:16355 2019/04/12 23:15:25 remote address: 223.xx.xx.xx:16360 2019/04/12 23:15:27 remote address: 223.xx.xx.xx:16367 2019/04/12 23:15:28 broken pipe 2019/04/12 23:15:35 remote address: 223.xx.xx.xx:16381 2019/04/12 23:15:35 broken pipe 2019/04/12 23:15:38 remote address: 223.xx.xx.xx:15363 2019/04/12 23:15:38 broken pipe 2019/04/12 23:15:43 broken pipe 2019/04/12 23:15:52 broken pipe 2019/04/12 23:15:57 broken pipe 2019/04/12 23:16:05 broken pipe 2019/04/12 23:16:35 remote address: 223.xx.xx.xx:15551 2019/04/12 23:16:54 remote address: 223.xx.xx.xx:15653 2019/04/12 23:17:09 remote address: 223.xx.xx.xx:15751 2019/04/12 23:17:17 remote address: 223.xx.xx.xx:15812 2019/04/12 23:17:24 broken pipe 2019/04/12 23:17:25 broken pipe 2019/04/12 23:17:30 broken pipe 2019/04/12 23:17:37 remote address: 223.xx.xx.xx:16096 2019/04/12 23:17:39 broken pipe 2019/04/12 23:17:42 remote address: 223.xx.xx.xx:16009 2019/04/12 23:17:47 broken pipe 2019/04/12 23:18:07 broken pipe

出现broken pipe后,感觉就象是被服务器reset了连接一样,页面中的某些元素就打不开了(例如图片就加载失败)。 客户端(win10 移动宽带200M): "client_windows_amd64.exe" -l 127.0.0.1:9527 -r 192.xx.xx.xx:21 -key "xxxxx" -crypt salsa20 -nocomp -datashard 5 -parityshard 5 -mtu 1350 -sndwnd 512 -rcvwnd 1024 -mode fast3

服务器端(centos7,墙外,1Gbps): { "listen": ":21", "target": "127.0.0.1:23", "key": " xxxxx", "crypt": "salsa20", "mode": "fast3", "mtu": 1350, "sndwnd": 1024, "rcvwnd": 512, "datashard": 5, "parityshard": 5, "nocomp": true, "quiet": true, "pprof": false }

在油管看视频一卡一卡的,实测速度还不如直接用SS。显然,很可能是因为我的参数设置问题,"broken pipe“应该只是个悲伤的结果。

所以,请教一下,有哪些可能会导致”broken pipe“(当然,QOS也是可能的原因,但这个我们不可控,所以我已经是在凌晨或深夜做的测试,测试前至少4小时内没开Kcpdun等大流量UDP应用。)

That's a useful answer
Without any help

autoexpire and scavengettl left as default, checkout logs below:

2019/04/17 10:30:21 version: 20190416
2019/04/17 10:30:21 initiating key derivation
2019/04/17 10:30:21 listening on: [::]:61000
2019/04/17 10:30:21 encryption: xor
2019/04/17 10:30:21 nodelay parameters: 1 10 2 1
2019/04/17 10:30:21 remote address: x.x.x.x:31000
2019/04/17 10:30:21 sndwnd: 768 rcvwnd: 2048
2019/04/17 10:30:21 compression: true
2019/04/17 10:30:21 mtu: 1350
2019/04/17 10:30:21 datashard: 10 parityshard: 3
2019/04/17 10:30:21 acknodelay: false
2019/04/17 10:30:21 dscp: 0
2019/04/17 10:30:21 sockbuf: 4194304
2019/04/17 10:30:21 smuxbuf: 4194304
2019/04/17 10:30:21 keepalive: 10
2019/04/17 10:30:21 conn: 1
2019/04/17 10:30:21 autoexpire: 0
2019/04/17 10:30:21 scavengettl: 600
2019/04/17 10:30:21 snmplog:
2019/04/17 10:30:21 snmpperiod: 60
2019/04/17 10:30:21 quiet: true


2019/04/17 10:35:57 connection: 0.0.0.0:33800 -> x.x.x.x:31000
2019/04/17 10:35:57 session normally closed
2019/04/17 10:46:35 session marked as expired
2019/04/17 10:46:35 connection: 0.0.0.0:57331 -> x.x.x.x:31000
2019/04/17 10:46:35 session normally closed
2019/04/17 11:02:54 session marked as expired
2019/04/17 11:02:54 connection: 0.0.0.0:51395 -> x.x.x.x:31000
2019/04/17 11:02:54 session normally closed
2019/04/17 11:02:57 session marked as expired
2019/04/17 11:02:57 connection: 0.0.0.0:50471 -> x.x.x.x:31000
2019/04/17 11:02:57 session normally closed
2019/04/17 11:02:59 session marked as expired
2019/04/17 11:02:59 connection: 0.0.0.0:39306 -> x.x.x.x:31000
2019/04/17 11:02:59 session normally closed
2019/04/17 11:03:02 session marked as expired
2019/04/17 11:03:02 connection: 0.0.0.0:60102 -> x.x.x.x:31000
2019/04/17 11:03:03 session normally closed
2019/04/17 11:03:04 session marked as expired
2019/04/17 11:03:04 connection: 0.0.0.0:45381 -> x.x.x.x:31000
2019/04/17 11:03:05 session normally closed
2019/04/17 11:03:06 session marked as expired
2019/04/17 11:03:06 connection: 0.0.0.0:36850 -> x.x.x.x:31000
2019/04/17 11:03:07 session normally closed
2019/04/17 11:03:13 session marked as expired
2019/04/17 11:03:13 connection: 0.0.0.0:57319 -> x.x.x.x:31000
2019/04/17 11:03:13 session normally closed
2019/04/17 11:03:15 session marked as expired
2019/04/17 11:03:15 connection: 0.0.0.0:36473 -> x.x.x.x:31000
2019/04/17 11:03:16 session normally close