From: Fred Stratton <fredstratton@imap.cc>
To: Michael Richardson <mcr@sandelman.ca>,
cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] dropbear stops working
Date: Mon, 13 Jan 2014 00:33:16 +0000 [thread overview]
Message-ID: <52D3344C.9020500@imap.cc> (raw)
In-Reply-To: <22341.1389572600@sandelman.ca>
[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]
Serial header should be in place on the 3800
http://wiki.openwrt.org/toh/netgear/wndr3800
On 13/01/14 00:23, Michael Richardson wrote:
> Michael Richardson <mcr@sandelman.ca> wrote:
> > 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 desktop).
>
> Perhaps I could configure a dropbear to login to a USB stick, and then
> remove the USB stick so that I could see what it's doing.
>
> (I was also thinking about soldering on a serial console )
>
>
>
> --
> ] Never tell me the odds! | ipv6 mesh networks [
> ] Michael Richardson, Sandelman Software Works | network architect [
> ] 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
[-- Attachment #2: Type: text/html, Size: 2282 bytes --]
next prev parent reply other threads:[~2014-01-13 0:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 0:20 Michael Richardson
2014-01-13 0:23 ` Michael Richardson
2014-01-13 0:33 ` Fred Stratton [this message]
2014-09-16 12:15 ` Michael Richardson
2014-09-16 12:20 ` Dave Taht
2014-09-16 12:19 ` Dave Taht
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=52D3344C.9020500@imap.cc \
--to=fredstratton@imap.cc \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=mcr@sandelman.ca \
/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