802.11r for hAP ac2?

Fusseldieb · Thu Sep 02, 2021 3:00 am

I've seen countless of posts and external pages regarding 802.11r support and most of them say that it's not yet implemented.

Is that true? Why?

I mean, it's supported by the chip of this router...

Thanks in advance.

Zacharias · Thu Sep 02, 2021 10:32 pm

Is that true?

As far as i know it is not implemented yet ...

whatever · Fri Sep 03, 2021 1:32 pm

It's not implemented because MikroTik did not implement it.

santyx32 · Sat Sep 04, 2021 4:18 am

I guess it'll never be implemented cause they're now focused on wifiwave2 drivers for their new devices.

mkx · Sat Sep 04, 2021 10:52 am

Wifi wave2 drivers and 802.11r functionality are not exclusive. The thing is that 802.11r works with some kind of AP coordination beyond what CAPsMAN can do currently, so CAPsMAN needs some work to be done. Might be that current CAPsMAN design can not easily accomodate needed coordination. Or the CAPsMAN development team currently works on something more important ... Or that current WiFi drivers (MT proprietary!) lack needed hooks and wifi devs work on something more important, such as wave2 drivers.

So let's stay optimistic and hope for something to happen around ROS 7.1.6 (or something).

mman1982 · Thu Jan 12, 2023 10:33 am

Is there any news on it??

mkx · Thu Jan 12, 2023 3:56 pm

Change log of just released v7.7 says that it contains initial release of capsman2 ... which works with wave2 drivers.

802.11r is not mentioned so I guess it's safe to assume that capsman2 doesn't support it (yet).

