Kcptun: 近两个月kcptun非常不稳定

Created on 12 Jun 2019 · 69Comments · Source: xtaci/kcptun

以前我都是长年ss+kcptun, 包括下载和youtube, 近期发现常掉线后升级过几次, 直到最近, 已经沦落到不可用的地步, 为此特地在网上搜索配置经验, 更改参数, 都无效

表现在好好的网站就打不开了, 下载的话启动半分钟就掉线了, 然后我就是不断地ctrl+c, 再重连(当然放任它不管也会自己在某个时候又连回去)
目前用kcptun下载已经废了, 只能切回ss, 那个下载速度啊....

由于已经升级过几次, 具体版本可不考了, 现在用的是5/15版

P.S. 打字这当口, 又断了

配置和日志如下:

server:

key:  xxx
crypt:  aes-192
mode:  manual
mtu:  1400
sndwnd:  128
rcvwnd:  1024
datashard:  30
parityshard:  15
dscp:  46
nocomp:  false
quiet:  false
interval:  20
resend:  2
nc:  1
acknodelay:  false
sockbuf:  4194304
keepalive:  10

client:

"nocomp" : false,
"key" : "xxx",
"crypt" : "aes-192",
"conn" : 1,
"quiet" : true,
"mode": "manual",
"mtu": 1400,
"sndwnd": 1024,
"rcvwnd": 1024,
"datashard": 30,
"parityshard": 15,
"dscp": 46,
"acknodelay": false,
"nodelay": 0,
"interval": 20,
"resend": 2,
"nc": 1,
"sockbuf": 4194304,
"keepalive": 10,
"autoexpire": -1

client启动后的日志永远如下:

2019/06/12 15:34:54 connection: 0.0.0.0:64480 -> my_server:port
2019/06/12 15:35:33 session marked as expired <nil>
2019/06/12 15:35:33 connection: 0.0.0.0:59008 -> my_server:port
2019/06/12 15:35:33 session normally closed <nil>
2019/06/12 15:36:33 session marked as expired <nil>
2019/06/12 15:36:33 connection: 0.0.0.0:63213 -> my_server:port
2019/06/12 15:36:33 session normally closed <nil>
2019/06/12 15:37:33 session marked as expired <nil>
2019/06/12 15:37:33 connection: 0.0.0.0:63982 -> my_server:port
2019/06/12 15:37:33 session normally closed <nil>
2019/06/12 15:38:33 session marked as expired <nil>
2019/06/12 15:38:33 connection: 0.0.0.0:60969 -> my_server:port
2019/06/12 15:38:33 session normally closed <nil>
2019/06/12 15:39:33 session marked as expired <nil>
2019/06/12 15:39:33 connection: 0.0.0.0:62457 -> my_server:port
2019/06/12 15:39:33 session normally closed <nil>
2019/06/12 15:41:06 session marked as expired <nil>
2019/06/12 15:41:06 connection: 0.0.0.0:55234 -> my_server:port
2019/06/12 15:41:06 session normally closed <nil>
2019/06/12 15:42:06 session marked as expired <nil>
2019/06/12 15:42:06 connection: 0.0.0.0:58081 -> my_server:port
2019/06/12 15:42:06 session normally closed <nil>

Source

walkerwzy

Most helpful comment

我提交了新的feature，但尚未release。

加入了 -tcp 参数，可以自行编译尝试一下，步骤:

$ sudo apt install libpcap-dev
$ export GO111MODULE=on
$ git clone https://github.com/xtaci/kcptun
$ cd kcptun/client
$ go build -o client_linux_amd64 .
$ cd ../server
$ go build -o server_linux_amd64 .

$ go version
go version go1.12.4 linux/amd64

启动参数在 json或命令行加入-tcp 即可

新feature的实现在这个库:
https://github.com/xtaci/tcpraw

注意，还在开发中，可能出各种故障，非常早期的阶段

xtaci on 27 Jun 2019

👍8

All 69 comments

-autoexpire 900

xtaci on 12 Jun 2019

@xtaci youtube仍然撑不过半分钟, 然后一两分钟后可以再连上, 再撑半分钟. 已设autoexpire为900, 甚至连服务端也把这个参数加上了

walkerwzy on 12 Jun 2019

我是用一段时间就断掉，中断时server端日志里报
2019/06/11 20:36:34 remote address: 127.0.0.1:33117
2019/06/11 20:36:34 remote address: 127.0.0.1:35235
2019/06/11 20:37:03 io: read/write on closed pipe
2019/06/11 20:37:04 io: read/write on closed pipe
2019/06/11 20:55:18 remote address: 127.0.0.1:40413
反复出现，过个几分钟才能重连上。客户端和服务器端都是最新的版本了。
-autoexpire 900、60、0都试过，没用

BH4WHN on 12 Jun 2019

I have no idea

xtaci on 12 Jun 2019

路过，从来不会断。

zhanhb on 12 Jun 2019

$ cat config.json 
{
    "server":"127.0.0.1",
    "server_port":1756,
    "password":"XXX",
    "timeout":300,
    "user":"nobody",
    "method":"salsa20",
    "fast_open":true,
    "nameserver":"4.2.2.1",
    "mode":"tcp_only"
}

xtaci on 12 Jun 2019

@zhanhb 你的版本, 和双端配置能分享一下吗? 我在不久前也从来不会断的

walkerwzy on 13 Jun 2019

cat config.json
{
    "server":"127.0.0.1",
    "server_port":8530,
    "local_port":1080,
    "password":"xxxx",
    "timeout":600,
    "method":"chacha20-ietf-poly1305",
    "fast_open":true,
    "plugin":"obfs-server",
    "plugin_opts":"obfs=http"
}

walkerwzy on 13 Jun 2019

一出新版本我就更新，客户端和服务器端都是，服务器端server-linux-amd64-*，客户端client-linux-mips-*, client-darwin-amd64-*, client-windows-amd64-*

zhanhb on 13 Jun 2019

我的启动参数是这样的

ss-server -s 0.0.0.0 --no-delay -p port -m aes-256-cfb -k 'ss_key' --plugin kcptun --plugin-opts 'key=kcptun_key;crypt=aes-128;mode=fast2;mtu=1200;dscp=46;datashard=0;nocomp;quiet'

