Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

移动4G cmnet 连不上 #2143

Closed
jmireles7 opened this issue Mar 3, 2019 · 36 comments

Comments

Projects
None yet
9 participants
@jmireles7
Copy link

commented Mar 3, 2019

Please read contributing guidelines. Thanks.

Describe the bug
A clear and concise description of what the bug is.

移动4G连上有问题,dns请求发不出去的样子,表现为连上后网页打不开,而telegram却能正常使用,同样的节点配置,使用v2rayNG 的ss功能可以正常连接!

根据之前的issues
#591

改DNS检查为allowed,无效
APN连接点的端口为80,无效
APN协议从"ipv4/ipv6"改成"ipv4",无效

补充,发现APN改为cmwap可以连上,改回cmnet又不行!cmwap无法使用微信的语音视频等功能…蛋疼

使用v2rayNG 的ss功能两个APN都能正常连接!
望大佬看看原因…

To Reproduce
Steps to reproduce the behavior:

  1. 关闭wifi
  2. 启动 shadowsocks 并连接
  3. 开启google
  4. 查看错误

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Smartphone (please complete the following information):

  • Android 8.0 OxygenOS 5.0.8
  • Device: [ OnePlus 3T ]
  • Version: [ONEPLUS A3010_28_181206]
  • Last version that did not exhibit the issue: [not applicable]

Configuration
Put an x inside the [ ] that applies.

  • IPv4 server address
  • IPv6 server address
  • Client IPv4 availability
  • Client IPv6 availability
  • Encrypt method:
  • Route
    • All
    • Bypass LAN
    • Bypass China
    • Bypass LAN & China
    • GFW List
    • China List
    • Custom rules
  • IPv6 route
  • Apps VPN mode
    • Bypass mode
  • Remote DNS: 8.8.8.8 (修改过,并无改善)
    *[x] DNS over UDP
  • Plugin configuration (if applicable):
  • Auto Connect
  • TCP Fast Open
  • If you're not using VPN mode, please supply more details here:

Additional context
Add any other context about the problem here.

上截图,为防止是线路导致的问题,我在家里的树莓派安装服务端,
404
_20190305221241
_20190305221245
_20190305221249

连接后访问国内网站某度,完全无法打开,截图中可以看到,shadowsocks 中间有发送与接收数据,由于找不到可以直接用ip访问的网站,我访问 http://119.29.29.29/,虽然是个404页面,但确实打开了。 然后某些直接使用ip连接的app也没有问题。

V2客户端正常

_20190305221434
_20190305221437

最后, 把APN换成 CMWAP 后就能正常打开网页 - -

@madeye

@Mygod

This comment has been minimized.

Copy link
Contributor

commented Mar 6, 2019

Disable DNS over UDP.

@Mygod Mygod closed this Mar 7, 2019

@jmireles7

This comment has been minimized.

Copy link
Author

commented Mar 8, 2019

@Mygod 恕在下愚钝,只找到DNS Forwading,并没有找到DNS over UDP 这个选项,而DNS Forwading开关并无改善此问题。

@Mygod

This comment has been minimized.

Copy link
Contributor

commented Mar 8, 2019

Use latest beta release.

@everthis

This comment has been minimized.

Copy link

commented Mar 12, 2019

same here, using v4.7.2 北京移动

@userid

This comment has been minimized.

Copy link

commented Mar 14, 2019

这是因为北京移动会偶尔禁掉正常的udp流量。而ss好像总会走一部分的UDP。
怀疑是4.7新加的"UDP fallback option"不完善, 降级到4.6.x 应该就好了。

@jmireles7

This comment has been minimized.

Copy link
Author

commented Mar 15, 2019

@Mygod 使用 GooglePlay 最新Beta版 4.7.3测试,问题依然存在。

@everthis

This comment has been minimized.

Copy link

commented Mar 15, 2019

Version 4.6.1 has the same problem on Galaxy s10 over China mobile network.

@Mygod

This comment has been minimized.

Copy link
Contributor

commented Mar 15, 2019

