Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Anders Kaseorg <andersk@mit.edu>
Cc: mosh-devel@mit.edu, dropbear@ucc.asn.au,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [mosh-devel] mosh-server vs dropbear vs openwrt
Date: Mon, 21 Oct 2013 20:06:28 -0700	[thread overview]
Message-ID: <CAA93jw5Ji9s_a-CptSBdcac4sdXF5Fz0bt_VqyFj6kfjBBW+_w@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1310212254440.20647@dr-wily.mit.edu>

OK, well...

On Mon, Oct 21, 2013 at 8:02 PM, Anders Kaseorg <andersk@mit.edu> wrote:
> On Mon, 21 Oct 2013, Dave Taht wrote:
>> Mon Oct 21 21:18:04 2013 authpriv.err dropbear[2995]:
>> ioctl(TIOCSCTTY): Input/output error
>> Mon Oct 21 21:18:04 2013 authpriv.err dropbear[2995]: /dev/pts/1: No
>> such file or directory
>> Mon Oct 21 21:18:04 2013 authpriv.err dropbear[2995]: open /dev/tty
>> failed - could not set controlling tty: No such device or address
>> Mon Oct 21 21:18:05 2013 authpriv.info dropbear[2994]: Exit (root):
>> Disconnect received
>
> Yes, there seems to be a problem with dropbear not liking ‘ssh -n -tt’ (or
> ‘ssh -tt </dev/null’).  This was also reported at
> https://github.com/keithw/mosh/issues/464 .

Not sure if that patch is the right thing, but for sure ssh -n -tt
doesn't work to my dropbear instance.

> Anders



-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

      reply	other threads:[~2013-10-22  3:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-21 21:21 [Cerowrt-devel] " Dave Taht
2013-10-21 21:27 ` [Cerowrt-devel] [mosh-devel] " Alex Chernyakhovsky
2013-10-21 21:30   ` Dave Taht
2013-10-21 21:53     ` Quentin Smith
2013-10-21 22:16       ` Dave Taht
2013-10-21 22:55         ` Outback Dingo
2013-10-21 23:03         ` Quentin Smith
2013-10-22  3:02 ` Anders Kaseorg
2013-10-22  3:06   ` Dave Taht [this message]

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=CAA93jw5Ji9s_a-CptSBdcac4sdXF5Fz0bt_VqyFj6kfjBBW+_w@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=andersk@mit.edu \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dropbear@ucc.asn.au \
    --cc=mosh-devel@mit.edu \
    /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