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

Shadowsocks 4.7.3 cannot connect #2184

Closed
AntonKosov opened this issue Apr 7, 2019 · 15 comments

Comments

Projects
None yet
3 participants
@AntonKosov
Copy link

commented Apr 7, 2019

When the app was updated from Google Play Store a few days ago, it stopped work. Testing of a connection writes "Internet Unavailable" after a while. All applications that are in bypass mode had access to the Internet. I tried to reinstall the app, but it didn't help. Version 4.6.5, which I installed from GitHub, works perfectly (I transferred all settings through a JSON file).

Here are some details:

  • Android version: 9
  • Device: Xiaomi Mi A1
  • Version: 4.7.3
  • Last version that did not exhibit the issue: 4.7.0

Configuration:

  • IPv4 server address
  • IPv6 server address
  • Client IPv4 availability
  • Client IPv6 availability
  • Encrypt method: AES-256-CFB
  • 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
  • DNS over UDP
  • Plugin configuration (if applicable):
  • Auto Connect
  • TCP Fast Open
@madeye

This comment has been minimized.

Copy link
Contributor

commented Apr 7, 2019

Can you visit 1.1.1.1 when connected?

@AntonKosov

This comment has been minimized.

Copy link
Author

commented Apr 7, 2019

4.6.5: everything works perfectly.
4.7.0: everything works perfectly.
4.7.1: 1.1.1.1 works, but others don't (google.com, for example).
4.7.3: 1.1.1.1 works, but others don't (google.com, for example).

@Mygod

This comment has been minimized.

Copy link
Contributor

commented Apr 7, 2019

Grab a logcat.

@AntonKosov

This comment has been minimized.

Copy link
Author

commented Apr 7, 2019

  1. Installed 4.7.3
  2. Imported my settings.
  3. Ran logcat.
  4. Pressed the connect button.
  5. Pressed the test panel.
  6. Got "Internet Unavailable".
  7. Stopped logcat

shadowsocks.txt

@madeye

This comment has been minimized.

Copy link
Contributor

commented Apr 7, 2019

@AntonKosov

This comment has been minimized.

Copy link
Author

commented Apr 7, 2019

This version works!

@madeye

This comment has been minimized.

Copy link
Contributor

commented Apr 7, 2019

Thanks!

So, it's the same problem found here: #2143 (comment)

It looks possible that system will ignore the VPN interface's default DNS.

It's still not clear to me why we cannot reproduce it on same MIUI and EMUI system locally.

@AntonKosov

This comment has been minimized.

Copy link
Author

commented Apr 7, 2019

I've got Xiaomi Mi A1 Global Version (Android One)

@madeye

This comment has been minimized.

Copy link
Contributor

commented Apr 7, 2019

@Mygod let's revert that commit for now. Otherwise, many users would be affected.

We can keep investing this issue, until the root cause is found.

@AntonKosov

This comment has been minimized.

Copy link
Author

commented Apr 7, 2019

Thanks! Let me know if you need to test the bugfix on my device.

madeye added a commit that referenced this issue Apr 7, 2019

@madeye

This comment has been minimized.

Copy link
Contributor

commented Apr 7, 2019

Looks duplicate to #2143.

@Mygod

This comment has been minimized.

Copy link
Contributor

commented Apr 7, 2019

@madeye Can you reproduce this issue?

@madeye

This comment has been minimized.

Copy link
Contributor

commented Apr 7, 2019

Nope, I can't.

@Mygod

This comment has been minimized.

Copy link
Contributor

commented Apr 9, 2019

I would still argue that this hack/workaround would break non-DNS traffic through port 53 (e.g. QUIC on UDP 53). I think their ROM is fundamentally broken for VPN.

@madeye

This comment has been minimized.

Copy link
Contributor

commented Apr 9, 2019

A better way is identifying DNS packet in tun2socks.

Let me try it later.

madeye added a commit that referenced this issue Apr 9, 2019

@madeye madeye closed this Apr 22, 2019

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.