Skip to main content

Hello

The graphic below is just to get your attention as I think it looks nice but adds nothing to the information being discussed other than the caption 😂. 

This link will take you to the article published in 2022. Below are quick links in the article that I decided to “star” as they highlight elements that I and other community members have been saying for years. I’m going to add an eighth (8th) mistake to avoid which is….

  • Make sure satellite nodes in a Mesh network do not have DHCP capability to assign IP Addresses to clients. IP Address assignment (DHCP capability) should only be allowed by the main node which is the router in a Mesh network.

Other points listed above are important as well, but some require additional expenditures such as Ethernet backhaul. I personally have my ASUS Wi-Fi 7 mesh network wired as such which provides rock solid performance for over sixty (60) clients. Thirty (30) of which are Sonos. IMO it’s a worthwhile investment. 

So, enough introduction. Click the link above and read the article yourself. Be warned there are links to advertisements and product promos on the website as well.  Enjoy!

Something to consider when using Ethernet backhand is POE (power over Ethernet) as it really simplifies placement and connection of your remote APs or nodes. It also let's you place the POE injector on your UPS so the mesh stays up when power glitches. 

If doing just a few devices individual power injectors makes sense, if multiple devices, at some point a POE capable Ethernet switch becomes more cost effective.

 

I've done this with my access points and a couple other devices. I'm kicking myself for not doing the same with my security cameras, when I update them they will be POE without question. Really dumb to have security cameras that can be disabled by flipping one breaker, with them POE and on the UPS I'd have at least 20 minutes of run-time. Dumb call on my part.

Reply


Terms & ConditionsCookie settings