Sounds like it might be local DNS issue. Dump logcat?

@Mygod Mygod reopened this Mar 15, 2019

@jmireles7

This comment has been minimized.

Copy link
Author

commented Mar 16, 2019

log.txt
我点击了若干次测试连接,并保存了 logcat 输出,请查看附件txt @Mygod

@luvvien

This comment has been minimized.

Copy link

commented Mar 19, 2019

Outline 了解一下

@madeye

This comment has been minimized.

Copy link
Contributor

commented Mar 19, 2019

@Mygod Is it possible an IPv6 related issue, as CMNET may assign IPv6 address to the client.

@madeye

This comment has been minimized.

Copy link
Contributor

commented Mar 19, 2019

@jmireles7 Could you check if you enabled IPv6 route option? If yes, please try disable it.

@Mygod

This comment has been minimized.

Copy link
Contributor

commented Mar 19, 2019

@madeye Just tested with cmnet with IPv6, everything seems fine.

@everthis

This comment has been minimized.

Copy link

commented Mar 20, 2019

Hello, I'm having trouble on my phone over China Mobile network in Beijing. I shared the same config through QR code with one of my colleagues(whose ISP is China Unicom). And everything was fine on his phone.

Besides, if I use China Unicom network with the same phone and the same SS config, everything is fine.

Here are some screenshots on my phone. Is there anything I can do to debug?

20190320_204950
Screenshot_20190320-210355_Shadowsocks

@jmireles7

This comment has been minimized.

Copy link
Author

commented Mar 21, 2019

Hi,
CMNET确实为我分配了一个IPV6的地址,但是在APP中关闭IPV6路由后依然面临同样的问题。

@yzou

This comment has been minimized.

Copy link

commented Mar 27, 2019

这个问题应该是修改了tun2socks 里面的dns gw 导致的,移动网络会分配一个dns 地址,dns 请求会发送到这个地址,然后只有发到172.19.0.2 地址的dns 请求才会tunnel 到配置的8.8.8.8,发到移动的dns 地址的dns请求会做 udprelay,但可能境外服务器请求不到移动的dns

badvpn commit:
shadowsocks/badvpn@ba4c45d

网卡dns 配置:
rmnet0:
221.179.155.193
221.179.155.209
2049:8000:2000:0:70::1
2049:8000:2000:0:170::1

tun0:
172.19.0.2

build debug 版本的 log 如下:

2019-03-27 22:46:47.948 23511-23511/? D/shadowsocks: [udp] server receive a packet
2019-03-27 22:46:47.948 23511-23511/? D/shadowsocks: [1080] [udp] cache hit: 221.179.155.209:53 <-> 127.0.0.1:35443
2019-03-27 22:46:50.952 23511-23511/? D/shadowsocks: [udp] server receive a packet
2019-03-27 22:46:50.952 23511-23511/? D/shadowsocks: [1080] [udp] cache hit: 221.179.155.193:53 <-> 127.0.0.1:60414
2019-03-27 22:46:52.955 23511-23511/? D/shadowsocks: [udp] server receive a packet
2019-03-27 22:46:52.956 23511-23511/? D/shadowsocks: [1080] [udp] cache hit: 221.179.155.193:53 <-> 127.0.0.1:35443
2019-03-27 22:46:55.963 23511-23511/? D/shadowsocks: [udp] server receive a packet
2019-03-27 22:46:55.963 23511-23511/? D/shadowsocks: [1080] [udp] cache miss: 221.179.155.193:53 <-> 127.0.0.1:56281
2019-03-27 22:46:57.965 23511-23511/? D/shadowsocks: [udp] server receive a packet
2019-03-27 22:46:57.965 23511-23511/? D/shadowsocks: [1080] [udp] cache miss: 221.179.155.193:53 <-> 127.0.0.1:38138

@yzou

This comment has been minimized.

Copy link

commented Mar 27, 2019

把这个改动回退就可以用移动网络了

shadowsocks/badvpn@ba4c45d

@Mygod

This comment has been minimized.

Copy link
Contributor

commented Mar 27, 2019

