Hi!
I am running dropbear 2013.56, connecting to the server with a PC but
not performing a clean close (I pulled my ethernet cable), this caused
dropbear to never drop its connection.
Looking at the utmp entries, I could see that the connection never got dropped,
the utmp entries was kept
Hi,
At the very least if there is traffic on the connection
(which -K will ensure) then TCP should timeout and the
connection should eventually (a minute or so?) close.
Can you get a packet capture with tcpdump?
Cheers,
Matt
On Wed, Mar 27, 2013 at 04:24:27PM +0100, Mattias Walström wrote:
I remember reporting this problem and sending a patch long time ago (for
version 0.52).
The problem with the keep-alive (if I remember correctly) was that every
time dropbear was sending the keep-alive message, it was also resetting the
timeout counter... so dropbear or dbclient never detect the
I thought those were fixed in 0.53 or perhaps 2011.54:
2011.54 - Tuesday 8 November 2011
- Fixed case where -K 1 keepalive for dbclient would cause a SSH_MSG_IGNORE
packet to be sent
0.53 - Thurs 24 February 2011
- Make -K (keepalive) and -I (idle timeout) work together sensibly in the
client.
Yep, you're right Matt... the latest version contains those fixes... (the
truth is that I'm still working with my patched 0.52 that is rock solid for
my usage)...
Regards,
Fabrizio
On Wed, Mar 27, 2013 at 11:47 AM, Matt Johnston m...@ucc.asn.au wrote:
I thought those were fixed in 0.53 or
