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

Still catched by Local ISP #33

Open
bash99 opened this issue Apr 28, 2018 · 2 comments
Open

Still catched by Local ISP #33

bash99 opened this issue Apr 28, 2018 · 2 comments

Comments

@bash99
Copy link

bash99 commented Apr 28, 2018

Version 1.1.2
Client
{
"ServerName":"www.oracle.com",
"Key":"XXXXXX",
"TicketTimeHint":3600,
"Browser":"chrome",
"FastOpen":false
}
Server
{
"WebServerAddr":"2.19.128.136:443",
"Key":"XXXXXX",
"FastOpen":false
}

ss-libev run with xchacha20-ietf-poly1305 method.

At first, connection is fine. after about an hour with some traffic (no big download, just some browser), 443 port is blocked in local ISP. Stop client for about a day, 443 port is opened again.

Local ISP is very sensitive that tls1.2 from ssr or tls from simple-obfs is blocked after some traffic too. Only ws over https can work on port 443.

@cbeuw
Copy link
Owner

cbeuw commented Apr 28, 2018

I think our traffic is still significant in that each TCP connection will lead to a TLS handshake with the proxy server. Frequent handshakes are not normal.

I'm thinking of establishing a fixed amount of standing TLS sessions and multiplex traffic through them.

@bash99
Copy link
Author

bash99 commented May 11, 2018

how about implement http/2 support?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants