I had complete failure to respond on 3.10.32-10 and -11 after less than a hour of uptime. I was assuming that it was due to my keeping the configuration files, and that something had changed in OpenWRT head and/or dnsmasq. I didn't have time to do another merge at the time, and had just flashed back to 3.10.32-9. When 3.10.32-12 came out I checked the files, and didn't find any issues with the configuration files. I also haven't had any more hangs. I have ipv6 through he, and syn flood protection turned on. No issues to date with -12. -- David P. On Fri, Mar 28, 2014 at 12:51 PM, Aaron Wood wrote: > As a contra-datapoint: > > 4d uptime here, but without any ipv6. A couple GB of data, both > WAN<->internal, and between 5GHz devices (pushing to an AppleTV). No real > traffic between 2.4 and 5GHz, though. > > WPA2 on all interfaces (babel and guest interfaces are disabled). > > -Aaron > > On Fri, Mar 28, 2014 at 5:39 PM, Dave Taht wrote: > >> This sounds like the problem jim gettys is having on 2.4ghz. It takes >> 1+ days to happen. We've ruled out ipv6 tunneling and syns as the >> cause... he is presently running without syn flood, ipv6, and now WPA >> support in the hope that that's a cause (there is a fix for WPA stuff >> in 3.10.34 pending) >> >> are you using WPA? >> >> taking a long term packet capture seems worthwhile. >> >> >> On Fri, Mar 28, 2014 at 1:04 AM, Toke Høiland-Jørgensen >> wrote: >> > So I've had a strange issue with the 5ghz network on my wndr after a few >> > days' uptime: Packets stopped getting through on the 5ghz network. I.e. >> > clients already connected could no longer connect to anything, and >> > trying to connect a new client resulted in the wlan association >> > succeeding, but the clients failing to get a DHCP lease. >> > >> > There's nothing in the logs to indicate what might be wrong (no DMA >> > errors or anything like that). 'logread' shows dnsmasq receiving and >> > replying to DHCP requests, but the answers never reach the clients. >> > >> > Restarting the wireless (i.e. running 'wifi') fixed it. >> > >> > Any ideas? I'm on 3.10.32-12(ish). Built from git commit >> > 9bbc728cb7508dce24c480ac63d6e4f63d5c02f5 from the cerowrt-3.10 repo. :) >> > >> > -Toke >> > >> > _______________________________________________ >> > Cerowrt-devel mailing list >> > Cerowrt-devel@lists.bufferbloat.net >> > https://lists.bufferbloat.net/listinfo/cerowrt-devel >> > >> >> >> >> -- >> 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 >> > > > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel > >