Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Fred Stratton <fredstratton@imap.cc>
To: Dave Taht <dave.taht@gmail.com>, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] going down the todo list
Date: Sun, 19 Jan 2014 16:11:56 +0000	[thread overview]
Message-ID: <52DBF94C.1000703@imap.cc> (raw)
In-Reply-To: <CAA93jw41axmmA=w2LNOwVSRGRQaBhfwo47HHvHZgS+spNuxdPQ@mail.gmail.com>

0) Themes

I would point out that changing theme is likely to give Rich Brown great 
difficulty, as it renders his wiki page obsolete.

I have installed the openwrt.org theme from 3.10.26-1 in 3.10.26-2. The 
bootstrap theme and openwrt theme can co-exist, and there is a menu to 
choose between them installed by default.

Installing both themes in each build solves the problem.

On 19/01/14 12:51, Dave Taht wrote:
> I am going to try to knock out a new release by tomorrow...
>
> -1) has minidnssd and upnp been working for others correctly?
>
> 0) Presently fooling with a new skin with the gui (it's in 3.10.26-2 -
> don't! install that unless you merely want to look at the gui). I have
> no opinion on graphical matters, yours solicited.
>
> 1) I have found that sqm does not always start correctly on boot. There is some
> dependency on something firing to get it to start.
>
> 2) dnsmasq's dnssec support isn't quite baked enough to think about
> putting into a "stabler" release.
>
> 3) I updated most of the onboard doc, still have to finish the credits file
>
> 4) bcp38 turns out to be hard to do correctly in our commonly
> double-natted universe. I think I will try to make the facility
> available but only enable it partially by default.
>
> 5) David personette fixed https support for the gui so we will switch
> to https for the next round
>
> 6) squash incoming diffserv bits. I think perhaps wireshark is
> grabbing the packets before iptables thus I don't see them squashed
>
> 7) native ipv6 and dhcpv6-pd support - as discussed on the list, a
> full solution is gated on steven barth. The massive rework of the
> routing infrastructure he put in friday needs to be tested too,
> though.
>
> I am hopefully gaining ipv6 from comcast today to see stuff for myself.
>
> 8) src/dst routing test of babels - needs work
>
> 9) updated shaperprobe, uftp4, and ditg - no progress
>
> 10) iwl related crash and unaligned instructions - I have some data on
> when and how much they happen now, still no insight as to why
>


  parent reply	other threads:[~2014-01-19 16:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-19 12:51 Dave Taht
2014-01-19 13:03 ` Maciej Soltysiak
2014-01-19 13:33 ` Richard O
2014-01-19 14:13 ` Sebastian Moeller
2014-01-19 16:11 ` Fred Stratton [this message]
2014-01-22  2:07   ` [Cerowrt-devel] going down the todo list/New GUI Rich Brown
2014-01-19 19:56 ` [Cerowrt-devel] going down the todo list Alijah Ballard
2014-01-19 20:26   ` Dave Taht
2014-01-19 22:19     ` Alijah Ballard
2014-01-19 22:25       ` 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=52DBF94C.1000703@imap.cc \
    --to=fredstratton@imap.cc \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /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