Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

It it important to rely on TCP guaranteed delivery even in case of mobile client which could disappear in a tunnel for a long time when TCP with standard settings give up and close the connection. Is it possible to make TCP implementation keep trying for up to 10-20 minutes? What settings should be done on linux and on mobile phones (android and iOS)? Thank you.

share|improve this question

man tcp - look for tcp_retries[1,2] for Linux machines. I have no idea what to do for Android and given Apples attitude to system-level tweaking there is probably absolutely no way to do this on iOS except when you jailbreak.

TCP socket timeouts put aside, most applications will implement their own timeouts which are probably considerably shorter than the ones from the transport layer. Whether this is configurable at all clearly depends on the application in question - there is no system-wide parameter for it.

share|improve this answer

It's not possible. The way to solve this problem is with a layer on top of the TCP layer that provides the semantics you need. This layer would have to add an identifier to each message, implement message acknowledgements, re-establish the TCP connection if it broken, and re-send all unacknowledged messages.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.