-
-
Notifications
You must be signed in to change notification settings - Fork 11.6k
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
with obfs plugin enabled the connection does not work on ss-libev 3.0.3 and ss-android 4.0.4/4.1.1 #1155
Comments
Could you try disabling tcp_fastopen? |
Disabled on server side, on android it is by default disabled as no Root permission. |
I tried your configs but cannot reproduce your issue locally. What's the version of your |
simple-obfs 0.0.2 |
Please try the latest commit of simple-obfs first. |
Just tried but got a issue during make: Best Regards, |
solved the dependency problem and compiled the simple-obfs 0.0.3 |
What's your network environment? WiFi or 3G/4G? |
I tested with both WiFi (company wifi, direct internet access) and 4G, both the same situation. |
If so, it looks a device bug. Could you connect to your server from a PC or other phone? For example, you can start a |
Since there's no windows-based client available now, I will try this tonight at home, on my linux box / merlin router. Will update the result then. Thanks. |
I think I've found the problem: Therefore I compared both mode:
The problem is that in plugin mode it is always listening to 127.0.0.1 but not the server ip. Is there a parameter in JSON that could change the behavior? I tried "server","server_host","local_address" but no one could change this. Thanks and Best Regards, |
According to your log, it's listening on
Also, if the plugin listened at local address. I don't think you would have any log like these
|
Sorry for the carelessness. I saw 'INFO: tcp server listening at 127.0.0.1:42144' only but missed '[simple-obfs] INFO: listening at 0.0.0.0:8191' Anyway for now I would use the standalone mode as a temporary workaround. Thanks and Regards. |
Closed due to inactivity. |
Environment
Configuration
server:
{
"server":"0.0.0.0",
"server_port":1202,
"local_address":"127.0.0.1",
"local_port":1080,
"password":"xxxxxxxx",
"timeout":600,
"method":"chacha20",
"plugin":"obfs-server",
"plugin-opts":"obfs=http",
"fast_open":true
}
client: V4.0.4/4.1.1 (both have the same problem)
Plugin: Simple obfuscation v0.0.5
configuration:
obfuscation wrapper: http
obfuscation hostname: cn.bing.com
Put an
x
inside the [ ] that applies.Symptom:
2017-03-08 04:59:48 INFO: using tcp fast open
2017-03-08 04:59:48 INFO: plugin "obfs-server" enabled
2017-03-08 04:59:48 INFO: UDP relay enabled
2017-03-08 04:59:48 INFO: initializing ciphers... chacha20
2017-03-08 04:59:48 INFO: tcp server listening at 127.0.0.1:53175
2017-03-08 04:59:48 INFO: udp server listening at 0.0.0.0:1202
2017-03-08 04:59:48 [simple-obfs] INFO: tcp port reuse enabled
2017-03-08 04:59:48 [simple-obfs] INFO: listening at 0.0.0.0:1202
2017-03-08 04:59:48 ERROR: failed to handshake with 127.0.0.1: invalid host name
2017-03-08 04:59:48 [simple-obfs] ERROR: remote recv: Connection reset by peer
2017-03-08 04:59:57 ERROR: failed to handshake with 127.0.0.1: invalid host name
2017-03-08 04:59:57 [simple-obfs] ERROR: remote recv: Connection reset by peer
2017-03-08 04:59:57 ERROR: failed to handshake with 127.0.0.1: invalid address type
2017-03-08 04:59:57 [simple-obfs] ERROR: remote recv: Connection reset by peer
What did you do / What did you see:
Could you kindly suggest how to solve this issue?
Thanks and Regards,
Ricky
The text was updated successfully, but these errors were encountered: