v7.13beta [testing] is released!

Mon Nov 13, 2023 4:22 pm

RouterOS version 7.13beta has been released on the "v7 testing" channel!

Before an upgrade:
1) Remember to make backup/export files before an upgrade and save them on another storage device;
2) Make sure the device will not lose power during upgrade process;
3) Device has enough free storage space for all RouterOS packages to be downloaded.

Notice - Starting from RouterOS version 7.13, significant changes have been made to the RouterOS wireless packages. This is done due to a new product development which will require more disk space for hardware drivers so we had to split it in order to maintain old products alongside the new ones. More wireless packages are yet to come.

1. When upgrading by using "check-for-updates", all versions earlier than 7.12 will display 7.12 as the latest available version. Upgrade from v7.12 to v7.13 or later versions must be done through 7.12 in order to convert wireless packages automatically. Fresh installation with Netinstall or manual package installation works in the same manner as always.

2. Drivers for older wireless and 60GHz interfaces, as well as the wireless management system CAPsMAN, are now part of a separate "wireless" package instead of being a part of the bundle package. This package can be uninstalled if not needed.

3. The existing "wifiwave2" package has been divided into distinct packages: "wifi-qcom" and "wifi-qcom-ac", and the necessary utilities for WiFi management are now included in the RouterOS bundle. RouterOS and "wifi-qcom-ac" packages alongside each other now fit into 16MB flash memory.

What's new in 7.13beta3 (2023-Nov-24 13:52):

*) bridge - added automatic "path-cost" values depending on interface rate;
*) bridge - fixed HW offload enable with multiple switches (introduced in v7.13beta1);
*) bridge - improved HW offload enable;
*) certificate - fixed CRL check (introduced in v7.13beta1);
*) certificate - fixed host certificate verification if host is IP address (introduced in v7.13beta1);
*) certificate - fixed manual URL addition for CRL (introduced in v7.13beta2);
*) certificate - improved CRL signature verification and download error messages;
*) certificate - use error topic for CRL update failures;
*) console - added "read" command under "file" menu;
*) console - added unset option for "ssid-regex" and "allow-signal-out-of-range" properties under "interface/wifi/access-list" menu;
*) console - fixed misaligned columns (introduced in v7.13beta1);
*) console - improved stability when removing script;
*) defconf - fixed bogus wifi password on certain Audience devices;
*) defconf - use "WISP Bridge" default configuration mode for RBGrooveGA-52HPacn device;
*) fetch - added "http-auth-scheme" parameter, allows to select HTTP basic or digest authentication;
*) fetch - added raw logging;
*) ospf - fixed LSA Type3 advertisement for OSPFv2;
*) qos-hw - added initial congestion avoidance support for 98DX224S, 98DX226S, and 98DX3236 switch chips (CLI only);
*) qsfp - fixed supported rates for breakout cables (introduced in v7.12);
*) sfp - added "1G-baseT" link mode for modules that supports "2.5G-baseT" mode;
*) sfp - allow 2.5G rates only in forced link mode;
*) sfp - fixed SFP and combo interface handling for CRS328-4C-20S-4S+ device (introduced in 7.13beta1);
*) sfp - ignore "rx-loss" in forced link mode;
*) sfp - ignore irrelevant extended compliance code for SFP modules;
*) sfp - show 10M and 100M supported rates for RJ45 copper modules;
*) ssh - added cipher and hash function acceleration for ARM64 and x86 architectures;
*) supout - include missing wireless information (introduced in v7.13beta1);
*) wifi - enable protected interworking ANQP responses;
*) wifi-qcom - added fast-path for received packets;
*) winbox - fixed memory allocation (introduced in v7.13beta2);

What's new in 7.13beta2 (2023-Nov-14 13:04):

*) bridge - fixed missing "S" flag after configuration changes (introduced in v7.13beta1);
*) certificate - added HTTP redirect support for CRL download;
*) certificate - added support for certificates with key size 16384;
*) console - added ":grep" command;
*) console - added "interface" name when printing "interface/pppoe-server" entries;
*) console - fixed missing escaped characters when using print in certain menus (introduced in v7.13beta1);
*) disk - fixed hang on reboot when network file systems mounted;
*) lora - added CUPs protocol support;
*) lte - disabled IMS service for Chateau 5G on A1 HR network;
*) ppc - fixed RouterOS bootup (introduced in v7.12);
*) route-filter - improved performance;
*) supout - added multiple WiFi sections;
*) wifi - improved system stability when using sniffer (introduced in v7.13beta1);
*) winbox - improved connection speed;

What's new in 7.13beta1 (2023-Nov-09 13:15):

!) package - convert "wireless" and "wifi" packages automatically, if upgrading from v7.12;
!) wifi - split existing "wifiwave2" package into separate packages "wifi-qcom", "wifi-qcom-ac", and include required utilities for WiFi management into bundle;
!) wireless - separate "wireless" package from bundle and build as a standalone package;
*) bridge - added automatic "path-cost" values depending on interface rate;
*) bridge - added bridge interface property "port-cost-mode" with "short" and "long" arguments;
*) bridge - fixed bogus VLAN entries from wifi when vlan-filtering is not enabled;
*) bridge - improved host flush when removing VLAN on HW offloaded bridge;
*) bth - added "VPN Prefer Relay Code" option;
*) certificate - add support for multiple DNS names for Let's Encrypt;
*) certificate - fixed certificate auto renewal via SCEP when certificate contains "subject-alt-name";
*) certificate - improved initial certificate creation using SCEP;
*) cloud - improved re-connect speed after network related connection errors;
*) console - added ":grep" command;
*) console - added ":onerror" command;
*) console - added ":serialize" and ":deserialize" commands for converting values to/from JSON;
*) console - added "read" command under "file" menu;
*) console - added "where" functionality for "export" command;
*) console - added flags to "print" command with "value-list";
*) console - added interface helper for "gateway" property under "ip/route" menu;
*) console - clear console history when resetting configuration;
*) console - disallow setting existing "name" under "system/script" and "system/scheduler" menus;
*) console - fixed "export" boolean arguments when saving output to file using API;
*) console - fixed "interface/ethernet/switch/port-isolation" export;
*) console - fixed "on-event" argument highlighting under "system/scheduler" menu;
*) console - fixed graphic distortions in WinBox;
*) console - fixed issue where API incorrectly asks for missing arguments;
*) console - fixed printing of "on-event" under "system/scheduler" menu;
*) console - fixed printing to file using API;
*) console - ignore negative values for ":delay" command;
*) console - improved flag printing in certain menus;
*) console - improved stability when running "tool/ping" from API;
*) console - removed "route-cache" setting from "ip/settings" menu;
*) console - replace reserved characters in file and script names with underscores;
*) console - resolve "wifiwave2" directory to "wifi";
*) console - show "l2vpn-link" address family under "routing/route" menu;
*) console - use more compact login screen for empty branding;
*) defconf - expire password when reverting configuration;
*) defconf - hide default configuration for users without "sensitive" policy;
*) defconf - updated configuration with new "wifi" directory;
*) defconf - use "fan-min-speed-percent=25" for CRS354-48P-4S+2Q+ device;
*) defconf - use device factory preset credentials when using CAPs mode;
*) defconf - use one SSID and enable FT when using "wifi" packages;
*) ethernet - improved packet CPU core classifier for Alpine CPUs for non IPv4/IPv6 traffic;
*) fetch - added "http-content-encoding" setting;
*) fetch - allow to receive HTTP response headers;
*) fetch - require "ftp" user policy;
*) firewall - added "nat-pmp" support;
*) firewall - added new IPv6 filter arguments "icmp-err-src-routing-header" and "icmp-headers-too-long" for "reject-with" setting;
*) firewall - do not mark all IPv6 GRE packets as invalid;
*) firewall - fixed altered address-list when upgrading from RouterOS v6;
*) firewall - fixed connections being tracked when tracking is disabled;
*) firewall - fixed IPv6 address-list timeout;
*) firewall - removed "prohibited" and "unreachable" IPv4 address-type arguments;
*) health - dynamically add and remove invalid sensors (e.g. sfp-temperature);
*) hotspot - fixed incorrect host moving to VLAN 0 when receiving packets through bridge;
*) ike2 - fixed ike2 double reply;
*) ipv6 - do not send out IPv6 RA deprecate message for re-used prefix;
*) isis - added IS-IS protocol support (CLI only);
*) l3hw - fixed routing for IPsec encapsulated packets;
*) leds - fixed LED indication in multi-APN setup for Chateau;
*) leds - improved LED indication during modem registration state for Chateau;
*) log - added "fetch" topic;
*) lora - fixed issue with lost LoRa configuration when rebooting the device;
*) lte - added RNDIS support for neoway N75-EA modem;
*) lte - added support for FOTA firmware upgrade from custom URL for R11eL-FG621-EA;
*) lte - disabled IMS service for Chateau 5G on A1 HR network;
*) lte - fixed rare cases where Chateau 5G in passthrough mode may stop forwarding packets;
*) lte - improved SIM slot status change notification handling for MBIM modems;
*) lte - replaced "passthrough-subnet-selection" with "passthrough-subnet-size" setting (CLI only);
*) lte - show each CA band in a new line;
*) mipsbe - improved system stability when removing USB devices;
*) mmips - properly mount and unmount USB devices;
*) modem - added option to read SMS using MBIM interface;
*) mpls - added "te-tunnel" property for VPLS monitor (CLI only);
*) mpls - fixed IPv6 RSVP-TE;
*) mpls - improved logging;
*) netinstall-cli - added more details to help messages;
*) ovpn - improved memory allocation during key-renegotiation;
*) ovpn - removed "ping-timer-rem" option from client config file;
*) package - added warning log about missing "wireless" or "wifi" package;
*) pimsm - improved elected BSR change;
*) poe-out - improved firmware upgrade stability for AF/AT controlled boards;
*) ppp - added remote-ipv6-prefix to IPv6 firewall address-list if "address-list" property is provided;
*) ppp - allow at-chat and info commands in "waiting for packets" state for modems with shared data/info channel;
*) ppp - improved IPv6 link-local address uniqueness;
*) pppoe-server - fixed connection count limit per license level;
*) profiler - improved "disk" and "supout.rif" classifiers;
*) qos-hw - added initial congestion avoidance support for 98DX224S, 98DX226S, and 98DX3236 switch chips (CLI only);
*) qsfp - added support for QSFP-to-SFP adapters;
*) quickset - show DDNS name as VPN address for devices with new style serial number;
*) sfp - improved link establishment with certain modules for hEX S device;
*) sfp - improved SFP interface handling for 98DX224S, 98DX226S, 98DX3236, 98DX8208, and 98DX8216 switch chips;
*) ssh - fix error that caused large chunks of text not being pasted in their entirety into console;
*) supout - added VXLAN FDB section;
*) switch - fixed service VLAN tagged IP multicast packets for 98DX8208, 98DX8216, 98DX8212, 98DX8332, 98DX3257, 98DX4310, 98DX8525, 98DX3255 switches;
*) system - added "rtrace" debugging tool (CLI only);
*) traffic-generator - improved system stability when modifying interfaces;
*) usb - added support for RTL8152 USB ethernet on ARM, ARM64 and x86;
*) vpls - improved performance when decapsulating data;
*) vrf - fixed ICMP reply lookup;
*) webfig - allow to display comments in multiline or compact modes;
*) webfig - make table headers always visible;
*) webfig - use local storage for user preferences;
*) wifi - added "flat-snoop" tool for surveying WiFi APs and stations (CLI only);
*) wifi - added "remove" command in "capsman/remote-cap" menu;
*) wifi - after radar detections, avoid selection of channels not permitted by the user;
*) wifi - changed CAPsMAN generated certificate common name;
*) wifi - fixed EAP authentication failures when the Session-Timout RADIUS attribute is defined;
*) wifi - fixed occasional failures to start on 20/40mhz-eC channels for 2.4GHz 802.11ax interfaces;
*) wifi - fixed overridden datapath settings on CAP when unsetting from CAPsMAN;
*) wifi - make slave APs use datapath bridge settings inherited from master by default;
*) wifi - removed "openflow-switch" setting;
*) winbox - added "Hw. Offload" property under "IP/Firewall/Filter" menu;
*) winbox - added "none" argument for "Preshared Key" under "WireGuard/Peers" menu;
*) winbox - added "Ping" button under "IP/DHCP Server/Leases" menu;
*) winbox - added "Tx bps" and "Rx bps" monitor values under "WiFi/Registration" menu;
*) winbox - added icon to entries under "WiFi/Access List" menu;
*) winbox - added missing "qos-classifier" argument for "Hw. Caps" under "WiFi/Radios" menu;
*) winbox - added missing arguments for "MAC Format" under "Wireless/Security Profiles/RADIUS" menu;
*) winbox - allow opening entries under "WiFi/Registration" menu;
*) winbox - fixed default "Name Format" property under "WiFi/Provisioning" menu;
*) winbox - fixed minor typo under "Routing/BFD" menu;
*) winbox - updated "wireless" and "wifi" menus;
*) wireless - fixed "wlan1" default name for RBSXTsqG-5acD and RBLDFG-5acD;
*) wireless - fixed snooper information gathering from re-assocation requests;

