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 <[email protected]> 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 > [email protected] > https://lists.bufferbloat.net/listinfo/cerowrt-devel _______________________________________________ Cerowrt-devel mailing list [email protected] https://lists.bufferbloat.net/listinfo/cerowrt-devel
