Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
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 17:55:21 +0100	[thread overview]
Message-ID: <DEE8CB88-535B-46D9-8EB9-5EA355A62266@gmx.de> (raw)
In-Reply-To: <DD766994-7C0D-42B3-8DF6-A302322E4546@gmail.com>

Hi Rich,


On Mar 24, 2014, at 17:32 , 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? 

	In most cases its packets, but with bfifo (which currently can not be selected? its bytes (the b in bfifo stands for bytes, if no value given this defaults to txquelength * MTU). I think it should be okay to ignore bfifo for now and just explain this as packets. If we expose bfifo as a selection we can always revisit that…

Best Regards
	Sebastian

> 
> 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
> 
> - I have added a BCP38 page to give an overview of that page. A question that I haven't seen addressed in the commentary on the list: Does this BCP38 implement also filter out spoofed source addresses? (I imagine it would, but the pages don't specifically say so.)
> 
> http://www.bufferbloat.net/projects/cerowrt/wiki/CeroWrt_and_BCP38
> 
> Although I try to write carefully, sometimes I'm just makin' stuff up. Comments requested. Thanks.
> 
> Rich
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel


  reply	other threads:[~2014-03-24 16:55 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 [this message]
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

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=DEE8CB88-535B-46D9-8EB9-5EA355A62266@gmx.de \
    --to=moeller0@gmx.de \
    --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