From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oa0-x235.google.com (mail-oa0-x235.google.com [IPv6:2607:f8b0:4003:c02::235]) (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 92A5821F390 for ; Wed, 9 Jul 2014 15:14:29 -0700 (PDT) Received: by mail-oa0-f53.google.com with SMTP id l6so8638011oag.26 for ; Wed, 09 Jul 2014 15:14:28 -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=CtPpb5w4oAOXs58zFWe8wJRmIl51G8kEptr0LWQ1G2E=; b=dN/bm309fWl8i5d/U1tx9n5Jz9FLH6kU51er1Jn5sPFOI3kadRC6OtnG9bGo65JRD3 9YJbcSPS1taid52Yi4+7govZJqpvwQI8P/I5i84mYyrjaJHbSAX8cfKeW4LyWpVLq3qA wTokmGz1snEmuQ4VCgHaGtEdroUPkc/2lE6zeNFnfKZAl586bCk0fIn+bm2w8VmURFiS 5Jc7atqQn56ZZJ8E3DAqlNze6Prh9s3Z3r+7B3ZOGubVeLFPpHr+PH1AX+q8bu5SdgQQ ClidAVtso1/CGuOEXn2cnBnJbEqFA7yhJIrOjcBo3ziCmLSOzfupsf5MlrLEKlQk5EYn 2UHw== MIME-Version: 1.0 X-Received: by 10.182.65.167 with SMTP id y7mr50698481obs.29.1404944068809; Wed, 09 Jul 2014 15:14:28 -0700 (PDT) Received: by 10.202.93.195 with HTTP; Wed, 9 Jul 2014 15:14:28 -0700 (PDT) In-Reply-To: References: Date: Wed, 9 Jul 2014 15:14:28 -0700 Message-ID: From: Dave Taht To: Ranga Krishnan Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "cerowrt-devel@lists.bufferbloat.net" Subject: Re: [Cerowrt-devel] Router ssh access unavailable on custom build 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: Wed, 09 Jul 2014 22:14:29 -0000 it appears the xinetd package was mucked with around may 15th, and perhaps that has some influence on your problem. On Mon, Jul 7, 2014 at 5:46 AM, Ranga Krishnan wrote: > > On Jul 6, 2014, at 11:00 AM, Dave Taht wrote: > > I would check for the presence of the dropbear-xinetd package and > /etc/xinetd.conf and xinetd.d/ssh > > > > The dropbear-xinetd package was absent while the other items > above were present. I created a new build with dropbear-xinetd but > the behavior is the same. is the xinetd binary present? > I used the failsafe mechanism to get telnet access into the boxes and > tried to pull in a good firmware image into /tmp as described here: > > https://archive.org/details/EnterOpenwrtFailsafeModeAndReflashAFirmware > > However when dropbear refused to start even manually I discovered > there is no dropbear executable on the router. > > I compiled this build with : > > CONFIG_DEFAULT_dropbear=3Dy > # CONFIG_PACKAGE_dropbear is not set > CONFIG_PACKAGE_dropbear-xinetd=3Dy > # CONFIG_PACKAGE_dropbearconvert is not set > # CONFIG_PACKAGE_dropbearconvert-xinetd is not set > > which was the config for 3.10.44-6 release, as described in > cerofiles-3.10 github repo, and which has a working ssh. > > Do I need CONFIG_PACKAGE_dropbear even though 3.10.44-6 > seems to get dropbear without including this config ? No, if you do that, you get dropbear starting at boot without xinetd. You CAN try it, but then you have to do some firewalling. > > In the absence of dropbear is there a good way to transfer files. > I couldn't find any file transfer options available in failsafe mode > other than a wget built into busybox. To use this I would > have to setup my mac as a webserver. I maintain a local fileserver, always, anyway, so it's a good idea. > > Ranga > --=20 Dave T=C3=A4ht NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_= indecent.article