Go Down

Topic: Ethernet Library: long-life TCP connection and Keep-Alive support (Read 1 time) previous topic - next topic

themilkman

Hi,
I try to establish a long life TCP (not http) connection between an Arduino with Ethernet-Shield (Client) and a server for my project.
Therefore I need a stable connection for...as long as possible.  :smiley-mr-green:

I'd like to ensure that both componets are connected to each other. On the server side (Java) there are of course the capabilities for TCP keep-alive connections. I thought the Ethernet Shield  would support this feature too. But now I do not find any useful information about this anymore. Am I wrong? In that case, what would be your recommendation to ensure a fast detection of a dead connection and a reconnect? Are there any best practices?
If it does support it - is it enabled by default (would break with the RFC I guess) or how may I configure/enable it?

And do other Shields like the redfly wireless shield support it?

Thank you very much for any answers/examples/tipps :-)

themilkman

zoomkat

Google forum search: Use Google Advanced Search and use Http://forum.arduino.cc/index in the "site or domain:" box.

themilkman

zoomkat: No, I did not yet. Currently I have no problem with the connection but the Arduino might be set in a more unreliable network environment. What could/should I see by connecting via telnet? Thanks for explanation.

zoomkat

Some previous arduino telnet discussions for your study:

https://www.google.com/search?hl=en&as_q=telnet&as_epq=&as_oq=&as_eq=&as_nlo=&as_nhi=&lr=&cr=&as_qdr=all&as_sitesearch=http%3A%2F%2Farduino.cc%2Fforum&as_occt=any&safe=off&tbs=&as_filetype=&as_rights=
Google forum search: Use Google Advanced Search and use Http://forum.arduino.cc/index in the "site or domain:" box.

Go Up