Why not ?Well, true enough. Unless the router is behind CGNAT...
What are you doing with a beta version on enterprise environment then ??Dear MT,
Can u check this issue please.
So many people using your hardware as enterprise things not just a home things
In previous versions Winbox showed possibility for 20/40/80/160 as channel width on AX2 and AX3.What settings do you want me to show, happy to help!
I NEVER would do such a thing@holvoetn: I can just imagine you reading the following resolution thinking... I told you so.
Sorry to burst your bubble but this is about wAP AC arm version...Wait what? wAP ac is mipsbe with AR9300, but the wifi-qcom-package works on it?
That's pretty cool!
Actually, since 7.12 it is.and also station-bridge is not supported on wifiwave2
Probably not enough space for the new wifi package ?Not realy sure if i became stupid or i don't understand something.
... What am i doing wrong?
If i upload old Wireless package back again, it installs normaly and i can see my Wifi interfaces.
If your provisioning rules are specific enough so it ends up only using AX, yes you need new rules for AC.Yes, I now see the CAP in CAPSMAN but for some reason the configuration isn't applied. Do I need to define separate configuration for AC and AX?
As a rule of thumb, the package is compatible with 802.11ac producs, which have an ARM CPU.
Because it is ROS, not WIndows, not Linux, not OS2, ...Why isn't there a way like "dir /s" in Windows to easily check what's taking up space in memory - and do that via the console?