Hello everyone,
at my home I use an AC3 hAP to generate 2 WiFi networks:
I would like to take advantage of 2 GHz and 5 GHz WiFi and am wondering what is the best approach to name the two networks:
For example:
Or will both 2GHz and 5GHz network interfaces show two networks with the same SSID?
Thank you for your help.
It depends on what you want. I.e. you could have a edicated IoT network on the 2.4GHz, while your corporate/home network is on 5GHz (or both 2.4GHz and 5GHz).
Shared SSID on two radios will support more clients. At the same time you have no control with what radio the client connects.
So…what do you want?
Hi,
I just wanted to flag up that I think the name should be changed to make it easier for clients to connect to the best WiFi.
So, if I have both 2 and 5 GHz radios with the same SSID (Home), which network will clients (e.g. a smartphone) capable of using 2GHz and 5 GHz connect to?
I’ve noticed that if both radios have the same SSID, the smartphone always connects to the 2GHz radio.
What’s the best way to name WiFi networks when both bands are available?
Thanks
I always keep the SSID identical and play with transmission power (lower 2.4GHz transmission power a lot). My client devices are smart enough to select the 5GHz radio, or roam to it when available.
Another disadvantage of having different SSID’s is the lack of roaming. You have to change manually, unless you loose connection.
Good suggestion! I will also play on power in the same way.
Roaming is what I would like to happen in my network as well.
If your hAP ac3 runs RouterOS version 7.13 or newer, you can install wifi-qcom-ac drivers … and uninstall wireless drivers. With this you’ll get newer, more potent drivers, on your AP. One if new features, which come with wifi-qcom(-ac), is suite of functions for better client mobility. It works with fairly new clients and works also for mobility between different frequency bands on the same AP. Some clients behave really smooth in such environments, some don’t exhibit any difference (compared to APs without mobility support), most are somewhere in between. Some (braindead? obsolete?) clients choke altogether and one has to create a separate SSID without support for advanced/modern features (many IoT clients fall into this category). If nothing else, you’ll get higher wireless speed for clients which support ac or newer standard.
I'm pondering this "trick" of playing with --- and by that I assume you mean lowering -- the 2.4 tx power level.
I assume this makes the clients thing that the 5ghz signal is stronger/better and therefore should be chosen.
What about when the 5ghz signal is low because of distance. That would be a situation when the client needs a stronger signal and would otherwise choose 2.4 but now only has a very weak 2.4 signal (which may or may not be stronger than the 5ghz signal, depending on the conditions between client and AP).
If one needs strong 2.4GHz signal for improved coverage, then the only way of decent mobility (in both directions, i.e. also from 2.4GHz to 5GHz) is to use new drivers (wifi) and rely on mobility functions … where client still has decisive powers.
Thanks for the suggestion.
I just updated to version 7.16.1 today.
Then I also install the ‘wifi-qcom-ac-7.16.1-arm.npk’ package and uninstall the wireless package.
I would like to make better use of this router’s potential.
By “mobility functions” do you mean clients being able to roam between 2.4 and 5?
Well … between any pair of APs with same SSID … from client’s point of view 2.4GHz and 5GHz are two different APs, it doesn’t know (nor care) that they’re radiating from approximately same location. In MT world all that takes is that both APs cooperate in certain ways … running ROS v7, wifi drivers and being controlled by same wifi entity (either capsman or even simply same CPU in case of dual-band APs).