From: Dave Taht <dave.taht@gmail.com>
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 10:38:21 -0700 [thread overview]
Message-ID: <CAA93jw6-89j_xhVYLeA1xNTZFz_sWW_zkobLVhOAqACmwNiCVw@mail.gmail.com> (raw)
In-Reply-To: <DD766994-7C0D-42B3-8DF6-A302322E4546@gmail.com>
BTW: how are you selecting the different gui?
On Mon, Mar 24, 2014 at 9:32 AM, 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
Usually packets, unless you are using the undocumented bfifo qdisc option.
>
> - 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
It's on by default, however, we MUST decide on some 100% robust method
for getting time on boot
before the stable release.
Otherwise boxes that sit for a while before being turned on (consider
boxes shipped on a boat
from china) or those that can't get ntp at all will be locked out.
I am enjoying the flood of ideas on this topic going by on another
thread. (it would be good
to broaden the thread to relevant ntp, dnssec mailing lists)
> - 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.)
Depends on your definition of "spoof".
1) For example a babel node with a real IP inside of a natted network
would still be accepted (and natted) on egress. Can't solve everything...
2) The implementation is capable of filtering out or accepting a large
number of networks, as per bcp38. The default is basically the best
that can be done for a home/natted network.
Given that this is intended to give a cluebat, showing an example for
a provider with a real network would be useful...
>
> 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.
good work!
> Rich
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next prev parent reply other threads:[~2014-03-24 17:38 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 [this message]
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=CAA93jw6-89j_xhVYLeA1xNTZFz_sWW_zkobLVhOAqACmwNiCVw@mail.gmail.com \
--to=dave.taht@gmail.com \
--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