Router: Linksys WRT160NL
Firmware: DD-WRT v24-sp2 (05/28/15) std - build 27096
Kernel: Linux 3.5.7.33 #23508 Thu May 28 01:43:57 CEST 2015 mips
Status: Working
Reset: Yes
Errors: No until today
After 2 weeks of running without an issue I noticed this message in dmesg.
ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0
ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
It doesn't seem to do much harm though but i have no clue what this message indicates. The router seems responsive and I have no issue connecting or performance issues.
Just posting my comments as reference.
Router: Linksys WRT160NL
Firmware: DD-WRT v24-sp2 (05/28/15) std - build 27096
Kernel: Linux 3.5.7.33 #23508 Thu May 28 01:43:57 CEST 2015 mips
Status: Working
Reset: Yes
Errors: No until today
After 2 weeks of running without an issue I noticed this message in dmesg.
ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000286c0
ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
It doesn't seem to do much harm though but i have no clue what this message indicates. The router seems responsive and I have no issue connecting or performance issues.
Just posting my comments as reference.
NetGear WNDR4300 - Flashed as update, no reset, and everything I tested so far works well - and I love the new dark theme.
Web interface seems faster as well, but that's subjective.
Haven't seen a TX DMA error...none!
After 4+ days of uptime, I added a port forward to the already existing 15 or so forwards, and the new entry does not forward.
I've rebooted several times, and then run a tcpdump to watch for the incoming packets, which do arrive from the outside world.
However, they are not re-routed inward, nor returned out the WAN.
Tonight I will check the iptables rules as I change the offending new port forward around to see if I can locate the problem, and report back.
I suspect a rogue port range forward, or perhaps a duplicate IP address on the LAN, but there's really no telling until I packet trace internally and on the router at the same time.
I know it'll need to be a 30-30-30 eventually to fix this problem, but one never knows...
Also, I have noticed with all the builds this year that the nat/portforwarding is flaky when you first update and you need to go in to this section and select save and apply as well. Otherwise the port forwarding does not appear to work as expected until you do so. eg. It seems to only effect port 80 from what I can tell though. I have a website on one of my setups and when I update it starts forwarding port 80 to port 81 until I do the save and apply.
BTW, these results are on both my atheros and broadcom buffalo models. 1750 and wzr's gnh2's.
Thanks for this! I have been trying to get EoIP running since build 24345. Save/Apply fixed the problem.