@yzou Interesting. I don't think reverting that commit is the right fix. Can you fill out the issue template as well? I will take a look later.

@madeye

This comment has been minimized.

Copy link
Contributor

commented Mar 27, 2019

It's possible that some app won't follow system's default DNS settings.

I think it's safe to revert that change, given there's no complain about that for years.

@Mygod

This comment has been minimized.

Copy link
Contributor

commented Mar 28, 2019

@madeye I don't think this is an app specific issue. For some reason, it seems to be sending its DNS queries to the wrong interface (a ROM-specific bug?). Our current implementation calls Network.getAllByName API to do local DNS resolving but maybe we need to check whether this API is working properly on older APIs. (as far as I remember, it's working perfectly on Android 9)

@madeye

This comment has been minimized.

Copy link
Contributor

commented Mar 28, 2019

IIRC, browsers like Chrome / FIrefox use their own DNS resolvers. Then we may see this kind of problem:

  1. An app reads the DNS config from system and connect to them directly.
  2. VPN connection is setup.
  3. That app keeps sending DNS queries to previous system's DNS, but cannot be redirected by tun2socks.
  4. DNS leak (to the remote server) happens.
@yzou

This comment has been minimized.

Copy link

commented Mar 28, 2019

@yzou Interesting. I don't think reverting that commit is the right fix. Can you fill out the issue template as well? I will take a look later.

@Mygod You can reproduce by connecting ss under wifi network, and then disable wifi network, then for China Mobile cmnet, rmnet0 interface will be active and set China Mobile DNS server on this interface.

I'm in Beijing using Huawei P20 Pro, my rmnet0 DNS servers are active after switching from wifi to mobile data.

I use this app to check interfaces' DNS config:
https://play.google.com/store/apps/details?id=com.frostnerd.dnschanger&rdid=com.frostnerd.dnschanger

@Mygod

This comment has been minimized.

Copy link
Contributor

commented Mar 28, 2019

Please fill out the issue template.

@yzou

This comment has been minimized.

Copy link

commented Mar 28, 2019

@Mygod

This comment has been minimized.

Copy link
Contributor

commented Mar 29, 2019

IIRC, browsers like Chrome / FIrefox use their own DNS resolvers. Then we may see this kind of problem:

  1. An app reads the DNS config from system and connect to them directly.
  2. VPN connection is setup.
  3. That app keeps sending DNS queries to previous system's DNS, but cannot be redirected by tun2socks.
  4. DNS leak (to the remote server) happens.

Tested on com.android.chrome 73.0.3683.90. Failed to observe such behavior. In fact everything works as expected. Additionally, I do not think this app should be responsible for other app/ROM's bugs.

@Mygod Mygod referenced this issue Mar 29, 2019

Closed

DNS failed to forward after network switch #2180

0 of 13 tasks complete
@Mygod

This comment has been minimized.

Copy link
Contributor

commented Mar 29, 2019

Originally posted by @madeye in #2180 (comment)

I cannot reproduce this problem with EMUI 9.0 on China Union network.

Since only CMNET has this issue, I guess it maybe related to VoIP.

So please help to confirm if VoIP enabled. If enabled, please disable it and try again.

I do have both VoLTE and Wi-Fi calling enabled on my CMNET card. Still cannot reproduce.

@yzou

This comment has been minimized.

Copy link

commented Mar 29, 2019

Connect ss under China Mobile 4G network, and sleep phone for a while, e.g. half an hour, I can see dns to China Mobile's DNS server in log:

image

And this time, I can't open any sites, including Twitter app.

The chrome error msg is:

You connection was interrupted
A netwrok change was detected
ERR_NETWORK_CHANGED

@Mygod

This comment has been minimized.

Copy link
Contributor

commented Mar 29, 2019

You mentioned put your phone to idle so I think your issue is unrelated to #2143.

@yzou

This comment has been minimized.

Copy link

commented Mar 29, 2019

Connect ss under China Mobile 4G network, and sleep phone for a while, e.g. half an hour, I can see dns to China Mobile's DNS server in log:

