From: Dave Taht <dave.taht@gmail.com>
To: David Personette <dperson@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] dnssec by default and other stories from the bleeding edge
Date: Wed, 19 Feb 2014 11:43:48 -0500 [thread overview]
Message-ID: <CAA93jw4_5CfmZbUK0C5TSgyLzvZhqQLzaCGPGT_4ZUxZMmFqWA@mail.gmail.com> (raw)
-1) The package repos have all moved on github... This will break everybody
building cerowrt themselves and get them to pay attention.
0) I'm having some trouble with default routes
1) The 3.10.28-12 non-release ahas dnssec enabled by default. (I think -
see /etc/dnsmasq.conf)
A concern of mine has long been that this is going to break in some scenarios,
notably with broken forwarders.
From my perspective, having it on by default ensures it gets tested. IF you have
dns issues (notably with getting time or other queries), you can turn it off
by commenting it out in that file.
I also kind of expect bug #113 to recur... a hook to turn off dnssec at boot,
and turn it on after time is obtained might be useful. (openwrt ntp
supports a script to run after it starts, I think)
Otherwise, leave it on and enjoy the glory of ad-free NXDOMAIN results.
There is still no NSEC3 support, I am not sure how much that matters.
2) There are some other fixes pending to deal with source specific routing,
multiple providers, and multiple dns upstreams, which require tight
dnsmasq and netifd integration and the retirement of resolve.conf.auto.
3) the bcp38 code does not look like I'll get a chance to finish it
any time soon.
I have a proof of concept in github, and a start at a script in
ceropackages. Needed
is a hook to insert/delete firewall rules at the right time and sense
if the external
interface is double natted. (help wanted)
4) next up is to get a reproducable build, and fix package signing.
5) There are still a few instruction traps in 3.10.28-12 in odhcpd,
those were fixed
last night but haven't made it to openwrt yet.
6) I think wifi can be tuned up a bit to behave better under rrul.
Anything else I should care about?
progress!
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
reply other threads:[~2014-02-19 16:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAA93jw4_5CfmZbUK0C5TSgyLzvZhqQLzaCGPGT_4ZUxZMmFqWA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dperson@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