参考这个项目https://github.com/zhanhb/kcptun-sip003-wrapper

zhanhb on 13 Jun 2019

你怎么在用obfs-server呢？这个好像已经废弃了吧，用v2ray-plugin代替吧

zhanhb on 13 Jun 2019

我的v2ray-plugin类似这样的配置 --plugin v2ray-plugin --plugin-opts 'server;fast-open;host=my_host_here;loglevel=error'

zhanhb on 13 Jun 2019

我去试试. 这个ss server很久没动过了, 而且直连现在也没问题, 只是最近kcptun老断, 我才开始找原因

walkerwzy on 13 Jun 2019

你连的是obfs-server，怎么在kcptun上找原因？你的配置有几层？

zhanhb on 13 Jun 2019

我觉得问题不在ss上，多台小鸡跑的都是不同版本的ss从来没出现频繁的断流除非出现高丢包。
也不知道是骡子不走还是磨子不转，已经困扰我快一个月了。
无奈昨天把服务器和客户端都退回4.24版，经过一晚上使用就断了一次。

BH4WHN on 14 Jun 2019

可能你用的那个混淆算法在客户端有bug吗？
我用的server是linux_amd64的，没出问题。客户端用的多的是darwin_amd64和linux_mips，这两个也没出问题，比较大的可能性是kcptun的client出问题。或者依赖系统的某个库出了问题吧（这个可能性应该不大）。

zhanhb on 14 Jun 2019

我换了VPS, 重新部署了shadowsocks, 插件改了v2ray, kcptun用的0515, 配置没变, 然后稳定了半个晚上, 又开始断了

walkerwzy on 14 Jun 2019

可能你用的那个混淆算法在客户端有bug吗？
我用的server是linux_amd64的，没出问题。客户端用的多的是darwin_amd64和linux_mips，这两个也没出问题，比较大的可能性是kcptun的client出问题。或者依赖系统的某个库出了问题吧（这个可能性应该不大）。

我用的是ss不是ssr，所以并没有混淆功能哦。

BH4WHN on 14 Jun 2019

混淆算法我指的这个 crypt=aes-128

zhanhb on 14 Jun 2019

你是ss经过v2ray-plugin，再通过kcptun转发的吗？我的是ss->kcptun或者ss->v2ray-plugin，两个配置都还挺稳定的。

zhanhb on 14 Jun 2019

我是17年开始用的kcptun
两个场景ss->kcptun和ss->kcptun->udp2raw
ss crypt用的chacha20
kcptun crypt用的salse20

BH4WHN on 14 Jun 2019

我也没遇到你说的问题

maxwellzh on 14 Jun 2019

我猜测是被墙定向流量识别了。或者某种行为导致某些运营商把它封了。
5月份我也没有问题。6月份开始的。家里时断时续，但是从公司连就完全不行。
服务器也是 io: read/write on closed pipe
客户端就是不停的open, close, io: read/write on closed pipe

kingsimba on 14 Jun 2019

持续观察吧，ISP block UDP的可能性比较大，可以尝试下udp2raw封装看有没有好转。

xtaci on 14 Jun 2019

如果只是udp的qos问题， udp2raw可以解决

xtaci on 14 Jun 2019

https://github.com/wangyu-/udp2raw-tunnel/blob/master/doc/kcptun_step_by_step.md

xtaci on 14 Jun 2019

不知道 -autoexpire 300和udp2raw的使用反馈如何？

xtaci on 16 Jun 2019

我说呢，原来很多人都如此问题。
5月份我也没有问题。6月份开始的。家里时断时续，但是从公司连就完全不行，偶尔会行。。。郁闷

becapital on 17 Jun 2019

-autoexpire 300和udp2raw的使用反馈如何？

用udp2raw faketcp mode 0和-autoexpire 300的那几组小鸡也是时断时续，断线频率看运气，基本没法稳定用了

BH4WHN on 18 Jun 2019

如果用来加速其他的非ss应用，是否有断线情况，如果没有断线情况，说明被加速的某个端口或协议存在缺陷，比如通过直接连接未被加速的某协议端口。

xtaci on 18 Jun 2019

持续观察吧，ISP block UDP的可能性比较大，可以尝试下udp2raw封装看有没有好转。

其实我在没有重新部署前就试了udp2raw, 居然无效, 这让我对它信心大打折扣.
kcptun加速其它应用还真不会, 网上一搜还是ss的

walkerwzy on 19 Jun 2019

@walkerwzy udp2raw是一个好项目，但会引入其他问题，例如不支持除了linux的其他os，任何基于raw socket的tcp 方案，都存在一定程度的os兼容性问题，要做好很难。

另外ss协议是有缺陷的，这点是毋庸置疑的。我确切知道的就有用来做kafka的消息跨机房传输，游戏，以及区块链的共识。

xtaci on 19 Jun 2019

我所在的城市今年开始运营商CU对所有家宽的udp进行qos（商宽未做限制），kcptun单独是绝对跑不起来的，流量一超过40Mbps以10秒为单位阻断，所以在家用的是udp2raw，但udp2raw问题也不小除了mode0能用，模式1-4都严重卡顿，还需要配置iptables，二、三层的跨层转发也算是费了不少力气，作者貌似也不维护了目前。udp2raw还什么替代品？

BH4WHN on 20 Jun 2019

之前公司不能用，家里可以，今天发现家里也完全啊不能用了。咋办

becapital on 23 Jun 2019

之前公司不能用，家里可以，今天发现家里也完全啊不能用了。咋办

你这种问题让大家怎么回答你啊，除了“凉拌”我还真不知道回复你啥

zhanhb on 23 Jun 2019

udp2raw的作者会在忙过这段后，做一些改进，到时能缓解一下。

xtaci on 24 Jun 2019

我提交了新的feature，但尚未release。

加入了 -tcp 参数，可以自行编译尝试一下，步骤:

$ sudo apt install libpcap-dev
$ export GO111MODULE=on
$ git clone https://github.com/xtaci/kcptun
$ cd kcptun/client
$ go build -o client_linux_amd64 .
$ cd ../server
$ go build -o server_linux_amd64 .

$ go version
go version go1.12.4 linux/amd64

启动参数在 json或命令行加入-tcp 即可

