Ubiquiti's "Zero Handoff" feature is different from what people here are asking for. It is effectively a "single channel" system like Meru/wiNG. Even Ubiquiti do not recommend it!Just wanted to say for everyone asking for roaming implementation like Ubiquiti has, did anyone actually tried it so far? I have several of this UniFI APs at one customer, and i tried zero hand off feature and made everything so much worse and unstable that i had to turn it off, it simple doesn't work as good as you would expect it..
Well yea its brand new thing introduced this year, i was just saying about zero handoff which was originally requested prior to 2017, im sure mikrotik will give us something similar to FastRoaming soon(i hope)Ubiquiti's "Zero Handoff" feature is different from what people here are asking for. It is effectively a "single channel" system like Meru/wiNG. Even Ubiquiti do not recommend it!Just wanted to say for everyone asking for roaming implementation like Ubiquiti has, did anyone actually tried it so far? I have several of this UniFI APs at one customer, and i tried zero hand off feature and made everything so much worse and unstable that i had to turn it off, it simple doesn't work as good as you would expect it..
What people here are asking for is an equivalent to Ubiquiti's Fast-Roaming https://help.ubnt.com/hc/en-us/articles/115004662107
Those standards are relatively recent/new and the number of client devices that are actually capable of using those is greatly exaggerated. Also they still do not allow the AP to dictate the client when and where to roam- that still is totally client's decision. The standards you are referring to just (potentially) make the roaming process faster/more efficient. But please note that clients that support (and can benefit from the use of) these standards are likely to be rather good roamers even on their own (i.e. without AP assistance).Some people argued here that this is client responsibility to swith AP. Yes, it is. But client logic relies on AP supported standards, like 802.11r/k.
Try reducing the tx-power of your APs? That helps, really helps.Without ACL workaround clients dont switch APs when they should.
Sounds reasonable. I will definitely try. As I suppose AP Tx power should correlate with clients Tx power.Try reducing the tx-power of your APs? That helps, really helps.
In my opinion only client should decide when it should roam. Not AP. Thats why I do not like ACL workaround, as I described in my first post.Also they still do not allow the AP to dictate the client when and where to roam- that still is totally client's decision.
Look around. What does people really want? Whey want to use WhatsApp/Viber/Skype/etc voice/video calls. They use iphone/ipad/android with latest firmware. Vast majority of these devices do support these standards (https://support.apple.com/en-gb/HT202628)Those standards are relatively recent/new and the number of client devices that are actually capable of using those is greatly exaggerated.
I'm getting rather good results with 50mW output power, which means setting tx-power to 15dBm for 802.11ac-capable interfaces (where tx-power means total power) and 12dBm for double-chain (10dBm for triple-chain) non-802.11ac-capable interfaces (where tx-power means power per chain). You may also consider decreasing the tx-power for 2.4GHz interfaces even further to give 5GHz band some priority.Would you recommended Tx power for me (I am a home user: iphone, android, laptops etc) for channels 1, 6, 11 and for 5G?
We also wanted to participate in this project to extend our infrastructure. It seems, EU money will go to another company. Perhaps Mikrotik don't need this money?The project requirements for WiFi4EU are:
(..)
support IEEE 802.11r
(..)
But unfortunately Microtik does not meet the requirements.
For Germany, Italy, Romania,France, Spain, the funds allocated for project WiFi4EU is 20 160 000 EURO. Mikrotik lost that money because they dont need this money. Another company example: ub*** ,cis***** etc. cover all requirements. MIkrotik why not wake up ?We also wanted to participate in this project to extend our infrastructure. It seems, EU money will go to another company. Perhaps Mikrotik don't need this money?The project requirements for WiFi4EU are:
(..)
support IEEE 802.11r
(..)
But unfortunately Microtik does not meet the requirements.
Mikrotik is on Wireless one way road with old legacy kernel and own wireless driver with mostly basic hardware support....For Germany, Italy, Romania,France, Spain, the funds allocated for project WiFi4EU is 20 160 000 EURO. Mikrotik lost that money because they dont need this money. Another company example: ub*** ,cis***** etc. cover all requirements. MIkrotik why not wake up ?We also wanted to participate in this project to extend our infrastructure. It seems, EU money will go to another company. Perhaps Mikrotik don't need this money?The project requirements for WiFi4EU are:
(..)
support IEEE 802.11r
(..)
But unfortunately Microtik does not meet the requirements.
Great news! In which version of ROS6? Is that only announcement of the development or some builds are available as of now?Since lately there is some developement in ROS6 features regarding long awaited features, I would like to bump this one.
- dot11k/r/v based roaming / AP steering in CAPsManager
- dot11k/r/v based band steering (also without CAPsManager)
- option for airtime fairness
Also from other threads:
- support of wave2 (MU-MIMO, beamforming); viewtopic.php?t=145047
- tunable DTIM and beacon interval; viewtopic.php?t=116221
- stop broadcasting device model and ROS version with the beacon; viewtopic.php?t=133186
- support dot11d including country code; viewtopic.php?t=72840; viewtopic.php?t=144151
Great news! In which version of ROS6? Is that only announcement of the development or some builds are available as of now?
Oh I see now. A hastily & hopeful interpretation of that by me, to the point that I upgraded multiple devices to v6.45.b62!!. So still waiting and hoping....at least some more attention might be drawn here reincarnating this wish list....Don't get me wrong! I was hopeful when dot1x and ike2 features were released in 6.45beta, that developement of often reqested features was sped up. So I brought up my favorites to give them some attention.