To upgrade, click "Check for updates" at /system package in your RouterOS configuration interface, or head to our download page: http://www.mikrotik.com/download

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while a router is not working as suspected or after some problem has appeared on the device

Please keep this forum topic strictly related to this particular RouterOS release.

Mon Nov 13, 2023 4:22 pm

See the updated user manual about WiFi:
https://help.mikrotik.com/docs/display/ROS/WiFi

mantouboji · Mon Nov 13, 2023 4:35 pm

still no ed25519 private key for ssh?

Mon Nov 13, 2023 4:37 pm

WHATTTT ??

Wifiwave2 compatibility for AC2, cap AC, cap XL AC, ... ???
Do I understand that correctly ?

Or is it only bringing everything in one menu structure ? Old and new wifi remain incompatible ?
Please ? Let it be the first option ...

Mon Nov 13, 2023 4:41 pm

Yes, WPA3 on AC devices, etc. Also old and new type of CAPsMAN can be managed on the same router. Not as a unified mechanism, but two separate and parallel systems on the same router.

Mon Nov 13, 2023 4:43 pm

Xmas is early this year

Mon Nov 13, 2023 4:48 pm

Just a tip for you all: To make the upgrade less confusing and more smooth, use check-for-updates from 7.12

nonolk · Mon Nov 13, 2023 4:48 pm

Champagne, I was going to replace my CapXl, to have only wifiwave2, but I'm now able to use wifiwave2 driver, thank you.

Mon Nov 13, 2023 4:57 pm

OMFG!!!! I had to check it out before believing - 5009 as wifi capsman, 2x cap ax and now 3x wap ac, all in the same capsman - FINALLLY!!!
working without issues, had to manually uninstall old wireless package after check for upgrade.

DanMos79 · Mon Nov 13, 2023 5:09 pm

What about the possibility of using the WifiWave2 driver on the RB4011iGS+5HacQ2HnD-IN without losing the 2.4 GHz WiFi?
Or is there an alternative to exchange the built-in 2.4 GHz card to ensure compatibility?

Mon Nov 13, 2023 5:12 pm

Unfortunately, it is not possible. If you need both - use wireless.npk. If you are satisfied with using just 5 GHz, then wifi-qcom-ac will work for you. Functionality in wifi (old wifiwave2) that has been changed is described in the changelog. Still, wifi package does not include drivers for RB4011 2 GHz wifi.

pcunite · Mon Nov 13, 2023 5:12 pm

Thank you for staying in the wireless game. Keep moving forward.

Mon Nov 13, 2023 5:18 pm

By the way, if someone decides to upgrade to beta and then wants to downgrade back to, for example, 7.12. You can execute "uninstall" command for wifi or wireless packages and run check-for-updates with ignore-missing parameter. Bundle to bundle downgrade will still work or downgrade for any other packages besides wireless/wifi. Of course, do not do this on AX devices or AC devices using wifi-qcom-ac package without preparing. After such downgrade, wireless will not work. For these routers, for downgrade, you will need to schedule uninstall for new wifi packages and then download 7.12 wifiwave2 package and bundle package manually. Then execute "/system package downgrade". Scheduled uninstall and downgrade will happen on the same reboot.

Here is an example:

/system package uninstall wifi-qcom
/tool/fetch  url="https://upgrade.mikrotik.com/routeros/7.12/wifiwave2-7.12-arm.npk"
/tool/fetch  url="https://upgrade.mikrotik.com/routeros/7.12/routeros-7.12-arm.npk"
/system package downgrade

Simonej · Mon Nov 13, 2023 5:25 pm

- I believe @DanMos79 is asking for an alternative DIY wireless card compatible with WifiWave2 drivers for RB4011, if available in the market.
- Just a confirmation, if I update from 7.12 to 7.13 an hAP ac2 with old Wireless driver, will have the new "wireless-7.13...-arm" package installed, not "wifi-qcom-ac-7.13...-arm", right?
- Also noticed that if anyone has scripts for devices configuration, /interface/wifiwave2 is now /interface/wifi
- No changes on support for VLAN tagging on 802.11ac chipsets?

Now it's time for an integrated multicast repeater (like Avahi) :)

blacksnow · Mon Nov 13, 2023 5:25 pm

First off, wonderful job on these updates!

A couple of questions and maybe minor reports. For the following "webfig - use local storage for user preferences;" I see this working but in some cases there are some wierd things happening.

1) Under the IP/Firewall tab, resizing the comments tab makes the # tab to the size that you set for comments the next time you revist the page. And trying to resize the # tab will work in the moment but then goes back to it's previous state after reloading the page.

2) In some cases making changes to tab sizes, ordering etc doesn't take effect if you make the change and then leave the page. However if you make the change and then log out it seems the setting is saved (generally).

Mon Nov 13, 2023 5:29 pm

Yes, these devices will install wireless package automatically and will also be shipped from the factory with wireless package. You can install wifi-qcom-ac package manually.

- I believe @DanMos79 is asking for an alternative DIY wireless card compatible with WifiWave2 drivers for RB4011, if available in the market.
- Just a confirmation, if I update from 7.12 to 7.13 an hAP ac2 with old Wireless driver, will have the new "wireless-7.13...-arm" package installed, not "wifi-qcom-ac-7.13...-arm", right?
- Also noticed that if anyone has scripts for devices configuration, /interface/wifiwave2 is now /interface/wifi

spippan · Mon Nov 13, 2023 5:29 pm

impressive and useful console additions. thanks
also the little added option to ping right away from the DHCP leases menu is a welcome addition.

Ullinator · Mon Nov 13, 2023 5:41 pm

I´ve updated my wAP AC with the wifi-qcom-ac package and the main ROS 7.13Beta1 package.
All went smooth and the change to my CAPsMAN-AX also went well.
But I get some strange error messages in the CAPsMAN AX for the AC-device:

hc_070.jpg

Is it required to update the CAPsMAN AX to 7.13 Beta1 also to make it work?

elbob2002 · Mon Nov 13, 2023 5:44 pm

I´ve updated my wAP AC with the wifi-qcom-ac package and the main ROS 7.13Beta1 package.
All went smooth and the change to my CAPsMAN-AX also went well.
But I get some strange error messages in the CAPsMAN AX for the AC-device:
Is it required to update the CAPsMAN AX to 7.13 Beta1 also to make it work?

Documentation states this:

Nstreme and Nv2 wireless protocols
VLAN configuration in the wireless settings (Per-interface VLANs can be configured in bridge settings)
Compatibility with station-bridging as implemented in the 'wireless' package

https://help.mikrotik.com/docs/display/ ... stfeatures

I think you might have omitted the new VLAN configuration.

tim427 · Mon Nov 13, 2023 5:47 pm

I still see some strange behaviour in the SNMP-BGP;

`bgp` as defined at https://oidref.com/1.3.6.1.2.1.15
Is missing the following properties;

