Hello Matt, On Thu, May 12, 2011 at 5:31 PM, Matt Johnston <[email protected]> wrote: > On Tue, May 10, 2011 at 08:58:33AM -0700, Sam Gandhi wrote: >> I am running dropbear 0.53 on my server, when I connect to this >> machine, when my connection closes, due to inactivity, I see following >> message: >> >> Bad packet length 1128090262. >> Disconnecting: Packet corrupt > > Hi, > > Is the server running with -I for the idle timeout, or is > something else closing the connection? If it's the latter I > wonder if whatever is closing the connection is writing > some message to the socket which isn't valid traffic? It's > also possible there could be bugs in the -I code.
Yes I am running server with -I option. > > What does a tcpdump or wireshark capture look like? After > the first few packets there should be nothing intelligible > in the byte stream (it's all encrypted). > I have attached wireshark capture -- at least -- I cant see anything wrong that dropbear server is doing, I am running ssh (OpenSSH_5.8p1 Debian-1ubuntu3, OpenSSL 0.9.8o 01 Jun 2010 ) client. I am wondering if SO_LINGER option on server is causing this? -Sam
dropbear.pcap
Description: application/cap