新feature的实现在这个库:
https://github.com/xtaci/tcpraw

注意，还在开发中，可能出各种故障，非常早期的阶段

xtaci on 27 Jun 2019

👍8

update:
tcpraw在kcptun的tcp分支，linux环境基本可用了，但cross-compile比较麻烦，依赖的libpcap不知道如何才能编译到其他的architecture上

xtaci on 30 Jun 2019

从6月30日到现在，这几天kcp貌似又恢复正常了，没有发现不稳定和不能连接。

becapital on 1 Jul 2019

@becapital 基本判定是ISP针对UDP的QoS行为。

另外kcptun从原则上我不是很愿意去支持TCP传输这种黑魔法（虽然技术上的困难也容易克服），想尽可能保持其纯粹性，但如果有PR提交给tcpraw这个项目上进行兼容性改进，我也可以表示欢迎，可以merge。但我个人是比较推荐 @wangyu- 的udp2raw方案，纯粹性。

xtaci on 1 Jul 2019

敏感月过去了？

zhanhb on 1 Jul 2019

敏感月过去了？

今天偶发性的可以用了，不可持续

sweetweapen on 1 Jul 2019

今天继续稳定，速度很快啊

becapital on 2 Jul 2019

楼上出现问题的各位，我认为你们不能用和你们的设置和软件基本上都没有什么关系。

GFW可以对不喜欢的IP针对性丢包、封禁（阻塞），这个太简单了。如果你们用的服务器的线路并不是那么高级（比如某某工包年），GFW判断IP误不误杀都无所谓的，被秒掉不要太轻松，一行命令就搞定。

5-6月间某为云内部的HK服务器IP也大面积被阻塞，客户无法登陆服务器，不乏许多大客户。结果某为内部也没办法，只能回复客户是国际层面的封禁，要不换个IP试试。某为那么大企业的IP都被阻塞，如果大家不能用了，我也建议先换个IP试试...

————引自某不愿意透露姓名的朋友

kcptun和udp2raw基本上啥都能穿透了，但是再能穿透，GFW如果直接不讲道理的进行系统/硬件级别的限速丢包阻塞，再穿透也没用。

当然也有其他可能，比如有人想暴破你的服务器（SS层面和服务器层面），网络上也有无数人用工具想要暴破你的服务器，创建个主机建议先做好安全工作...

我怀疑GFW特别喜欢拿同网段不同IP暴破SS，我抓过一段时间LOG之后，把暴破的网段全部封了，LOG就清静了。当然这个操作有没有实际的用途我并不清楚，SS本身就有不错的密码错误封禁机制，疑似GFW的很多IP连一次就不连了，不了解其对速度的影响...

总之，如果线路出现问题，不如先换一个IP/换个端口再来一次？

@BH4WHN 你这个情况看起像GFW对你的服务器运营商特别关照了，你用的是啥服务器商？有没有换一个试试？

@becapital 确实是敏感月过了，和各个软件基本没什么关系...

RebelliousWhiz on 2 Jul 2019

我这边也是间歇性不能用，服务端 io: read/write on closed pipe
用iperf3测试udp倒是没什么问题，ping丢包率也只有10几
外面套了一层udp2raw暂时能用了

s34304 on 3 Jul 2019

今天，公司里，又不行了。。。郁闷，间歇性的发作。

becapital on 3 Jul 2019

楼上出现问题的各位，我认为你们不能用和你们的设置和软件基本上都没有什么关系。

GFW可以对不喜欢的IP针对性丢包、封禁（阻塞），这个太简单了。如果你们用的服务器的线路并不是那么高级（比如某某工包年），GFW判断IP误不误杀都无所谓的，被秒掉不要太轻松，一行命令就搞定。

5-6月间某为云内部的HK服务器IP也大面积被阻塞，客户无法登陆服务器，不乏许多大客户。结果某为内部也没办法，只能回复客户是国际层面的封禁，要不换个IP试试。某为那么大企业的IP都被阻塞，如果大家不能用了，我也建议先换个IP试试...

————引自某不愿意透露姓名的朋友

kcptun和udp2raw基本上啥都能穿透了，但是再能穿透，GFW如果直接不讲道理的进行系统/硬件级别的限速丢包阻塞，再穿透也没用。

当然也有其他可能，比如有人想暴破你的服务器（SS层面和服务器层面），网络上也有无数人用工具想要暴破你的服务器，创建个主机建议先做好安全工作...

我怀疑GFW特别喜欢拿同网段不同IP暴破SS，我抓过一段时间LOG之后，把暴破的网段全部封了，LOG就清静了。当然这个操作有没有实际的用途我并不清楚，SS本身就有不错的密码错误封禁机制，疑似GFW的很多IP连一次就不连了，不了解其对速度的影响...

总之，如果线路出现问题，不如先换一个IP/换个端口再来一次？

@BH4WHN 你这个情况看起像GFW对你的服务器运营商特别关照了，你用的是啥服务器商？有没有换一个试试？

@becapital 确实是敏感月过了，和各个软件基本没什么关系...

已经非常确定的是本地宽带运营商对家宽的udp做了qos（我测试了我两处房子不同宽带账号同一运营商的家宽，同时也测试了单位同一运营商的商用宽带，商宽未限制udp），家宽只要是udp大流量持续10s就阻断，东南西北各个方向的vps都测试过早就排除了vps供应商的问题。

BH4WHN on 3 Jul 2019

今天，公司里，又不行了。。。郁闷，间歇性的发作。

公司防火墙一般都会默认开启防止udp泛洪攻击，到达设定阈值防火墙就会阻断并日志记录。

BH4WHN on 3 Jul 2019

kcptun-linux-386-20190703.tar.gz
kcptun-linux-amd64-20190703.tar.gz
kcptun-linux-arm5-20190703.tar.gz
kcptun-linux-arm6-20190703.tar.gz
kcptun-linux-arm7-20190703.tar.gz
kcptun-linux-arm64-20190703.tar.gz
kcptun-linux-mips-20190703.tar.gz
kcptun-linux-mipsle-20190703.tar.gz

支持 -tcp选项的kcptun，两端都需要开启，可以试用一下并反馈问题。

xtaci on 3 Jul 2019