`bgpLocalAs` (https://oidref.com/1.3.6.1.2.1.15.2)
`bgpIdentifier` (https://oidref.com/1.3.6.1.2.1.15.4)
`bgpPeerInUpdateElapsedTime` (https://oidref.com/1.3.6.1.2.1.15.3.1.24)

Also incorrect values are presented, and not updated over time;

`bgpPeerFsmEstablishedTime` (https://oidref.com/1.3.6.1.2.1.15.3.1.16); this one should indicate how long (in seconds) this peer has been in the Established state or how long since this peer was last in the Established state.

These values aren't updated over time, nor after a reboot (and therefore a new Established) and completely inaccurate!

After a reboot, all the BGP-sessions are established at almost the same timestamp (+/- 10 minutes ago), side-by-side the output of snmpwalk '.1.3.6.1.2.1.15.3.1.16' is shown. 10 minutes should result in 600 seconds, these values are far off and quite random;

snm_screenshot.png

Mon Nov 13, 2023 5:51 pm

Please keep this and other version topics related to the particular version. Issues that were present in older versions should be reported to support@mikrotik.com and/or discussed in separate forum threads. These forum topics are created in order to find "what got broken". There is no need to repeat the same reports on every release, even though any relevant fixes or changes are not listed in the changelog.

alibloke · Mon Nov 13, 2023 5:59 pm

I tried to upgrade my rb5009 from 7.12 to 7.13beta1 but I get the following error:

/system/package/update> install 
            channel: testing
  installed-version: 7.12
     latest-version: 7.13beta1
             status: wifi-qcom-ac-7.13beta1-arm64.npk missing, use ignore-missing or disable package(s)

seriosha · Mon Nov 13, 2023 6:14 pm

FC:AB:90:E7:AE:VB@wifi2 roamed to FC:AB:90:E7:AE:VB@wifi1, signal strength -66
Well, it's works ok.
Updated Hap ac2.

Ullinator · Mon Nov 13, 2023 6:27 pm

I´ve updated my wAP AC with the wifi-qcom-ac package and the main ROS 7.13Beta1 package.
All went smooth and the change to my CAPsMAN-AX also went well.
But I get some strange error messages in the CAPsMAN AX for the AC-device:
Is it required to update the CAPsMAN AX to 7.13 Beta1 also to make it work?

Documentation states this:

Nstreme and Nv2 wireless protocols
VLAN configuration in the wireless settings (Per-interface VLANs can be configured in bridge settings)
Compatibility with station-bridging as implemented in the 'wireless' package
https://help.mikrotik.com/docs/display/ ... stfeatures

I think you might have omitted the new VLAN configuration.

Thanks for the reply, but I don´t understand what that exactly means? Maybe you can explain?
All VLANS are configured in the CAPsMAN only via "Configuration -> Datapath" and it seems to work:

hc_074.jpg

It´s working with all my CAP AX devices in the same manner (all 7.12). Actually it looks like a "cosmetic" error only.....but I will test the VLAN functionallity on the AC device later.....

osc86 · Mon Nov 13, 2023 6:29 pm

I don't think it's a good idea to automatically install wireless package on chr. Having multiple WiFi / Wireless menus in winbox after installing the wireless package is extremely confusing.

Amm0 · Mon Nov 13, 2023 6:36 pm

Very impressive! Upgrade worked on my RB1100AHx4-Dude test box. Looking forward to testing Wave2 support on 16MB ARMs — that was a welcome surprise – I'd given up on that long ago.

The new :serialize and :deserialize caught my eye — JSON support has been lacking for a decade and seems to work in initial testing:

{
  :local arr {a=1;b="abc"}
  :local json [:serialize $arr to=json]
  :local arrFromJson [:deserialize $json from=json]
  :put "serialized json: $json"
  :put "deserialized json:"
  :put $arrFromJson
  :put "type of deserialized json: $[:typeof $arrFromJson]"
}

But perhaps the :[de]serialize should default the to= and from= to "json". While I like the optimism for more "serializers", default values are helpful & there is just one to/from format, RN...

Mon Nov 13, 2023 6:41 pm

Now also upgrade from ARM64 routers with installed wifiwave2 package should work. Sorry for any inconvenience caused.

gigabyte091 · Mon Nov 13, 2023 6:45 pm

Tested with RB5009, AX3, cAP ax. Everything works fine for now. This is quite a large number of changes, good work guys.

Few questions, PPSK maybe ?? :D

And now on my CAPsMAN controller in WiFi menu i dont have any more that interfaces are controlled by capsman but on CAPs I have that. This is something new ?

patrick7 · Mon Nov 13, 2023 6:46 pm

Grep is nice, but please make it as a pipe argument. Like

/interface/print | grep anything

Or like "utility" on IOS XR

show run | utility egrep ....

raphaps · Mon Nov 13, 2023 6:56 pm

*) ovpn - improved memory allocation during key-renegotiation;

After over an hour of extensive testing, forcing key renegotiation every 60 seconds, I can state that the memory leak issue related to OpenVPN key renegotiation has been fixed. Thanks to the Mikrotik team and to Oskars who responded to my support ticket regarding this problem.

colinardo · Mon Nov 13, 2023 6:56 pm

New :grep command crashes console when invoking with the following pattern

:grep script="system clock print" pattern=".*"

I know this pattern does not make any practical sense here but it crashed the console repeatedly with high cpu usage. The command used doesn't matter, it happens on every command used.

screenshot.png

just4info

#edit# Bug is fixed in RouterOS 7.13beta2

mkamau · Mon Nov 13, 2023 7:05 pm

just done a lab test on the isis and so far so good, thanks mikrotik team for this

DarkNate · Mon Nov 13, 2023 7:09 pm

*) firewall - added "nat-pmp" support;

Why? NAT-PMP was already obsoleted by RFC6887. It would've made more sense to implement PCP, which is also usable in 464xlat, NAT64 and MAP-T.

ToTheFull · Mon Nov 13, 2023 7:14 pm

Thanks Guys... all working here
flat-snoop :)

ffernandes · Mon Nov 13, 2023 7:17 pm

qrt-ac with 128mb...
will have a try

bommi · Mon Nov 13, 2023 7:27 pm

still no ed25519 private key for ssh?

Already included in 7.12.

Amm0 · Mon Nov 13, 2023 7:33 pm

Grep is nice, but please make it as a pipe argument. Like
Code: Select all
/interface/print | grep anything

There is no "pipe" as it the CLI isn't a Bourne-based shell, that part is to be expected...

But I would have guess the command is:
:grep [/interface/print as-value] pattern=".*"
but that actually causes the console to CRASH — with the ".*", just using "." works without a crash.

Ignoring the ".*" crash, :grep is still pretty funky in how it work AFAIK... e.g. :grep runs a command provided and uses the terminal output from that command based on pattern=... So while this works to search the command's output, and prints the results to terminal (without a pipe needed & there is "as-array" options to use in script)
:grep "/interface/print" pattern="."

BUT... this "grep runs a command string" logic means to search a file, which you'd typically associate with `grep`, requires a :put...which is kinda strange in the current CLI scheme (but works):
:grep ":put [/file get myfile contents ]" pattern="."

Also there is a "filename=" attribute but that's for OUTPUT, which isn't entirely clear. It be nice if the was some in-file= or out-file= (not particular on names, but way to use files directly on INPUT be nice)

Anyway :grep a bit confusing, since it's neither the file-based UNIX screme... or even RouterOS script, since you'd kinda expect :grep to take RSC string to parse, not a command to exec (which in RouterOS usually require the [cmd as-value] syntax...

pe1chl · Mon Nov 13, 2023 7:35 pm

I don't think it's a good idea to automatically install wireless package on chr. Having multiple WiFi / Wireless menus in winbox after installing the wireless package is extremely confusing.

It seems what is happening here is that "wireless" was part of the "routeros" package in versions 7.x up to 7.12, and when you now upgrade to 7.13beta it doesn't bother to check if you were really using any wireless functions, and just installs the "wireless" package that has now become separate.
But you can just "uninstall" it and remove some functions.
Unfortunately not all, because "the necessary utilities for WiFi management are now included in the RouterOS bundle." as it is written in the release notes.

I welcome the partial split into separate packages as we knew it in v6, but maybe the "WiFi" menu should go into a separate "wifi" package so we can uninstall that as well.

osc86 · Mon Nov 13, 2023 7:38 pm

I welcome the partial split into separate packages as we knew it in v6, but maybe the "WiFi" menu should go into a separate "wifi" package so we can uninstall that as well.

+1, it's a mess currently

2023-11-13 at 18.41.17.png

pe1chl · Mon Nov 13, 2023 7:42 pm

But I would have guess the command is:
:grep [/interface/print as-value] pattern=".*"
but that actually causes the console to CRASH — with the ".*", just using "." works without a crash.

Ignoring the ".*" crash, :grep is still pretty funky in how it work AFAIK... e.g. :grep runs a command provided and uses the terminal output from that command based on pattern=... So while this works to search the command's output, and prints the results to terminal (without a pipe needed & there is "as-array" options to use in script)
:grep "/interface/print" pattern="."

Handling of output and redirection has always been funky... hopefully they will now sit down and fix that.

I expect any command like set $name [/some/command/print] to set the variable to the output of that command without printing that output on the console. I.e. that [...] is capturing the output and returning it for storage in the variable.
But it does not work that way, at least not for all commands and options. There are awful hacks like as-value which do not work combined with other options like count-only.
That really should be cleaned up!

Amm0 · Mon Nov 13, 2023 7:51 pm

That really should be cleaned up!

The new serialize and previous :convert fit nicely. But :grep seem askew from RouterOS CLI "philosophy" POV – e.g. everything is already key-values tables and there [:find] to search command output.

NOW... :sed for strings be way more useful than :grep. e.g. actually help with CLI's limited string manipulation today...

naxus · Mon Nov 13, 2023 7:54 pm

Upgrade on 3 hap ax2 and audience was smooth, caps man works fine as on 7.12. capsman is on hapax2.

patrick7 · Mon Nov 13, 2023 8:03 pm

There is no "pipe" as it the CLI isn't a Bourne-based shell, that part is to be expected...

That's a question of a few lines code :-)
The biggest advantage is that you can attach "| grep" to any command, which is more pleasant than surround a grep string around the command.

gigabyte091 · Mon Nov 13, 2023 8:04 pm

Is it normal that there is no more wifiwave2 tab ? Now it's called just wifi. It's on ax3

ayrsbsdu · Mon Nov 13, 2023 8:06 pm

Hello.

Please, help with questions. Which package should I install on each device if only 5 GHz is needed? 2.4GHz I don't need.
1) Capsman: CCR2004-16G-2S+ (ARM 64bit) + cAP ac (ARM);
2) Without capsman standalone hAP ac lite (MIPSBE RB952Ui-5ac2nD).Or will Wi-Fi never work on hAP ac lite (MIPSBE RB952Ui-5ac2nD) anymore?
3) New capsman support ec-certificate (prime256v1) or just rsa (2048)?

Florian · Mon Nov 13, 2023 8:10 pm

Wifiwave 2 working on hap ac2 here, well done ! Slight increase in performances, and wpa3 available, nice !

Edit : and the ipv6 deprecated addresses is fixed too.

pe1chl · Mon Nov 13, 2023 8:13 pm

There is no "pipe" as it the CLI isn't a Bourne-based shell, that part is to be expected...
That's a question of a few lines code :-)
The biggest advantage is that you can attach "| grep" to any command, which is more pleasant than surround a grep string around the command.

Yeah, that is what Cisco also did when extending their IOS that way. Although the called it "include" rather than "grep".

BrianHiggins · Mon Nov 13, 2023 8:14 pm

Unfortunately, it is not possible. If you need both - use wireless.npk. If you are satisfied with using just 5 GHz, then wifi-qcom-ac will work for you. Functionality in wifi (old wifiwave2) that has been changed is described in the changelog. Still, wifi package does not include drivers for RB4011 2 GHz wifi.

Just curious, since I think this release says both versions of wireless and wifi (formerly wave2) are now supported side by side, why can't the 2ghz radio continue to operate on the older driver and the 5ghz radio operate on the new driver? It would seem that to be the ideal balance of support & features.

disclaimer, I've not at all touched wave2/wifi driver yet, I've been letting others be the beta tester and when it's really production ready then I'll do my own testing & deployment, so maybe this answer is already obvious to some.

patrick7 · Mon Nov 13, 2023 8:16 pm

Yeah, that is what Cisco also did when extending their IOS that way. Although the called it "include" rather than "grep".

On XR, apart from include/exclude, there's "utility" which allows you to pipe through the most important linux commands:

#sh run | utility ?
cut Cut out selected fields of each line of a file
egrep Extended regular expression grep
fgrep Fixed string expression grep
head Show set of lines/characters from the top of a file
less Fixed string pattern matching
more Paging Utility More
no-more Disable Paging Utility More
script Launch a script for post processing
sign Sign the CLI output with enrolment key
sort Sort, merge, or sequence-check text files
tail Copy the last part of files
uniq Report or filter out repeated lines in a file
wc Counting lines/words/characters of a file
xargs Construct argument list(s) and invoke a program

