v7.13beta [testing] is released!

@Strods, @ Normis
Lost features:

  • VLAN configuration in the wireless settings (Per-interface VLANs can be configured in bridge settings)
    Could you please explain what this exactly means?
    What is the right way with AC-devices to configure VLANs in the CAPsMAN V3?
    Could you please explain what exactly this means?
    My wAP AC (compatible version) shows an error in my CAPsMAN V3 (for the AX and AC devices), that VLANs on the AC-device couldn’t be configured.
    What is the right way to do it?
    Thanks a lot!!:wink:

“Default VLAN ID to assign to client devices connecting to this interface (only relevant to interfaces in AP mode).
When a client is assigned a VLAN ID, traffic coming from the client is automatically tagged with the ID and only packets tagged with with this ID are forwarded to the client.
Default: none
802.11n/ac interfaces do not support this type of VLAN tagging under the wifiwave2 package, but they can be configured as VLAN access ports in bridge settings.”

This means to me that I can only have one VLAN per WLAN Interface ? I hope, that limitation will not stay for long. I was so happy until now for the life extension for my CAP ACs, but this is a huge limitation.

I decided to test the new build. Installed on wap ac.
after installation - routeros-7.13beta1-arm I reset to defconf


From manual:
“wifiwave2” package has been divided into distinct packages: “wifi-qcom” and “wifi-qcom-ac”

After it installed
“wifi-qcom-ac-7.13beta1-arm”
I see a interfaces wifi-2.4 and wifi-5

I don’t understand.

i think that
wifi-qcom-7.13beta1-arm - for 2.4hz
wifi-qcom-ac-7.13beta1-arm - for 5hz
wireless-7.13beta1-arm - old drivers

Please describe the differences between the packages. Why AC contains 2.4

Thank you very much, this is amazing. While I can work around the VLAN limitation on ac devices, I hope this limitation can be removed in later releases.

Thanks to the wifi changes and IPv6 fixes, it may now finally be worth upgrading all my old devices from ROS 6 long-term to ROS 7.

@evbocharov: the “qcom-ac” driver is for qcom ac devices, but not limited to ac interfaces. The qcom non-ac driver is for ax devices.

Indeed, that is not good! In my current network (still running classic wireless) I have all devices on a single SSID and I assign the VLAN for several categories of devices via user-manager.
While that is somewhat of a specialty for WPA2-PSK (using MAC), it is standard practice to do with WPA2-EAP, and it certainly should be supported.
(other manufacturers support this for WPA2-EAP and even for WPA2-PPSK so I cannot believe it is a limitation of the hardware)

Chateau LTE6. Missing wireless driver package, please install it to use built-in wireless properly. Ac package.

Upgraded my RB5009 (CAPsMAN), hAP ax3 (CAP) and hAP ac3 (CAP) from 7.12rc5 to 7.13beta1 using the “check for updates” and everything went fine.

RB5009 had wifiwave2 package before, now it only has routeros (since WiFi menu + CAPsMAN feature is now bundled).

hAP ax3 had wifiwave2 package before, now it has wifi-qcom.

hAP ac3 had wifiwave2 package before, now it has wifi-qcom-ac.

I think a lot of the confusion and difficulty with packages could be solved when the /system/package window is extended with a tab that shows all available but currently not installed packages, and a button to download them for installation at next reboot.
This should be easy to do (at least in any configuration where “check for updates” is working) because all packages are available from the update server.
Much more convenient than having to download a zip file, extract package, and upload to the router… of course that method can remain available for routers that aren’t connected to internet.

Quick test of hap ac² (256MB RAM version) with wifi-qcom-ac driver.

  • AP: Performance is great, download speed on ac clients is similar to the same client on hap ax². The only real issue is the lack of VLAN tagging without bridge filtering.
  • Station: With the legacy driver I could set country to “etsi 5.7-5.8 srd” which allowed connecting to 5 GHz Android hotspots on channel 149. This etsi setting is no longer available in the new driver and selecting my real country does not include SRD frequencies (although it should). Is there any way around this limitation other than selecting a non-valid country?

Edit:

Looks like you can hack around this by creating vlan interfaces on top of your main bridge interface and joining them to your wifi interfaces via additional local bridges. These kind of legacy setups are deprecated and may cause issues with STP, but this way you can keep doing hw accelerated vlan filtering on the switch chip and have your wifi traffic tagged anyway.

chr.PNG
.
chr … for oracle or azure ? … ?