2019/07/04 13:52:42 tcp: true
2019/07/04 13:52:42 SetDSCP: invalid operation
2019/07/04 13:52:42 SetReadBuffer: invalid operation
2019/07/04 13:52:42 SetWriteBuffer: invalid operation
2019/07/04 13:52:42 connection: 172.16.1.1:35914 -> x.x.x.x:1790
2019/07/04 13:54:28 session marked as expired x.x.x.x:1790
2019/07/04 13:54:29 session normally closed x.x.x.x:1790
2019/07/04 13:54:29 SetDSCP: invalid operation
2019/07/04 13:54:29 SetReadBuffer: invalid operation
2019/07/04 13:54:29 SetWriteBuffer: invalid operation
客户端上述提示，用不起来，内存半小时占满宕机。

BH4WHN on 4 Jul 2019

kcptun-linux-386-20190704.tar.gz
kcptun-linux-amd64-20190704.tar.gz
kcptun-linux-arm5-20190704.tar.gz
kcptun-linux-arm6-20190704.tar.gz
kcptun-linux-arm7-20190704.tar.gz
kcptun-linux-arm64-20190704.tar.gz
kcptun-linux-mips-20190704.tar.gz
kcptun-linux-mipsle-20190704.tar.gz

可以再试下这个

xtaci on 4 Jul 2019

不是root权限不能运行么？

zhanhb on 4 Jul 2019

不是root权限不能运行么？

-tcp 参数必须要root

xtaci on 4 Jul 2019

kcptun-linux-386-20190704.tar.gz
kcptun-linux-amd64-20190704.tar.gz
kcptun-linux-arm5-20190704.tar.gz
kcptun-linux-arm6-20190704.tar.gz
kcptun-linux-arm7-20190704.tar.gz
kcptun-linux-arm64-20190704.tar.gz
kcptun-linux-mips-20190704.tar.gz
kcptun-linux-mipsle-20190704.tar.gz

