Posted: Mon Mar 24, 2025 17:10 Post subject: Linksys MX5500 (Atlas 6 Pro) issues on latest beta.
Hello,
My router is having serious issues with DD-WRT on the beta versions from 3-13 and 3-18 (I started using DD-WRT on it since the beta version before 3-13 and had a different problem than now, back then the 2.4ghz was not working and couldn't connect to it, now the 2.4ghz frequency works fine for a bit then dies overtime and need a full reset to get it back up)
Right now, it behaves like this:
On router startup, clients connect and everything works fine for around 1-2 hours then the 2.4ghz (wlan0) completely becomes unreachable.
If I use youtube, for example, the process is sped up and dies within 25 minutes. Managed to finally get some worthwhile logs.
I'm using my router in my home network, connecting smart devices like Wiz lights, Xiaomi appliances, a coffee machine, and my smartphones/computers.
By the way, if anyone reading this may know why I'm having difficulties connecting a Philips/L'or wireless coffee machine to my router after installing DD-WRT then that may be useful.
Edit: Seems like the code dump was too long. Attaching as .txt
If you need anything else like my settings, I would oblige, but they are mostly defaults. I did assign my 2.4ghz to the proper channel (6 + 10 at 40mhz) and the 5.0 ghz (44 at 80 mhz). I do know I have/need help with some other stuff but this problem has been an headache to keep tinkering around.
MX5500 Logs.txt
Description:
MX5500 Logs using Firmware DD-WRT v3.0-r60467 std (03/24/25)
Have you configured the wireless settings using the recomended settings here:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324014 _________________ Main Router: Dynalink WRX36, PPPoE, Gateway Mode, Network IPV4 - Isolated Vlan's. Unifi AC-Pro x 3 AP's, Router Wi-Fi Disabled. Paid Commercial Wireguard Client's & WG server, DNSMasq, Static Leases with Cloudflare SmartDNS, DNSMasq Adblocking via egc script.
No one can build you the bridge on which you, and only you, must cross the river of life!
Looks like you're using SFE. Maybe try either turning it off or change it to use NSS-ECM instead. I do see this in the log, which may or may not be of concern as these are merely warnings, with one exception which happens several times below this:
Code:
kern.warn kernel: [ 319.139682] ath11k c000000.wifi: failed to update rx tid queue, tid 0 (-105)
kern.warn kernel: [ 319.139744] ath11k c000000.wifi: failed to update reo for rx tid 0: -105
kern.info kernel: [ 319.145884] wlan0: HW problem - can not stop rx aggregation for 4c:c6:4c:14:dc:14 tid 0
kern.warn kernel: [ 334.554280] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 3224
kern.warn kernel: [ 334.554770] ath11k c000000.wifi: failed to configure rx tid 0 queue for pn replay detection -105
kern.warn kernel: [ 334.561232] ath11k c000000.wifi: failed to offload PN replay detection -105
kern.err kernel: [ 334.570338] wlan0: failed to remove key (0, 4c:c6:4c:14:dc:14) from hardware (-105)
Also, your router has a oops partition in place to capture kernel opps dumps. You can find it by doing a #cat /proc/mtd. Look for "oops" in the list and find its associated mtdN, then you can read this partition to see if the kernel has crashed at all.
Code:
strings /dev/mtdN
_________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: VLANs, Samba, WG, Entware - r60xxx
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r60xxx
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r60xxx
- Linksys MX4300: (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r60xxx
- Linksys MR7350: WDS Station for extended Ethernet r60xxx
- Linksys MR7500, MX8500: None in production. Just testing. r60xxx
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
- Forum member #248
I had seen that thread before, I had followed the guides on WRT before but I have reset to factory so maybe some things were off. I double checked just now, and made some changes according to the images so I will tell you now what I just changed and what remains different from that guide:
- Network mode is set to mixed on both of my wlans (I want to test NG mixed and so on, but since it is unstable I can't attest if it benefits me or not right now).
- I have more settings than the picture that were left as default like Allow Channel Overlapping, BSS Color, Legacy Rates, Cell Density, Diassoc Low ACK and so on that are left as default.
- Protection mode was set to none on my router, is now set to RTS/CTS at 784 threshold for both Wlans
- Disabled Multi User Beamforming on both Wlans (which is different than the WRT wiki article said, but followed image to test).
- Changed beacon intervals and DTIM interval.
- Changed ACK timing to 0 (it was previously set to 500), my appartment is really small (25 square meters) so I didn't want to set it to 3150 like the image.
Just rebooted the router to test, but you think those settings in question are the problem?
Looks like you're using SFE. Maybe try either turning it off or change it to use NSS-ECM instead. I do see this in the log, which may or may not be of concern as these are merely warnings, with one exception which happens several times below this:
Code:
kern.warn kernel: [ 319.139682] ath11k c000000.wifi: failed to update rx tid queue, tid 0 (-105)
kern.warn kernel: [ 319.139744] ath11k c000000.wifi: failed to update reo for rx tid 0: -105
kern.info kernel: [ 319.145884] wlan0: HW problem - can not stop rx aggregation for 4c:c6:4c:14:dc:14 tid 0
kern.warn kernel: [ 334.554280] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 3224
kern.warn kernel: [ 334.554770] ath11k c000000.wifi: failed to configure rx tid 0 queue for pn replay detection -105
kern.warn kernel: [ 334.561232] ath11k c000000.wifi: failed to offload PN replay detection -105
kern.err kernel: [ 334.570338] wlan0: failed to remove key (0, 4c:c6:4c:14:dc:14) from hardware (-105)
Also, your router has a oops partition in place to capture kernel opps dumps. You can find it by doing a #cat /proc/mtd. Look for "oops" in the list and find its associated mtdN, then you can read this partition to see if the kernel has crashed at all.
Code:
strings /dev/mtdN
Changed it to NSS-ECM and testing now.
I also did the other thing that you asked, and it is a long output... Attached as .txt
Edit: Note that the output of oops was taken after a reboot as I changed the settings as I mentioned early - in case that matters at all.
I also did the other thing that you asked, and it is a long output... Attached as .txt
That is a record of dozens of kernel crashes. Looks like they could be related the the ath11k driver. On well functioning routers, the oops partition should be empty. This is most certainly your problem...or at least a big part of it. _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: VLANs, Samba, WG, Entware - r60xxx
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r60xxx
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r60xxx
- Linksys MX4300: (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r60xxx
- Linksys MR7350: WDS Station for extended Ethernet r60xxx
- Linksys MR7500, MX8500: None in production. Just testing. r60xxx
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
- Forum member #248
I also did the other thing that you asked, and it is a long output... Attached as .txt
That is a record of dozens of kernel crashes. Looks like they could be related the the ath11k driver. On well functioning routers, the oops partition should be empty. This is most certainly your problem...or at least a big part of it.
How should I proceed? The router was working incredible well with all my devices before flashing DD-WRT (not complaining), I decided to flash because the web UI from linksys was shameful and I was unhappy with it... Saying all this because I'm uncertain if by your answer you are telling me that I'm screw, or that my hardware is bad (router is new, bought from a retail shop in december), or that there are settings to tweak.
One thing is for sure though, although I had one reset within 30-45 minutes, at least the clients stayed connected on reboot (wiz lights), the coffee machine did connect to the AP, and youtube is no longer forcing the crash within 25 minutes so there is some improvement going on so far.
EDIT:
It seems that reboots are still there, it gets quickened by having all my devices on but really by putting a 4k stream from youtube and another one in my pc at 1080. Not sure, will keep looking.
I am seeing a very similar issue too with my MR7350. I have edited and sent both yours and my oops dumps to the developer. Hopefully he can sort this out fairly quickly. All we can do now is wait. _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: VLANs, Samba, WG, Entware - r60xxx
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r60xxx
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r60xxx
- Linksys MX4300: (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r60xxx
- Linksys MR7350: WDS Station for extended Ethernet r60xxx
- Linksys MR7500, MX8500: None in production. Just testing. r60xxx
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
- Forum member #248
I am seeing a very similar issue too with my MR7350. I have edited and sent both yours and my oops dumps to the developer. Hopefully he can sort this out fairly quickly. All we can do now is wait.
Thank you, I will keep hanging around then. By the way, after the wlan0 (2.4ghz) eventually on the automatic reboots (or over some hours) gets basically disabled with messages of "auth/deauth" the wlan1 (5ghz) just works perfectly from there on out - was it not for smart home devices, then the router "just works" for PCs/phones.
kernel-panic69 wrote:
What about disabling legacy rates per other device discussions... this forum needs the slamming head into brick wall emoticon.
I will try it, thank you very much.
Off-Topic to kernel-panic69 - and everyone can skip the part below (including Kernel-Panic69):
Edit: I may have read too deep into the slamming brick wall emoticon part because I'm oversensitive this morning (apparently ), you just were helping. Will leave my rant anyway.
Code:
If the answer is known, and you see 3 different guys (one of which referred to a post about ideal basic settings) then maybe it is worthwhile to make a new pinned post or set such thing to default in DD-WRT.
You may think everybody just post their thread up without reading anything, but this problem has been going for a while and I have browsed this forum and others (including openWRT to see if it is something basic going on) with no clear answer (TO ME, and at my skill level). Worst part is finding threads were Guru's are extremely delicate about thread resurrection, others about thread hijacking and specifically ask for a new thread to try and help users - then your post indicates that making a thread is somewhat a problem. I honestly get it; people that do not read, that want food straight to their mouth, and people asking the same thing over and over are annoying to those of you that actually are here everyday tackling those things on - but keep in mind that some people do try, and their skill level just doesn't allow them to do better (case in point, I have been practically googling most settings I have been asked to turn off and acronyms because the last time I used DD-WRT was over 8 years ago).
I just don't know what I'm doing, humbly, to put my time where my mouth is and write that thread to contribute - and I'm not asking anyone to follow my "brilliant, definitely novel" idea.
TL;DR: Just ignore the rant above, but if you feel something has become annoying because it is a FAQ now, maybe it is a time saver to pin a new thread with recommended settings and basics, if someone that knows what they are doing writes it. As I said, disabled legacy rates and I'm trying as per your recommendation, thank you (all of you, because tinkering with this alone over several days was making me think of just going back to factory firmware and move on; but I want to continue now).
@kernel-panic69: I know Kernel, the main reason I said what I said was not to attack you (and if it seemed that way sorry). I just know how painful it becomes to say the same time over and over - I have seen your post around all the place helping people.
Still, if anyone needs some more logs, want me to take more steps, more oops or anything, I'll be around (hopefully).
No need for any additional logs at this point. Both yours and my kernel dumps recorded to oops are incomplete so I have connected my mr7350 back up to serial to try to get a complete capture of the crash. It varies from around 2 hours up to 8 hours between crashes, so when it happens, it happens.
EDIT: By running iperf3 on it, I was able to crash it in under 5 minutes. Log has been sent to the management. _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: VLANs, Samba, WG, Entware - r60xxx
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r60xxx
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r60xxx
- Linksys MX4300: (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r60xxx
- Linksys MR7350: WDS Station for extended Ethernet r60xxx
- Linksys MR7500, MX8500: None in production. Just testing. r60xxx
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
- Forum member #248
), you just were helping. Will leave my rant anyway.