Closed Juul closed 8 years ago
Wifi seems to be working again though I did nothing to fix it. It looks like the adhoc connection to the nearest node 100.64.24.129 is stable and the internet is flowing through that node.
When connected via ethernet to 100.64.2.1 the internet is stable and the packets flow through 100.64.24.129. When connected to 100.64.2.1 via wifi I am getting frequent and unpredictable outages every few minutes usually lasting less than 2 minutes (often 30-50 seconds). I was also noticing these before the complete wifi failure. I am not getting any more "Failed to stop TX DMA" messages. This may be a different problem entirely. During these outages the client can ping 100.64.2.1 and 100.64.2.1 can ping 8.8.8.8 but the client cannot ping 8.8.8.8. This has been tested with multiple different clients (os x and linux). I verified with traceroute from 100.64.2.1 to 8.8.8.8 that the packets are still going through 100.64.24.129 during the outages.
After a soft reboot of 100.64.2.1 the intermittent connectivity problems started reoccurring. Tried powering off the router for 30 seconds and powering it back on. Will report back.
The hard reboot seems to have fixed the issue.
This is fixed by newest OpenWRT version and we have since upgraded to this version.
The node 100.64.2.1 is no longer allowing clients to associate. SSIDs are broadcast normally but I cannot associate on 2.4 GHz (haven't tried on 5 GHz) and dmesg was full of lines like:
Ethernet connectivity is working correctly and I am in fact online via this node. There is now a bunch of eeprom read failures in the dmesg log but those are an artefact of my debugging attempts.