> > In case it's not clear. I am NOT happy with how device manufacturers ship old > code and never update it. > I was unhappy about my home network and my paying job is to provide components for such. My home network wasn't resilient enough to carry entertainment, productivity (including distance learning) and medical traffic. The fixes so far have been: o) Don't use an all in one AP anywhere, just use it for wireless bridging o) Use a fronthaul architecture (2.5G - will go to 100G when Fi-Wi is ready) o) Use a dedicated firewall & dhcp server with AQM such as fq_codel (I use a protectcli vault) o) Connect the APs (4 for me in 100 sq ft) configured in bridge mode and optimize spacetime, allow for proper RF overlap - not too much, not too little, but just right like the story says. o) Use AP's that support the 6G band o) Use keep connect devices to detect AP failures and power cycle them (hammer approach) o) Use separate ethernet switches where 802.3 switching is needed (don't use the AP integrated switches, they go down per the crappy gateway sw you're likely talking about) o) Implement DHCP guard to protect against rogue DHCP servers Then for monitoring o) Install rpi 5bs with INTC BE200 and pcie Wi-Fi adapters in the rooms that need monitoring o) Install kismet and integrate with kismet to monitor o) Turn on firewall & WAN port monitoring services Only access to devices is ssh with encryption keys, and configure ssh passwordless access. Now, my family can be entertained, do their work and learning, and use their medical instruments with high in-home reliability. It's a thankless job we Dads must do. The home frustration level goes way down and the complaints of "Dad, the internet isn't working again" have gone away - except for when the OSP goes down. The OSP provider tends to send information to me when that happens so my family can work around it. Bob