可以再试下这个
2019/07/04 15:42:32 version: 20190704
2019/07/04 15:42:32 initiating key derivation
2019/07/04 15:42:32 listening on: 127.0.0.1:12323
2019/07/04 15:42:32 encryption: none
2019/07/04 15:42:32 nodelay parameters: 0 30 2 1
2019/07/04 15:42:32 remote address: x.x.x.x:1779
2019/07/04 15:42:32 sndwnd: 256 rcvwnd: 1536
2019/07/04 15:42:32 compression: false
2019/07/04 15:42:32 mtu: 1200
2019/07/04 15:42:32 datashard: 10 parityshard: 3
2019/07/04 15:42:32 acknodelay: false
2019/07/04 15:42:32 dscp: 0
2019/07/04 15:42:32 sockbuf: 16777217
2019/07/04 15:42:32 smuxbuf: 67108864
2019/07/04 15:42:32 keepalive: 10
2019/07/04 15:42:32 conn: 1
2019/07/04 15:42:32 autoexpire: -1
2019/07/04 15:42:32 scavengettl: 900
2019/07/04 15:42:32 snmplog:
2019/07/04 15:42:32 snmpperiod: 60
2019/07/04 15:42:32 quiet: false
2019/07/04 15:42:32 tcp: true
2019/07/04 15:42:32 SetDSCP: invalid operation
2019/07/04 15:42:32 SetReadBuffer: invalid operation
2019/07/04 15:42:32 SetWriteBuffer: invalid operation
2019/07/04 15:42:32 connection: 172.16.1.251:48496 -> x.x.x.x:1779
2019/07/04 15:43:14 stream opened in: 127.0.0.1:55398 out: x.x.x.x:1779(3)
2019/07/04 15:43:14 stream opened in: 127.0.0.1:55396 out: x.x.x.x:1779(5)
2019/07/04 15:43:15 stream closed in: 127.0.0.1:55398 out: x.x.x.x:1779(3)
2019/07/04 15:43:15 stream opened in: 127.0.0.1:55400 out: x.x.x.x:1779(7)
2019/07/04 15:43:15 stream opened in: 127.0.0.1:55402 out: x.x.x.x:1779(9)
2019/07/04 15:43:15 stream closed in: 127.0.0.1:55396 out: x.x.x.x:1779(5)
2019/07/04 15:43:15 stream opened in: 127.0.0.1:55404 out: x.x.x.x:1779(11)
2019/07/04 15:43:15 stream opened in: 127.0.0.1:55406 out: x.x.x.x:1779(13)
2019/07/04 15:43:15 stream opened in: 127.0.0.1:55408 out: x.x.x.x:1779(15)
2019/07/04 15:43:15 stream opened in: 127.0.0.1:55410 out: x.x.x.x:1779(17)
2019/07/04 15:43:16 stream opened in: 127.0.0.1:55412 out: x.x.x.x:1779(19)
2019/07/04 15:43:16 stream opened in: 127.0.0.1:55414 out: x.x.x.x:1779(21)
2019/07/04 15:43:17 stream opened in: 127.0.0.1:55416 out: x.x.x.x:1779(23)
2019/07/04 15:43:17 stream opened in: 127.0.0.1:55418 out: x.x.x.x:1779(25)
2019/07/04 15:43:18 stream opened in: 127.0.0.1:55420 out: x.x.x.x:1779(29)
2019/07/04 15:43:18 stream opened in: 127.0.0.1:55422 out: x.x.x.x:1779(27)
2019/07/04 15:43:19 stream opened in: 127.0.0.1:55424 out: x.x.x.x:1779(33)
2019/07/04 15:43:19 stream opened in: 127.0.0.1:55426 out: x.x.x.x:1779(31)
2019/07/04 15:43:19 stream opened in: 127.0.0.1:55430 out: x.x.x.x:1779(35)
2019/07/04 15:43:19 stream opened in: 127.0.0.1:55428 out: x.x.x.x:1779(37)
2019/07/04 15:43:19 stream opened in: 127.0.0.1:55434 out: x.x.x.x:1779(39)
2019/07/04 15:43:19 stream opened in: 127.0.0.1:55432 out: x.x.x.x:1779(41)
2019/07/04 15:43:19 stream opened in: 127.0.0.1:55438 out: x.x.x.x:1779(43)
2019/07/04 15:43:19 stream opened in: 127.0.0.1:55436 out: x.x.x.x:1779(45)
2019/07/04 15:43:19 stream opened in: 127.0.0.1:55440 out: x.x.x.x:1779(47)
2019/07/04 15:43:19 stream opened in: 127.0.0.1:55448 out: x.x.x.x:1779(49)
2019/07/04 15:43:19 stream opened in: 127.0.0.1:55446 out: x.x.x.x:1779(55)
2019/07/04 15:43:19 stream opened in: 127.0.0.1:55444 out: x.x.x.x:1779(51)
2019/07/04 15:43:19 stream opened in: 127.0.0.1:55442 out: x.x.x.x:1779(53)
2019/07/04 15:43:20 stream opened in: 127.0.0.1:55450 out: x.x.x.x:1779(57)
2019/07/04 15:43:20 stream opened in: 127.0.0.1:55452 out: x.x.x.x:1779(59)
2019/07/04 15:43:20 stream opened in: 127.0.0.1:55454 out: x.x.x.x:1779(61)
2019/07/04 15:43:20 stream opened in: 127.0.0.1:55456 out: x.x.x.x:1779(63)
2019/07/04 15:43:20 stream opened in: 127.0.0.1:55458 out: x.x.x.x:1779(65)
2019/07/04 15:43:21 stream opened in: 127.0.0.1:55460 out: x.x.x.x:1779(69)
2019/07/04 15:43:21 stream opened in: 127.0.0.1:55462 out: x.x.x.x:1779(67)
2019/07/04 15:43:21 stream opened in: 127.0.0.1:55464 out: x.x.x.x:1779(71)
2019/07/04 15:43:22 stream opened in: 127.0.0.1:55468 out: x.x.x.x:1779(73)
2019/07/04 15:43:22 stream opened in: 127.0.0.1:55466 out: x.x.x.x:1779(75)
2019/07/04 15:43:23 stream opened in: 127.0.0.1:55470 out: x.x.x.x:1779(77)
2019/07/04 15:43:23 stream opened in: 127.0.0.1:55472 out: x.x.x.x:1779(79)
2019/07/04 15:43:23 stream opened in: 127.0.0.1:55474 out: x.x.x.x:1779(81)
2019/07/04 15:43:23 stream opened in: 127.0.0.1:55476 out: x.x.x.x:1779(83)
2019/07/04 15:43:23 stream opened in: 127.0.0.1:55478 out: x.x.x.x:1779(85)
2019/07/04 15:43:23 stream opened in: 127.0.0.1:55480 out: x.x.x.x:1779(87)
2019/07/04 15:43:23 stream opened in: 127.0.0.1:55482 out: x.x.x.x:1779(89)
2019/07/04 15:43:23 stream opened in: 127.0.0.1:55484 out: x.x.x.x:1779(91)
2019/07/04 15:43:24 stream opened in: 127.0.0.1:55486 out: x.x.x.x:1779(93)
2019/07/04 15:43:24 stream opened in: 127.0.0.1:55488 out: x.x.x.x:1779(95)
2019/07/04 15:43:24 stream opened in: 127.0.0.1:55490 out: x.x.x.x:1779(97)
2019/07/04 15:43:24 stream opened in: 127.0.0.1:55492 out: x.x.x.x:1779(99)
2019/07/04 15:43:24 stream opened in: 127.0.0.1:55494 out: x.x.x.x:1779(101)
2019/07/04 15:43:24 stream opened in: 127.0.0.1:55496 out: x.x.x.x:1779(103)
2019/07/04 15:43:24 stream opened in: 127.0.0.1:55498 out: x.x.x.x:1779(105)
2019/07/04 15:43:25 stream opened in: 127.0.0.1:55502 out: x.x.x.x:1779(107)
2019/07/04 15:43:25 stream opened in: 127.0.0.1:55500 out: x.x.x.x:1779(109)
2019/07/04 15:43:25 stream opened in: 127.0.0.1:55504 out: x.x.x.x:1779(111)
2019/07/04 15:43:26 stream opened in: 127.0.0.1:55508 out: x.x.x.x:1779(115)
2019/07/04 15:43:26 stream opened in: 127.0.0.1:55506 out: x.x.x.x:1779(113)
2019/07/04 15:43:27 stream opened in: 127.0.0.1:55510 out: x.x.x.x:1779(117)
2019/07/04 15:43:27 stream opened in: 127.0.0.1:55512 out: x.x.x.x:1779(119)
2019/07/04 15:43:27 stream opened in: 127.0.0.1:55514 out: x.x.x.x:1779(121)
2019/07/04 15:43:27 stream opened in: 127.0.0.1:55516 out: x.x.x.x:1779(123)
2019/07/04 15:43:27 stream opened in: 127.0.0.1:55518 out: x.x.x.x:1779(127)
2019/07/04 15:43:27 stream opened in: 127.0.0.1:55520 out: x.x.x.x:1779(125)
2019/07/04 15:43:27 stream opened in: 127.0.0.1:55522 out: x.x.x.x:1779(129)
2019/07/04 15:43:27 stream opened in: 127.0.0.1:55526 out: x.x.x.x:1779(131)
2019/07/04 15:43:27 stream opened in: 127.0.0.1:55524 out: x.x.x.x:1779(133)
2019/07/04 15:43:28 stream opened in: 127.0.0.1:55528 out: x.x.x.x:1779(135)
2019/07/04 15:43:28 stream opened in: 127.0.0.1:55530 out: x.x.x.x:1779(137)
2019/07/04 15:43:28 stream opened in: 127.0.0.1:55534 out: x.x.x.x:1779(141)
2019/07/04 15:43:28 stream opened in: 127.0.0.1:55532 out: x.x.x.x:1779(139)
2019/07/04 15:43:28 stream opened in: 127.0.0.1:55536 out: x.x.x.x:1779(143)
2019/07/04 15:43:28 stream opened in: 127.0.0.1:55538 out: x.x.x.x:1779(145)
2019/07/04 15:43:28 stream opened in: 127.0.0.1:55540 out: x.x.x.x:1779(147)
2019/07/04 15:43:29 stream opened in: 127.0.0.1:55542 out: x.x.x.x:1779(149)
2019/07/04 15:43:29 stream opened in: 127.0.0.1:55544 out: x.x.x.x:1779(151)
2019/07/04 15:43:29 stream opened in: 127.0.0.1:55546 out: x.x.x.x:1779(153)
2019/07/04 15:43:30 stream opened in: 127.0.0.1:55548 out: x.x.x.x:1779(157)
2019/07/04 15:43:30 stream opened in: 127.0.0.1:55550 out: x.x.x.x:1779(155)
2019/07/04 15:43:30 stream opened in: 127.0.0.1:55554 out: x.x.x.x:1779(159)
2019/07/04 15:43:30 stream opened in: 127.0.0.1:55552 out: x.x.x.x:1779(161)
2019/07/04 15:43:31 stream closed in: 127.0.0.1:55512 out: x.x.x.x:1779(119)
2019/07/04 15:43:31 stream closed in: 127.0.0.1:55402 out: x.x.x.x:1779(9)
2019/07/04 15:43:31 stream closed in: 127.0.0.1:55424 out: x.x.x.x:1779(33)
2019/07/04 15:43:31 stream closed in: 127.0.0.1:55472 out: x.x.x.x:1779(79)
2019/07/04 15:43:31 stream closed in: 127.0.0.1:55510 out: x.x.x.x:1779(117)
2019/07/04 15:43:31 stream closed in: 127.0.0.1:55426 out: x.x.x.x:1779(31)
2019/07/04 15:43:31 stream closed in: 127.0.0.1:55470 out: x.x.x.x:1779(77)
2019/07/04 15:43:31 stream closed in: 127.0.0.1:55400 out: x.x.x.x:1779(7)
2019/07/04 15:43:31 stream closed in: 127.0.0.1:55428 out: x.x.x.x:1779(37)
2019/07/04 15:43:31 stream closed in: 127.0.0.1:55474 out: x.x.x.x:1779(81)
2019/07/04 15:43:31 stream closed in: 127.0.0.1:55514 out: x.x.x.x:1779(121)
2019/07/04 15:43:31 stream closed in: 127.0.0.1:55404 out: x.x.x.x:1779(11)
2019/07/04 15:43:31 stream closed in: 127.0.0.1:55476 out: x.x.x.x:1779(83)
2019/07/04 15:43:31 stream closed in: 127.0.0.1:55516 out: x.x.x.x:1779(123)
2019/07/04 15:43:31 stream closed in: 127.0.0.1:55406 out: x.x.x.x:1779(13)
2019/07/04 15:43:31 stream closed in: 127.0.0.1:55430 out: x.x.x.x:1779(35)
2019/07/04 15:43:31 stream opened in: 127.0.0.1:55558 out: x.x.x.x:1779(165)
2019/07/04 15:43:31 stream opened in: 127.0.0.1:55556 out: x.x.x.x:1779(163)
2019/07/04 15:43:31 stream closed in: 127.0.0.1:55520 out: x.x.x.x:1779(125)
2019/07/04 15:43:31 stream closed in: 127.0.0.1:55410 out: x.x.x.x:1779(17)
2019/07/04 15:43:31 stream closed in: 127.0.0.1:55434 out: x.x.x.x:1779(39)
2019/07/04 15:43:31 stream closed in: 127.0.0.1:55478 out: x.x.x.x:1779(85)
2019/07/04 15:43:31 stream closed in: 127.0.0.1:55518 out: x.x.x.x:1779(127)
2019/07/04 15:43:31 stream closed in: 127.0.0.1:55408 out: x.x.x.x:1779(15)
2019/07/04 15:43:31 stream closed in: 127.0.0.1:55432 out: x.x.x.x:1779(41)
2019/07/04 15:43:31 stream closed in: 127.0.0.1:55480 out: x.x.x.x:1779(87)
2019/07/04 15:43:31 stream opened in: 127.0.0.1:55560 out: x.x.x.x:1779(167)
2019/07/04 15:43:31 stream opened in: 127.0.0.1:55562 out: x.x.x.x:1779(169)
2019/07/04 15:43:31 stream opened in: 127.0.0.1:55564 out: x.x.x.x:1779(171)
2019/07/04 15:43:32 stream closed in: 127.0.0.1:55412 out: x.x.x.x:1779(19)
2019/07/04 15:43:32 stream closed in: 127.0.0.1:55450 out: x.x.x.x:1779(57)
2019/07/04 15:43:32 stream closed in: 127.0.0.1:55414 out: x.x.x.x:1779(21)
2019/07/04 15:43:32 stream closed in: 127.0.0.1:55452 out: x.x.x.x:1779(59)
2019/07/04 15:43:32 stream closed in: 127.0.0.1:55528 out: x.x.x.x:1779(135)
2019/07/04 15:43:32 stream closed in: 127.0.0.1:55486 out: x.x.x.x:1779(93)
2019/07/04 15:43:32 stream closed in: 127.0.0.1:55488 out: x.x.x.x:1779(95)
2019/07/04 15:43:32 stream closed in: 127.0.0.1:55530 out: x.x.x.x:1779(137)
2019/07/04 15:43:32 stream opened in: 127.0.0.1:55566 out: x.x.x.x:1779(173)
2019/07/04 15:43:32 stream opened in: 127.0.0.1:55568 out: x.x.x.x:1779(175)
2019/07/04 15:43:32 stream opened in: 127.0.0.1:55570 out: x.x.x.x:1779(177)
2019/07/04 15:43:32 stream opened in: 127.0.0.1:55572 out: x.x.x.x:1779(179)
2019/07/04 15:43:32 stream opened in: 127.0.0.1:55574 out: x.x.x.x:1779(181)
2019/07/04 15:43:32 stream opened in: 127.0.0.1:55576 out: x.x.x.x:1779(183)
2019/07/04 15:43:32 stream opened in: 127.0.0.1:55578 out: x.x.x.x:1779(185)
2019/07/04 15:43:33 stream closed in: 127.0.0.1:55542 out: x.x.x.x:1779(149)
2019/07/04 15:43:33 stream closed in: 127.0.0.1:55460 out: x.x.x.x:1779(69)
2019/07/04 15:43:33 stream closed in: 127.0.0.1:55418 out: x.x.x.x:1779(25)
2019/07/04 15:43:33 stream closed in: 127.0.0.1:55502 out: x.x.x.x:1779(107)
2019/07/04 15:43:33 stream closed in: 127.0.0.1:55500 out: x.x.x.x:1779(109)
2019/07/04 15:43:33 stream closed in: 127.0.0.1:55544 out: x.x.x.x:1779(151)
2019/07/04 15:43:33 stream closed in: 127.0.0.1:55416 out: x.x.x.x:1779(23)
2019/07/04 15:43:33 stream closed in: 127.0.0.1:55462 out: x.x.x.x:1779(67)
2019/07/04 15:43:33 stream opened in: 127.0.0.1:55580 out: x.x.x.x:1779(187)
2019/07/04 15:43:34 stream closed in: 127.0.0.1:55466 out: x.x.x.x:1779(75)
2019/07/04 15:43:34 stream closed in: 127.0.0.1:55506 out: x.x.x.x:1779(113)
2019/07/04 15:43:34 stream closed in: 127.0.0.1:55422 out: x.x.x.x:1779(27)
2019/07/04 15:43:34 stream closed in: 127.0.0.1:55548 out: x.x.x.x:1779(157)
2019/07/04 15:43:34 stream closed in: 127.0.0.1:55420 out: x.x.x.x:1779(29)
2019/07/04 15:43:34 stream closed in: 127.0.0.1:55508 out: x.x.x.x:1779(115)
2019/07/04 15:43:34 stream closed in: 127.0.0.1:55468 out: x.x.x.x:1779(73)
2019/07/04 15:43:34 stream closed in: 127.0.0.1:55550 out: x.x.x.x:1779(155)
2019/07/04 15:43:34 stream opened in: 127.0.0.1:55584 out: x.x.x.x:1779(191)
2019/07/04 15:43:34 stream opened in: 127.0.0.1:55582 out: x.x.x.x:1779(189)
2019/07/04 15:43:34 stream opened in: 127.0.0.1:55586 out: x.x.x.x:1779(193)
2019/07/04 15:43:34 stream opened in: 127.0.0.1:55588 out: x.x.x.x:1779(195)
2019/07/04 15:43:35 stream closed in: 127.0.0.1:55484 out: x.x.x.x:1779(91)
2019/07/04 15:43:35 stream closed in: 127.0.0.1:55436 out: x.x.x.x:1779(45)
2019/07/04 15:43:35 stream closed in: 127.0.0.1:55560 out: x.x.x.x:1779(167)
2019/07/04 15:43:35 stream closed in: 127.0.0.1:55522 out: x.x.x.x:1779(129)
2019/07/04 15:43:36 stream closed in: 127.0.0.1:55572 out: x.x.x.x:1779(179)
2019/07/04 15:43:36 stream closed in: 127.0.0.1:55494 out: x.x.x.x:1779(101)
2019/07/04 15:43:36 stream closed in: 127.0.0.1:55454 out: x.x.x.x:1779(61)
2019/07/04 15:43:36 stream closed in: 127.0.0.1:55568 out: x.x.x.x:1779(175)
2019/07/04 15:43:36 stream closed in: 127.0.0.1:55456 out: x.x.x.x:1779(63)
2019/07/04 15:43:36 stream closed in: 127.0.0.1:55496 out: x.x.x.x:1779(103)
2019/07/04 15:43:36 stream closed in: 127.0.0.1:55538 out: x.x.x.x:1779(145)
2019/07/04 15:43:36 stream closed in: 127.0.0.1:55536 out: x.x.x.x:1779(143)
2019/07/04 15:43:36 stream closed in: 127.0.0.1:55578 out: x.x.x.x:1779(185)
2019/07/04 15:43:36 stream closed in: 127.0.0.1:55498 out: x.x.x.x:1779(105)
2019/07/04 15:43:36 stream closed in: 127.0.0.1:55540 out: x.x.x.x:1779(147)
2019/07/04 15:43:36 stream closed in: 127.0.0.1:55458 out: x.x.x.x:1779(65)
2019/07/04 15:43:37 stream closed in: 127.0.0.1:55580 out: x.x.x.x:1779(187)
2019/07/04 15:43:37 stream closed in: 127.0.0.1:55504 out: x.x.x.x:1779(111)
2019/07/04 15:43:37 stream closed in: 127.0.0.1:55546 out: x.x.x.x:1779(153)
2019/07/04 15:43:37 stream closed in: 127.0.0.1:55464 out: x.x.x.x:1779(71)
2019/07/04 15:43:39 stream closed in: 127.0.0.1:55482 out: x.x.x.x:1779(89)
2019/07/04 15:43:39 stream closed in: 127.0.0.1:55562 out: x.x.x.x:1779(169)
2019/07/04 15:43:39 stream closed in: 127.0.0.1:55526 out: x.x.x.x:1779(131)
2019/07/04 15:43:40 stream closed in: 127.0.0.1:55492 out: x.x.x.x:1779(99)
2019/07/04 15:43:40 stream closed in: 127.0.0.1:55490 out: x.x.x.x:1779(97)
2019/07/04 15:43:40 stream closed in: 127.0.0.1:55566 out: x.x.x.x:1779(173)
2019/07/04 15:43:40 stream closed in: 127.0.0.1:55534 out: x.x.x.x:1779(141)
2019/07/04 15:43:40 stream closed in: 127.0.0.1:55532 out: x.x.x.x:1779(139)
2019/07/04 15:43:40 stream closed in: 127.0.0.1:55570 out: x.x.x.x:1779(177)
2019/07/04 15:43:43 stream closed in: 127.0.0.1:55564 out: x.x.x.x:1779(171)
2019/07/04 15:43:43 stream closed in: 127.0.0.1:55524 out: x.x.x.x:1779(133)
2019/07/04 15:43:46 stream closed in: 127.0.0.1:55552 out: x.x.x.x:1779(161)
2019/07/04 15:43:46 stream closed in: 127.0.0.1:55584 out: x.x.x.x:1779(191)
2019/07/04 15:43:46 stream closed in: 127.0.0.1:55554 out: x.x.x.x:1779(159)
2019/07/04 15:43:46 stream closed in: 127.0.0.1:55582 out: x.x.x.x:1779(189)
2019/07/04 15:43:47 stream closed in: 127.0.0.1:55556 out: x.x.x.x:1779(163)
2019/07/04 15:43:47 stream closed in: 127.0.0.1:55558 out: x.x.x.x:1779(165)
2019/07/04 15:43:48 stream closed in: 127.0.0.1:55576 out: x.x.x.x:1779(183)
2019/07/04 15:43:48 stream closed in: 127.0.0.1:55574 out: x.x.x.x:1779(181)
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 stream closed in: 127.0.0.1:55586 out: x.x.x.x:1779(193)
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 io: read/write on closed pipe
2019/07/04 15:44:13 stream closed in: 127.0.0.1:55588 out: x.x.x.x:1779(195)
2019/07/04 15:44:13 stream closed in: 127.0.0.1:55442 out: x.x.x.x:1779(53)
2019/07/04 15:44:13 stream closed in: 127.0.0.1:55448 out: x.x.x.x:1779(49)
2019/07/04 15:44:13 stream closed in: 127.0.0.1:55444 out: x.x.x.x:1779(51)
2019/07/04 15:44:13 stream closed in: 127.0.0.1:55446 out: x.x.x.x:1779(55)
2019/07/04 15:44:13 stream closed in: 127.0.0.1:55440 out: x.x.x.x:1779(47)
2019/07/04 15:44:13 stream closed in: 127.0.0.1:55438 out: x.x.x.x:1779(43)
2019/07/04 15:44:57 session marked as expired x.x.x.x:1779
2019/07/04 15:44:57 session normally closed x.x.x.x:1779
2019/07/04 15:44:57 SetDSCP: invalid operation
2019/07/04 15:44:57 SetReadBuffer: invalid operation
2019/07/04 15:44:57 SetWriteBuffer: invalid operation
2019/07/04 15:44:57 connection: 172.16.1.251:42293 -> x.x.x.x:1779
2019/07/04 15:44:57 stream opened in: 127.0.0.1:55670 out: x.x.x.x:1779(13)
2019/07/04 15:44:57 stream opened in: 127.0.0.1:55662 out: x.x.x.x:1779(3)
无法工作，内存占用正常了

