From: Sebastian Moeller <moeller0@gmx.de>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] cerowrt-3.10.32-12 released
Date: Fri, 21 Mar 2014 23:00:00 +0100 [thread overview]
Message-ID: <3F98D180-3AF8-4AFA-80B4-A13E55CAA03A@gmx.de> (raw)
In-Reply-To: <CAA93jw6Y3V29Ynk+2DE+5RrPzSe7X6WeoJK9CcPAHPTRUBsCdQ@mail.gmail.com>
Hi Dave,
wow, after enabling NDP-Proxy 'hybrid mode' (on sw10), for the first time, my macbook got working ipv6 through cerowrt. (My setup is a bit peculiar as the primary router gets a /56 from the ISP but only hands out /64s, don't ask me why). Now I need to understand why this does not work for SW00 or SE00, but these are peanuts now :)
On Mar 21, 2014, at 18:47 , Dave Taht <dave.taht@gmail.com> wrote:
> - 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)
I did not notice this even though my primary router furnishes cerowrt with 192.168.2.104 (but no additional subnets in there), the internet works and I can reach machines in the primary subnet just fine, so nothing to see here ;) Greart work Dave and Toke.
>
> 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.
I seem to recall that there is a page in the openwrt wiki about how to enable that access, which is quite involved (for a layman), so having cerowrt solve this problem in a better fashion would be much appreciated.
>
> 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.
I guess having an easy way to set exceptions is really a good solution.
>
> 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.
Tried it, seems to work.
>
> - 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.
With 3.10.32-9 I could het the usual TX hangs on both radio0 and radio1 by running RRUL against cerowrt (on a wndr3700v2), I did not manage to actually wedge either radio so I had to reboot though.
From (on the 5GHz radio):
bash-3.2$ date ; ./netperf-wrapper --ipv4 -l 300 -H gw.home.lan rrul -p all_scaled --disable-log -t noAQM_noLLA_16M2M_hms-beagle_2_nacktmulle
Fri Mar 21 22:50:17 CET 2014
root@nacktmulle:~#dmesg
[...]
[ 3466.207031] ath: phy1: Failed to stop TX DMA, queues=0x00e!
[ 3485.308593] ath: phy1: Failed to stop TX DMA, queues=0x00e!
[ 3511.449218] ath: phy1: Failed to stop TX DMA, queues=0x00e!
[ 3513.500000] ath: phy1: Failed to stop TX DMA, queues=0x00e!
[ 3545.664062] ath: phy1: Failed to stop TX DMA, queues=0x00e!
[ 3561.769531] ath: phy1: Failed to stop TX DMA, queues=0x00e!
[ 3591.925781] ath: phy1: Failed to stop TX DMA, queues=0x00e!
[ 3615.042968] ath: phy1: Failed to stop TX DMA, queues=0x00a!
[ 3630.140625] ath: phy1: Failed to stop TX DMA, queues=0x00e!
[ 3663.308593] ath: phy1: Failed to stop TX DMA, queues=0x00e!
[ 3666.351562] ath: phy1: Failed to stop TX DMA, queues=0x00e!
[ 3688.468750] ath: phy1: Failed to stop TX DMA, queues=0x00e!
[ 3701.585937] ath: phy1: Failed to stop TX DMA, queues=0x00e!
root@nacktmulle:~# cat /sys/kernel/debug/ieee80211/phy1/ath9k/reset
Baseband Hang: 0
Baseband Watchdog: 0
Fatal HW Error: 0
TX HW error: 0
TX Path Hang: 25
PLL RX Hang: 0
MAC Hang: 0
Stuck Beacon: 0
MCI Reset: 0
But that is not any different from earlier cerowrt versions...
>
> 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…
Ah, okay so now I will switch to the 2,4GHz radio to see whether I can wedge that…
best regards & many thanks
Sebastian
>
> 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
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2014-03-21 22:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 17:47 Dave Taht
2014-03-21 18:51 ` Toke Høiland-Jørgensen
2014-03-21 22:00 ` Sebastian Moeller [this message]
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=3F98D180-3AF8-4AFA-80B4-A13E55CAA03A@gmx.de \
--to=moeller0@gmx.de \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@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