Hi, I've had these mesh nodes for a couple of years now, using Stock Linksys firmware, and have run repeatedly into the dreaded 2123 error as detailed in https://smith6612.me/2024/09/16/linksys-mesh-router-velop-error-2123-please-fix-it/ and I've had enough.
I'm hiding as much as I can to maintain brevity in this post, but I have several questions. So, first some background info.
Home layout summary
My setup is simple, yet not. FttH coming in to AT&T's ONT, from there to their 'residential gateway', and from there to the main MX5500 node. Out from the main node to an 8 port gigabit switch, and 5 lines from the switch to a rack mounted patch panel which connect to individual Cat 5e / Cat 6A runs to rooms where the satellite MX5500 nodes are located.
I have a two story home with an unfinished basement, so all of the above networking stuff other than the satellites are all in the basement. Runs to the main floor were originally 5e but I have replaced them with 6A. Runs to the second floor are 5e intact as installed by the builder (and for good reason). I've verified each and every terminal point throughout the system that I am actively using, and all runs are solid.
I realize that I would be better off setting up a (new) router inside my RG and then purchasing and installing 'proper' APs, but that is simply not in my budget any time soon, as I already spent a pretty penny on these nodes (3 packs x2 for a total of 6 nodes) back when they were newly released. I also initially used them as a true mesh system, only moving to a wired AP layout when I continued to have issues with the mesh itself. Connectivity wise, the wired AP setup worked really well, giving great throughput in every room that I tested, both wired and wireless, until the 2123 hits - then wired performance drops significantly (upload, of all things) and WiFi connectivity throughput drops somewhat significantly. If I am able to catch it in time and clean out the device logs I can keep it going for a good amount of time, but sometimes that 2123 hits within a week of clearing, and I don't have the time (nor patience anymore) to babysit that log every other day, especially since I don't have an easy cli method to clear the log, and logging in to the system (using either the Android app or else directly into the webpanel interface is tedious and slow.
With my family's need for device connectivity, as well as the fact that I WFH, along with the fact that we have a whole slew of appliances that also need connectivity, as well as other IoT devices, I need to set this up in this manner. I plan to keep at least one (probably 2) of the 6 nodes as ready to use backups (1 configured as the main node and one as a satellite) in case anything stupid happens along the way (read: I try something and it breaks lol).
That covers all of that, please ask if I am being unclear in my description, I'll be happy to provide more info.
The problem is that the dreaded 2123 error happens all too quickly in my setup, and after dealing with Linksys 'tech support' 3 different times, all with the same end result (factory reset and start over) I'm done with it. I decided to try DD-WRT first as I had used it in the past, but I'm having issues having that work correctly, so I've come here hoping for a better result.
My questions:
-
I've read a lot of the wiki regarding installation. I see that the 'firmware selector' allows me to dl Sysupgrade or Factory images for my MX5500s. Can either of those be used to flash over DD-WRT?
-
Being snapshots, am I correct in assuming these would be considered 24.10 or newer, so that I can simply use the 'apk' commands to add LuCI to the resutling installation on any given node?
-
I read elsewhere in a thread that LuCI is not required for wired APs at all - and I'm somewhat familiar with *nix cl, but I'd prefer to use a GUI for ease of use as a backup to using cl to manage the satellite nodes. Any problems doing this?
I think that covers me - I'm going to flash the factory build onto the 4 nodes I have that are currently on (factory reset) factory images in the meantime.