BH4WHN on 4 Jul 2019

嗯，再检查下，你这个是什么环境，我这边比较正常

xtaci on 4 Jul 2019

kcptun肯定不稳定了，但是我搭建的SS，走的是tcp吧，我小白。最近也出现问题了？

becapital on 5 Jul 2019

kcptun肯定不稳定了，但是我搭建的SS，走的是tcp吧，我小白。最近也出现问题了？

可能gfw有加入新的强有力的开发人员了吧

zhanhb on 5 Jul 2019

kcptun肯定不稳定了，但是我搭建的SS，走的是tcp吧，我小白。最近也出现问题了？

可能gfw有加入新的强有力的开发人员了吧

很明显是运营商的锅啊

maxwellzh on 5 Jul 2019

kcptun肯定不稳定了，但是我搭建的SS，走的是tcp吧，我小白。最近也出现问题了？

可能gfw有加入新的强有力的开发人员了吧

很明显是运营商的锅啊

对的，ISP，成本考虑

xtaci on 5 Jul 2019

楼上出现问题的各位，我认为你们不能用和你们的设置和软件基本上都没有什么关系。

GFW可以对不喜欢的IP针对性丢包、封禁（阻塞），这个太简单了。如果你们用的服务器的线路并不是那么高级（比如某某工包年），GFW判断IP误不误杀都无所谓的，被秒掉不要太轻松，一行命令就搞定。

