Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Jim Gettys <jg@freedesktop.org>
To: Rich Brown <richb.hanover@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Updates to the wiki for 3.10.32-12
Date: Mon, 24 Mar 2014 14:23:15 -0400	[thread overview]
Message-ID: <CAGhGL2Df6_Ev478Lu0bqQ+xwS-T2asDr8H6QBRGbjZMATykeGQ@mail.gmail.com> (raw)
In-Reply-To: <DD766994-7C0D-42B3-8DF6-A302322E4546@gmail.com>

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

On Mon, Mar 24, 2014 at 12:32 PM, Rich Brown <richb.hanover@gmail.com>wrote:

> Folks,
>
> I updated the wiki to incorporate features of 3.10.32-12.
>
> - The SQM page has been updated to include current screen shots and
> describe the options. A question: what are the units for the Hard Limit on
> ingress/egress?
>
>
> http://www.bufferbloat.net/projects/cerowrt/wiki/Setting_up_SQM_for_CeroWrt_310
>
> - The Release Notes page has been updated to mention DNSSEC and BCP38. I'm
> still not clear whether DNSSEC is turned on/operational by default. What
> should that page say?
>
> http://www.bufferbloat.net/projects/cerowrt/wiki/CeroWrt_310_Release_Notes
>
>
DNSSEC works for me...

There are plug-ins for both firefox and chrome for dnssec, so it's easy to
know if it is working.  www.bufferbloat.net is signed (even for IPv6) so
it's easy to check (cheery green key in the URL bar on my chrome).
                                 - Jim

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

      parent reply	other threads:[~2014-03-24 18:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-24 16:32 Rich Brown
2014-03-24 16:55 ` Sebastian Moeller
2014-03-24 16:55 ` Toke Høiland-Jørgensen
2014-03-24 17:38 ` Dave Taht
2014-03-25 11:41   ` Rich Brown
2014-03-25 13:15     ` David Personette
2014-03-24 18:23 ` Jim Gettys [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=CAGhGL2Df6_Ev478Lu0bqQ+xwS-T2asDr8H6QBRGbjZMATykeGQ@mail.gmail.com \
    --to=jg@freedesktop.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=richb.hanover@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