pe1chl · Mon Nov 13, 2023 8:20 pm

Just curious, since I think this release says both versions of wireless and wifi (formerly wave2) are now supported side by side, why can't the 2ghz radio continue to operate on the older driver and the 5ghz radio operate on the new driver? It would seem that to be the ideal balance of support & features.

+1

noradtux · Mon Nov 13, 2023 8:26 pm

still no ed25519 private key for ssh?

For login? That has been added with 7.12.

ivicask · Mon Nov 13, 2023 8:37 pm

Does new wireless drivers suport QCA9556?(wap ac)?

Amm0 · Mon Nov 13, 2023 8:45 pm

On XR, apart from include/exclude, there's "utility" which allows you to pipe through the most important linux commands:

Sacrilegious! ;) I personally use RouterOS over Linux since I like everything has a schema/tables and syntax is typed and regularized. RouterOS is more "nothing is a file", than the UNIX "everything is a file". And I'm not sure Cisco IOS is a great model to follow either.

I'm with @pe1chl , fixing "print" current inconstancies would add a lot more value... RouterOS config is not file with strings where UNIX commands are more useful.

epkulse · Mon Nov 13, 2023 8:54 pm

Does new wireless drivers suport QCA9556?(wap ac)?

I have the old wap-ac (qca9550L), seems it is not supported. Wifi-interfaces can´t be setup.

JohnTRIVOLTA · Mon Nov 13, 2023 8:59 pm

Yes, WPA3 on AC devices, etc. Also old and new type of CAPsMAN can be managed on the same router. Not as a unified mechanism, but two separate and parallel systems on the same router.

Wave 2 driver for ipq4xxx ?!

Guscht · Mon Nov 13, 2023 9:04 pm

*) firewall - added "nat-pmp" support;

oh god no!! I am still recovering from nat-ein, which gave me severe depression and life-crisis...

alibloke · Mon Nov 13, 2023 9:12 pm

OMFG!!!! I had to check it out before believing - 5009 as wifi capsman, 2x cap ax and now 3x wap ac, all in the same capsman - FINALLLY!!!
working without issues, had to manually uninstall old wireless package after check for upgrade.

Do you have the new version wAPac with an arm CPU?

evbocharov · Mon Nov 13, 2023 9:23 pm

Hello. ros7.12+wifiwave2.
How to update correctly while saving the config?

Mon Nov 13, 2023 9:28 pm

Just upgrade in testing channel.

alibloke · Mon Nov 13, 2023 9:43 pm

Do devices running the new wifi-qcom-ac package still have the old wifiwave2 limitation where VLANs couldn't be configured?

Ca6ko · Mon Nov 13, 2023 9:44 pm

- I believe @DanMos79 is asking for an alternative DIY wireless card compatible with WifiWave2 drivers for RB4011, if available in the market.

Does new wireless drivers suport QCA9556?(wap ac)?

qrt-ac with 128mb...

The wifi-qcom-ac-7.13beta1-arm.npk package contains drivers for IPQ4019 and QCA9984 (4011) only

rextended · Mon Nov 13, 2023 9:49 pm

…
What's new in 7.13beta1 (2023-Nov-09 13:15):
…
…
…
…
…
…

DDDM · Mon Nov 13, 2023 9:57 pm

Unfortunately, it is not possible. If you need both - use wireless.npk. If you are satisfied with using just 5 GHz, then wifi-qcom-ac will work for you. Functionality in wifi (old wifiwave2) that has been changed is described in the changelog. Still, wifi package does not include drivers for RB4011 2 GHz wifi.

Can you tell me if this router is going to receive ability to handle future PCI AX wifi card by Mikrotik? I brought one but I'm disappointed WifiWave2 is not usable for the 2.4Ghz network. Can you give more information please ?

alibloke · Mon Nov 13, 2023 10:06 pm

Do devices running the new wifi-qcom-ac package still have the old wifiwave2 limitation where VLANs couldn't be configured?

Found it in the wiki:

802.11ac chipsets do not support this type of VLAN tagging (vlan-id), but they can be configured as VLAN access ports in bridge settings.

bommi · Mon Nov 13, 2023 10:18 pm

Do devices running the new wifi-qcom-ac package still have the old wifiwave2 limitation where VLANs couldn't be configured?
Found it in the wiki:
Code: Select all
802.11ac chipsets do not support this type of VLAN tagging (vlan-id), but they can be configured as VLAN access ports in bridge settings.

I just did the upgrade on my capsman controller and on one of my cap xl ac accesspoints.
Right now it seems that I can set one datapath config with one vlan-id for the master configuration and exactly one datapath config for all slave configurations.
In this case all slave configurations are sharing the same vlan-id.

WiesiDeluxe · Mon Nov 13, 2023 10:19 pm

Best Update this Year, thanks Mikrotik

patrick7 · Mon Nov 13, 2023 10:36 pm

I'm with @pe1chl , fixing "print" current inconstancies would add a lot more value... RouterOS config is not file with strings where UNIX commands are more useful.

So you prefer the following syntax

:grep script={/log print} pattern="a pattern"

over

/log print | grep "a pattern"

?

leonardogyn · Mon Nov 13, 2023 10:48 pm

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

THANK YOU a million times, Mikrotik Dev Team :)

wtechlink · Mon Nov 13, 2023 10:49 pm

*) firewall - added "nat-pmp" support;
oh god no!! I am still recovering from nat-ein, which gave me severe depression and life-crisis...

Why is that? I'm running carrier grade NAT on some 2216's for customers and was looking into either the nat-ein or nat-pmp to try to get customers gaming setups happy with NAT types. Just trying to find a way to not get a double NAT for gaming consoles without having to give every customer a public IP.

leonardogyn · Mon Nov 13, 2023 11:00 pm

incorrect/out of place TX/RX rates still shown on the webfig header on 7.13beta1 ...
.

TXRX.png

mkx · Mon Nov 13, 2023 11:15 pm

Do devices running the new wifi-qcom-ac package still have the old wifiwave2 limitation where VLANs couldn't be configured?
Found it in the wiki:
Code: Select all
802.11ac chipsets do not support this type of VLAN tagging (vlan-id), but they can be configured as VLAN access ports in bridge settings.

Just upgraded my hAP ac2 . The above is a bummer for me, I have VLANs configured on switch chip (under /interface/ethetnet/switch/, so bridge is clueless about VLANs. Thus my setup relies on wireless driver to deal with VLAN tags (just as legacy wireless driver does ... at least it did up to and including 7.11.2).

Mikrotik, any chance to add this feature to the new wifi-qcom-ac drivers?

On the side note: 7.12 left around 700kB of storage unused. 7.13beta1 with legacy wireless left around 400kB of storage unused. After uninstalling wireless and installing wifi-qcom-ac there's around 330kB free.
Eventually I uninstalled wifi-qcom-ac (so no wireless/wifi package installed) and there's around 3200kB storage free. (settings in /interface/wifi remained).

Amm0 · Mon Nov 13, 2023 11:19 pm

Code: Select all
:grep script={/log print} pattern="a pattern" 
over
Code: Select all
/log print | grep "a pattern"
?

actually, neither, there is already "where"...

/log print where topics~"info"

NOT trying to pick a fight. My point is there is no/limited use for a :grep as there is already regex searching... I like UNIX, but there is nothing to "pipeline" in RouterOS — most operations essentially view/modify psuedo-database tables, not files. So files-based tools don't get you much.

biomesh · Mon Nov 13, 2023 11:41 pm

Opened SUP-134289 for an issue on CCR2004-16G-2S+ where I could not communicate with any device on the gigabit ports (this includes the CCR2004 and other devices on the same vlan on different devices crs317 etc)

Revert to 7.12 and it works correctly.

maigonis · Tue Nov 14, 2023 12:01 am

Tested in lab env, standalone and capsman managed APs. Setup was simple, hexs as capsman, cap ac, hap ac2 and hap ax lite as caps. Cap ac in standalone mode pushed on avg 550mbps downstream, peaked at almost 600mbps near AP (2-3m) on wifi6 phone (Samsung S10+), 5ghz band. That's in line whit that chipset, so performance is there.

Capsman tests showed the same performance - no more throughput penalty by enabling centralized management. Rest of capsman is the same as ww2 on ax lineup, plus some new additional features, besides now ac APs can be mixed whit ax APs. They both can be managed from the same ww2 capsman and roaming whit steering, also FT, in theory works (looked at beacon info, lab is too small for me to test practially). Besides that you get WPA3, management frame protection, beam forming, etc goodies. I have to do tests whit more devices, but one of old issues was that AP could not do 2x2 downstream to some STAs, so they where limited to 1x1 and that resulted in /2 throughput.

PS: Published text seemed confusing to me, so to clear up to some who don't understand packages still. By default ac lineup (that can be upgraded to ww2) will still use the same legacy wireless driver, to use ww2 you need to install ww2 package manually.

Kentzo · Tue Nov 14, 2023 12:45 am

*) firewall - added new IPv6 filter arguments "icmp-err-src-routing-header" and "icmp-headers-too-long" for "reject-with" setting;

What are the corresponding ICMPv6 Type 1 codes, is it now like this?

0: icmp-address-unreachable
1: icmp-admin-prohibited
2: icmp-not-neighbour
3: icmp-no-route
4: icmp-port-unreachable
7: icmp-err-src-routing-header
8: icmp-headers-too-long

What about codes 5 (source address failed ingress/egress policy) and 6 (reject route to destination)?

Amm0 · Tue Nov 14, 2023 1:03 am

*) firewall - added new IPv6 filter arguments "icmp-err-src-routing-header" and "icmp-headers-too-long" for "reject-with" setting;
What about codes 5 (source address failed ingress/egress policy) and 6 (reject route to destination)?

Dunno about "code 5" (src addr policy), but code 6 is action= "reject" action already.

ffernandes · Tue Nov 14, 2023 1:11 am

too bad mipsbe doesnt have wifiwave2 support or even a better wifi drivers!!!
qrt-5-ac (RB911G-5HPacD)
netmetal5 (RB911G-5HPacD)

Kentzo · Tue Nov 14, 2023 2:18 am

Dunno about "code 5" (src addr policy), but code 6 is action= "reject" action already.

Mmm... do you mean that "action=reject" aka "action=reject reject-with=icmp-network-unreachable" sends ICMPv6 Type 1 Code 6 and not ICMPv6 Type 1 Code 0?

Either way, there are 9 codes in the RFC but only 7 possible choices. Two codes are missing.

lazywizard · Tue Nov 14, 2023 3:01 am

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

Any documentation on congestion avoidance yet? I don't see any mention of it on Quality of Service (QoS) or QoS with Switch Chip yet. Coming soon for 98DX8208/98DX8216?

nichky · Tue Nov 14, 2023 3:06 am

if i upfrade my all devices to 7.13beta , will capsaman still working fine?

gigabyte091 · Tue Nov 14, 2023 5:35 am

Capsman works fine in my case, vlans and everything

mantouboji · Tue Nov 14, 2023 5:38 am

strange in my net, sorry.

gigabyte091 · Tue Nov 14, 2023 5:44 am

