OK, I built this latest dnsmasq as a test for cerowrt-3.10-50 users:
login to the router
cd /tmp
wget
http://snapon.lab.bufferbloat.net/~cero2/dnsmasq/dnsmasq-full_2.73-3_ar71xx.ipk
opkg install ./dnsmasq-full_2.73-3_ar71xx.ipk
(ignore the warnings about not overwriting several files)
I did a fe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/01/15 17:44, Dave Taht wrote:
> Wow, this thread goes back a ways. Is ds.test-ipv6.com still
> configured wrong, and does it pass now? It passes for me (but I am
> behind a more modern openwrt box right now)
ds.test-ipv6.com is still showi
On Wed, Jan 7, 2015 at 8:12 PM, Aaron Wood wrote:
> So it appears that Marvell pushed a bunch of patches to OpenWRT on
> Christmas, and as a result, trunk OpenWRT (kernel 3.18) can run, and run
> pretty well, on the 1900AC.
>
> https://forum.openwrt.org/viewtopic.php?pid=258634#p258634
The rest o
Wow, this thread goes back a ways. Is ds.test-ipv6.com still
configured wrong, and does it pass now? It passes for me (but I am
behind a more modern openwrt box right now)
Is there another site that demonstrates this problem?
BTW: For a while there (on comcast), in production, I ran with pure
ipv
Do those patches include Broadcom wireless AC support for mainline or
wireless-next or is it still a Wireless free 'open' wireless router?
On Jan 7, 2015 8:13 PM, "Aaron Wood" wrote:
> So it appears that Marvell pushed a bunch of patches to OpenWRT on
> Christmas, and as a result, trunk OpenWRT (
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OK, it's taken some time, but with this insight, I've recoded the
relevant stuff to look for the limits of the signed DNS tree from the
DNS root down. That's clearly the correct way to do it, and should
avoid the original problem here, caused by send
