Opened 8 years ago

Last modified 4 years ago

#11836 new bug

Network Stack Doesn't Detect Dead or Dropped Network Connections

Reported by: AGMS Owned by: nobody
Priority: normal Milestone: R1
Component: Network & Internet Version: R1/Development
Keywords: Dropped Dead Connection Timeout Disconnect Keep-alive Cc: agmsmith@…, ttcoder
Blocked By: Blocking:
Platform: All


BeOS and Linux both detect dead network connections, while Haiku doesn't.

This is most annoying when running a BeShare server (Atrus is one, see plus you need the Muscle library too and the muscled daemon). Every time a connection is lost (client turned off their computer without shutting down (often because of a crash), or router was rebooted and didn't close the TCP stream) the result is a dead connection. The BeShare server and Atrus both still see the dead connection as existing, resulting in that user being logged in multiple times. With BeOS/Linux, the dead connection is noticed and disconnected after about a minute.

Maybe something to do with implementing keep-alive packets?

  • Alex

Change History (7)

comment:1 by bbjimmy, 7 years ago

add me for cc

comment:2 by waddlesplash, 7 years ago

This happens the other direction too (non-Haiku server dies unexpectedly, client on Haiku doesn't detect connection death), in the case of the Kitchen buildserver at least. Which is really annoying, because it means the client has to be manually restarted every time the server disconnects...

If someone could find time to investigate this, I'd be very grateful.

comment:3 by cocobean, 4 years ago

Last edited 4 years ago by cocobean (previous) (diff)

comment:4 by waddlesplash, 4 years ago

Absolutely nothing has changed on R1/beta1 so retesting there would be useless. Nothing at all in the network stack has changed wrt. this ticket (in fact the TCP module's keepalive system has not changed at all), so there is nothing to retest. Please stop asking for retests on tickets that you know nothing about.

comment:5 by ttcoder, 4 years ago

Cc: ttcoder added

comment:6 by humdinger, 4 years ago

No need to be so surly bout it, waddlesplash.
"Nothing has changed in that area since R1/beta1. Please check on that before advising to re-test next time, cocobean." works just as well and won't make others feel rejected and dumb.

comment:7 by kp3ft, 4 years ago

Same here with hrev-51795, x86-gcc2, Feb. 11, 2018 kernel. VNC and SSHD connections show they are running, but they lose connection at random intervals.

Note: See TracTickets for help on using tickets.