I tried Wireguard now (BTH) and it's working fine, did you check the config after the update ?

nichky · Tue Nov 14, 2023 5:53 am

Capsman works fine in my case, vlans and everything

on the v7.13?

riv · Tue Nov 14, 2023 6:47 am

FINALLY!!
IS-IS is coming

loloski · Tue Nov 14, 2023 7:17 am

7.12 stable to 7.13beta1 will fail to update if zerotier package was install on hapac2

Tue Nov 14, 2023 7:51 am

Capsman works fine in my case, vlans and everything
on the v7.13?

Yes.

Tue Nov 14, 2023 7:53 am

It seems the wireguard is broken , can't connect to anywhere .

3 different ones on 1 RB5009 working just fine here.

Jotne · Tue Nov 14, 2023 8:03 am

Now that MT are working on the console commands, its also time to fix the logging (syslog) to become RFC compatible.
viewtopic.php?t=124291
https://www.rfc-editor.org/rfc/rfc5424

gigabyte091 · Tue Nov 14, 2023 8:03 am

on the v7.13?

Yes, on 7.13, works without a problem.

Tested Wireguard on hex S and it's working without a problem.

Tue Nov 14, 2023 8:08 am

Several complaints here about specific issues - Zerotier, Wireguard, etc.
but Zero tickets about that to support@mikrotik.com. Please remember that actual "bugs" must be reported to support@mikrotik.com complemented with logs, supout files, etc.

gigabyte091 · Tue Nov 14, 2023 8:16 am

hAP ax lite LTE6 7.13beta1 working without a problem (wifi, VLANs, WG, LTE)

Tue Nov 14, 2023 8:20 am

Upgrade AC2.
At first I thought wireless settings were not transferred, but then I noticed there are 2 references in the menu: wifi and wireless.
It's there under wireless /wireless (there is also wireless/capsman).
Confusing !

Tue Nov 14, 2023 8:26 am

If you install wireless and wifi packages at the same time, then of course there are two menus. You can run both of them at the same time as separate solutions on a single router. In 99% of cases you will require either wireless or wifi package and then there will be only one menu. Uninstall the package that you will not use. By the way - nothing has changed there since 7.12. Then you simply had wifiwave2 and wireless menu. Still two menus.

Tue Nov 14, 2023 8:52 am

OK, now I see. Still need to get used to the new naming style.

But I wasn't able to use the Wifi part for the radios on AC2 until I uninstalled wireless package.
And only then was I able to install qcom-ac and then I could configure radios under the new settings.
So running both on same device doesn't seem to be possible if you want to control local radios ? It's one or the other. (not that I want to do both)

Tue Nov 14, 2023 9:01 am

holvoetn. You don't need "wireless" package. Just keep the wifi package. The new WIFI features like WPA3 are only available if you use the wifi package.
Wireless package is the old one

Tue Nov 14, 2023 9:05 am

Wireless package and wifi package can be installed on a router at the same time, but one of them will be disabled. Both can not work at the same time. Have a look at the "/system package print" and see which package is active. Wifi menu is a configuration menu and does not care about extra packages. It will be present on any router.

Tue Nov 14, 2023 9:07 am

@normis:
That conclusion I made already on my previous post.

As a consequence everything needs to be reconfigured for a device where you do that replacement (and that "replacement" part is in the documentation, so that's clear).
Fully understandable reconfiguring is needed, no mistake there, but necessary to be pointed out because a lot of users will fail to make that conclusion on their own.

Tue Nov 14, 2023 9:09 am

If you install wireless and wifi packages at the same time, then of course there are two menus. You can run both of them at the same time as separate solutions on a single router.

Wireless package and wifi package can be installed on a router at the same time, but one of them will be disabled. Both can not work at the same time.

You do know you're contradicting yourself here a little bit ?
Hence my confusion.

Tue Nov 14, 2023 9:13 am

@strods or @normis:
I do have one question which is not mentioned in the docs (or not clear enough):
hAP ac^3, does that also include LTE version ?

Tue Nov 14, 2023 9:20 am

You can use both at the same time if you need to run two CAPsMANs, not if you just want to use wireless

accarda · Tue Nov 14, 2023 9:20 am

About this new WiFi, I have a question: if you have both devices, compliant with new WiFi and not AND you are currently managing everything via CAPsMAN on a router (say RB4011 non WiFi model) would you be able to run both CAPsMAN, new for wifi compatible devices and legacy v2 for those that will still have legacy wireless package ?
Or single CAPsMAN instance would be able to control both types ? (or do you need to give up on some of them?)

rolling · Tue Nov 14, 2023 9:21 am

Hi, i upgrade to 7.13b1 muy Rb751 but i not undertand the new wireless reqs.
After upgrade i've wifi and wireless, but like @normis reply @holvoetn i remove wireless package for configure wifi.
When i go configure it i can't add beacouse not detect wifi interface.
Drivers package are not in exra-packages....
What must i do?

https://picallow.com/wifi-2/

Tue Nov 14, 2023 9:22 am

Did you enable the package too? Check if it's enabled in Packages menu

rolling · Tue Nov 14, 2023 9:26 am

On packages i only have routeros package after delete wireless.
On extra packages for mipsbe only are wireless package not drivers packages....

Tue Nov 14, 2023 9:30 am

What model router do you have? Full model name

blimbach · Tue Nov 14, 2023 9:30 am

@strods or @normis

Is there any hope that the restrictions regarding the VLAN ID in dynamic interfaces will be lifted in the AC driver?

(802.11ac chipsets do not support this type of VLAN tagging , but they can be configured as VLAN access ports in bridge settings.)

I have currently solved this in my lab with "slaves-static" in my CAP properties and manual assignment of the resulting interfaces to the bridge with PVID.

However, I consider this solution to be very error-prone in larger environments, as everything has to be done manually.

Nevertheless, this release is a big step in the right direction! Thank you very much!
-Boris

rolling · Tue Nov 14, 2023 9:31 am

@normis --> RB951Ui-2HnD

https://picallow.com/wifi-2/

Tue Nov 14, 2023 9:33 am

qcom-ac package does not work on mipsbe. Only arm.

https://help.mikrotik.com/docs/display/ ... ss'package

As a rule of thumb, the package is compatible with 802.11ac producs, which have an ARM CPU.

Tue Nov 14, 2023 9:34 am

You only installed bundle on RB951?
You needed to use CHECK FOR UPDATES, see above instructions.

Or you need to manually install wireless package

new wifi package is available only on select few AC models (new ARM), not all of them. This is why you need to read the changelog and instructions in the first post

loloski · Tue Nov 14, 2023 9:35 am

In Hapac2 DOH is working fine for a few minutes then all of the sudden the configuration revert back to the original setting prior of the change, at first I thought I'm just crazy but it happen to me more than 3 times now

Guscht · Tue Nov 14, 2023 9:41 am

Just to clarify:

I am using a CCR as CAPSMAN-device and have a bunch of cAPac-devices - no wifiwave2 stuff.
If I upgrade to 7.13, I am able to use cAPax-devices under the same CAPSMAN, on the same CCR?

loloski · Tue Nov 14, 2023 9:42 am

Sorry for not filling a proper bug report don't have a good experience of doing it for some occasions now, it's either no one answer or the support claims it's a support issues I'm tired already sorry

rolling · Tue Nov 14, 2023 9:42 am

oufff thanks @holvoetn.

Yes you are right @normis, sorry.
I see two wifi and wireless options on winbox menu and it has led me to confusion.
Will it be possible to have only one option on the menu in the future?

Tue Nov 14, 2023 9:49 am

Wifi menu is included in the bundle as described in changelog. All routers will have "WifiI" menu. You can not run router without system (a.k.a. bundle) package.
If you require "legacy" wireless (either router requires 60 GHz support, legacy wireless support or you need to use old CAPsMAN for legacy devices), then you can install wireless.npk. There will be two menus on your router after that - wifi and wireless. These are not duplicates or related interfaces. Two separate functions. Wireless - CAPsMAN and general wireless menu for "old" wireless devices, WiFi menu for new style wifi management on ARM ac/ax router itself or CAPsMAN for wifi routers.

tim427 · Tue Nov 14, 2023 10:35 am

Please keep this and other version topics related to the particular version. Issues that were present in older versions should be reported to support@mikrotik.com and/or discussed in separate forum threads. These forum topics are created in order to find "what got broken". There is no need to repeat the same reports on every release, even though any relevant fixes or changes are not listed in the changelog.

Hmm, okay.. It was "broken/incomplete" during the introduction, but indeed, not introduced with this version. I'll create a new topic.

pe1chl · Tue Nov 14, 2023 11:11 am

Wifi menu is included in the bundle as described in changelog. All routers will have "WifiI" menu. You can not run router without system (a.k.a. bundle) package.

"our" suggestion was that you move the WiFi menu and associated software into a separate package as well, so that it can be uninstalled on routers where no wireless interfaces are present and the user does not want to use CAPsMAN on it either.

Tue Nov 14, 2023 11:12 am

RouterOS consists of things that many people don't use. Even in Windows you have menus you can't use.

pe1chl · Tue Nov 14, 2023 11:52 am

RouterOS consists of things that many people don't use. Even in Windows you have menus you can't use.

At least on Windows you can install and uninstall drivers for different hardware independently, so that you are not confronted with "when you install the driver for this 5 GHz radio, your 2 GHz radio will become inoperative"...

Tue Nov 14, 2023 11:57 am

How is that relevant in this situation? Nothing has been broken, upgrade is transparent. Just ignore the capsman menu, you will get used to it.

spippan · Tue Nov 14, 2023 12:55 pm

Hello.

Please, help with questions. Which package should I install on each device if only 5 GHz is needed? 2.4GHz I don't need.
1) Capsman: CCR2004-16G-2S+ (ARM 64bit) + cAP ac (ARM);
2) Without capsman standalone hAP ac lite (MIPSBE RB952Ui-5ac2nD).Or will Wi-Fi never work on hAP ac lite (MIPSBE RB952Ui-5ac2nD) anymore?
3) New capsman support ec-certificate (prime256v1) or just rsa (2048)?

if in doubt => https://help.mikrotik.com/docs/display/ ... stfeatures

short info from that link:

compatible:

Audience
Audience LTE kit
Chateau (all variants of D53)
hAP ac^2
hAP ac^3
cAP ac
cAP XL ac
LDF 5 ac
LHG XL 5 ac
LHG XL 52 ac
NetMetal ac^2
mANTBox 52 15s
wAP ac (RBwAPG-5HacD2HnD)
SXTsq 5 ac

NOT compatible:

RB4011iGS+5HacQ2HnD-IN (no support for the 2.4GHz interface)
Cube 60Pro ac (no support for 60GHz interface)
wAP ac (RBwAPG-5HacT2HnD) and 
all other devices with a MIPSBE CPU <=====

was wondering about a similar thing but no ... this locks out my old trusty RB962UiGS-5HacT2HnT too (hAP ac)

spippan · Tue Nov 14, 2023 12:57 pm

