Recent content by ducky124

Your router is not looping back traffic properly, Plex is not at fault, and ports are fine. The cleanest fix is DNS override or always using the local IP. http://192.168.x.x:32400/web use this to connect to Plex instead of https://app.plex.tv/desktop/

nothing like beating a dead horse.

that design is close to 10 years old. Just throw it away.

When you format it with the router naming is one of the options. No really sure what you are askinh in second question

Yes, did reset on the nodes, flashed with stock firmware and then reset the be88u and set up from scratch. Ethernet backhaul.

I had similar issues at first with my BE88U and mesh nodes. I did a reset and set everything up from scratch, but the problems persisted. I even started to wonder if there might be an issue with the new BE88U itself. Since I had always run my mesh nodes without issues on Merlin before, I kept...

If you're ready to invest, it might be worth future-proofing the setup with a new BE router. Of course, that depends on your budget. If you're looking to save, a used AX router from eBay could still be a solid upgrade without breaking the bank.

You don't necessary have malware on your phone. This could have happened during a normal browsing session. A page you visited could have been injected with hidden JavaScript that automatically beaconed out to in the background. You never had to click anything. Or possibly a seemingly normal ad...

Look at it this way: upgrading to Wi-Fi 7 is like trading your clunky old shuttlecraft for a warp-capable starship. Your current router? It’s basically running on dilithium fumes. With Wi-Fi 7, you’ll be streaming, gaming, and downloading at speeds that would make even the USS Enterprise...

Bad block errors usually point to failing internal flash memory, which can cause random reboots when the router hits a corrupted area. You can try backing up your config, doing a full factory reset (set up manually, don’t restore the old file), and reflashing the firmware to see if it...

I ran into the same issue recently after getting my new BE88U. No matter what I tried, my AX88U Pro mesh node with Ethernet backhaul never showed any connected clients, even though I knew they were connected. I even ran signal tests to confirm they were actually using the node. Eventually, I...

Brand new BE88U, previously only ran Beta 2 and Beta 3 firmware. The final release is running perfectly overall — my two mesh nodes are up and stable, and both my guest and two separate IoT networks are functioning flawlessly. The only issues so far: Adaptive QoS bandwidth monitoring still...

I’ve got two mesh nodes up and running perfectly. In my experience, it helps to start the setup using Ethernet backhaul—just plug them in with a cable first. Once everything’s connected and working, you can switch to wireless. It seems to make the whole AiMesh setup process a lot smoother.

Running Beta 2 since yesterday afternoon. So far the only issue I have seen is the upload/download bandwidth gauges are not working in Adaptive QoS.

yeah, realized that after i hit send