From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ob0-x22a.google.com (mail-ob0-x22a.google.com [IPv6:2607:f8b0:4003:c01::22a]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 1E70E21F26A for ; Tue, 16 Sep 2014 05:19:11 -0700 (PDT) Received: by mail-ob0-f170.google.com with SMTP id uy5so3620815obc.29 for ; Tue, 16 Sep 2014 05:19:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=JAK2qwvBLAufZOMNXDp00kwRoIveBF4/x/lymu5mNFw=; b=TaGhuAQa8LSABpTiMC0C72ZP+EB+ef+orbAKH6gwu2CZ3xdy8fDENYeORbocAttmVl +zMjctwMsis7//nehzHb1OBDgpYav6ic73WYNcnCIP7+6MTYcxBpAeFuSjYzXbtctzKJ PXdg+75wDIQzvTY89tS3iK3zbNyeWl9qLmB4gQhCg2PxQjlRb3R7qoMrsfxdlaW+XrYd MKZN77qisokbh2QSWExHB8qXHRGccBsN9aDIIBet4pfp+zSHaiTbM3BYRuJ5VW7/jbLM ASy24ocohIjlnUBJ8dBVn/qDIXJlGWYeOyrqWIFfD4XIPxMAZIiyaJaIpDXb+0DGRiCU BIng== MIME-Version: 1.0 X-Received: by 10.182.186.73 with SMTP id fi9mr35429010obc.0.1410869950739; Tue, 16 Sep 2014 05:19:10 -0700 (PDT) Received: by 10.202.227.76 with HTTP; Tue, 16 Sep 2014 05:19:10 -0700 (PDT) In-Reply-To: <21789.1389572443@sandelman.ca> References: <21789.1389572443@sandelman.ca> Date: Tue, 16 Sep 2014 15:19:10 +0300 Message-ID: From: Dave Taht To: Michael Richardson Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: cerowrt-devel Subject: Re: [Cerowrt-devel] dropbear stops working X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2014 12:19:40 -0000 It is highly likely you ran out of flash space. As best as I recall, babel then was logging to flash, which we fixed somewhere around feburary. You might be able to get somewhere by deleting that log file. On Mon, Jan 13, 2014 at 2:20 AM, Michael Richardson wrot= e: > > Hi, I was running 3.8 until two weeks ago. I had a problem that had > developed where by dropbear (ssh daemon) simply stopped being willing to > accept logins. I still had access through the web ui, but it's hard to > investigate problems that way... > > I flashed a new 3800 with 3.10 back on Dec. 25th, and all was well. > I could ssh in, no problem. I went to ssh today, and I get the same > problem as before... My experience from before was that a reboot did *not= * > solve the problem. > > ssh -v gives me: > > obiwan-[~/galaxy/orlando/r6743] mcr 10015 %ssh -v root@budmgmt > OpenSSH_6.0p1 Debian-4, OpenSSL 1.0.1e 11 Feb 2013 > debug1: Reading configuration data /home/mcr/.ssh/config > debug1: /home/mcr/.ssh/config line 170: Applying options for * > debug1: Reading configuration data /etc/ssh/ssh_config > debug1: /etc/ssh/ssh_config line 19: Applying options for * > debug1: Connecting to budmgmt [172.30.42.1] port 22. > debug1: Connection established. > debug1: identity file /home/mcr/.ssh/id_rsa type 1 > debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048 > debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048 > debug1: identity file /home/mcr/.ssh/id_rsa-cert type -1 > debug1: identity file /home/mcr/.ssh/id_dsa type 2 > debug1: Checking blacklist file /usr/share/ssh/blacklist.DSA-2048 > debug1: Checking blacklist file /etc/ssh/blacklist.DSA-2048 > debug1: identity file /home/mcr/.ssh/id_dsa-cert type -1 > debug1: identity file /home/mcr/.ssh/id_ecdsa type -1 > debug1: identity file /home/mcr/.ssh/id_ecdsa-cert type -1 > ssh_exchange_identification: Connection closed by remote host > [2] 17811 exit 255 ssh -v root@budmgmt > > I typically operate with about 6 private keys loaded into ssh-agent on my > desktop. On a whim I tried unset SSH_AUTH_SOCK in a fresh shell, but > that didn't change things, nor did combinations after that of things like= : > > %ssh -i ~/.ssh/id_dsa -v root@budmgmt > > on the "budmgmt" IP (the 172.30.42.1 untagged on 3800), I should even be = able > to login with a password, but it never gets to that point. I'm thinking = that > either something has filled up in a way that survives reboots. > > When I had this problem before, I tried starting a new copy of dropbear > From the Network/Fireall/Custom Rules file, since that is a shell > script I can hack: > dropbear -p 2221 & > > but that didn't work (nothing listening on port 2221). > I can see nothing in the logs (which also come via UDP/syslog to my deskt= op). > > I'm looking for any advice on how to: > a) restore my ssh access. > b) get better diagnostics from dropbear. > > Failing this, I'll upgrade the other unit, restore my settings, and test > things daily. > > -- > ] Never tell me the odds! | ipv6 mesh netwo= rks [ > ] Michael Richardson, Sandelman Software Works | network archite= ct [ > ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails= [ > > > > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel > --=20 Dave T=C3=A4ht https://www.bufferbloat.net/projects/make-wifi-fast