From: Robert Bradley <robert.bradley1@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] cerowrt-3.10.36-4 released
Date: Thu, 10 Apr 2014 15:06:25 +0100 [thread overview]
Message-ID: <5346A561.30901@gmail.com> (raw)
In-Reply-To: <85984.1397137700@turing-police.cc.vt.edu>
[-- Attachment #1: Type: text/plain, Size: 1693 bytes --]
On 10/04/2014 14:48, Valdis.Kletnieks@vt.edu wrote:
> On Wed, 09 Apr 2014 23:45:23 -0700, Dave Taht said:
>> + dnsmasq 2.69 with dnssec enabled by default
>> + possible workaround for wifi bug #442 in increased qlen_*
>> + fix for ipv6 access to https://gw.home.lan:81
>> + fresh merge with opewrt
>> + update to 2048 bit cert generation
>> + fix for openssl heartbleed (fix also in -3) bug
>> + tested for an hour
>> + change to sqm to basically always use "simplest.qos" on inbound
>>
>> - I'm very, very, very, very, very, very, very, very, very tired.
>>
>> I really hope this results in a stable cerowrt. Please beat the hell out of it.
> Trying to flash openwrt-ar71xx-generic-wndr3800-squashfs-sysupgrade.bin
> gets me this message at the bottom of the screen:
>
> The uploaded image file does not contain a supported format. Make sure that you choose the generic image format for your platform.
>
>
Try using TFTP with the *factory.img file instead, since that worked for me.
On a separate note, this new release seems to work fine, unlike my
attempts to automate configuration changes! The only two issues I had were:
- I had to add my cable modem configuration address to the BCP38
exception list (192.168.100.1). This gets used for nothing except
configuration and checking the modem logs so this is understandable. I
also end up adding a static route anyway since if Internet breaks, I
need a route to the modem...
- dnsmasq's default of dnssec-check-unsigned broke my DNS, since my ISP
servers do not support DNSSEC. In that case, everything winds up as
failing.
Other than that it seems fine for the moment.
--
Robert Bradley
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]
next prev parent reply other threads:[~2014-04-10 14:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 6:45 Dave Taht
2014-04-10 6:46 ` Dave Taht
2014-04-10 17:33 ` Dave Taht
2014-04-11 18:25 ` Jim Gettys
2014-04-10 13:48 ` Valdis.Kletnieks
2014-04-10 14:06 ` Robert Bradley [this message]
2014-04-10 14:32 ` Toke Høiland-Jørgensen
2014-04-10 15:18 ` Robert Bradley
2014-04-10 15:21 ` Toke Høiland-Jørgensen
2014-04-10 17:29 ` Dave Taht
2014-04-10 17:57 ` Toke Høiland-Jørgensen
2014-04-10 19:06 ` Sebastian Moeller
2014-04-11 12:34 ` Robert Bradley
2014-04-10 16:40 ` Valdis.Kletnieks
2014-04-10 16:48 ` Toke Høiland-Jørgensen
2014-04-10 16:51 ` Valdis.Kletnieks
2014-04-10 16:54 ` Toke Høiland-Jørgensen
2014-04-10 18:02 ` Sebastian Moeller
2014-04-13 0:22 ` Jim Reisert AD1C
2014-04-13 0:30 ` Sebastian Moeller
2014-04-13 0:44 ` Jim Reisert AD1C
2014-04-10 16:46 ` Jim Gettys
2014-04-10 17:31 ` Dave Taht
2014-04-10 17:35 ` Jim Gettys
2014-04-11 9:50 ` David Personette
2014-04-11 10:43 ` Aaron Wood
2014-04-12 11:45 ` Neil Shepperd
2014-04-12 19:04 ` Dave Taht
[not found] ` <CANp2as81TR_kCR8a_sZs045tXFGADL1W4CFtNEJiJrjutmL7cg@mail.gmail.com>
2014-04-11 16:31 ` Dave Taht
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=5346A561.30901@gmail.com \
--to=robert.bradley1@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