5-6月间某为云内部的HK服务器IP也大面积被阻塞，客户无法登陆服务器，不乏许多大客户。结果某为内部也没办法，只能回复客户是国际层面的封禁，要不换个IP试试。某为那么大企业的IP都被阻塞，如果大家不能用了，我也建议先换个IP试试...

————引自某不愿意透露姓名的朋友

kcptun和udp2raw基本上啥都能穿透了，但是再能穿透，GFW如果直接不讲道理的进行系统/硬件级别的限速丢包阻塞，再穿透也没用。

当然也有其他可能，比如有人想暴破你的服务器（SS层面和服务器层面），网络上也有无数人用工具想要暴破你的服务器，创建个主机建议先做好安全工作...

我怀疑GFW特别喜欢拿同网段不同IP暴破SS，我抓过一段时间LOG之后，把暴破的网段全部封了，LOG就清静了。当然这个操作有没有实际的用途我并不清楚，SS本身就有不错的密码错误封禁机制，疑似GFW的很多IP连一次就不连了，不了解其对速度的影响...

总之，如果线路出现问题，不如先换一个IP/换个端口再来一次？

@BH4WHN 你这个情况看起像GFW对你的服务器运营商特别关照了，你用的是啥服务器商？有没有换一个试试？

@becapital 确实是敏感月过了，和各个软件基本没什么关系...

