Handling connection failures.

Checking to see if the connection is dropping for any reason like Android OS killing the service, connection time outs, etc.

added component::circumvention/snowflake priority::medium severity::normal snowflake-mobile status::new type::task labels

Add snowflake-mobile keyword to Hashik's GSoC 2020 tickets.

Trac:
Keywords: N/A deleted, snowflake-mobile added

Trac:
Keywords: N/A deleted, Snowflake_Android added

Trac:
Keywords: Snowflake_Android deleted, N/A added

Trac:
Cc: cohosh, phw, arlolra, dcf to cohosh, phw, arlolra, dcf, HashikD

Hey! what is considered as a connection termination or failure of the client for (or client leaving) Snowflake proxy?

What is the final state that I should look for to mark the end of the connection for WebRTC; to go ahead and close the connections and restart a the SDP offer request from the broker?

In onIceConnectionChange what is the final state that I should look for: here are the list of state

I am getting mixed answers, sometimes it's logging "Failed" as the final state other times "closed".

Feel free to ask for clarification if I am not clear enough.

Trac:
Status: new to needs_information

This is a really good question, and one that we've worked on with the other proxy implementations.

There are a few things we can look for to close a connection. In the Google API, there should be an OnClose event: https://webrtc.org/getting-started/data-channels#open_and_close_events that we can add a listener to. You can see that in our Javascript proxy code here.

We also want to close if there is an error (see here).

We also added a timeout as an extra check. We can do this because the underlying layer is sending keep-alive messages every 10 seconds. You can see that in the existing code here.

We also want to close the connection if it is closed or we receive an error from the WebSocket side. See here.

Trac:
Status: needs_information to new

moved to tpo/anti-censorship/pluggable-transports/snowflake#34278 (closed)