|
Irrespective of the kit you use, the best way to extend Wi-Fi coverage is to create "cellular" network of multiple AP's. The "trick" is how you establish the "backhaul" links between AP's (and everything else.)
The best way to establish the backhauls is with "proper" cabled ethernet links. Thence, with careful radio channel planning you can get over the bandwidth clobberiing of repeaters and "mesh" systems that occurs when outpost AP's are tuned to the same radio channel as any other nearby AP's.
Next best is probably to tunnel the backhaul over the mains using powerline type technologies.
Least good is to establish the backhaul using Wi-Fi. But as speeds are getting faster, if that's good enough for you use case, it can be fine - especially with things like "tri-band" (which has backhaul and client access on different radio frequencies.) However, the fundamental of Wi-Fi are the same as ever - Wi-Fi is an only-one-thing-at-a-time-can-transmit techology, whether that would be transmitter is a client, AP, repeater, "mesh" link or anything else. By removing backhaul links from the Wi-FI airwaves (e.g. using ethernet or powerline) you increase the the air time available to the remaining devices.
SSID names is a matter of preference. If you name them all the same, then client may (just "may") automatically "roam" between AP's, if the SSID's differ, client will never roam until they completely loose connection but you will know for sure which AP you are talking to. There's no "right" or "wrong" way to do this, it's a matter of preference.
In enterprise systems it is possible to bind different SSID's to different VLAN's (virtual LAN's) and whilst some of the pro-sumer grade gear may offer this, the vast majority if "basic" SOHO kit does not (with the exception of the "guest" SSID some routers offer) so even if you set up differing SSID names, it's most likely they are all connected to the same common network, the upshot being that different SSID's hasn't effected separation of one group of clients from another. |
|