坐标上海电信,服务器是bwg,好像已经被GFW不讲理丢包阻塞了,昨晚开始tcp,udp,icmp基本都被丢包,不过暂时udp还能偷一点流量,视频看不了了,网页暂时还能打开

irvingow on 7 Jul 2019

上海电信 version: 20180316 树莓派，很稳定。

networkextension on 8 Jul 2019

https://github.com/xtaci/kcptun/releases/tag/20190708

xtaci on 8 Jul 2019

mac系统没有iptable 我看release里面有darwin，mac也支持么?

sweetweapen on 8 Jul 2019

mac系统没有iptable 我看release里面有darwin，mac也支持么?

不支持MAC

xtaci on 8 Jul 2019

如果UDP能用，就用UDP， TCP当作一个fallback的方案吧。

xtaci on 8 Jul 2019

👍1

https://github.com/xtaci/kcptun/issues/696

xtaci on 12 Jul 2019

mac系统没有iptable 我看release里面有darwin，mac也支持么?

不支持MAC

@xtaci 请问一下，您说的不支持Mac，是说现在发布的keptun最新版本不支持Mac下的Shadowsocks-NG吗？我装的Shadowsocks-NG是最新1.94版，里面的kcptun插件我看还是20190905版，但我用一键脚本安装kcptun是安装的最新20191127版，最后一直连不上，反复提示stream opened和stream closed。想知道是不是版本不对应的原因，最新kcptun是不适配Mac吗？那20190905的kcptun客户端版对应的服务器端版本号也是20190905吗？它支持Mac不？