image

And this time, I can't open any sites, including Twitter app.

The chrome error msg is:

You connection was interrupted
A netwrok change was detected
ERR_NETWORK_CHANGED

Back from sleep, I saw these log, it must be the reason of network broken (only qq can receive msg):

2019-03-29 18:50:17.654 1223-14623/? V/ActivityManager: Activity slept: token=Token{8d29eec ActivityRecord{ffefd9f u0 com.github.shadowsocks/.MainActivity t13669}} callingPid=0
2019-03-29 18:50:35.178 1223-1300/? I/NotificationService: enqueueNotificationInternal: pkg=com.github.shadowsocks id=1 notification=Notification(channel=service-vpn pri=-2 contentView=null vibrate=null sound=null tick defaults=0x0 flags=0x40 color=0xff607d8b vis=PRIVATE)
2019-03-29 18:50:35.180 1223-1300/? I/NotificationService: enqueueNotificationInternal Channel Info : pkg=com.github.shadowsocks id=1 importance =2
2019-03-29 18:50:35.229 2882-3003/? I/AppManager: app:com.github.shadowsocks Notification update time:920126195
2019-03-29 18:50:58.121 27216-18428/? I/chatty: uid=10197(com.github.shadowsocks) DefaultDispatch identical 1 line
2019-03-29 18:51:15.874 1223-5092/? V/ActivityManager: Activity slept: token=Token{8d29eec ActivityRecord{ffefd9f u0 com.github.shadowsocks/.MainActivity t13669}} callingPid=0
2019-03-29 18:51:18.440 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:18.442 12043-12043/? I/chatty: uid=10197(com.github.shadowsocks) /data/app/com.github.shadowsocks-HmiSya_RBDoipJt3enF-bw==/lib/arm64/libss-local.so identical 23 lines
2019-03-29 18:51:18.442 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:20.489 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:20.492 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:22.538 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:22.541 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:24.585 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:24.587 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:24.588 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:25.444 1223-1300/? I/NotificationService: enqueueNotificationInternal: pkg=com.github.shadowsocks id=1 notification=Notification(channel=service-vpn pri=-2 contentView=null vibrate=null sound=null tick defaults=0x0 flags=0x40 color=0xff607d8b vis=PRIVATE)
2019-03-29 18:51:25.446 1223-1300/? I/NotificationService: enqueueNotificationInternal Channel Info : pkg=com.github.shadowsocks id=1 importance =2
2019-03-29 18:51:25.497 2882-3003/? I/AppManager: app:com.github.shadowsocks Notification update time:920176463
2019-03-29 18:51:25.500 11639-11639/? D/NotificationEntryMgr: updateNotification(StatusBarNotification(pkg=com.github.shadowsocks user=UserHandle{0} id=1 tag=null key=0|com.github.shadowsocks|1|null|10197: Notification(channel=service-vpn pri=-2 contentView=null vibrate=null sound=null tick defaults=0x0 flags=0x62 color=0xff607d8b vis=PRIVATE)))
2019-03-29 18:51:25.509 11639-11667/? D/ReporterUtil: e id:344 type:{pkg:com.github.shadowsocks,hw_type:null,hw_btw:false,onGoing:true,importance:2}
2019-03-29 18:51:26.633 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:26.635 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:28.681 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:28.682 12043-12043/? I/chatty: uid=10197(com.github.shadowsocks) /data/app/com.github.shadowsocks-HmiSya_RBDoipJt3enF-bw==/lib/arm64/libss-local.so identical 7 lines
2019-03-29 18:51:28.683 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:30.728 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:30.733 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:32.777 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:32.778 12043-12043/? I/chatty: uid=10197(com.github.shadowsocks) /data/app/com.github.shadowsocks-HmiSya_RBDoipJt3enF-bw==/lib/arm64/libss-local.so identical 5 lines
2019-03-29 18:51:32.778 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:34.825 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:34.825 12043-12043/? I/chatty: uid=10197(com.github.shadowsocks) /data/app/com.github.shadowsocks-HmiSya_RBDoipJt3enF-bw==/lib/arm64/libss-local.so identical 1 line
2019-03-29 18:51:34.825 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:36.872 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:36.874 12043-12043/? I/chatty: uid=10197(com.github.shadowsocks) /data/app/com.github.shadowsocks-HmiSya_RBDoipJt3enF-bw==/lib/arm64/libss-local.so identical 7 lines
2019-03-29 18:51:36.874 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:38.921 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:38.922 12043-12043/? I/chatty: uid=10197(com.github.shadowsocks) /data/app/com.github.shadowsocks-HmiSya_RBDoipJt3enF-bw==/lib/arm64/libss-local.so identical 3 lines
2019-03-29 18:51:38.924 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:40.969 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:40.974 12043-12043/? I/chatty: uid=10197(com.github.shadowsocks) /data/app/com.github.shadowsocks-HmiSya_RBDoipJt3enF-bw==/lib/arm64/libss-local.so identical 16 lines
2019-03-29 18:51:40.974 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:43.016 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:43.018 12043-12043/? I/chatty: uid=10197(com.github.shadowsocks) /data/app/com.github.shadowsocks-HmiSya_RBDoipJt3enF-bw==/lib/arm64/libss-local.so identical 8 lines
2019-03-29 18:51:43.018 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:45.065 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:45.067 12043-12043/? I/chatty: uid=10197(com.github.shadowsocks) /data/app/com.github.shadowsocks-HmiSya_RBDoipJt3enF-bw==/lib/arm64/libss-local.so identical 10 lines
2019-03-29 18:51:45.068 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:46.341 27216-27648/? I/chatty: uid=10197(com.github.shadowsocks) DefaultDispatch identical 1 line
2019-03-29 18:51:47.113 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:47.114 12043-12043/? I/chatty: uid=10197(com.github.shadowsocks) /data/app/com.github.shadowsocks-HmiSya_RBDoipJt3enF-bw==/lib/arm64/libss-local.so identical 4 lines
2019-03-29 18:51:47.114 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:49.161 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:49.162 12043-12043/? I/chatty: uid=10197(com.github.shadowsocks) /data/app/com.github.shadowsocks-HmiSya_RBDoipJt3enF-bw==/lib/arm64/libss-local.so identical 1 line
2019-03-29 18:51:49.162 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:51.209 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:51.214 12043-12043/? I/chatty: uid=10197(com.github.shadowsocks) /data/app/com.github.shadowsocks-HmiSya_RBDoipJt3enF-bw==/lib/arm64/libss-local.so identical 7 lines
2019-03-29 18:51:51.214 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:53.257 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:53.261 12043-12043/? I/chatty: uid=10197(com.github.shadowsocks) /data/app/com.github.shadowsocks-HmiSya_RBDoipJt3enF-bw==/lib/arm64/libss-local.so identical 16 lines
2019-03-29 18:51:53.262 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:54.720 1223-14623/? V/ActivityManager: Activity slept: token=Token{8d29eec ActivityRecord{ffefd9f u0 com.github.shadowsocks/.MainActivity t13669}} callingPid=0
2019-03-29 18:51:55.305 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:55.310 12043-12043/? I/chatty: uid=10197(com.github.shadowsocks) /data/app/com.github.shadowsocks-HmiSya_RBDoipJt3enF-bw==/lib/arm64/libss-local.so identical 20 lines
2019-03-29 18:51:55.310 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:57.353 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:57.355 12043-12043/? I/chatty: uid=10197(com.github.shadowsocks) /data/app/com.github.shadowsocks-HmiSya_RBDoipJt3enF-bw==/lib/arm64/libss-local.so identical 8 lines
2019-03-29 18:51:57.356 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:59.401 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:51:59.407 12043-12043/? I/chatty: uid=10197(com.github.shadowsocks) /data/app/com.github.shadowsocks-HmiSya_RBDoipJt3enF-bw==/lib/arm64/libss-local.so identical 28 lines
2019-03-29 18:51:59.408 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:52:01.448 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:52:01.450 12043-12043/? I/chatty: uid=10197(com.github.shadowsocks) /data/app/com.github.shadowsocks-HmiSya_RBDoipJt3enF-bw==/lib/arm64/libss-local.so identical 7 lines
2019-03-29 18:52:01.450 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:52:01.451 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:52:01.451 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:52:01.451 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:52:01.452 12043-12043/? I/chatty: uid=10197(com.github.shadowsocks) /data/app/com.github.shadowsocks-HmiSya_RBDoipJt3enF-bw==/lib/arm64/libss-local.so identical 3 lines
2019-03-29 18:52:01.452 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:52:03.226 26639-21619/? V/FA-SVC: Fetching remote configuration: com.github.shadowsocks
2019-03-29 18:52:03.496 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:52:05.545 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:52:05.551 12043-12043/? I/chatty: uid=10197(com.github.shadowsocks) /data/app/com.github.shadowsocks-HmiSya_RBDoipJt3enF-bw==/lib/arm64/libss-local.so identical 16 lines
2019-03-29 18:52:05.551 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:52:07.593 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:52:07.607 12043-12043/? I/chatty: uid=10197(com.github.shadowsocks) /data/app/com.github.shadowsocks-HmiSya_RBDoipJt3enF-bw==/lib/arm64/libss-local.so identical 22 lines
2019-03-29 18:52:07.607 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:52:09.641 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:52:09.651 12043-12043/? I/chatty: uid=10197(com.github.shadowsocks) /data/app/com.github.shadowsocks-HmiSya_RBDoipJt3enF-bw==/lib/arm64/libss-local.so identical 12 lines
2019-03-29 18:52:09.652 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:52:11.689 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:52:11.697 12043-12043/? I/chatty: uid=10197(com.github.shadowsocks) /data/app/com.github.shadowsocks-HmiSya_RBDoipJt3enF-bw==/lib/arm64/libss-local.so identical 15 lines
2019-03-29 18:52:11.698 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:52:13.737 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected
2019-03-29 18:52:13.747 12043-12043/? I/chatty: uid=10197(com.github.shadowsocks) /data/app/com.github.shadowsocks-HmiSya_RBDoipJt3enF-bw==/lib/arm64/libss-local.so identical 19 lines
2019-03-29 18:52:13.747 12043-12043/? E/shadowsocks: getpeername: Transport endpoint is not connected

