我的配置如下
{
"localaddr": ":12949",
"remoteaddr": "118.193.195.23:8989",
"key": "122313",
"crypt": "aes",
"mode": "fast3",
"conn": 1,
"autoexpire": 60,
"mtu": 1350,
"sndwnd": 1024,
"rcvwnd": 1024,
"datashard": 10,
"parityshard": 3,
"dscp": 0,
"nocomp": false,
"acknodelay": true,
"nodelay": 0,
"interval": 20,
"resend": 2,
"nc": 1,
"sockbuf": 4194304,
"keepalive": 10
}
然后在ss端用了127.0.0.1:12949之后,无法打开网页,但是测试原vps连接可以
我看终端的日志
2016/12/27 16:31:19 stream opened
2016/12/27 16:31:19 stream opened
2016/12/27 16:31:19 stream opened
2016/12/27 16:31:19 stream opened
2016/12/27 16:31:19 stream closed
2016/12/27 16:31:19 stream opened
2016/12/27 16:31:23 stream opened
2016/12/27 16:31:28 stream closed
2016/12/27 16:31:28 stream closed
2016/12/27 16:31:28 stream closed
2016/12/27 16:31:28 stream closed
2016/12/27 16:31:28 stream closed
感觉很奇怪,是哪里配置错误了吗?
version: 20161222
OS:OSX 10.12.2
1.检查下服务器版本和客户端版本是否相同。
2.检查服务器端日志,是否收到请求。
3.“测试原 vps 连接可以”,可以理解为使用 shadowsocks 客户端直接连接 vps 的shadowsocks 服务是正常的?如果是这个意思,问题就出现在 kcptun 客户端或者服务端。
4.看到你 shadowsocks 加速端口为 :8989,本地端口为: 12949,shadowsocks 客户端检查下是否正确。
2016/12/27 16:57:41 version: 20161222
2016/12/27 16:57:41 listening on: 127.0.0.1:12949
2016/12/27 16:57:41 target: 118.193.195.23:8989
2016/12/27 16:57:41 encryption: aes
2016/12/27 16:57:41 nodelay parameters: 1 10 2 1
2016/12/27 16:57:41 sndwnd: 1024 rcvwnd: 1024
2016/12/27 16:57:41 compression: true
2016/12/27 16:57:41 mtu: 1350
2016/12/27 16:57:41 datashard: 10 parityshard: 3
2016/12/27 16:57:41 acknodelay: false
2016/12/27 16:57:41 dscp: 0
2016/12/27 16:57:41 sockbuf: 4194304
2016/12/27 16:57:41 keepalive: 10
2016/12/27 16:57:41 snmplog:
2016/12/27 16:57:41 snmpperiod: 60
服务器端似乎并未收到请求
我的服务器端配置如下
{
"listen": "127.0.0.1:12949",
"target": "118.193.195.23:8989",
"key": "122313",
"crypt": "aes",
"mode": "fast3",
"mtu": 1350,
"sndwnd": 1024,
"rcvwnd": 1024,
"datashard": 10,
"parityshard": 3,
"dscp": 0,
"nocomp": false,
"acknodelay": false,
"nodelay": 0,
"interval": 20,
"resend": 2,
"nc": 1,
"sockbuf": 4194304,
"keepalive": 10
}
而ss的配置是127.0.0.1:12949
所以不太明白问题出在哪里
服务端
"listen":"127.0.0.1:12949" 改为
"listen":"0.0.0.0:12949"
target可以改成127.0.0.1(你这样也没错)
服务端
"listen":"127.0.0.1:12949" 改为
"listen":"0.0.0.0:12949"
target可以改成127.0.0.1(你这样也没错)
十分感谢您的回复
已经修改可是问题依旧,能否帮忙看看文件的配置呢
https://github.com/saber1024/kcptun-windows-amd64-20161222
服务端配错了,listen是指监听来自kcptun的端口,而target是指发到ss处理
@codingwen 十分感谢您的回复
我尝试修改了这两个地方,但是还是那个问题
请问您能帮我修改一下吗?十分需要这个
https://github.com/saber1024/kcptun-windows-amd64-20161222
client应该连server的8888啊连8989什么鬼
On Dec 28, 2016 9:07 AM, "shiki" notifications@github.com wrote:
服务端配错了,listen是指监听来自kcptun的端口,而target是指发到ss处理
请问您能帮我修改一下吗?十分需要这个
https://github.com/saber1024/kcptun-windows-amd64-20161222—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/xtaci/kcptun/issues/356#issuecomment-269406645, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJnw_F1sRtV-R3fhgMq2QOikSOQO1orAks5rMbZJgaJpZM4LWH8s
.
{
"localaddr": ":12949",
"remoteaddr": "118.193.195.23:12949",
"key": "122313",
"crypt": "aes",
"mode": "fast3",
"conn": 1,
"autoexpire": 60,
"mtu": 1350,
"sndwnd": 1024,
"rcvwnd": 1024,
"datashard": 10,
"parityshard": 3,
"dscp": 0,
"nocomp": false,
"acknodelay": true,
"nodelay": 0,
"interval": 20,
"resend": 2,
"nc": 1,
"sockbuf": 4194304,
"keepalive": 10
}
{
"listen": "0.0.0.0:12949",
"target": "127.0.0.1:8989",
"key": "122313",
"crypt": "aes",
"mode": "fast3",
"mtu": 1350,
"sndwnd": 1024,
"rcvwnd": 1024,
"datashard": 10,
"parityshard": 3,
"dscp": 0,
"nocomp": false,
"acknodelay": false,
"nodelay": 0,
"interval": 20,
"resend": 2,
"nc": 1,
"sockbuf": 4194304,
"keepalive": 10
}
127.0.0.1:8989
127.0.0.1:12949
以上配置试一下
@lizongzeshunshun 还是不行,我截了2边的图给你看
归档.zip
@xtaci
求帮助
很简单啊, A连B,B连C, C连D,D连E,每个环节都通了就通了啊。
请注意服务器的target
服务端这里
"listen": "127.0.0.1:12949",
"target": "118.193.195.23:8989",
118.193.195.23:8989这个地址的ss运行的是好的"listen": ":12949"就可以了客户端这里
"localaddr": ":12949",
"remoteaddr": "118.193.195.23:12949",
remoteaddr没错,
localaddr配置的端口确定没被占用
最后要注意的是客户端上的ss配置中的server和server_port配置成本地kcptun的localaddr的值,而ss的local_port不必变更
以你现在的配置为例,运行之后,查看一下客户端的12949端口使用情况,对应的IP是127.0.0.1还是0.0.0.0之类,对应配置到ss配置文件中去
Most helpful comment
服务端
"listen":"127.0.0.1:12949" 改为
"listen":"0.0.0.0:12949"
target可以改成127.0.0.1(你这样也没错)