Wifi menu is included in the bundle as described in changelog. All routers will have "WifiI" menu. You can not run router without system (a.k.a. bundle) package.
"our" suggestion was that you move the WiFi menu and associated software into a separate package as well, so that it can be uninstalled on routers where no wireless interfaces are present and the user does not want to use CAPsMAN on it either.

loved the ROS v6 MODULARITY where one could disable and even better, uninstall unused parts.

@normis
any chance getting this back to v7?

zandhaas · Tue Nov 14, 2023 1:01 pm

Hi all,

I'm a bit confused.

I have a HAPac2 and I need both the 2.4GHz and 5 GHz.

What is the way to go for me?

Do I need the qcom-ac and the wireless package or?????

Tue Nov 14, 2023 1:03 pm

zandhaas use check for updates button and ignore the above ranting. nothing special has to be done. upgrade and forget

Tue Nov 14, 2023 1:08 pm

I have a HAPac2 and I need both the 2.4GHz and 5 GHz.
What is the way to go for me?

All of our products based on IPQ4018/4019 chips use the same driver for 2.4GHz and 5GHz interfaces.
If your device is listed as 'compatible' here https://help.mikrotik.com/docs/display/ ... patibility then all wifi interfaces will work with wifi-qcom-ac.

Also, the wifi-qcom-ac package is incompatible with the 'wireless' package. You can't have both installed at the same time.

YO3IPT · Tue Nov 14, 2023 1:30 pm

Good afternoon,

Wonderful news about wave2 support on hAP ac2.
I would like ask some questions regarding plans for further enhancement of the wifi package:
1) Is there going to be support for WDS ( dynamic and static mesh mode) in the new wifi2 packages? It would be useful for Audience devices that could be run in mesh mode and offer fast roaming + WPA3 for clients at the same time.
2) Will the NV2 protocol be made available for wifi2 devices ?(again, for wireless PTMP / Mesh mode, one might use NV2 for the wireless backbone and 802.11 standard for client access)
3) Ability to assign a VLAN tag to a wireless interface without using Bridge filtering on AC devices (this was asked before - useful for hAP ac2 devices with switch chip enabled VLAN filtering and multiple VLAN tagged wireless interfaces - which is a quite common usecase)

Adding support for these features would make MikroTik equipment one of the most versatile and feature rich platforms available out there!

zandhaas · Tue Nov 14, 2023 1:51 pm

zandhaas use check for updates button and ignore the above ranting. nothing special has to be done. upgrade and forget

Thank you Normis

Jotne · Tue Nov 14, 2023 1:56 pm

This was not easy to understand.
On a RB951 I did upgrade from 7.11 to 7.12 to 7.13beta1 running a simple configuration with wifi and nat.
After upgrade to 7.13beta1, I got a new package named wireless.
I do also see all my wifi configuration are under wireless tab and not under wifi.
If wireless package are not needed, why is it thee still?
And there are no config in Wifi, only in Wireless tab. Should not that be converted, so I could remove the Wireless package and save space?
How to convert it now?

clambert · Tue Nov 14, 2023 1:57 pm

*) console - added "where" functionality for "export" command;

I can´t find the "where" clause in export command.

Tue Nov 14, 2023 1:59 pm

@Jotne:
The way I understand it:
upgrade to 7.13 chain unbundled wireless from the core ROS package.
That's why you see it being mentioned again (it was also like that in older ROS6 versions).
And you DO need that package or your wireless radios will not work anymore (I think but easy to test).

Wifi section is for those devices using qcom/qcom-ac drivers (AX devices and AC devices listed as compatible).
For those AC devices you DO need to uninstall wireless, install qcom-ac and then setup the radios again under the new structure.
That's how I had to do it for AC2.
If you do not do that last step (uninstall wireless / install qcom-ac), device will remain working with "old" wireless drivers.

gigabyte091 · Tue Nov 14, 2023 2:01 pm

Okay, I updated ax3 to 7.13beta1, only ROS package, nothing else, do I need to install another package or what ?

Tue Nov 14, 2023 2:03 pm

Okay, I updated ax3 to 7.13beta1, only ROS package, nothing else, do I need to install another package or what ?

Does it work ?
On my AX3 (and AX2) I see ros package and wifi-qcom. I didn't do anything but check for upgrades and hit 'the' button.
But when did you do that upgrade ?

Because there is a post from strods Mon Nov 13, 2023 5:41 pm indicating there was an issue with arm64 installs.
viewtopic.php?p=1035711#p1035711

gigabyte091 · Tue Nov 14, 2023 2:07 pm

Yesterday, around 5:45pm, but in my case ax3 is capsman controller and router wireless interfaces are disabled. This is at my parents house. I can enable interfaces to test them.

Jotne · Tue Nov 14, 2023 2:10 pm

The way I understand it:

That makes some sense.

mkx · Tue Nov 14, 2023 2:11 pm

The document, linked by @EdPa in post #2, says:

The configuration menu used to be called 'wifiwave2' in RouterOS versions before 7.13, where it was a part of the 'wifiwave2' software package.

So when 7.12 with installed wifiwave2 package gets upgraded to 7.13beta1 (or newer), wifi-qcom (or wifi-qcom-ac) package replaces the previously installed wifiwave2 package. At the same time, the configuration subtree /interface/wifiwave2 gets renamed to /interface/wifi, but structure under it remains unchanged.

If, OTOH, one upgrades device by manually uploading package files, then it's necessary to upload correct wifi package as well (as it used to be necessary to manually upload wifiwave2 package previously).

gigabyte091 · Tue Nov 14, 2023 2:16 pm

Okay, so now it's clear to me, tnx @mkx

Tue Nov 14, 2023 2:21 pm

So when 7.12 with installed wifiwave2 package gets upgraded to 7.13beta1 (or newer), wifi-qcom (or wifi-qcom-ac) package replaces the previously installed wifiwave2 package.

I noticed an important difference on AC2 (no previous wifiwave2).
Wireless was there after upgrade, not qcom-ac (and yes, I DID use the advised approach of "check for updates" and "update").
I had to manually uninstall wireless, only THEN could I install qcom-ac (it wouldn't as long as wireless was there) and continue under the new structure.
Not before.

Space issue, perhaps ? I didn't check logs ...

mantouboji · Tue Nov 14, 2023 2:31 pm

*) certificate - add support for multiple DNS names for Let's Encrypt;

test successful like this:

`
/certificate/enable-ssl-certificate dns-name=DOMAIN1,DOMAIN2
`

ToTheCLI · Tue Nov 14, 2023 2:38 pm

I upgraded to 7.13beta1 after 7.12stable from winbox on hapac2 and then removed wireless package and then installed qcom-ac package, noticed bandwidth was so low about 20Mbps, so I reset the hapac2 without default config, and bandwidth improved, even better then with 7.12stable (600Mbps on 80Mhz wide Channel).

Z0ltan · Tue Nov 14, 2023 2:52 pm

Can someone please shed some light how to make CAPSMAN work with wifi-qcom-ac? I have a wAP AC (the supported version), I installed 7.13b1 on it and it shows up on my CAPSMAN controller (RB4011 with manually installed wifiwave2 package, already managing 2 hap ax2-s) but I cannot provision the CAP and I also don't have the "Manager" setting (to choose if it's managed locally or via CAPSMAN). I did add 2ghz n / 5 ghz ac to my already working configuration templates, is there anything else I need to do?

mkx · Tue Nov 14, 2023 2:54 pm

So when 7.12 with installed wifiwave2 package gets upgraded to 7.13beta1 (or newer), wifi-qcom (or wifi-qcom-ac) package replaces the previously installed wifiwave2 package.
I noticed an important difference on AC2 (no previous wifiwave2).
Wireless was there after upgrade...

Sure thing ... because wifi-qcom-ac doesn't replace wireless. And since configuration structure is significantly different, I'm sure there isn't a good config translator from legacy to wifi syntax. Which means that automatic replacement of wireless with wifi-qcom-ac would mean those people would be wireless-less. So IMO it's good that bundled legacy wireless is replaced by separate wireless package, which enabled users to perform further steps when ad as they see fit.

parham · Tue Nov 14, 2023 3:00 pm

Hi support & Dev team

I was hope to have more free space with 7.13 but its less.

check the before and after, I use WAP R AC with R11e-4G.

before update 14.5MB of 15.2MB 4% free

Screenshot 2023-11-14 at 12.49.18.png

after update 14.9MB of 15.2MB 2% free

Screenshot 2023-11-14 at 12.54.43.png

As a side note, I have dead mikrotik when I was installed Zerotier after few reboot since 7.6 to 7.12

OMG, Now I can't even install Zerotier

Screenshot 2023-11-14 at 13.06.43.png

Thanks
Parham

Tue Nov 14, 2023 3:08 pm

This upgrade does not in any way free disk space. However, on a device which does not need to have wireless package, for example, CRS which do not run CAPsMAN, you know have separate wireless package. It is not a part of bundle any more. You can now uninstall it, and you will not only save disk space, but also a little bit of RAM.

Tue Nov 14, 2023 3:11 pm

Can someone please shed some light how to make CAPSMAN work with wifi-qcom-ac? I have a wAP AC (the supported version), I installed 7.13b1 on it and it shows up on my CAPSMAN controller (RB4011 with manually installed wifiwave2 package, already managing 2 hap ax2-s) but I cannot provision the CAP and I also don't have the "Manager" setting (to choose if it's managed locally or via CAPSMAN). I did add 2ghz n / 5 ghz ac to my already working configuration templates, is there anything else I need to do?

Did you uninstall wireless package and install qcom-ac ?
You need to do this manually on ac devices in order to be able to use qcom-ac driver.

Kevdevon · Tue Nov 14, 2023 3:12 pm

If anyone else has ADHD, take your meds and then try and understand the new wifi, lol.
Side note: Trying to understand it before going ahead with the firmware upgrade.

Z0ltan · Tue Nov 14, 2023 3:13 pm

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?

Tue Nov 14, 2023 3:15 pm

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?

If your provisioning rules are specific enough so it ends up only using AX, yes you need new rules for AC.

Z0ltan · Tue Nov 14, 2023 3:22 pm

Is there a way to define provisioning in such a way to use the best available? I only need to define which SSID-s go on 2.4GHZ and which ones to 5GHZ but I have no need to specify AC or AX - also I want fast transition if possible.

parham · Tue Nov 14, 2023 3:25 pm

This upgrade does not in any way free disk space. However, on a device which does not need to have wireless package, for example, CRS which do not run CAPsMAN, you know have separate wireless package. It is not a part of bundle any more. You can now uninstall it, and you will not only save disk space, but also a little bit of RAM.

So the WAP R AC has a both band WiFi however I don't need CAPSMAN maybe the CAPSMAN should have own package and Im sure lots of people not using it.

Traveller · Tue Nov 14, 2023 3:40 pm

Space issue, perhaps ?

Yes. In 16 MB Hap Ac2 does not put two packages at the same time. Only one: Wireless or Wi-Fi.

osc86 · Tue Nov 14, 2023 3:59 pm