@yzou

This comment has been minimized.

Copy link

commented Mar 29, 2019

You mentioned put your phone to idle so I think your issue is unrelated to #2143.

It's not a must.

@madeye

This comment has been minimized.

Copy link
Contributor

commented Mar 29, 2019

getpeername: Transport endpoint is not connected

Means shadowsocks client cannot reach the server. It looks our background service is killed or suspended by the system.

Make sure you exclude shadowsocks from battery optimization in EMUI.

@yzou

This comment has been minimized.

Copy link

commented Mar 29, 2019

I can see all processes active in bg through ps -Af

@madeye madeye referenced this issue Apr 7, 2019

Closed

Shadowsocks 4.7.3 cannot connect #2184

5 of 17 tasks complete
@zxkane

This comment has been minimized.

Copy link

commented Apr 11, 2019

遇到类似的问题,在联通4g网络下部分app(Google doc)不能走VPN连接。同样的服务端,同样的配置。4g下可以在浏览器或 app google访问google。ss测试连接服务端也正常。

Wifi下就没有问题,各种服务都可以访问。

一加5,andriod9

@Aodi

This comment has been minimized.

Copy link

commented Apr 19, 2019

北京移动,ssr,4G不行,wifi正常。试了多种解决方法,都不能解决。

@madeye

This comment has been minimized.

Copy link
Contributor

commented Apr 19, 2019

@yzou please help to confirm the issue is fixed in latest version.

@madeye madeye closed this Apr 22, 2019

@madeye madeye added the no response label Apr 22, 2019

@yzou

This comment has been minimized.

Copy link

commented Apr 22, 2019

@yzou please help to confirm the issue is fixed in latest version.

It's fixed. Great work!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.