shadowsocks / go-shadowsocks2

Modern Shadowsocks in Go

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

client can connect to the shadowsocks2 server,but can't connect to internet.

33cn opened this issue · comments

commented

root@ecs-fbcd:~/gop/bin# ./go-shadowsocks2 -s 'ss://AEAD_AES_256_GCM:abcdefghi@:443' -verbose
2020/08/13 17:36:27 tcp.go:105: listening TCP on :443
2020/08/13 17:36:33 tcp.go:136: proxy 122.224.166.26:29697 <-> 220.181.52.3:443
2020/08/13 17:36:33 tcp.go:131: failed to connect to target: dial tcp [2402:db40:5100:1011::5]:443: connect: network is unreachable
2020/08/13 17:36:33 tcp.go:136: proxy 122.224.166.26:29921 <-> 114.221.144.19:8080
2020/08/13 17:36:33 tcp.go:136: proxy 122.224.166.26:29889 <-> 101.124.19.122:443
2020/08/13 17:36:34 tcp.go:136: proxy 122.224.166.26:30209 <-> 36.152.5.59:80
2020/08/13 17:36:48 tcp.go:136: proxy 122.224.166.26:34145 <-> 203.119.216.255:80
2020/08/13 17:37:13 tcp.go:136: proxy 122.224.166.26:37313 <-> 39.102.45.64:1883

client can connect to the shadowsocks2 server,but can't connect to internet.

on my server, I can ping google

root@ecs-fbcd:~/gop/bin# ping google.com
PING google.com (172.217.163.238) 56(84) bytes of data.
64 bytes from hkg12s18-in-f14.1e100.net (172.217.163.238): icmp_seq=1 ttl=115 time=1.65 ms
64 bytes from hkg12s18-in-f14.1e100.net (172.217.163.238): icmp_seq=2 ttl=115 time=1.57 ms
64 bytes from hkg12s18-in-f14.1e100.net (172.217.163.238): icmp_seq=3 ttl=115 time=1.58 ms
^C
--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 1.575/1.607/1.659/0.059 ms

I also can't seem to get outbound -- just experimented with running the server on a digitalocean VM I'm already using for something else, and the Qt5 windows client locally, and while the client can connect to the server, none of my local apps seems to be able to get outbound when connecting through the client.

root@ecs-fbcd:~/gop/bin# ./go-shadowsocks2 -s 'ss://AEAD_AES_256_GCM:abcdefghi@:443' -verbose
2020/08/13 17:36:27 tcp.go:105: listening TCP on :443
2020/08/13 17:36:33 tcp.go:136: proxy 122.224.166.26:29697 <-> 220.181.52.3:443
2020/08/13 17:36:33 tcp.go:131: failed to connect to target: dial tcp [2402:db40:5100:1011::5]:443: connect: network is unreachable
2020/08/13 17:36:33 tcp.go:136: proxy 122.224.166.26:29921 <-> 114.221.144.19:8080
2020/08/13 17:36:33 tcp.go:136: proxy 122.224.166.26:29889 <-> 101.124.19.122:443
2020/08/13 17:36:34 tcp.go:136: proxy 122.224.166.26:30209 <-> 36.152.5.59:80
2020/08/13 17:36:48 tcp.go:136: proxy 122.224.166.26:34145 <-> 203.119.216.255:80
2020/08/13 17:37:13 tcp.go:136: proxy 122.224.166.26:37313 <-> 39.102.45.64:1883

client can connect to the shadowsocks2 server,but can't connect to internet.

on my server, I can ping google

root@ecs-fbcd:~/gop/bin# ping google.com
PING google.com (172.217.163.238) 56(84) bytes of data.
64 bytes from hkg12s18-in-f14.1e100.net (172.217.163.238): icmp_seq=1 ttl=115 time=1.65 ms
64 bytes from hkg12s18-in-f14.1e100.net (172.217.163.238): icmp_seq=2 ttl=115 time=1.57 ms
64 bytes from hkg12s18-in-f14.1e100.net (172.217.163.238): icmp_seq=3 ttl=115 time=1.58 ms
^C
--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 1.575/1.607/1.659/0.059 ms

What client are you using? I see your command to start the server, but what command are you using to start the client?

commented

+1