Are you planning to implement PPSK in near future ?
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!
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!
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;
-
Read this:
http://forum.mikrotik.com/t/v7-13beta-testing-is-released/171132/185 -
Implement the netmap method for CGNAT and no customer will call you about NAT issues on their Xbox or PS:
http://forum.mikrotik.com/t/how-to-edge-router-and-bng-optimization-for-isps/150007/1
“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.
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
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
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 
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.
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?
@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.
Can someone clearly explain the syntax and use of the new commands:
:serialize
:deserialize
:onerror
:grep
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
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
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…
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!
My home router is like a production. Remote working + several servers.
A year ago I thought a $500 router would last me a few years, but I’m slowly realizing that I bought a castrated expensive model 
I wanted the best LTE possible (and at that time there was no AX version).
I’ll wait until 7.13 comes out of beta and take @pe1chl Netinstall’s advice, maybe it will work.
I have upgraded from 7.12 but I had to revert: several devices on my network did not get addresses from DHCP anymore.
These were all ethernet-connected devices on different VLANs on a VLAN-filtering bridge.
The bridge has protocol-mode=none (no STP) but I notice that in the export I made when running 7.13beta2 the affected ports had additional “internal-path-cost=10 path-cost=10” added that wasn’t there in 7.12 export (ok, that is probably due to a change in the beta1 version mentioned above).
The DHCP service was logging “dhcp,warning dhcp-iot offering lease 192.168.3.3 for xx:xx:xx:xx:xx:xx without success”.