Conditions:
- I'm doing a major home renovation, and I can/will run ethernet to most or all rooms in the house.
- It's an urban environment with lots of intrusive neighboring wifi signals.
- The house is a rectangle, oriented portait-wise like your smartphone: 2 stories + attic, with a main front room, space in the middle, and smaller rooms in each rear corner. The internet modem is in the front main room on the 1st story. All of the ethernet lines can terminate at a switch here, so I figure the router can be here next to the modem.
- Notwithstanding wires in the walls, most client devices will be wireless; we are a 21st-century family with phones/tablets/laptops, no desktops.
1) I figure Cat6 cabling. Gigabit wired in the walls should do for wired backend networking for the foreseeable mid-range future. Right?
2) My first thought is, Plume. Three per floor on both floors, in front room/rear left corner/rear right corner. They'll use wired backhaul so the wireless only needs to handle the single hop to client devices. This way the house will be saturated with signal, and it will be relatively low-power so it won't strangle my neighbors' wifi and cause an escalating RF war. Even if the neighbors do get monstrous high-power stuff like Google Wifi, my little pods can just use a different channel for their single hop to clients, and I won't be disturbed.
But, but... Plume pods are *designed* for multi-hop. Is it silly to get Plume when I have wired backhaul and hops are unnecessary?
I think I probably want one of the modern "mesh" systems because I have read, and personally experienced, that roaming from AP to AP is terrible when you just do the "same SSID trick with old-fashioned APs. So I could do something like, Eero (AP front and back downstairs, and one in the attic, = signals blanketing the house). Or Orbi (one AP in front, one in back, done). But won't these options ignite the RF war?
And I know: Unifi Unifi Unifi. But I think Unifi is not user-friendly enough for this application. I am fairly savvy, I can tread water if dunked in a CLI, but I don't particularly want to jump in and live there on purpose.
Anyway, I appreciate all thoughts.
- I'm doing a major home renovation, and I can/will run ethernet to most or all rooms in the house.
- It's an urban environment with lots of intrusive neighboring wifi signals.
- The house is a rectangle, oriented portait-wise like your smartphone: 2 stories + attic, with a main front room, space in the middle, and smaller rooms in each rear corner. The internet modem is in the front main room on the 1st story. All of the ethernet lines can terminate at a switch here, so I figure the router can be here next to the modem.
- Notwithstanding wires in the walls, most client devices will be wireless; we are a 21st-century family with phones/tablets/laptops, no desktops.
1) I figure Cat6 cabling. Gigabit wired in the walls should do for wired backend networking for the foreseeable mid-range future. Right?
2) My first thought is, Plume. Three per floor on both floors, in front room/rear left corner/rear right corner. They'll use wired backhaul so the wireless only needs to handle the single hop to client devices. This way the house will be saturated with signal, and it will be relatively low-power so it won't strangle my neighbors' wifi and cause an escalating RF war. Even if the neighbors do get monstrous high-power stuff like Google Wifi, my little pods can just use a different channel for their single hop to clients, and I won't be disturbed.
But, but... Plume pods are *designed* for multi-hop. Is it silly to get Plume when I have wired backhaul and hops are unnecessary?
I think I probably want one of the modern "mesh" systems because I have read, and personally experienced, that roaming from AP to AP is terrible when you just do the "same SSID trick with old-fashioned APs. So I could do something like, Eero (AP front and back downstairs, and one in the attic, = signals blanketing the house). Or Orbi (one AP in front, one in back, done). But won't these options ignite the RF war?
And I know: Unifi Unifi Unifi. But I think Unifi is not user-friendly enough for this application. I am fairly savvy, I can tread water if dunked in a CLI, but I don't particularly want to jump in and live there on purpose.
Anyway, I appreciate all thoughts.