I have experience with the v2 (old build) & v4 (latest build) variants of this router.
With the v2 I too experienced a complete loss of connectivity on 2.4 GHz after a couple of days uptime and never did get to the bottom of it.
With the v4 I have experienced unstable connectivity on 2.4 GHz out of the box. Clients will reconnect when there is heavy traffic (download tests for example) and there would be a high number of errors recorded when reading the debug diagnostics for the driver.
If you monitor the events being raised you can see stations being deleted and added in very quick succession. I couldn't get any debug output from hostapd though so it's a bit like working blind.
I did change 'disassoc_low_ack' to '0' in the hostap .config and clients did seem to remain connected for much longer even during heavy traffic.
I also subsequently later on changed the ACK timing to '0' from '2000' (disables it I believe, shows N/A in status) which has resolved some of the errors I mentioned above.
I'm really just changing things and gauging the results to try and get a stable wireless connection - trial and error. I've also scheduled the router to reboot every day to try and mitigate against the complete loss of connectivity I saw on v2.
Don't get me wrong I've had great results speed wise but it's all for nothing if a client can't stay connected for any length of time reliably.
I could also just be in a very noisy environment but I have my doubts.
Also httpd with HTTPS enabled is quite unreliable, it keeps dropping connections randomly leading to the pages being rendered incorrectly with missing elements.
I'm wondering...what channel width were you using on the 2.4Ghz radio? Was it the v2 or v4 that was dying?
v2 2.4 GHz radio died after a few days uptime
v4 2.4 GHz radio was unstable every day with many disconnections
I didn't test 5 GHz much as I was too busy trying to get a stable 2.4 GHz connection.
I had mine at 40. I changed it to 20. I've been up now for over 24Hrs. I was having trouble with even a full day before the change. I'll see how the weekend goes.
This change seems to have solved my problem. I've been up now for several days without a loss of wifi on the 2.4Ghz band.
Posted: Thu Feb 22, 2018 6:31 Post subject: a few stupid questions
I have a v2 and I'm on build 30082. Lately I havent been able to stream some fairly low bitrate kids shows to a fire tv running kodi in the same room as the router and server both connected via ethernet. Constant buffering. I dont know where to start so I figured I'd start here and see if there's a good reason to upgrade to a newer DD-WRT build. I tried rebooting both router and fire tv with no change. Do I use the -IL, -US, or the file with neither suffix?
LEDE has been rock solid for me so far on my v4 with clients connected for hours on end without any problems.
I'll update in a week or so as the dreaded v2 bug only kicked off after a couple days and it could still be lurking.
One week later no problems to report, the wireless issues therefore must be specific to dd-wrt and / or the drivers in use.
I've started to experience issues with ath0. About every couple of days I'll loose that radio. Ath1 stays up but for some reason the 2.4Ghz radio will just dies. Making a change to the config, which drops the interface and brings it back up will fix the issue. I don't even have to reboot the box, so I'm starting to wonder if it's not DD-WRT as well. I'm running 31899 but I've tried newer and older builds and I'm running into the same issue. I know these boxes are now consumable goods and don't last for ever, but it's only been in service about 18 months. I'm considering doing the same thing. Did you use a howto to transition to OpenWRT from DD-WRT or was it as easy as loading the appropriate firmware?
I've pointed out before, that I've noticed that the radio drops after about 70ish days consistently on 30082... by drop i mean I can see the clients connected on the staus page but DD refuses to give them an IP.
I think there's many bugs lurking that's never been addressed, and the severity depends on build and environment. You just gotta find a build that works and stick with it sadly.
You could always go back to stock to test... personally never got any drops with stock.