updated a CCR2004 to 7.13beta1. Moved some hapac2 w/ wifi-qcom-ac package over to the new "WiFi capsman". The remaining devices lost connection to old capsman v1. Is it not possible to have both capsman versions running on the same device? I don't see any other reason why capsmanv1 should've stopped working.. I see incoming traffic from caps on port 5246/udp but capsman ignores it or discards the packet. Are they even using different ports for communication? I couldn't find it in the provided docs.

Tue Nov 14, 2023 4:14 pm

Let's start from the beginning again. Hope this helps:

New Wireless packages

From 7.13 we are separating the older wireless package out from routeros.npk bundle and renaming wifiwave2 package to wifi. The new wifi package is now part of the routeros.npk bundle, beginning a new and exciting era for wifi features.

We are also separating core wifi features from the drivers, reducing used space on the router. Note that upgrade will take care of the new packages automatically, you do not need to worry about anything, if you use "check for updates" feature. Technically the bundle only includes the core wifi package with capsman, so devices that don't have any wireless cards, but are only used for capsman, will not use space unnecessarily if you don't install the separately available driver packages.

Due to this, you will now see the wifi menu even on devices that don't have any wireless interfaces. The new wifi package is also now compatible with more devices than before - you can install the new wifi package even on 802.11AC devices that have the ARM CPU type.* This opens up more compatibility options with the new 802.11AX devices and even allows devices to use both wireless packages (old/integrated + new wifi package) in the same device, which means you can now use a single router to run both old and new CAPsMAN.

(* more details about supported devices and exceptions are in the documentation https://help.mikrotik.com/docs/pages/vi ... d=46759946 )

Software upgrade PSA

Because of the introduction of a new wireless package, we would like to bring your attention, that RouterOS will now show upgrade only up to 7.12 if using an older version of software. You will have to first upgrade to 7.12 and only then newer RouterOS versions will become available to you.

Tue Nov 14, 2023 4:17 pm

updated a CCR2004 to 7.13beta1. Moved some hapac2 w/ wifi-qcom-ac package over to the new "WiFi capsman". The remaining devices lost connection to old capsman v1. Is it not possible to have both capsman versions running on the same device? I don't see any other reason why capsmanv1 should've stopped working.. I see incoming traffic from caps on port 5246/udp but capsman ignores it or discards the packet. Are they even using different ports for communication? I couldn't find it in the provided docs.

See 1 post above yours (and normis' post in between ours).
Space issue on ac2 will prevent both packages from being present.
You need both if you want old and new environment to be controlled on the same device.

Amm0 · Tue Nov 14, 2023 4:31 pm

RouterOS consists of things that many people don't use. Even in Windows you have menus you can't use.

There are skins to remove it from UI: https://help.mikrotik.com/docs/display/ ... bfig-Skins

Compared with alternative of not being able to run BOTH legacy and AX capsman, which was previously annoying, seems like fair trade.

MartinsG · Tue Nov 14, 2023 4:34 pm

I am having probelm with "assocation rejected, can't find PMKSA" with CAPsMAN on ax3

16:04:11 wireless,debug 12:**:**:**:78:91@wifi1 assocation rejected, can't find PMKSA
16:04:13 wireless,debug 12:**:**:**:9E:78:91@wifi1 assocation rejected, can't find PMKSA
16:05:11 wireless,debug BE:**:**:**:AE:CF:03@2Ghz-2Stavs_TV2 assocation rejected, can't find PMKSA
16:05:52 wireless,debug E6:**:**:**:3C:C5@2Ghz-Lampina-ac31 assocation rejected, can't find PMKSA

And device jumping arround till finally find where to connect and quite ofter then it is far away CAP and i have fealing that e.g. PC start to awoid that CAP next time.
In this extract is Android (Samsung S22), iOS (iPhone14) and win10.

CAPsMAN and CAP is on 7.13beta1
And somewhere i found that that is something to do with pmkid, this is what i have there:

/interface wifi security add authentication-types=wpa2-psk,wpa3-psk connect-priority=0/1 disable-pmkid=yes disabled=no ft=yes ft-over-ds=yes name=Sec_01

osc86 · Tue Nov 14, 2023 5:28 pm

..which means you can now use a single router to run both old and new CAPsMAN.

It's not working here, at least not in parallel, since both capsman daemons try to bind to the same port 5246/udp, and the one that boots up first, wins.
On my device it's either A or B, and I don't see an option to bind either version to a specific ip or interface.

Santi70 · Tue Nov 14, 2023 5:41 pm

I have a question, if I upload an hAP ac2 to version 7.13b1 and install the "wifi-qcom-ac" package, can I join its wireless interfaces to a capsman server that is on an hAP ax3 that is in version 7.12?

alibloke · Tue Nov 14, 2023 6:11 pm

..which means you can now use a single router to run both old and new CAPsMAN.
It's not working here, at least not in parallel, since both capsman daemons try to bind to the same port 5246/udp, and the one that boots up first, wins.
On my device it's either A or B, and I don't see an option to bind either version to a specific ip or interface.

Have the two capsmanagers listen on different interfaces/VLANs:
Legacy:

/caps-man/manager/interface> print 
Flags: * - DEFAULT
Columns: INTERFACE, FORBID
#   INTERFACE       FORBID
0 * all             yes   
1   [capsman-interface]  no

qcom:

 /interface/wifi/capsman> print 
                   enabled: yes
                interfaces: [other-capsman-interface]

osc86 · Tue Nov 14, 2023 6:42 pm

@alibloke, Although this solution might work, I don't believe it's optimal. I've always understood this to be a list of interfaces from which connections from caps are permitted, rather than capsman binding to these interfaces; instead of 0.0.0.0.

Even if it works, I'd consider this bad practice. Two separate management networks or VLANs would be required. This could be avoided if capsman could bind to IP addresses instead of interfaces, so you would only need to assign two IPs to the same management network: one for the old capsman and the other for the new one.

A better option would have been to use another port for the new capsman and a multicast-based service discovery protocol to locate a compatible capsman. Maybe in ROS8..

Jotne · Tue Nov 14, 2023 6:43 pm

The new wifi package is now part of the routeros.npk bundle, beginning a new and exciting era for wifi features.

I do think that the wording here are messing with people. There are no "wifi package" as in a separated package. The new "wifi" are part og the standard routeros package.

Since its a part of a default package, all routers will see the new Wifi menu. Also it not clearly written when your need the old wireless package, type a list of devices (or type of devises) that need the wirelses package.

But if all you need to do is to upgrade to 7.12, then 7.13 and all should be taken care of, we should not worry about the naming of stuff.

Ullinator · Tue Nov 14, 2023 7:21 pm

@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!!😉

woland · Tue Nov 14, 2023 7:37 pm

"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.

evbocharov · Tue Nov 14, 2023 7:47 pm

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

whatever · Tue Nov 14, 2023 7:58 pm

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.

pe1chl · Tue Nov 14, 2023 8:07 pm

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.

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)

mukkelek · Tue Nov 14, 2023 8:14 pm

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

CTassisF · Tue Nov 14, 2023 8:22 pm

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.

pe1chl · Tue Nov 14, 2023 8:27 pm

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.

whatever · Tue Nov 14, 2023 10:05 pm

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:

Found it in the wiki:
Code: Select all
802.11ac chipsets do not support this type of VLAN tagging (vlan-id), but they can be configured as VLAN access ports in bridge settings.
Just upgraded my hAP ac2 . The above is a bummer for me, I have VLANs configured on switch chip (under /interface/ethetnet/switch/, so bridge is clueless about VLANs.

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.

floaty · Tue Nov 14, 2023 10:47 pm

chr.PNG

.
chr ... for oracle or azure ? ... ?

floaty · Tue Nov 14, 2023 11:06 pm

or outsourcing your ROS-scripts to this babe ... ?!
.

bare-metal.PNG

wfburton · Wed Nov 15, 2023 12:08 am

I welcome the partial split into separate packages as we knew it in v6, but maybe the "WiFi" menu should go into a separate "wifi" package so we can uninstall that as well.
+1, it's a mess currently
2023-11-13 at 18.41.17.png

Yes please make wifi a wperate package. My mikrotik router doesn't supoort wifi!

CRS309-1G-8S+

Amm0 · Wed Nov 15, 2023 12:13 am

+1, it's a mess currently
2023-11-13 at 18.41.17.png
Yes please make wifi a wperate package. My mikrotik router doesn't supoort wifi!
CRS309-1G-8S+

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.

Z0ltan · Wed Nov 15, 2023 12:22 am

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).

wfburton · Wed Nov 15, 2023 12:23 am

Yes please make wifi a wperate package. My mikrotik router doesn't supoort wifi!
CRS309-1G-8S+
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.

I unistalled wireless and CAPsMAN2 was automatically removed. But still, I don't need wifi and it would be nice not to have it installed.

omega-00 · Wed Nov 15, 2023 1:55 am

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.

thenetworks · Wed Nov 15, 2023 5:55 am

'AMPERA' = 400G ?

Wed Nov 15, 2023 8:06 am

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.

Wed Nov 15, 2023 8:11 am

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.

guipoletto · Wed Nov 15, 2023 8:40 am

*) 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" ?

Wed Nov 15, 2023 8:58 am

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.

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

Wed Nov 15, 2023 9:01 am

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

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

gigabyte091 · Wed Nov 15, 2023 9:13 am

Are you planning to implement PPSK in near future ?

BrateloSlava · Wed Nov 15, 2023 9:55 am

Good afternoon.

I set up a test network at home on 7.13. The CAPsMAN controller was installed on RB750Gr3, access points - cAP ac, wAP ac.

Configurations were exported using the command "export compact terse show-sensitive file"

Access points:

/interface wifi channel add band=2ghz-n disabled=no frequency=2412,2437,2462 name=Home-2.4GHz width=20mhz
/interface wifi channel add band=5ghz-ac disabled=no frequency=5180,5260,5500,5580,5745 name=Home-5GHz skip-dfs-channels=disabled width=20/40/80mhz

/interface wifi security add authentication-types=wpa2-psk,wpa3-psk disabled=no management-protection=allowed name=sec-home passphrase=secret-pass wps=disable

/interface wifi steering add disabled=no name=steering-LAN neighbor-group=NBG-Group-LAN rrm=yes wnm=yes

/interface wifi configuration add channel=Home-2.4GHz country=Ukraine disabled=no name=cfg-Home-2 security=sec-home security.ft=yes .ft-over-ds=yes ssid=MikroAP-Loc steering=steering-LAN
/interface wifi configuration add channel=Home-5GHz country="United States" disabled=no name=cfg-Home-5 security=sec-home security.ft=yes .ft-over-ds=yes ssid=MikroAP-Loc steering=steering-LAN

/interface wifi set [ find default-name=wifi1 ] channel.frequency=2412,2437,2462 configuration=cfg-Home-2 configuration.manager=capsman-or-local .mode=ap disabled=no
/interface wifi set [ find default-name=wifi2 ] channel.frequency=5180,5260,5500,5580,5745 configuration=cfg-Home-5 configuration.manager=capsman-or-local .mode=ap disabled=no

Controller:

