Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Fred Stratton <fredstratton@imap.cc>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] cerowrt-3.10.2-1 dev release + owamp
Date: Fri, 26 Jul 2013 07:21:32 +0100	[thread overview]
Message-ID: <3A95A665-3348-44F5-84E8-E59720086E09@imap.cc> (raw)
In-Reply-To: <CAA93jw6jj2TweWXiaG1EnPREacZ2vgufPO=EeNuQJfRa3XWH9w@mail.gmail.com>

I can certainly confirm this, having spent several fruitless hours with the build.

6in4 remains broken for henet.

dnsmasq appears not to recognise additional domain name servers. The ISP I use has a very slow domain name service, to which the system now defaults. The consequence of this is that opkg times out, and no packages can be installed.

It is still not possible to watch a video stream and download files simultaneously on an ADSL line.


On 26 Jul 2013, at 06:20, Dave Taht <dave.taht@gmail.com> wrote:

> sysupgrade -n doesn't work with this release. Stay away. I have a new
> build of 3.10.3-1 and am trying to fix it...
> 
> I did find the problem on the ubnt builds - I'd switched to the new
> babeld from quagga, but failed to install it by default.
> 
> in openwrt trunk, elliptic curve has been enabled in openssl. It's
> long past time we enable https for configuration by default, and might
> as well figure out how to turn perfect forward secrecy on as well in
> the post-snowden era.
> 
> owamp seemingly works well, with a couple glitches here and there. I
> got to where the lab was synced to about 1ms resolution... and 5 more
> gpses arrived today....
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel


  reply	other threads:[~2013-07-26  6:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-23 18:45 Dave Taht
2013-07-26  5:20 ` Dave Taht
2013-07-26  6:21   ` Fred Stratton [this message]
2013-07-26  9:54     ` Sebastian Moeller
2013-07-26 10:51     ` David Personette
2013-07-26 14:31       ` Fred Stratton
2013-07-26 15:51         ` Sebastian Moeller
2013-07-31 19:50           ` Fred Stratton
2013-07-31 20:38             ` Sebastian Moeller
2013-07-31 21:37               ` Fred Stratton
     [not found]                 ` <7AA8F2EC-633F-4DF6-86D1-73B7BAB6DDB7@gmx.de>
2013-07-31 22:35                   ` Fred Stratton
     [not found]                     ` <94CA76B3-44B9-41E8-9893-864BBEEFB70D@gmx.de>
2013-08-03 10:36                       ` Fred Stratton
2013-08-03 18:56                         ` Fred Stratton
     [not found]                         ` <AE353C99-CFF9-49F7-B3CB-912DD2078E2F@gmx.de>
2013-08-03 21:28                           ` Fred Stratton
2013-08-04 13:03                           ` Fred Stratton
2013-08-11 20:25   ` Sebastian Moeller
2013-08-11 21:52     ` Dave Taht
2013-08-12  8:55       ` Sebastian Moeller
     [not found] <46820144-E1DD-4858-A2B6-38F95D2894DB@imap.cc>
2013-08-05 10:47 ` Fred Stratton
2013-08-07 13:38   ` Sebastian Moeller
2013-08-07 23:21     ` Fred Stratton
2013-08-08  9:41       ` Sebastian Moeller
2013-08-08 10:26         ` Fred Stratton

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=3A95A665-3348-44F5-84E8-E59720086E09@imap.cc \
    --to=fredstratton@imap.cc \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /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