Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Ranga Krishnan <ranga@eff.org>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Router ssh access unavailable on custom build
Date: Wed, 9 Jul 2014 15:25:29 -0700	[thread overview]
Message-ID: <CAA93jw6O4QA_4UVFee1ip5i_aSP87wR8VLbxvosU0HtrFk0RUg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5_jjEMgEhd2qRj5XKXwNhzwv=PBpajfhCJdSc_E1vfdw@mail.gmail.com>

other fallout of the shifting around of everything pre-barrier-breaker
freeze is my automagic update script (pullhead) wasn't doing updates
of the oldpackages repo.

On Wed, Jul 9, 2014 at 3:14 PM, Dave Taht <dave.taht@gmail.com> wrote:
> 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 <ranga@eff.org> wrote:
>>
>> On Jul 6, 2014, at 11:00 AM, Dave Taht <dave.taht@gmail.com> 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=y
>> # CONFIG_PACKAGE_dropbear is not set
>> CONFIG_PACKAGE_dropbear-xinetd=y
>> # 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
>>
>
>
>
> --
> Dave Täht
>
> NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article



-- 
Dave Täht

NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article

  reply	other threads:[~2014-07-09 22:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-06 17:32 Ranga Krishnan
2014-07-06 18:00 ` Dave Taht
2014-07-07 12:46   ` Ranga Krishnan
2014-07-09 22:14     ` Dave Taht
2014-07-09 22:25       ` Dave Taht [this message]
2014-07-06 21:34 ` Michael Richardson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA93jw6O4QA_4UVFee1ip5i_aSP87wR8VLbxvosU0HtrFk0RUg@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=ranga@eff.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox