From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] cerowrt-3.10.32-12 released
Date: Fri, 21 Mar 2014 17:47:42 +0000 [thread overview]
Message-ID: <CAA93jw6Y3V29Ynk+2DE+5RrPzSe7X6WeoJK9CcPAHPTRUBsCdQ@mail.gmail.com> (raw)
- currently untested (but a really small delta from -10 and -11)
+ Resync with openwrt head
+ dnsmasq 2.69rc1 (close approximation thereof)
+ This is the first release with toke's bcp38 code installed (and
enabled by default). I am hoping people simply don't even notice it's
there... (it's off the firewall web page)
The only problems I foresee happening are
1) some devices are dependent on double-nat to be configurable -
notably most cable modems depend on 192.168.100.1 to get configured
the first time. I thought about adding that in as a default exception,
and still may.
2) People using this on an interior gateway on a complex network will
need to either disable bcp38 or (preferably) add their rfc1918
network(s) to the exception list on the interior gateway (not on the
external gateway). For example, the yurtlab lives on subnets
172.21.0.0/20.
3) I am not prescient, however, and the only way to find out what
problems will be created is to inflict it on^H^H^H^H^H^H^H kindly ask
the cerowrt userbase to try it.
- Jim Gettys tells me that after a day or so of heavy use of
3.10.32-9, the 2.4ghz radio gets thoroughly wedged after a succession
of DMA tx errors and only a reboot can clear it.
I am in the process of rebuilding the yurtlab and can get back into
heavy wifi testing over the next week or so. In the interim,
please beat up wifi any way you can...
I would really like to get to a stable beta release by the end of the month.
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next reply other threads:[~2014-03-21 17:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 17:47 Dave Taht [this message]
2014-03-21 18:51 ` Toke Høiland-Jørgensen
2014-03-21 22:00 ` Sebastian Moeller
2014-03-21 22:53 ` Toke Høiland-Jørgensen
2014-03-21 23:04 ` Sebastian Moeller
2014-03-21 23:26 ` Toke Høiland-Jørgensen
[not found] ` <608F3E46-3D81-48A3-B60C-E90661DD3AB2@gmx.de>
2014-03-22 11:08 ` Toke Høiland-Jørgensen
2014-03-22 17:09 ` Dave Taht
2014-03-22 18:18 ` Toke Høiland-Jørgensen
2014-03-22 20:20 ` Sebastian Moeller
2014-03-22 19:23 ` Sebastian Moeller
2014-03-22 19:36 ` Toke Høiland-Jørgensen
2014-03-22 20:24 ` Sebastian Moeller
2014-03-24 0:56 ` Valdis.Kletnieks
2014-03-24 14:35 ` Jim Reisert AD1C
2014-03-26 4:37 ` Kai Yang
2014-03-24 16:32 ` [Cerowrt-devel] upnp oddness (was " Valdis.Kletnieks
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=CAA93jw6Y3V29Ynk+2DE+5RrPzSe7X6WeoJK9CcPAHPTRUBsCdQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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