If referring to title of this thread (which is asking about hAP ac2), there's still a show stopper: wifiwave2 driver still can't be installed on hAP ac2 (and it doesn't seem that this restriction will be lifted any time soon - if ever).

strarsis · Sun Mar 05, 2023 5:14 pm

Support for 802.11r on the RBmAP2n would be great! I have issues with clients connecting to the one AP with the worse signal.

massinia · Sun Mar 05, 2023 6:50 pm

I have issues with clients connecting to the one AP with the worse signal.

You can make an ACL to prevent low signal clients from connecting, search on forum there are many guides.

Sun Mar 05, 2023 6:52 pm

Support for 802.11r on the RBmAP2n would be great! I have issues with clients connecting to the one AP with the worse signal.

Aint gonna happen... Not on map.

anav · Mon Mar 06, 2023 2:52 am

IS "r" a standard of wifi6? If so, of course MT will provide it. They are always up to date providing us modern wifi and not just cute buzz words.

Wifi 6 is defined as the sixth version or generation of wireless local area networking technologies, as per the Wi-Fi Alliance, that is compatible with the Institute of Electrical and Electronics Engineers (IEEE) 802.15.4. 1ax standards and enables the efficient performance of networked devices in dense conditions
Talks about Mu-MIMO and OFDMA, but nothing about k, v, r standards.

k became standard 2008
v became standard 2011
r became standard 2008
ac (wifi5) standard 2013
ax standard 2019

If k,v,r actually helps clients achieve better roaming and its available on all phones, and there is no better alternative, then it boggles logic as to why not implemented ????

arm920t · Mon Mar 06, 2023 5:11 am

Huawei,cisco,aruba even tp-link have 802.11k/v/r implement in there APs.Come on Mikrotik it is 2023 now.

Rox169 · Mon Mar 06, 2023 8:04 am

hi,

check changelogs.... MT already implemented 800.11 r.k.w only v is missing....

Mon Mar 06, 2023 8:48 am

Only within same AP for now, as far as I understood (i.e. moving from 2.4 to 5Ghz on same AP and vice versa).

Mon Mar 06, 2023 8:49 am

802.11k is supported in wifiwave2.
the other one are coming too.

Mon Mar 06, 2023 8:51 am

@normis:
full subnet or only within AP ?

mkx · Mon Mar 06, 2023 9:09 am

802.11k is supported in wifiwave2.
the other one are coming too.

As the thread title says ... for hAP ac2? I'd love to see that ...

Rox169 · Mon Mar 06, 2023 11:16 am

802.11k is supported in wifiwave2.
the other one are coming too.

Hello Normis,

please do not forget the standard 800.11 v

Tue Mar 28, 2023 2:35 pm

We have no plans to add these features to old chipsets. Only ww2 package gets regular updates to newer standards and features

mkx · Tue Mar 28, 2023 8:37 pm

We have no plans to add these features to old chipsets. Only ww2 package gets regular updates to newer standards and features

Again: this thread is about hAP ac2, which features IPQ4018 chipset. Which in principle is supported by wifiwave2. So we're not asking to support legacy chipsets, we're asking MT to create slimed-down ww2 package which will fit on hAP ac2.

Tue Mar 28, 2023 8:46 pm

And IPQ-4019 supports it as well

A couple of other devices besides AC3, Audience and Chateau who carry that one (but looking at product matrix, not that much benefit to gain there ...).

4018 however, that's another thing. Cap AC, Cap XL AC, AC2, wap AC, Wap R, ... mighty interesting if that could be true.

mkx · Tue Mar 28, 2023 8:48 pm

Indeed, my Audience happily runs it. And my hAP ac2 is eagerly awaiting it.

pe1chl · Tue Mar 28, 2023 8:49 pm

That will never be possible! My hAP ac2 has only 1200 kB free space in a bog standard 7.9beta4 install. It will run out of space soon even without new drivers.
(note that old MIPSBE devices with 16MB flash have a lot more free space)
Only when offloading of space towards a USB stick would be supported, it could work. But even then it would probably require modularization of RouterOS v7 (so we can de-install unused features), also contrary to the current policy of putting everything in one package as much as possible.

Tue Mar 28, 2023 8:53 pm

Consider this:
despite the road which has been taken with ROS7 to be pretty monolithic (which at that point in time I understood) , that path has been left behind with wifiwave2, container, rose, zerotier ... and whatelse will be coming.
So might as well go back to cutting the core down to the bare minimum as it was with ROS6.

Simple example: ROS7 has wifi legacy embedded which for quite a few devices is to be replaced with wifiwave2. Waste of resources, I would say.

Just my 0.02€.

pe1chl · Tue Mar 28, 2023 8:58 pm

Well, what I hate even more is that wifiwave2 cannot co-exist with existing wireless. I have a RB4011iGS+5HacQ2HnD. It has the resources to run wifiwave2 on 5GHz, but when I install it I will lose 2GHz, which I cannot do because I have some old slow stuff connected to that. If only the wifiwave2 would load first, detect the devices it supports, and then leave it to the existing wireless drivers to support the 2GHz interface...
And that for such a "flagship router"... I think MikroTik should give a mini-PCI card to those that request it, that replaces the 2GHz wifi with something compatible with wifiwave2.

Tue Mar 28, 2023 9:01 pm

Yeah, RB4011iGS+5HacQ2HnD is a funny one having having 2 different wifi environments.

Theoretically that swap of mini-PCIe card should be doable.
Practically, depends on the sales numbers, I guess.

anav · Wed Mar 29, 2023 2:51 pm

There is nothing funny and nothing to hate but your own stupidity if made bad decisions knowing full well the limitations of older gen WIFI, after your first foray into mt wifi. I learned my lesson on capac and ended up with 3 thinking I was on top of the world.........wrongo, so yes, hate but hate yourself for the second or third time you bought one. The fact that normis had to be politically correct above is very telling. No new features in OLD chipsets including OLD standards. BUT we will add new features by adding OLD standards into wifiwav2. Thats called progress.

I am hoping my ax3 is not another paper weight!

pe1chl · Wed Mar 29, 2023 3:42 pm

It is time to add you to my foe list again, sore loser!

Wed Mar 29, 2023 4:11 pm

You can stop dreaming, like it was already said multiple times, ww2 package uses stock driver, which is very large. We can't and wont take it apart, it would render useless our efforts to make stock qualcomm driver work in ROS. that was the whole point, take the driver and use it.

Wed Mar 29, 2023 4:35 pm

But but ... Normis,
please enlighten me.

So are you saying that the wifiwave2 package uses the legacy parts to function ?
And there is no way to consolidate those ?

That's a bummer.

anav · Wed Mar 29, 2023 5:37 pm

Where did you see that Holve... WifiWave2 FULLY replaces old wifi. Its one or the other not both. As for RB4011 turn wifi off and get a capax ;-P

anuser · Wed Mar 29, 2023 10:36 pm

You can stop dreaming, like it was already said multiple times, ww2 package uses stock driver, which is very large. We can't and wont take it apart, it would render useless our efforts to make stock qualcomm driver work in ROS. that was the whole point, take the driver and use it.

Well, ww2 package includes stock drivers for all (new) chipsets. You could actually create ww2 package for each chipset which could fit.

So a "wifiwave2-lite" package for e.g. IPQ/4018/IPQ4019 devices with 16MB of ROM seems not be unrealistic to me at all

pe1chl · Wed Mar 29, 2023 10:46 pm

So a "wifiwave2-lite" package for e.g. IPQ/4018/IPQ4019 devices with 16MB of ROM seems not be unrealistic to me at all

Read what I wrote above: a hAP ac2 has only 1200kB (1.2MB) of free space left with a bare 7.9 install of RouterOS.
That will fill up "soon" with the new 7.x releases and the additional new feature here and there that they introduce.

anuser · Thu Apr 06, 2023 11:19 pm

So a "wifiwave2-lite" package for e.g. IPQ/4018/IPQ4019 devices with 16MB of ROM seems not be unrealistic to me at all
Read what I wrote above: a hAP ac2 has only 1200kB (1.2MB) of free space left with a bare 7.9 install of RouterOS.
That will fill up "soon" with the new 7.x releases and the additional new feature here and there that they introduce.

Well, the whole "wifiwave2-7.8-arm.npk" has
- 10,1 MB (10.625.169 Bytes) packed
- 25,0 MB (26.241.088 Bytes) unpacked

wifiwave2-7.8-arm\lib\firmware\IPQ4019 has
- 1,30 MB (1.368.091 Bytes) unpacked

=> I still think you can pack all needed parts into an wifiwave2-IPQ4019.npk and still have some hundreds of KB left.

I don´t know whether MikroTik would have to pay additional licensing fees to the vendor if they release the wifiwave2 vendor based drivers for older devices like hAP ac, cAP ac...

anuser · Wed Apr 12, 2023 11:07 pm

Well, 802.11k, 802.11v, 802.11r for hAP ac2, cAP ac, wAP ac 1. gen, exists...
... with OpenWRT (officially) starting with release 22.03:
https://openwrt.org/toh/mikrotik/hap_ac2
https://openwrt.org/toh/mikrotik/rbcapgi-5acd2nd_cap_ac
https://openwrt.org/toh/hwdata/mikrotik ... hnd_wap_ac

There is also a wireless controller: https://openwrt.org/docs/guide-user/network/wifi/dawn
Of course not as polished as CAPsMAN

Thu Apr 13, 2023 9:00 am

While you are all talking here, 802.11r/k are already implemented.
https://help.mikrotik.com/docs/display/ROS/WifiWave2

pe1chl · Thu Apr 13, 2023 10:27 am

But not on hAP ac2, cAP ac, wAP ac 1. gen as the previous poster writes!
You have announced yourself that MikroTik will abandon development for such units and will only go forward with wifiwave2.

Thu Apr 13, 2023 10:28 am

Ah yes, wrong topic, sorry

What I wrote previously is still correct. No new drivers for old chips.

pe1chl · Thu Apr 13, 2023 10:38 am

And also no new drivers for old units. So no wifiwave2 for hAP ac2 and no usable wifiwave2 for RB4011 (because 2GHz does not work).
Essentially there is a cut in the MikroTik product line. Before that point you can have features like 4-address mode (transparent bridge) and modes optimized for Pt(m)P use (Nstreme, NV2), after that point you can have wave2 and 802.11k/r and maybe v.
There is no way of having them both, and there are only very few devices where the user can select which one they want.

Thu Apr 13, 2023 10:45 am

We do not have "PER MODEL" packages. Only then we could do this. But change like that would require something like RouterOS v8, where all NPK package system is different, and we can make RouterOS-v8-hAP-ac.npk

Thu Apr 13, 2023 2:19 pm

We do not have "PER MODEL" packages. Only then we could do this. But change like that would require something like RouterOS v8, where all NPK package system is different, and we can make RouterOS-v8-hAP-ac.npk

I like the sound of this....

Smaller packages, less ram, more functionality

anuser · Thu Apr 13, 2023 9:37 pm

We do not have "PER MODEL" packages. Only then we could do this. But change like that would require something like RouterOS v8, where all NPK package system is different, and we can make RouterOS-v8-hAP-ac.npk

This is actually not needed, you can make an "PER CHIPSET" addon wifiwave2 package, i.e. "RouterOS-wifiwave2-IPQ40xx.npk"

Thu Apr 13, 2023 10:56 pm

Exactly since wifwave2 IS a separate package.

mkx · Fri Apr 14, 2023 8:35 am

I guess that what @normis meant was that they would have to introduce device-specific packages. Which MT never had IIRC. There are platform-specific packages and there are optional packages (and MT went in direction to eliminate or minimize need for the later in v7). And yes, many of us are opposing the idea of "grand unification" of packages and what @normis mentioned (with some distinct disgust in the sub-tone) seems the right way for us. I'm just not convinced that it would need major ROS version (v8) to be able to do that though.

Right now package file names are in format

<package_name>-<version>-<platform>.npk

and it would need to be extended to (optionally) include device model name (or some such; I think it would be better than chipset name ... most people can figure out device model but not used chipset). So package handling would have to be improved at least to accomodate the following:

handling the optional device model name part of package name ... both in terms of file name as well as checking if a package is appropriate for particular device
dependency checking as to prevent installation of multiple packages all providing same functionality
dependency checking as to force installation packages which provide required functionality
mechanism to automatically upgrade optional packages (which worked in v6)

I don't see how improved package handler would require major ROS release.

Fri Apr 14, 2023 9:13 am

We can't have PER-CHIPSET packages, since NAND/RAM is different per model, not per chipset

anuser · Fri Apr 14, 2023 11:07 am

We can't have PER-CHIPSET packages, since NAND/RAM is different per model, not per chipset

Well

Really?

Let´s take a look at the current Extra packages at https://mikrotik.com/download

1. ARM => "all_packages-arm-7.8.zip\wifiwave2-7.8-arm.npk\lib\firmware\"
- IPQ4019
- IPQ5018
- IPQ5018cs
- QCA9888
- QCA9984
- qcn6122 (Side note qcn6122 == Wi-Fi 6E)

=> Naive notion: Delete all folders except the one(s) for IPQ4019 and create an wifiwave2-7.8-arm-ipq40xx.npk?
=> Problem solved: 802.11r for hAP ac2 is available with RouterOS and may be for other IPQ40xx based MikroTik devices, too.

2. ARM64 => "all_packages-arm64-7.8.zip\wifiwave2-7.8-arm64.npk\lib\firmware\":
- IPQ6018
- IPQ8074v1
- IPQ8074v2

3. MIPSBE => "all_packages-mipsbe-7.8.zip" => No wifiwave2 package
4. MMIPS => "all_packages-mmips-7.8.zip\wifiwave2-7.8-mmips.npk\" => No firmware files
5. SMIPS => "all_packages-smips-7.8.zip" => No wifiwave2 package
6. TILE => "all_packages-tile-7.8.zip\wifiwave2-7.8-tile.npk\" => No firmware files
7. PPC => "all_packages-ppc-7.8.zip\wifiwave2-7.8-ppc.npk\" => No firmware files
8. X86 => "all_packages-x86-7.8.zip\wifiwave2-7.8.npk\" => No firmware files

pe1chl · Fri Apr 14, 2023 11:50 am

We can't have PER-CHIPSET packages, since NAND/RAM is different per model, not per chipset

But you CAN have all kinds of other optional packages, like container, rose-storage, user-manager etc, that are voluntarily added and are nicely updated when the router is updated.
So I don't understand why you cannot have a chipset-dependent package that the user could extract out of a zip, upload to the router, it would be installed and then upgraded for the life of the router. Maybe the user would upload the wrong one, and it would not work and be ignored or disturb things, but that could be fixed by removing it and uploading the correct one.
Also, you could include such an optional package during the manufacturing process, maybe in disabled state.

Fri Apr 14, 2023 11:59 am

Those are still based on ARCH, not CHIP.

Container package is present in all ZIP files, arm arm64 and x86.
There is no hAP ac3 version of container. It is all the same in all arm routers.

What you are asking is one package for hAP ac3 and another package for hAP ac3

anuser · Fri Apr 14, 2023 12:07 pm

According to https://mikrotik.com/products/matrix all 32 MikroTik IPQ-40xx based products share the same architecture, i.e. ARM 32 bit. Yet again
=> Naive notion: Delete all folders except the one(s) for IPQ4019 and create an wifiwave2-7.8-arm-ipq40xx.npk?
=> Problem solved: 802.11r for hAP ac2 is available with RouterOS and may be for other IPQ40xx based MikroTik devices, too
=> Everyone is happy

Fri Apr 14, 2023 12:13 pm

Yeah, but not the same resources memory and flashwise.

I still think conceptually it should be possible to run wifiwave2 on AC2, cAP AC, cAP XL AC, wAP AC, ... but then the wifiwave2 package needs to be stripped from all excess fat for it to fit.
And then there is still the question if it will run properly on those devices.
Unless a major overhaul is done on the monolithic base package as it is now to create more room and that I fully understand is not a small task.

So, I keep hoping ... someday maybe ?

Fri Apr 14, 2023 12:18 pm

yes, it is not a "drop in stock driver", there is work to be done for each model anyway, even if model-specific NPK would exist

pe1chl · Fri Apr 14, 2023 12:51 pm

Those are still based on ARCH, not CHIP.

Container package is present in all ZIP files, arm arm64 and x86.
There is no hAP ac3 version of container. It is all the same in all arm routers.

What you are asking is one package for hAP ac3 and another package for hAP ac3

I presume you mean to mention two different models there. Look: in the all_packages there is a package for "lora". That will only work on devices that have lora, right?
Yet, it is in the ARM all_packages file that I can download on my RB4011. Same with "gps". Or "ups". Those are all packages that can be installed but may not do anything useful unless installed on the correct model of router within that architecture, or when having external hardware connected that not everyone has.
So I don't think it is impossible to have a specific reduced version of wifiwave2 that works on some routers but not on others, within the same architecture.

pe1chl · Fri Apr 14, 2023 12:56 pm

I still think conceptually it should be possible to run wifiwave2 on AC2, cAP AC, cAP XL AC, wAP AC, ... but then the wifiwave2 package needs to be stripped from all excess fat for it to fit.
And then there is still the question if it will run properly on those devices.

I guess it would only be possible when the big "routeros" package is slimmed down as well, and the parts that would usually not be used on a home access point moved out into separate packages that can be uninstalled first.
As wifiwave2 apparently cannot co-exist with the existing wireless drivers and management software at all, the first candidate would obviously be "wireless".
(any device now running wifiwave2 apparently ALSO has the old wireless code still present, but disabled. even the RB4011 cannot run them both at the same time!)

Fri Apr 14, 2023 12:57 pm

In some other thread Normis explicitly mentioned wireless is NEEDED as base for wifiwave2. So that's not an option to leave out.
Unless I misunderstood.

pe1chl · Fri Apr 14, 2023 1:12 pm

In some other thread Normis explicitly mentioned wireless is NEEDED as base for wifiwave2.

Ok, maybe there are some "invisible" parts that are required. But in general the wifiwave2 package replaces commands (others go away) and apparently also disables drivers from wireless.
I would love to see wifiwave2 operating on 5 GHz and wireless driving 2 GHz on my RB4011, but it is not possible.

Fri Apr 14, 2023 1:18 pm

No, I don't think I ever said that. WW2 package is separate and not related to old Wireless

anuser · Fri Apr 14, 2023 1:23 pm

yes, it is not a "drop in stock driver", there is work to be done for each model anyway, even if model-specific NPK would exist

So it´s only about time and money. How would you estimate the costs? I.e. If we start a Indiegogo project, how moch money would we need to raise in order to get MikroTik start developing wifiwave2 drivers for older IPQ40xx products like hAP ac2, cAP ac, ,,,?

pe1chl · Fri Apr 14, 2023 1:33 pm

Probably it works better when you are a distributor and call them saying "hey we have sold 50000 of those cAP ac and now this customer wants to order 50000 more cAP ax but only when you make the old units operate to the same standards and management"

Fri Apr 14, 2023 1:37 pm

No, I don't think I ever said that. WW2 package is separate and not related to old Wireless

Then I obviously misunderstood:
viewtopic.php?t=178111#p993013

mkx · Fri Apr 14, 2023 2:28 pm

No, I don't think I ever said that. WW2 package is separate and not related to old Wireless
Then I obviously misunderstood:
viewtopic.php?t=178111#p993013

Yes. In post you linked @normis was talking about Qualcomm-provided "stock" wireless drivers ... not the Mikrotik's own legacy "stock" driver.

Other than that: I can understand that the "slimmed down" packages would have to be per device model. E.g. Audience is based on IPQ4019 (more or less the same as IPQ4018, which is base of e.g. hAP ac2), but runs merrily the "full" wifiwave2 drivers (because it's got necessary flash space). Which is why I included bullet about package dependency in my post #44 above ... it's not needed (but potentially disastrous) if one would install full wave2 driver, available from wifiwave2-7.9-arm.npk, and on top of that also IPQ401x trimmed-down wave2 driver, available from wifiwave2-7.9-arm-IPQ401x.npk. Naming the trimmed-down package e.g. wifiwave2-7.9-arm-RBD52G.npk would not per-se solve the problem though.

pe1chl · Fri Apr 14, 2023 6:04 pm

I don't think that would be unsolvable. In the past we also had times when a "new" wireless driver was available as an optional package, and you could install it in addition to a full install.
Ok, that has sometimes caused headaches when in a new RouterOS version that "new" driver became the standard one and was not available for upgrade anymore, leading to some subtle problems, but often it just went fine.
And in that case the situation "user installs specific driver while wireless is already installed" was the desired situation that would have to be allowed. In the "current use case" the installation script for wifi driver packages could first check if another package is already present and then refuse to install itself, logging "package not installed, remove this package first".

Ca6ko · Tue Apr 18, 2023 12:26 pm

See what the new wifi driver is called. The 802.11ac Wave 2 standard came out in 2015.
"How you name the yacht that's how it will sail."

/Captain Vrungel/
I would call the new driver WifiAX, which makes sense, and cut the WifiWave2 version down leaving only the ac device drivers in it.
This should be done after the WifiWave2 package adds support for capsman v6.

pe1chl · Tue Apr 18, 2023 12:39 pm

Yeah, but that is probably not going to happen...
The situation is that early on, MikroTik (like some similar companies) did a lot of in-house work to make better drivers for WiFi than the chip manufacturers provided as reference code.
They added extra features, even including completely reworked channel access protocols (Nstreme, NV2) that were incompatible with industry standards.
In the meantime, the standards evolved (wave2, ax) and the quality of manufacturer drivers improved as well.
So we got in the situation that those that had developed their own drivers and did not keep track of developments in the standards world and the drivers got behind the cheapo device manufacturers that only copied the manufacturer reference drivers. They got wave2, ax, 802.11k/r/v etc WAY before MikroTik and similar manufacturers did.
They also made capsman to be completely intertwined with their own drivers, and now that they finally made the decision to abandon the in-house drivers and start from the reference drivers again, they face a lot of difficulties as we have seen. Capsman incompatible, 4-address mode gone, etc.
So for existing customers there will be a lot of loss of functionality, but for new customers it brings them back to the state of technology that has improved for over 5 years without them taking advantage of it.

Unfortunately (see topic of this thread) in that same timeframe it was decided that "16M flash is enough for everybody" and apparently they lost sight on the competitor's devices (w.r.t. memory capacity) and nobody asked "hey why is the competitor putting 256M flash in their devices? is there a reason for that?" and they kept designing, making and selling 16M devices that are now a dead-end.

Tue Apr 18, 2023 5:04 pm

excellent summary, pe1chl

strarsis · Sun Sep 03, 2023 6:10 pm

So from what I understand is that one can install the `WifiWave2` package on a Mikrotik device and get 802.11r and WPA3?
Only a few features would not be supported anymore, but I do not use them anyway. That would be awesome!
Is the mAP (mispbe) device also supported?

Sun Sep 03, 2023 6:18 pm

No.

See here
https://help.mikrotik.com/docs/display/ ... ckwireless

strarsis · Sun Sep 03, 2023 6:22 pm

No.

See here
https://help.mikrotik.com/docs/display/ ... ckwireless

Pardon my ignorance, but my mikrotik mAP has a wireless package listed under packages. Shouldn't this be sufficient?

Sun Sep 03, 2023 6:25 pm

Did you even bother to read the info in that link ?

Compatibility
Due to storage, RAM, and architecture requirements, only the following products can replace their bundled wireless software package with wifiwave2:

hAP ac³ (non-LTE)
Audience and Audience LTE6 kit
RB4011iGS+5HacQ2HnD*
* The 2.4GHz wireless interface on the RB4011iGS+5HacQ2HnD is not compatible with the wifiwave2 package. It will not be usable with the package installed.

mcdebugger · Tue Nov 28, 2023 10:49 pm

Seems like everything will change with RouterOS v7.13

Wireless goes to be separate package, WiFi menu will get bundled, new wifi drivers will be split into 2 packages: wifi-qcom-ac (for ac devices), wifi-qcom (for ax).

See WiFi at RouterOS Documentation

Tue Nov 28, 2023 11:20 pm

Already tested on ac2 and cap ac, it works just fine !

killersoft · Tue Dec 05, 2023 10:49 pm

tested WPA3 on a cAP AC on 7.13rc2 and it works

anav · Tue Dec 05, 2023 11:28 pm

Now lets get real and work on WIFI -7, that is where the meat is on the wifi BONE.

anuser · Sat Dec 16, 2023 9:51 am

Nice, finally vendor's chipset drivers for cAP ac. So the 128 MB RAM of the cAP ac is no longer a problem?

Sat Dec 16, 2023 9:53 am

RAM never has been the real problem (at least not the most stringent).
Flash storage always has been.

robtor · Fri Dec 22, 2023 2:23 pm

I can also state that it now works like a charm on the cAP ac2

infabo · Sat Dec 23, 2023 4:23 pm

excellent summary, pe1chl

I appreciate your honesty.