/interface wifi channel add band=2ghz-n disabled=no frequency=2412,2437,2462 name=Home-2.4GHz width=20mhz
/interface wifi channel add band=5ghz-ac disabled=no frequency=5180,5260,5500,5580,5745 name=Home-5GHz skip-dfs-channels=disabled width=20/40/80mhz

/interface wifi security add authentication-types=wpa2-psk,wpa3-psk disabled=no group-key-update=1h management-protection=allowed name=secur-Home passphrase=secret_pass wps=disable

/interface wifi steering add disabled=no name=steering-Home neighbor-group=NB-group-Home rrm=yes wnm=yes

/interface wifi configuration add channel=Home-5GHz country="United States" disabled=no name=Home-5ghz security=secur-Home security.ft=yes .ft-over-ds=yes ssid=MikroAP steering=steering-Home
/interface wifi configuration add channel=Home-2.4GHz country=Ukraine disabled=no name=Home-2ghz security=secur-Home security.ft=yes .ft-over-ds=yes ssid=MikroAP steering=steering-Home

/interface wifi access-list add action=accept allow-signal-out-of-range=10s disabled=no interface=all mac-address=44:D8:78:27:F9:B7 signal-range=-50..120 ssid-regexp=MikroAP*
/interface wifi access-list add action=reject disabled=no interface=all mac-address=44:D8:78:27:F9:B7 ssid-regexp=MikroAP*
/interface wifi access-list add action=accept allow-signal-out-of-range=5s disabled=no interface=all signal-range=-82..-10 ssid-regexp=MikroAP*
/interface wifi access-list add action=reject disabled=no interface=all signal-range=-120..-83 ssid-regexp=MikroAP*

/interface wifi provisioning add action=create-dynamic-enabled comment="5.0GHz Slava - Home" disabled=no master-configuration=Home-5ghz name-format=%I supported-bands=5ghz-ac
/interface wifi provisioning add action=create-dynamic-enabled comment="2.4GHz Slava - Home" disabled=no master-configuration=Home-2ghz name-format=%I supported-bands=2ghz-n

/interface wifi capsman set ca-certificate=auto enabled=yes package-path="" require-peer-certificate=no upgrade-policy=none

When exporting such an access point configuration, outputting the “channel.frequency” values is redundant, because frequency values are specified in "configuration"
When setting up CAPsMAN in a similar configuration, do the parameters in “signal-range” now have any meaning?

To be honest, in my apartment the scanner picks up about 100+ Wi-Fi networks in the 2.4 GHz range and about 15+ in the 5.0 GHz range. With new drivers "wifi-qcom-ac" and new settings, using WiFi has become much more comfortable.
Thank you very much for this update!

osc86 · Wed Nov 15, 2023 10:21 am

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.

This was the missing information. I've set everything to auto, and while the correct certificates were generated, it didn't work.
I've manually selected the proper certificates in both capsman, restarted both services and now it's working again.
Thanks!

Wed Nov 15, 2023 10:27 am

What's new in 7.13beta2 (2023-Nov-14 13:04):

*) bridge - fixed missing "S" flag after configuration changes (introduced in v7.13beta1);
*) certificate - added HTTP redirect support for CRL download;
*) certificate - added support for certificates with key size 16384;
*) console - added ":grep" command;
*) console - added "interface" name when printing "interface/pppoe-server" entries;
*) console - fixed missing escaped characters when using print in certain menus (introduced in v7.13beta1);
*) disk - fixed hang on reboot when network file systems mounted;
*) lora - added CUPs protocol support;
*) lte - disabled IMS service for Chateau 5G on A1 HR network;
*) ppc - fixed RouterOS bootup (introduced in v7.12);
*) route-filter - improved performance;
*) supout - added multiple WiFi sections;
*) wifi - improved system stability when using sniffer (introduced in v7.13beta1);
*) winbox - improved connection speed;

DenisPDA · Wed Nov 15, 2023 10:43 am

What's new in 7.13beta2 (2023-Nov-14 13:04):

7.13b2.JPG

DarkNate · Wed Nov 15, 2023 10:54 am

Why is that? I'm running carrier grade NAT on some 2216's for customers and was looking into either the nat-ein or nat-pmp to try to get customers gaming setups happy with NAT types. Just trying to find a way to not get a double NAT for gaming consoles without having to give every customer a public IP.

1. Read this:
viewtopic.php?p=1036258#p1035722

2. Implement the netmap method for CGNAT and no customer will call you about NAT issues on their Xbox or PS:
viewtopic.php?t=176358

infabo · Wed Nov 15, 2023 11:21 am

"wifiwave2" package has been divided into distinct packages: "wifi-qcom" and "wifi-qcom-ac"

IMHO this was a bad naming decision. It is causing confusion already and it is going to confuse - ongoing.

qcom stands for qualcomm.
you need a package called "wifi-qcom-ac" for AC devices.
But you need a "generically named" package like "wifi-qcom" for AX devices.
This is inconsistent in naming. Then you already create a future-problem.
How do you name the drive-package for the standard that follows AX? aka wifi7? I would assume "wifi-qcom-be".
So you tell users: "install wifi-qcom for AX, but wifi-qcom-be for wifi7 LOL".
I assume you anticipated to put 802.11be and all upcoming device drivers into the wifi-qcom package - because disk-space is not an issue anymore on modern/upcoming devices (128MB or even more).
But I don't like this kind of thinking. "super-bundles" that grow in size and somewhen in 2028 that wifi-qcom package has 80MB because you can't remove AX-drivers because you made a bad packagename decision back in 2023.

Better would have been:

* wifi-qcom-ac
* wifi-qcom-ax

Furthermore, better not integrating the new "wifi" config-module into the base ROS bundle already. Having a wifi menu without actually having wifi anywhere? Pretty weird decision.

So better package bundling from my point of view:

* wifi-common (or wifi-base or wifi-config) -> put the wifi config module stuff into this package
* wifi-qcom-ac -> only the AC drivers and related to AC. depends on wifi-common.
* wifi-qcom-ax -> only the AX drivers and related to AX. depends on wifi-common.

Then tell people:

Old wireless: install package "wireless"
New wireless: install package "wifi-common" and depending on your chipset use either "wifi-qcom-ac" or "wifi-qcom-ax".

No confusion. Everybody understands without even reading a manual.

pablolite · Wed Nov 15, 2023 11:30 am

On router Chateau 5g will i be able to use the new wifi and zerotier at the same time?

I am using it at home and purchased as "future proof".
Am I facing a replacement? Alternatively to what model?

https://mikrotik.com/product/chateau_5g

alibloke · Wed Nov 15, 2023 11:55 am

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.

I deleted all certificates and regenerated new ones for both types of capsman, but certificates are generated from the "new" CA for legacy caps when requested: SUP-134480

Wed Nov 15, 2023 12:10 pm

On router Chateau 5g will i be able to use the new wifi and zerotier at the same time?

I am using it at home and purchased as "future proof".
Am I facing a replacement? Alternatively to what model?

A device with 16Mb of flash does not really fit my definition of future proof ...
FWIW I face exactly the same problem with AC3 LTE, having zerotier on it but also limit of 16Mb storage, of which 346Kb is free right now (whereas regular AC3 has 128Mb, go figure).
It is what it is, I suppose.

Make a backup, move it off device.
Upgrade and see what happens.
Remove wireless package, install qcom-ac package.
Worst case (if it doesn't work) you need to downgrade and then you can restore backup.

I'm not going to try on that AC3 LTE, it's a production device so I'm not touching it until all wrinkles are ironed out

pe1chl · Wed Nov 15, 2023 12:25 pm

In my experience, you can sometimes gain a little space on those 16MB flash devices especially when in the past you have done a lot of upgrading (especially when it was originally delivered with RouterOS v6) or you have done a lot of configuration experiments that you have later removed.
In this case, do a full "/export show-sensitive file=backup" of the configuration and download the backup file, then netinstall the device without default configuration, connect to it from winbox via MAC address, upload your backup.rsc, open terminal and do /export to see if the config is really (almost) empty and then "/import verbose=yes backup.rsc". Hopefully it completes without error, else you can see on the terminal what has failed and use from-line=xxx to restart after the failure.

Now you have completely rebuilt the configuration database, and it is often a bit smaller.
Do NOT use "/system/backup" for this, it will just dump and restore the database and it will be just as large as before.

pe1chl · Wed Nov 15, 2023 12:32 pm

*) disk - fixed hang on reboot when network file systems mounted;

That is interesting! Strods says 'Please remember that actual "bugs" must be reported to support@mikrotik.com complemented with logs, supout files, etc.' above.
I reported this bug both on the 7.12 topic and as a ticket, and now it is reported as fixed (I will test) while my ticket has not even been acknowledged yet, it is still "waiting for support"... so maybe the developers ARE reading the topics?

mkx · Wed Nov 15, 2023 12:35 pm

*) disk - fixed hang on reboot when network file systems mounted;
That is interesting! Strods says 'Please remember that actual "bugs" must be reported to support@mikrotik.com complemented with logs, supout files, etc.' above.

@pe1chl, do I understand you correctly that you're complaining about MT fixing a bug which was not properly reported (and you'd like them to reintroduce that bug in following releases)?

Oh my, people are never satisfied whatever one does.

Sertik · Wed Nov 15, 2023 12:44 pm

Can someone clearly explain the syntax and use of the new commands:

:serialize
:deserialize
:onerror
:grep

videolab · Wed Nov 15, 2023 12:55 pm

Hi,
romon problems encountered on netpower 15 - CRS318-1Fi-15Fr-2S in the presence of VLAN.
To solve the problem I deactivated and reactivated romon

Wed Nov 15, 2023 12:58 pm

serialize,deserialize - convert provided value from/to specified format
onerror - catch errors
grep - like linux grep tool

Press F1 and you will see the parameters and descriptions:

some examples:

:put [:serialize to=json value=a,b,c]
["a","b","c"]

:grep pattern="veth" script="/interface print"    
18 X veth1          veth                                  00:00:00:00:00:00

pe1chl · Wed Nov 15, 2023 1:13 pm

That is interesting! Strods says 'Please remember that actual "bugs" must be reported to support@mikrotik.com complemented with logs, supout files, etc.' above.
@pe1chl, do I understand you correctly that you're complaining about MT fixing a bug which was not properly reported (and you'd like them to reintroduce that bug in following releases)?

Oh my, people are never satisfied whatever one does.

And it is not a complaint, I just labeled it as "interesting".
Probably the change was made as the result of someone else's ticket.
Well, actually the bug isn't even fixed...

pe1chl · Wed Nov 15, 2023 1:14 pm

*) disk - fixed hang on reboot when network file systems mounted;
That is interesting! Strods says 'Please remember that actual "bugs" must be reported to support@mikrotik.com complemented with logs, supout files, etc.' above.
I reported this bug both on the 7.12 topic and as a ticket, and now it is reported as fixed (I will test) while my ticket has not even been acknowledged yet, it is still "waiting for support"... so maybe the developers ARE reading the topics?

Well, actually the bug isn't fixed. When I do a user manager backup to an NFS-mounted disk I still cannot unmount the disk afterwards and it still hangs on reboot!