or outsourcing your ROS-scripts to this babe … ?!
.
bare-metal.PNG

[quote=wfburton post_id=1036179 time=1699999721 user_id=215408]
[quote=osc86 post_id=1035735 time=1699897103 user_id=106192]
+1, it’s a mess currently

2023-11-13 at 18.41.17.png
[/quote]
Yes please make wifi a wperate package. My mikrotik router doesn’t supoort wifi!

CRS309-1G-8S+
[/quote]

It may not have wifi interface… but it still support being a CAPsMAN2 controller…so it appears just like <least favorite> routing protocol you’re not using…



You shouldn’t get a the “messy” duplicate Wi-Fi and Wireless in menu in your case.

Can somebody please post a working config with wifi-qcom-ac managed by CAPSMAN and working VLAN? I tried manually enabling bridge VLAN filtering, assign correct PVID and create VLAN entry for tagged/untagged traffic but it doesn’t work (says password incorrect but the same config works on the hap ax2).

Seeing multiple crashes on my RB5009 within the first 24 hours, which utilises BGP/OSPF/VRRP and was also testing out the ‘wifi’ capsman control.
Was no indication of the cause after reboot but I’ve shot a supout off in a ticket.

‘AMPERA’ = 400G ?

Both CAPsMAN systems can work at the same time. Yes, they use the same port, but they differ the “call” from CAP and recognise which one must manage the CAP. Common mistake might be that old CAPsMAN is trying to generate certificate on a system where WiFi CAPsMAN was already made on older version. That is why in this release, WiFi CAPsMAN has a different name for generated certificates. If both CAPsMAN systems are not working at the same time, then check “/certificates” menu and see if there are certificates for both managers. If not, then remove them, disable/enable both managers, and see how it goes. If it is still not working, as always, bugs are not fixed in user forum - write to support@mikrotik.com and send in supout file.

About “many” menus. In the past, you had menus - CAPsMAN and Wireless. Always. If you added wifiwave2 package, then you also had the third menu for wireless. Now in “worst” case scenario you have two menus (less than before) - wireless and wifi. Of course, each of these feature sets must be under different menus because they are unrelated and have different purposes. Wifi is and will always be there because it is part of the bundle and is becoming new standard for new products. For old ones (legacy), you will see two menus. Consider this as an extra feature. You can now on old legacy wireless router run its own wireless and, if you want, can run CAPsMAN for wifi devices at the same time. If you do not like it, then as suggested above, you can hide it with skins functionality.

*) bridge - added automatic “path-cost” values depending on interface rate;

For flappy interfaces, and/or Wireless, what are the implications of this?


*) bridge - added bridge interface property “port-cost-mode” with “short” and “long” arguments;

The only reference i found to this is in the CRS3xx-specific manual
Was this previously restricted to CRS3xx, and is now a routerOS-wide feature?


*) qos-hw - added initial congestion avoidance support for 98DX224S, 98DX226S, and 98DX3236 switch chips (CLI only);

I see in a CRS318P-16G-2S+:


/interface ethernet switch qos tx-manager queue
set *1 schedule=low-priority-group weight=1
set *2 schedule=low-priority-group weight=2
set *3 schedule=low-priority-group weight=3
set *4 schedule=high-priority-group use-shared-buffers=yes weight=3
set *5 schedule=high-priority-group use-shared-buffers=yes weight=4
set *6 schedule=high-priority-group use-shared-buffers=yes weight=5
set *7 use-shared-buffers=yes
set *8 use-shared-buffers=yes

are there changes in forwarding, compared to past behavior?
shouldn’t never-configured-before keys be hidden in the implicit configuration?
(i.e, not visible in /export without verbose)


*) system - added “rtrace” debugging tool (CLI only);

Is this a IP/routing thing, or a linux stack/trace thing?


*) webfig - allow to display comments in multiline or compact modes;

Since we’re in the mood for both console-related improvements, and comment-related imporvements:
can we get /xxx print comments=inline CLI option?
sometimes on big prints, even using proplist=“” to narrow down paramenters, comments break formatting and readability


*) wifi - added “flat-snoop” tool for surveying WiFi APs and stations (CLI only);

docs? how does this differ from “/interface/wireless/scan” ?

yes, because RB5009 does not have wifi card inside, but it can be capsman. So no driver package, but has wifi menu.
hAP devices have wifi cards, so they also in addition have driver packages for those wifi interfaces

no, only one driver for your wifi interface is needed. wireless-qcom is for AX devices, you have a AC model