I've got a router and 4 APs (sometimes 5 for the far yard in the nicer weather) and if you add up all the TVs, thermostats, AVRs, streaming boxes, laptops, phones, tablets, cameras, garage doors, outlets and other misc items I'll bet I have about 75 potential wireless clients in the house plus all the wired devices so it can begin to look more like a small office.Personally, I think 802.11r will be far more useful. I can see the usefulness of 802.11k or 802.11v when in a business network with multiple nodes and lots of clients, allowing to better spread the load. Not that useful in a typical home setup.
For home use in particular, it's the least useful. It's focused on sub-second roaming, mainly by using pre-authentication (oversimplification).Personally, I think 802.11r will be far more useful.
For home use in particular, it's the least useful. It's focused on sub-second roaming, mainly by using pre-authentication
11k and v are of more practical use, IF STAs use the information and roaming directions they provide.
The biggest mistake people make with mesh and. multi-AP systems is having too much overlap between APs/nodes.
The biggest mistake people make with mesh and. multi-AP systems is having too much overlap between APs/nodes. If a STA doesn't hit the roam-trigger RSSI, it won't roam. If there are multiple APs with similar signal levels in range, the STA may bounce between them.
It's why I tell folks that a wired and/or dedicated backhaul radio/network is a must for a successful mesh deployment.
THAT is just not true. MESH is a topology, not a technology.If it's wired, then it's no longer a mesh - it's just a bunch of APs.
The idea behind a mesh is that you have multiple nodes talking to one another over wifi, not necessarily in a star-shaped network but potentially daisy-chained, or some other form of network. Like a fishing net.
When you start plugging these with Ethernet backhauls, then it just becomes a managed AP infrastructure.
VoIP and Wi-Fi calling are definitely targets for 11r. The problem is that it really requires 802.1x to achieve fastest transitions. 11r is also supposed to support PSK authentication, but it may not be actually implemented on AP and/or STA.I was thinking about people moving around with their cell phone for example, some of which might be using Wifi-calling. I've seen a few complain about that with the current home mesh solutions like Orbi or Lyra.
You should read my articleUnless I misunderstood Wikipedia, I thought these two were more about capacity information, allowing clients to be moved to another AP if one already had too many clients - which would indicate having lots of busy clients, and having sufficient coverage overlap to make it practical?
IEEE 802.11s defined wireless mesh networks, which are based on ad hoc wireless links.THAT is just not true. MESH is a topology, not a technology.
VoIP and Wi-Fi calling are definitely targets for 11r. The problem is that it really requires 802.1x to achieve fastest transitions. 11r is also supposed to support PSK authentication, but it may not be actually implemented on AP and/or STA.
The problem most people have with roaming is that their STAs don't roam at all or are very slow (double-digit seconds) to change. This is due to STA algorithms, not delays due to authentication.
You should read my article
Among other things, 11k lets APs request information on signal levels and link rates from STAs and makes it available to STAs to aid in roaming decisions. 11v also provides info, but includes a transition management request function. This is a more polite way of asking a STA to move vs. deauthentication.
In other words for 11r to help, a STA has to make intelligent and fast (under 5 seconds) roaming decisions in the first place.
Correct but I never said wireless mesh and neither did others. They said MESH and they also said you can't have a mesh with wires.IEEE 802.11s defined wireless mesh networks, which are based on ad hoc wireless links.
In my experience, "mesh" connotes wireless backhaul, not wired.
Maybe that's why consumer marketeers switched to using the more neutral "Wi-Fi System" to describe multi AP systems.
At any rate, backhaul bandwidth matters in any multi-node AP system, no matter what you call it and it's tough for any wireless technology to beat Ethernet for bandwidth and reliability.
Asus added 802.11k and 802.11v support a few months ago. There is also a new option for 802.11r, but I don't see it enabled yet.
On the W10 device, look in the advanced NIC settings to see if it supports "Roaming Aggressiveness" or a similarly named feature. IIRC there will be 4-5 levels if supported.I've been curious about the level of implementation of k and v since the time you mentioned it a few weeks or a month ago in some other place on the forum, but I hadn't bothered to see if client switching between my main AP (router) and satellite AP (not AiMesh) had improved. I tried today, and it turns out that switching appears to have significantly improved. Now my MacBookPro, my Galaxy Note 8, and my wife's W10 laptop all readily switch to the AP with the stronger signal when there is a reasonable difference in signal strength between the two APs. I used to need to have Roaming Assistant enabled, but its no longer needed. Kinda cool. As for my wife's W10 laptop, the auto setting for Roaming tendency will have the computer stick with an AP until the signal strength drops below something like -82 dBm. Setting the Roaming tendency to "Bandwidth optimized" causes switching at something closer to -65 to -70 dBm which is much better.
IIRC there will be 4-5 levels if supported.
On the W10 device, look in the advanced NIC settings to see if it supports "Roaming Aggressiveness" or a similarly named feature. IIRC there will be 4-5 levels if supported.
There may also be a "Preferred Band" setting to select 5 v 2.4 spectrum and other RF management features such a "Channel Width". I personally find that setting these to more limited values (i.e. 20MHz channel limit) improves stability and overall performance. I rarely need the "highest possible bandwidth" on my portable devices and gladly trade these things for stability. As always, this advice is worth what you paid!
Thanks. Adjusting the Roaming Tendency option allowed for my wife's W10 laptop to hop to the better AP at the appropriate signal strength difference. I know this isn't related to AiMesh, but with the apparent support of k and v, it seems like the AP implementation works quite well now, at least for the devices that I've tried.
Which Roaming Tendency option did you select?
OE
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!