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
Subject: Re: [Cerowrt-devel] Router ssh access unavailable on custom build
Date: Sun, 6 Jul 2014 11:00:24 -0700	[thread overview]
Message-ID: <CAA93jw6g9pg0OVusoPWaS1CQi-5xXSFg0Xk2Q1DJ7ax=4S5n7A@mail.gmail.com> (raw)
In-Reply-To: <A919D7BF-32A2-4712-AE72-1E5EE37ED688@eff.org>

[-- Attachment #1: Type: text/plain, Size: 2332 bytes --]

I would check for the presence of the dropbear-xinetd package and
/etc/xinetd.conf and xinetd.d/ssh

Openwrt uses dropbear (a lightweight ssh clone) directly. Cero uses xinetd
for extra security.

As for your other issues, a 3.3v serial cable is invaluable in
circumstances like this, I typically use a bus pirate to get onto the 4
header pins in the router.

On Jul 6, 2014 10:33 AM, "Ranga Krishnan" <ranga@eff.org> wrote:
>
> Dave,
>
> Appreciate any suggestions debugging the problem below.
>
> I finally flashed a build I made onto the router and it seems to boot
fine and
> is broadcasting the two SSIDs I programed into it but I cant ssh into the
router,
> neither through wireless nor an ethernet cable.
>
> ----------------xxxxxxxxx--------------------
> $:OpenWireless ranga$ ssh root@172.30.42.1
> ssh: connect to host 172.30.42.1 port 22: Connection refused
> ----------------xxxxxxxxxx-------------------
>
> All ports except 53 seem to be blocked. Even the webserver
> we have running on 80/443 is not responding.
>
> -----------------------xxxxxxxxxxxx-----------------------
> $:OpenWireless ranga$ nmap 172.30.42.1
>
> Starting Nmap 6.46 ( http://nmap.org ) at 2014-07-06 07:23 PDT
> Nmap scan report for 172.30.42.1
> Host is up (0.0010s latency).
> Not shown: 999 closed ports
> PORT   STATE SERVICE
> 53/tcp open  domain
>
> Nmap done: 1 IP address (1 host up) scanned in 2.59 seconds
> ----------------------xxxxxxxxxxxxx-----------------------
>
> I started with the etc directory in 3.10.40-6 and removed a few things
> and made some changes in /etc/config. I kept the /etc/config/firewall
> file unchanged. So I am not sure if it is the firewall blocking the ports.
> Here is a link to the /etc I placed in cerowrt/files directory to have it
> compiled into the build.
>
> https://github.com/TWEFF/OpenWireless/tree/master/etc
>
> Could it be that when building, the permissions with which
> the files are being created in the firmware image are not what
> they need to be, and this is causing the problems I am seeing ?
> Is there any way to analyze the firmware image without flashing
> it onto a router ?
>
> Thanks,
> Ranga
>
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>

[-- Attachment #2: Type: text/html, Size: 3176 bytes --]

  reply	other threads:[~2014-07-06 18:00 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 [this message]
2014-07-07 12:46   ` Ranga Krishnan
2014-07-09 22:14     ` Dave Taht
2014-07-09 22:25       ` Dave Taht
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='CAA93jw6g9pg0OVusoPWaS1CQi-5xXSFg0Xk2Q1DJ7ax=4S5n7A@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