Next rock continues..

Another, however, is that my main home #router, a #Netgear #Nighthawk #R8000, is now not getting access to the internet through the #ATT router. My phone says, "Cannot provide Internet," and I haven't yet unlimbered my #laptop to actually log in to the routers to see what the hell is going on.

Just in case the old #DLink-645 (running #OpenWRT) has lost it, can anyone recommend a good, inexpensive, 2.4GHz/5GHz home router?

Help?

Thanks!

@baweaver
So I don't know whether to replace the #Linksys #Nighthawk #R8000 with a higher-end and more capable #router (such as #Ubiquiti, if I could afford such), or go with #repeaters (about the requirements of which I know nothing), or get an additional relatively low-end (read: #affordable) router and put the #IoT devices on a separate #subnet as originally ideated. Or something else. 🤔

Open to suggestions. Please. My #SBH is going spare about not being able to reach the printer.. 🙄🤪😔

@baweaver
As I said, I've got no idea about the #network #hardware, and severely limited funds. If I could have gotten the #DLink running, I would have had it be #DHCP #server for the #IoT devices in a separate subnet, since the #Linksys #R8000 isn't up to the combined task.

The R8000 logs don't even show #association requests for the devices not coming up, so I don't know if it's a #traffic issue or a router limitation.

@baweaver
I'm disappointed that my first foray into #OpenWRT came a cropper; the #DLink DIR-645 I #bricked with it was my main #Wifi #router before I moved up to the #Linksys #Nighthawk #R8000 2.4GHz/5GHz one I'm using now. (Which is having difficulty handling all my normal and #IoT devices, hence looking for alternatives. 😔)

Some #infrastructure-type things (like printers, #Raspi devices, and #PlayStation #consoles 🤣) really *need* to be #hardwired. 🙄😁🤪. #DHCP is giving me the red-arse..