MikroTik

Posted: **Tue Dec 19, 2023 5:29 pm**

You are correct, at the same time the package names are confusing. I'd suggest renaming it or making it bold in the docs.
Does this help? viewtopic.php?t=202578

yes, but this belongs to the docs, thanks

Posted: **Tue Dec 19, 2023 5:30 pm**

We will update the table so that everyone has all questions answered. When forum users approve it, we will put it into docs.

Posted: **Tue Dec 19, 2023 5:39 pm**

I have several scripts like these (they serve to telegram alert temperature and voltage etc. of the LTE modem) and they no longer work:

Try with:

:global temp2
:global url "https://192.168.5.2:8443/json.htm?usern ... lue=$temp2";
/tool fetch keep-result=no url=$url mode=http
(not https)

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

Posted: **Tue Dec 19, 2023 5:50 pm**

I had already tried but it does not work

Posted: **Tue Dec 19, 2023 6:34 pm**

No such thing here.
Stable since update last Friday.
This is getting annoying for me, it's the same error and reboots I had a few releases ago related with some OVPN issue.

Capture.JPG

Same behavior here - after updating my RB5009 to 7.13 I keep getting 1-2 reboots per day without sup and with "probably power outage" message in the log.
P.S. Running OVPN and Wireguard on this box.

Posted: **Tue Dec 19, 2023 6:57 pm**

I only run wireguard in mine. No ovpn.

Posted: **Tue Dec 19, 2023 8:00 pm**

My Telegram script works fine in v7.13

:global tgFunc do={
    :do {
        :local BotToken "XXXXXXXXX:XXXXXXXXXXX-XXXXXXXXXXXXXXXXXX"
        :local ChatID "XXXXXXXXX"
        :local parseMode "HTML"
        :local DisableWebPagePreview true
        :local SendText $1

        /tool fetch url="https://api.telegram.org/bot$BotToken/sendMessage\?chat_id=\
            $ChatID&parse_mode=$parseMode&text=$SendText&disable_web_page_preview=\
            $DisableWebPagePreview" keep-result=no
        
        :log info "=> Telegram message sent successfully"
    } on-error={
        :log info "=> Telegram message sent failed"
    }
}

BR.

I have several scripts like these (they serve to telegram alert temperature and voltage etc. of the LTE modem) and they no longer work:

:global temp2
:global url "https://192.168.5.2:8443/json.htm?username=mE&ghy&l&password=dGMntyhju&type=command&param=udevice&idx=57&nvalue=0&svalue=$temp2";
/tool fetch keep-result=no url=$url mode=https

:global temp1
:set temp1 55
:global temp (:tostr(:put [/ interface lte at-chat input="at+qtemp" lte1 wait=yes as-value]));
:global tempstring ([:pick $temp 0]);
:global temp2 ([:pick $tempstring 47] . [:pick $tempstring 48]);
:if ($temp2 > $temp1) do= {/tool fetch url="https://api.telegram.org/botx:x/sendmessage?chat_id=-xxx&text=EM160 Warning!!! Temperature is $temp2 Degrees" keep-result=no}

I have the same issue and I had to rollback to 7.12.1 to recover the functionality

Posted: **Tue Dec 19, 2023 8:39 pm**

again the device won't boot after upgrading from 7.12 to 7.13 and I'll have to fly halfway around the world again to do the Netinstall in person and who knows if it will reinstall.

Time to install out-of-band access? I have one that requires a flight to get to too.. It corrupted during the v6.x to v7.x upgrade.. Using a remote system to access the serial console, also connected to the RouterBoot port, reinstalled the system,

Posted: **Tue Dec 19, 2023 9:10 pm**

Is there a guide on making both CAPSMANs work at the same time on the same MikroTik device?

I've tried but they don't seem to be able to coexist. I suspect that may have to be listening on different interfaces, can't check that right now but would appreciate any advise.

Edit: Tried running them on different VLAN ifaces with no luck - as soon as I enable the new CAPsMAN the old one seem to stop working and I lose all wi-fi connections, CAP interfaces, etc.

Posted: **Tue Dec 19, 2023 10:10 pm**

CCR1016 after updating to 7.13 not show lte interface anymore.
But in USB list it showing.

wireless already installed

At 7.12 all ok.
The same on hAP ac^3. Sometime after reboot I've got lte interface and internet access but can't access web interface of the modem in hilink mode.

Same here ros7.13 rb5009 .. no more usb lte interface but is listed in usb ?

Posted: **Tue Dec 19, 2023 10:14 pm**

Also I think the cpu start to be more utilised ? in profile the most cpu usage is "unclasified" is someone notice something simillar with 7.13 ?

Posted: **Tue Dec 19, 2023 10:31 pm**

Is there a guide on making both CAPSMANs work at the same time on the same MikroTik device?

I've tried but they don't seem to be able to coexist.

Check this out and see if it helps.

Posted: **Tue Dec 19, 2023 10:32 pm**

Is there a guide on making both CAPSMANs work at the same time on the same MikroTik device?

I have not tried it myself, but I think there have been user reports that you need a dedicated CA for each CAPsMAN to make them co-exist. Is that true for you?

Posted: **Tue Dec 19, 2023 10:37 pm**

Updated soft- and firmware to 7.13 on these models (> 50 devices in total) without any issues:

- x86
- RB5009UPr+S+
- RBcAPGi-5acD2nD (cAP ac)
- RB760iGS (hEX S)
- CRS309-1G-8S+
- RB750GL
- RB952Ui-5ac2nD
- RB4011iGS+
- RBwAPG-60ad
- RBwAPG-60ad-A
- RBwAPG-60ad-SA
- RBD22UGS-5HPacD2HnD
- RBwAPG-5HacD2HnD (wAP ac)

Posted: **Tue Dec 19, 2023 11:27 pm**

Is there a guide on making both CAPSMANs work at the same time on the same MikroTik device?

I've tried but they don't seem to be able to coexist.
Check this out and see if it helps.

Thank you, sir. Unfortunately, wiping all certificates and starting with new ones didn't solve the issue. I am filing a support case.

Posted: **Wed Dec 20, 2023 4:45 am**

I tested this version on my CCR 1016 where MPLS and VPLS {LDP} is running. After 3 to 5 minutes router reboots and it keeps repating over and over. On version 7.12.1 everything is ok. Has anyone same experience? No error in log.

This same, but reboots about 10 seconds.

Posted: **Wed Dec 20, 2023 8:24 am**

My RB5009 also reboots once in 1-2 days of uptime since 7.13. Openvpn & wireguard enabled on the device.

Posted: **Wed Dec 20, 2023 9:30 am**

The same for me mpls/vpls/ldp running, after a few minutes, "kernel error" and crash/reboot. Works without issues in 7.12.1.
Rb4011/Audience/hap ax3

Posted: **Wed Dec 20, 2023 10:05 am**

Hmmm... all my fetch scripts works well without ftp policy. WDIDW?

Also how to disable this new fetch logging?

Posted: **Wed Dec 20, 2023 10:49 am**

I would also like to disable fetch logging

Posted: **Wed Dec 20, 2023 11:37 am**

Hmmm... all my fetch scripts works well without ftp policy. WDIDW?

Also how to disable this new fetch logging?

/system logging
set 0 disabled=yes
add topics=info,!fetch

Posted: **Wed Dec 20, 2023 11:46 am**

Hmmm... all my fetch scripts works well without ftp policy. WDIDW?

Also how to disable this new fetch logging?
Code: Select all
/system logging
set 0 disabled=yes
add topics=info,!fetch

I just edited default info rule. Is it correct?

Posted: **Wed Dec 20, 2023 11:48 am**

Code: Select all
/system logging
set 0 disabled=yes
add topics=info,!fetch
I just edited default info rule. Is it correct?

Yes.
You have already added it in the new rule

Posted: **Wed Dec 20, 2023 1:44 pm**

Hi Everyone,

So I spent a bit of time moving one of my to hAPac2's to the new wave2 firmware and then setting up CAPsMAN for the Wave2 on my RB3011 to control it, everything works except when an iphone tries to connect, works fine on the old CAPsMAN with the old firmware but will not associate with the new wave2.

Android, Linux, Windows, even the Google Chromecast with Google TV was fine. iphone just did not get past initial connection.

Tried even locking it back to 20Mhz channels, has anyone seen similar behavior?

Kind Regards,
Jim.

Posted: **Wed Dec 20, 2023 3:26 pm**

Can you create a new topic and add your config to it, @jimmer?

Posted: **Wed Dec 20, 2023 3:43 pm**

IDK if someone else agrees but Mikrotik Versioning is broken.

It happened before with 7.10 where "They" released as stable a beta software, where lot of features where broken, like openvpn, and now they are pushing 7.13 which changes the drivers paradigm which, IMO, it should be a MAJOR VERSION, e.g. 8.0.0 instead of 7.13.

Now my old devices are not supported, and will not have any security updates after 7.12.1

Very dissapointed about this development movement...

Posted: **Wed Dec 20, 2023 3:48 pm**

Now my old devices are not supported, and will not have any security updates after 7.12.1

Why do you think so? That's simply not true.

Posted: **Wed Dec 20, 2023 3:49 pm**

should there be a wifi menu on a device with no wifi hardware? (RB750GR2 updated from 7.12.1)

I understand the need for wireless menu if using capsman but not the wifi menu. I assume I am now able to remove the wireless package if not using capsman?
I have removed it to test and the wireless menu disappears as expected but I still have the Wifi menu

Posted: **Wed Dec 20, 2023 3:55 pm**

Now my old devices are not supported, and will not have any security updates after 7.12.1
Why do you think so? That's simply not true.

https://help.mikrotik.com/docs/display/ ... %27package

Incompatible 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

Lost features
The following notable features are lost when running 802.11ac products with drivers that are compatible with the 'wifi' management interface

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

News for you, I have many MIPSBE devices, and I use those "lost" features....

Posted: **Wed Dec 20, 2023 3:58 pm**

I understand the need for wireless menu if using capsman but not the wifi menu. I assume I am now able to remove the wireless package if not using capsman?
I have removed it to test and the wireless menu disappears as expected but I still have the Wifi menu

capsman for wave2/wifi is part of main bundle and hence wifi menu will always be present. wireless package contains legacy wireless drivers and legacy capsman. If you don't need either of them, then it's fine to remove wireless package altogether.

Posted: **Wed Dec 20, 2023 3:59 pm**

News for you, I have many MIPSBE devices, and I use those "lost" features....

mipsbe devices don't qualify for wave2/wifi drivers, so you have to keep using legacy wireless package. And that one provides all the "lost" features, so don't worry, you can still use them.

Posted: **Wed Dec 20, 2023 4:07 pm**

News for you, I have many MIPSBE devices, and I use those "lost" features....
mipsbe devices don't qualify for wave2/wifi drivers, so you have to keep using legacy wireless package. And that one provides all the "lost" features, so don't worry, you can still use them.

Well, when using old products with the old drivers at least you "lose" the functionality of winbox remembering the window settings for your wireless menus... because apparently it confuses the old and new wireless menus, just like the users do.

Posted: **Wed Dec 20, 2023 4:10 pm**

should there be a wifi menu on a device with no wifi hardware? (RB750GR2 updated from 7.12.1)

I think no, but MikroTik think yes. So that is what we have.
It also takes space on devices that already are very short on space.
And having both the old and new wireless menus on the same device is all the more frustrating on e.g. the RB4011 where only one of them can work (it has both WiFi supported by the old driver and only the 5GHz supported by the new driver).

Posted: **Wed Dec 20, 2023 4:26 pm**

you "lose" the functionality of winbox remembering the window settings for your wireless menus... because apparently it confuses the old and new wireless menus,

I guess this is fixed in 7.14, changelog says menu was renamed.

Posted: **Wed Dec 20, 2023 6:05 pm**

should there be a wifi menu on a device with no wifi hardware? (RB750GR2 updated from 7.12.1)
I think no, but MikroTik think yes. So that is what we have.
It also takes space on devices that already are very short on space.
And having both the old and new wireless menus on the same device is all the more frustrating on e.g. the RB4011 where only one of them can work (it has both WiFi supported by the old driver and only the 5GHz supported by the new driver).

I just hope, once the situation settles, that WiFi gets renamed to Wireless. I somehow don't like that word at all. But that would mean even more confusion. Let's give it another 1-2 years, where everybody forgets pre wave2 era :-)

Posted: **Wed Dec 20, 2023 7:09 pm**

News for you, I have many MIPSBE devices, and I use those "lost" features....

"Legacy" wireless package is still available for MIPSBE devices, is fully supported and (as I understand) will keep receiving security fixes. And there are no "lost feature" in the legacy wireless package as compared to what you had in versions before 7.13.

Posted: **Wed Dec 20, 2023 10:29 pm**

Hi, I have updated my hAP ac2 and switched to wifi-qcom-ac drivers.
Seems there is problem with my old ipad mini 2 running software version 12.5.7. Ipad is unable to connect to wifi network, it is reporting invalid password.
But password is correct. Androids works ok, windows 10 ok, even old rpi connects ok.

AP shows only this in log:

debug: 6C:70:9F:1F:49:86@wifi5g associated, signal strength -80
debug: 6C:70:9F:1F:49:86@wifi5g disassociated, connection lost, signal strength -80

Can somebody confirm that olders apple devices works with this wifi-qcom-ac drivers. Then it may be some config issue, but I am not sure what it can be, when other OS works ok.

Posted: **Wed Dec 20, 2023 10:59 pm**

DNS DoH Error

Hello everyone, after updating to version 7.13 I am now increasingly getting the error message: DoH server connection error: remote disconnected while in HTTP exchange

I use a 5009 router, before that it was version 7.12.1, in this version I never saw the error message.

Secure DNS works as far as can be seen, no failures, just the sporadic error message. About 5 -10 per day.
Has anyone had similar experiences? No settings was changed only install the update ...

Posted: **Wed Dec 20, 2023 11:15 pm**

About 5 -10 per day.
Has anyone had similar experiences?

You are not alone. If you are on Cloudflare I noticed the same thing.

DoH.png

Posted: **Thu Dec 21, 2023 10:52 am**

About 5 -10 per day.
Has anyone had similar experiences?
You are not alone. If you are on Cloudflare I noticed the same thing.
DoH.png

Yes, I also use Cloudflare for this.
Then it's probably a general problem.

Posted: **Thu Dec 21, 2023 11:00 am**

Hi, I have updated my hAP ac2 and switched to wifi-qcom-ac drivers.
Seems there is problem with my old ipad mini 2 running software version 12.5.7. Ipad is unable to connect to wifi network, it is reporting invalid password.
But password is correct. Androids works ok, windows 10 ok, even old rpi connects ok.

AP shows only this in log:
Code: Select all
debug: 6C:70:9F:1F:49:86@wifi5g associated, signal strength -80
debug: 6C:70:9F:1F:49:86@wifi5g disassociated, connection lost, signal strength -80
Can somebody confirm that olders apple devices works with this wifi-qcom-ac drivers. Then it may be some config issue, but I am not sure what it can be, when other OS works ok.

Disable WPA3. I have same problem with older apple devices with any AP vendor not only Mikrotik.

Posted: **Thu Dec 21, 2023 11:34 am**

L41G-2axD&FG621-EA still has "LTE SIM locked after reboot" problem while modem firmware is up to date.

viewtopic.php?p=1043521

SUP-138300

Posted: **Thu Dec 21, 2023 12:08 pm**

Is anyone trying IS-IS cli? is it good?
I did a quick lab on the rc version (only between ros devices) and so far.. it was ok.
I had no time to test interoperability, it will be my next move.

Other routing protocols ( BGP, OSPF ) cannot redistribute IS-IS routes

Posted: **Thu Dec 21, 2023 12:33 pm**

Other routing protocols ( BGP, OSPF ) cannot redistribute IS-IS routes

I wonder if they did it on purpose, like you're on parole, so don't hang out with your mates... yet ;-)

Posted: **Thu Dec 21, 2023 2:01 pm**

My RB5009 also reboots once in 1-2 days of uptime since 7.13. Openvpn & wireguard enabled on the device.

Same with me.

This is my 2nd problem with v7.x.x update on New Arm Device.
Previously, in v7.11.1 My HAP AX3 wifi stop working after 1-2 hours. (Later Fixed with v7.12)
Now My RB5009 keeps rebooting every day (2-4 hours interval).

It seem like v7 "Stable" Release Channel is not stable after all.

Please MTik, Provide us (New Arm Device User) with Long-Term Release Channel.

Posted: **Thu Dec 21, 2023 2:19 pm**

Hi, I have updated my hAP ac2 and switched to wifi-qcom-ac drivers.
Seems there is problem with my old ipad mini 2 running software version 12.5.7. Ipad is unable to connect to wifi network, it is reporting invalid password.
But password is correct. Androids works ok, windows 10 ok, even old rpi connects ok.

AP shows only this in log:
Code: Select all
debug: 6C:70:9F:1F:49:86@wifi5g associated, signal strength -80
debug: 6C:70:9F:1F:49:86@wifi5g disassociated, connection lost, signal strength -80
Can somebody confirm that olders apple devices works with this wifi-qcom-ac drivers. Then it may be some config issue, but I am not sure what it can be, when other OS works ok.
Disable WPA3. I have same problem with older apple devices with any AP vendor not only Mikrotik.

But WPA3 shows on network, even when WPA3-PSK is unchecked and FT (roaming) is enabled...
Now reading on reddit:
noticed that iOS devices are unable to connect with WPA2/WPA3-mixed mode networks when 802.11r/k is enabled. WPA2- or WPA3-only with fast roaming works. Or mixed mode without fast roaming works.

That is reason, why I have switched to new drivers, to finally have roaming working, WPA3 just as bonus. It is issue with old apple software or also with new devices?

Edit: Seems there is already forum about this problem! viewtopic.php?p=1040086#p1040086

Posted: **Thu Dec 21, 2023 2:20 pm**

It seem like v7 "Stable" Release Channel is not stable after all.

Please MTik, Provide us (New Arm Device User) with Long-Term Release Channel.

Once again, you are misunderstanding the meaning of the word "stable".
It means it is a release that is not being modified all the time (such as a beta or rc).
It does NOT mean that the functioning of the software is stable.

When you want stability in the software itself, the first thing to do is not upgrade so soon after new "stable" versions are released.
And preferably also wait for a .1 and even .2 release.

Posted: **Thu Dec 21, 2023 3:05 pm**

Any reason for http://upgrade.mikrotik.com/routeros/LATEST.7 to still say "7.12.1" ?

Posted: **Thu Dec 21, 2023 3:20 pm**

Any reason for http://upgrade.mikrotik.com/routeros/LATEST.7 to still say "7.12.1" ?

The reason likely is that all older versions first need to upgrade to 7.12.1 before upgrading further.
7.12 versions will probably fetch another URL or send a special parameter to indicate that they can go to 7.13+

Posted: **Thu Dec 21, 2023 3:24 pm**

But WPA3 shows on network, even when WPA3-PSK is unchecked and FT (roaming) is enabled...
Now reading on reddit:
noticed that iOS devices are unable to connect with WPA2/WPA3-mixed mode networks when 802.11r/k is enabled. WPA2- or WPA3-only with fast roaming works. Or mixed mode without fast roaming works.

That is reason, why I have switched to new drivers, to finally have roaming working, WPA3 just as bonus. It is issue with old apple software or also with new devices?

Such issues are quite common when enabling new options and expecting old devices to connect... Even when WPA2 with only 802.11r/k is enabled, there are devices that will no longer connect or will lose connection when they roam to another AP.
That is just a fact of life. WiFi standards are complicated and client software is often garbage.

Posted: **Thu Dec 21, 2023 3:48 pm**

Any reason for http://upgrade.mikrotik.com/routeros/LATEST.7 to still say "7.12.1" ?
The reason likely is that all older versions first need to upgrade to 7.12.1 before upgrading further.
7.12 versions will probably fetch another URL or send a special parameter to indicate that they can go to 7.13+

I checked and now the 7.13 version retrieves http://upgrade.mikrotik.com/routeros/NEWESTa7.stable instead. It returns 7.13 now.

Posted: **Thu Dec 21, 2023 5:57 pm**

After updating Wireless Wire Cube Pro(CubeG-5ac60aypair) to 7.13, the bridge is no longer available. The 60 GHz link picks up, but the traffic does not run (Access to the Slave is lost). To roll back to 7.12.1, you need to remove the wireless package

Posted: **Thu Dec 21, 2023 7:29 pm**

After updating Wireless Wire Cube Pro(CubeG-5ac60aypair) to 7.13, the bridge is no longer available. The 60 GHz link picks up, but the traffic does not run (Access to the Slave is lost). To roll back to 7.12.1, you need to remove the wireless package

It's bonding problem, solution for now is to remove wireless interfaces from bonding, remove bonding from bridge and add wireless interfaces to bridge on master and slave.

Posted: **Fri Dec 22, 2023 2:56 am**

It seem like v7 "Stable" Release Channel is not stable after all.

Please MTik, Provide us (New Arm Device User) with Long-Term Release Channel.
Once again, you are misunderstanding the meaning of the word "stable".
It means it is a release that is not being modified all the time (such as a beta or rc).
It does NOT mean that the functioning of the software is stable.

When you want stability in the software itself, the first thing to do is not upgrade so soon after new "stable" versions are released.
And preferably also wait for a .1 and even .2 release.

I think what was meant here is that new ARM devices are sold with preinstalled v7 and users are naturally just hit "update". And telling users "hey that's not meant to be stable" is not the way to go. Ppl paid money not for being beta testers.

So I do agree that since there are devices sold with v7 it need an LTS channel.

And all the moves towards being more user-friendly with all the mobile apps bells and whistles are just got wasted. Btw, the app doesn't show the wireless menu so you cannot configure legacy drivers from there anymore.

Posted: **Fri Dec 22, 2023 6:07 am**

my LTE doesn't work since i upgraded to 7.13.

It was working perfectly fine on previous versions

Posted: **Fri Dec 22, 2023 7:41 am**

After upgrade on hap ac2 I have zero space left and I can't even make a backup. How I can save some space? In package list there is a routeros and wireless packages,

My ac2 has the same issue, as I use the routeros package to upgrade first and then look for wifi-qcom-ac to add wifi but even with 16% still have no luck

Screenshot 2023-12-22 123714.png

Posted: **Fri Dec 22, 2023 8:17 am**

Try to remove some files if you have them. My 3 hap ac2 all upgraded without problems. Also Wap AC and AC3.

Posted: **Fri Dec 22, 2023 8:17 am**

my LTE doesn't work since i upgraded to 7.13.

It was working perfectly fine on previous versions

Device?

Posted: **Fri Dec 22, 2023 8:20 am**

Try to remove some files if you have them. My 3 hap ac2 all upgraded without problems. Also Wap AC and AC3.

by looking thru the Files, seems I can see any file on it so I still unable to install wireless package. Can you please show me some ways to check for any remain files ? Thanks

Posted: **Fri Dec 22, 2023 8:28 am**

Try to remove some files if you have them. My 3 hap ac2 all upgraded without problems. Also Wap AC and AC3.
by looking thru the Files, seems I can see any file on it so I still unable to install wireless package. Can you please show me some ways to check for any remain files ? Thanks

Any optional packages installed consume flash storage ... and 7.13 does require more space than 7.12, on ARM platform and 16MB flash only base package (routeros) and newly introduced wireless driver packages (wireless or wifi-qcom or wifi-qcom-ac) use up almost all flash space. No room for any other optional package.

Posted: **Fri Dec 22, 2023 8:41 am**

It looks like you will need to netinstall it. You have 2,5 MB of space and qcom ac driver is arround 2,9 MB. Interesting, that there are such differences between the same devices.

Posted: **Fri Dec 22, 2023 8:44 am**

by looking thru the Files, seems I can see any file on it so I still unable to install wireless package. Can you please show me some ways to check for any remain files ? Thanks

Have a look at configurations like large IP address lists and/or the certificates stored in the device, especially CA cert bundles. These may take up a considerable amount of storage as well.

Worst case: Netinstall and carefully reconfigure from export (_not_ backup). While time consuming, this will free up as much as possible.

Posted: **Fri Dec 22, 2023 8:51 am**

It looks like you will need to netinstall it. You have 2,5 MB of space and qcom ac driver is arround 2,9 MB. Interesting, that there are such differences between the same devices.

If device is upgraded from 7.12.1 to 7.13, then initially there will be wireless package installed. The second step is then to uninstall wireless and install wifi-qcom-ac. And the second step will end up with even less free flash space (200kB IIRC). So if already upgrade is failing, then there's quite a lot of space to be freed before wifi drivers can be installed.

Posted: **Fri Dec 22, 2023 9:26 am**

It looks like you will need to netinstall it. You have 2,5 MB of space and qcom ac driver is arround 2,9 MB. Interesting, that there are such differences between the same devices.

yes, that's what I've just done with my `bricked` ac2 with netinstall and now I manage to have both routeros and wifi-qcom-ac packages.

p/s. turns out, after using new version 7.13 with wifi-qcom-ac, there is no available storage so additional config like DoH can not be saved. Those settings cannot be kept and the Ac2 also significant hot with wireless. I decided to keep no-wifi and new routeros only.

Posted: **Fri Dec 22, 2023 9:30 am**

I tested this version on my CCR 1016 where MPLS and VPLS {LDP} is running. After 3 to 5 minutes router reboots and it keeps repating over and over. On version 7.12.1 everything is ok. Has anyone same experience? No error in log.
This same, but reboots about 10 seconds.

This morning I've updated a CCR2004 with MPLS/VPLS, LDP. The router has restarted in less than 1 minute. Downgraded to 7.12.1 seems to be stable.

Posted: **Fri Dec 22, 2023 10:42 am**

I have not tried it myself, but I think there have been user reports that you need a dedicated CA for each CAPsMAN to make them co-exist. Is that true for you?

I run "old" CAPsMAN for my cAP-ac with VLAN config and the "new" CAPsMAN for my cAP-ax with VLAN config in one CCR.
Both work good, but I think they are "isolated" things, regarding roaming and such stuff. Dont think old one tells new one, "bro, a device registered by me is coming in your region soon..." or vice versa.

For the "new" CAPsMAN, the auto-generated certs have to stay there. The CAPsMAN-system (the new one) doesnt work, if the certs are deleted, even if the CAPs (clients) should not look/verify for the CAPsMAN-certs.They (CAPs) log "unable to connect" or so, dont remember the exact wording...

Posted: **Fri Dec 22, 2023 10:51 am**

Cap AC is an ARM device, so you can use qcom ac driver on it and use only new Capsman. But there will be some adjustments needed considering VLANs.

Posted: **Fri Dec 22, 2023 11:04 am**

I have not tried it myself, but I think there have been user reports that you need a dedicated CA for each CAPsMAN to make them co-exist. Is that true for you?
I run "old" CAPsMAN for my cAP-ac with VLAN config and the "new" CAPsMAN for my cAP-ax with VLAN config in one CCR.
Both work good, but I think they are "isolated" things, regarding roaming and such stuff. Dont think old one tells new one, "bro, a device registered by me is coming in your region soon..." or vice versa.

Old capsman doesn't even tell itself about device about to roam ... the r/k/v/... doesn't exist in old capsman at all.

If you had new capsman on two devices, each controlling par to CAP fleet, roaming between them would not be seamless as well ... roaming only works well if both originating and destination radios are both controlled by same wave2/wifi instance (which means same capsman with capsman device's local wave2 radios as well ... even though technically they are not provisioned by capsman).

Posted: **Fri Dec 22, 2023 11:23 am**

This same, but reboots about 10 seconds.
This morning I've updated a CCR2004 with MPLS/VPLS, LDP. The router has restarted in less than 1 minute. Downgraded to 7.12.1 seems to be stable.

Opened support ticket SUP-138412

Posted: **Fri Dec 22, 2023 11:34 am**

I did the update to RouterOS 7.13 on my RB5009 yesterday.
So far everything has gone well.

Today, however, when I tried to connect to my home network via Wireguard
I found that I couldn't get a connection.

After a check, I realized that the router has problems reaching IPv6 addresses.
When updating via IPv64, only the IPv4 is updated.

If I call up the IP check from DeDyn, for example, I get this error:

[admin@MikroTik] > /tool fetch url="https://checkipv6.dedyn.io/" mode=https src-path="/" dst-path="/deSEC-IPv6.txt"
  status: failed

failure: resolving error

Interestingly, the nslookup still seems to work, because ...

[admin@MikroTik] > put [:resolve checkipv6.dedyn.io]           
2a01:4f8:10a:1044:deec:642:ac10:8

But what also works is the ping.

[admin@MikroTik] > ping 2a01:4f8:10a:1044:deec:642:ac10:80
  SEQ HOST                                     SIZE TTL TIME       STATUS                                                                                                                                       
    0 2a01:4f8:10a:1044:deec:642:ac10:80         56  59 14ms73us   echo reply                                                                                                                                   
    1 2a01:4f8:10a:1044:deec:642:ac10:80         56  59 13ms968us  echo reply                                                                                                                                   
    2 2a01:4f8:10a:1044:deec:642:ac10:80         56  59 13ms962us  echo reply                                                                                                                                   
    3 2a01:4f8:10a:1044:deec:642:ac10:80         56  59 14ms195us  echo reply

Has anyone here also noticed the problem after the update?

- Yes, the router has already been restarted several times
- Yes IPv6 seems to work, otherwise there is no ping
- My computer behind it in the home network can also use IPv6 without stress (I have pi-holes for DNS)
- The router is supposed to learn the DNS servers from the ISP (ticked for this)

Posted: **Fri Dec 22, 2023 11:37 am**

Device?

HUAWEI
E3372h -507

Posted: **Fri Dec 22, 2023 11:40 am**

Not realy sure what you mean with LTE not working and device Huawei. Maybe i misunderstood something.

Posted: **Fri Dec 22, 2023 11:48 am**

If I call up the IP check from DeDyn, for example, I get this error:

Yes, this is a problem where fetch fails with ipv6-only addresses. Reported as SUP-134908. Received any answer and support as aware, but no solution, yet.

Posted: **Fri Dec 22, 2023 11:56 am**

If I call up the IP check from DeDyn, for example, I get this error:
Yes, this is a problem where fetch fails with ipv6-only addresses. Reported as SUP-134908. Received any answer and support as aware, but no solution, yet.

Okay, thanks for the info. At least a bug has already been recognized here and they are (hopefully) working on a solution :)
Then I'll wait until then and only use IPv4.

Posted: **Fri Dec 22, 2023 12:57 pm**

After the upgrade, there is no free disk space and the router forgets the settings after a reboot. There is also no way to make a backup.
Device: hAP ac^2

Posted: **Fri Dec 22, 2023 1:19 pm**

After the upgrade, there is no free disk space and the router forgets the settings after a reboot. There is also no way to make a backup.
Device: hAP ac^2

Clearly not enough space then.
Netinstall using only routeros package to make it as clean as possible but make sure to export your config first using show-sensitive (export, not backup).
Move that file to your PC. Have a look at it to see it's complete (passwords etc.)
Netinstall
Then load wireless-qcom-ac package on AC2.
Import config again bit by bit, reviewing settings which are already there.
Obviously, you need to redo the complete wifi-part under the new menu structure, use the exported info as guideline.

Posted: **Fri Dec 22, 2023 1:25 pm**

After the upgrade, there is no free disk space and the router forgets the settings after a reboot. There is also no way to make a backup.
Device: hAP ac^2

The fasted solution for this is a netinstall of your device. (as metioned already several times in this thread).

I also did a netinstall on my device and everything is working flawless with the qcom-ac device driver. And yes not much room left for other packages i.e. zerotier can not be installed anymore after installing the qcom drivers. I'm using the ac2 just as an access point and have a RB4011 as main router on which I have installed zerotier.

Posted: **Fri Dec 22, 2023 1:40 pm**

And yes not much room left for other packages i.e. zerotier can not be installed anymore after installing the qcom drivers. I'm using the ac2 just as an access point and have a RB4011 as main router on which I have installed zerotier.

Even with "wireless" on the hAP ac2 there is almost no space, probably because (for unclear reasons) the base part of the new WiFi is already part of the routeros package, so after upgrade you have two different wireless admin menus, one of them sitting unused.
In version 7.12.1 the space on hAP ac2 was already quite low (1MB) and the 7.13 version will make it worse.

For now I remain on 7.12.1

Posted: **Fri Dec 22, 2023 2:27 pm**

Sorry, the more I read the more confused I get.

My AP network consists currently of
1 RB4011 (used also as CAPsMAN)
1 HAP ac2 (CAP)
1 HAP ax3 (supposed to be CAP but not possible (yet); therefore configured standalone)

After update of the AC2 I have routeros + wireless installed and all seems to work fine.
Still interested to get some features from wifi_qcom_ac but there are questions:
- is my assumption correct that the CAPsMAN from RB4011 won't be able to manage the AC2 anymore?
- what happens when I update the RB4011 to 7.13. Would it change anything with regards to CAPsMAN?
- what happens when I switch the RB4011 to wifi_qcom_ac? I would lose the 2,4GHz band? And what would be the thing with CAPsMAN? Would it be able to control the AX3 and AC2 (when running with qcom_ac)?

Posted: **Fri Dec 22, 2023 2:49 pm**

@woro: there are two versions of capsman: legacy which can provision CAPs with legacy wireless (currently your hAP ac2) and wave2/wifi, which can control CAPs with new wave2/wifi (currently your hAP ax3).

There's a problem with wireless version of RB4011 running new drivers, but I'll assume you have the wireless-less RB4011. In this case there's no stopping you from upgrading all your devices to 7.13. You'll be able to uninstall wireless package from RB4011 and hAP ac2, install wifi-qcom-ac on hAP ac2 (and keep wifi-qcom on hAP ax3). This will then allow you to confiugre RB4011 as new capsman which will be able to run both your APs.

If your RB4011 actually does have wireless ... then yes, you are choosing between having both 2.4GHz and 5GHz bands available (in theory you should be able to run both capsman verisons on single RB4011 but this doesn't seem to work right now) and having only 5GHz band available (but the 5GHz will run much better and single capsman will be able to control all devices helping with roaming performance)

Posted: **Fri Dec 22, 2023 3:07 pm**

@mkx: sorry for being unspecific. I'm using the RB4011 also as CAP for both bands right now (the APs are all distributed over the different floors) and I'm also not very keen in losing 2.4G in one of them. (Also trying to limit number of devices due to power consumption.)
But what I understand is that I can
- switch AC2 to wifi5/wave2
- update RB4011 to 7.13 (keeping wireless)
- can manage the AX3 and AC2 with new capsman (included in routeros package) in theory (but you are saying it's not working right now?)
If the latter works (or works soon) it still would be better because roaming between AX3 and AC2 is more important than with RB4011. So I could run the RB4011 radios standalone (like I do with AX3 right now) instead.

Posted: **Fri Dec 22, 2023 4:19 pm**

Yes, the RB4011 functionality you want (capsman for wave2/wifi caps and local wireless) is supposed to work. Even if some users reported issues, it's a supposedly supported configuration and I believe that MT will iron out any glitches eventually. If you feel adventureous, then you can try it now. If not, then wait for 7.14 or 7.15.

Posted: **Fri Dec 22, 2023 7:03 pm**

DHCP Server behavior:
Have a DHCP-Reservation for a device. Its in the leases and inactive.
Device requests an IP and gets something in the pool.
Enable Reservation and Reboot device.
Device is handed the Dynamic address.
This continues until you delete the Dynamic lease.
The next DHCP request will prompt the proper DHCP Reservation.

Posted: **Fri Dec 22, 2023 7:57 pm**

7.13 with wifi-qcom-ac here on Chateau LTE12 since last saturday already. I am very pleased. With legacy wireless I had to work with access-lists to force devices to use 5g by disallowing 2g for good 2g signal conditions. On old wireless drivers devices kept preferring 2g and basically no device switched over to 5g. What a pain it was to find the "sweet spot" (signal range) for the access-list range-setting and it kind of worked well in the end. After tinkering back then. But it was still not perfect, as devices kept 5g connection until they lost signal.

But now, 802.11r/k seems to do the job pretty well. Enabled FT (ft=yes ft-over-ds=yes) and devices roam like a charm.

Wifi signal and RSSI reported on the devices (where available) did not change. But that is maybe just physics I (or MT) can't change by software/drivers.

Overall: thumbs up MT!

Posted: **Fri Dec 22, 2023 7:58 pm**

I've the same problems with Huawei H3372-153 LTE modem. In the System>Resources>USB menu device is listed, but interface is not usable.
Downgraded to 7.12.1 and it works ok.
Device: RB5009 (v1)

Posted: **Sat Dec 23, 2023 12:06 am**

I update one pair of LHG 52ac and other pair LHG 5 ac XL, outdoor on link couple km, with new WifiWave2 drivers.
First impression is working better in test have better speed, TX and RX rate are more stable.

Bad thing
Something is not right with signal strength, before update has been around -50 now is -74. Check power it is the maximum like before.
It is not possible to scan nearby frequencies just frequencies define by country.
Not possible to selected other frequencies just define by country selection.

Anyone other tested on some outdoor links ?

Posted: **Sat Dec 23, 2023 1:27 am**

Also I think the cpu start to be more utilised ? in profile the most cpu usage is "unclasified" is someone notice something simillar with 7.13 ?

Yes, on a few Hex models, and RB5009UG, CPU is frozen on 350Mhz and doesnt change, i have also netinstalled it back with factory setting to test & its still the same. After downgrading to 7.12 everything is good.

Posted: **Sat Dec 23, 2023 3:18 pm**

After the upgrade, there is no free disk space and the router forgets the settings after a reboot. There is also no way to make a backup.
Device: hAP ac^2
The fasted solution for this is a netinstall of your device. (as metioned already several times in this thread).

I also did a netinstall on my device and everything is working flawless with the qcom-ac device driver. And yes not much room left for other packages i.e. zerotier can not be installed anymore after installing the qcom drivers. I'm using the ac2 just as an access point and have a RB4011 as main router on which I have installed zerotier.

I know what to do. This message is feedback. The Mikrotik company must understand that with each such release it loses the loyalty of its customers.

Posted: **Sat Dec 23, 2023 3:27 pm**

Then load wireless-qcom-ac package on AC2.

RouterOS version 7.13 have been released in the "v7 stable" channel!

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.

I do not need wifi-qcom-ac for hAP ac^2

Posted: **Sat Dec 23, 2023 3:33 pm**

There are no loyalty problems. The one who knows why Mikrotik will use it no matter what. Those are already quite old devices but they still tried and offered us solution for them to achieve much better Wifi speeds then before. I had zero problems for now on all devices, Hap Ac² (5 devices), Ac³, Wap Ac, 5009 and Cap Ax. I still must upgrade one Hap Ac² and Ac³ that are on remote locations.

Posted: **Sat Dec 23, 2023 3:54 pm**

I do not need wifi-qcom-ac for hAP ac^2

And yet you do IF you want to have wave2 drivers on AC2.
No qcom-ac = no wave2. Simple.

If you want to stay on legacy wifi, then you only need base ROS and wireless.

Posted: **Sat Dec 23, 2023 11:40 pm**

hap ax2 - boot loop after upgrade from 7.12.1
with or without wifiwave2 package installed
the only way out is netinstall + restore

Posted: **Sun Dec 24, 2023 12:46 pm**

I do not need wifi-qcom-ac for hAP ac^2
And yet you do IF you want to have wave2 drivers on AC2.
No qcom-ac = no wave2. Simple.

If you want to stay on legacy wifi, then you only need base ROS and wireless.

Yes, I want stay on legacy because need a capsman

Posted: **Mon Dec 25, 2023 12:24 pm**

With wave2 you can also have capsman and with much better performance than the old capsman

Posted: **Mon Dec 25, 2023 12:38 pm**

With wave2 you can also have capsman and with much better performance than the old capsman

WifiWave2 CAPsMAN can only control WifiWave2 interfaces, and WifiWave2 CAPs can join only WifiWave2 CAPsMAN, similarly, regular CAPsMAN only supports non-WifiWave2 caps.

Posted: **Mon Dec 25, 2023 4:22 pm**

And yet you do IF you want to have wave2 drivers on AC2.
No qcom-ac = no wave2. Simple.

If you want to stay on legacy wifi, then you only need base ROS and wireless.
Yes, I want stay on legacy because need a capsman

It doesn't look like the legacy works well, I have constant disconnects with 7.13, looks like it is mostly on audience devices. Also still can't make both CAPsMANs work on the same 4011, so I'm starting to consider a downgrade. :(

Posted: **Mon Dec 25, 2023 6:57 pm**

About 5 -10 per day.
Has anyone had similar experiences?
You are not alone. If you are on Cloudflare I noticed the same thing.
DoH.png

The same issue "DoH server connection error: Idle timeout - waiting data" with Cloudflare Doh after upgrade to v7.13

Posted: **Tue Dec 26, 2023 11:12 am**

I have 2 hap ac2 and 2 hap ax2.
If i will upgrade to 7.13, the wireless packages of ac2 will be upgraded to the new drivers packages or i have to manually install them? if upgraded automatically will it keep all my confgurations? what if i have to installed them manually? do i have to reconfigure all my wifis from scratch?

Sorry tried to read all the 2 pages here and i am more confused than ever.

In any case a regular user wants the wifi to be upgraded to the newest version (new drivers etc) without reconfigure all from scratch. is it the case here?

Posted: **Tue Dec 26, 2023 11:29 am**

If i will upgrade to 7.13, the wireless packages of ac2 will be upgraded to the new drivers packages or i have to manually install them?

Manually.

do i have to reconfigure all my wifis from scratch?

Yes, you do.

Posted: **Tue Dec 26, 2023 11:45 am**

If i will upgrade to 7.13, the wireless packages of ac2 will be upgraded to the new drivers packages or i have to manually install them?
Manually.

do i have to reconfigure all my wifis from scratch?
Yes, you do.

Thanks so much for the quick reply.

Posted: **Tue Dec 26, 2023 3:09 pm**

In any case a regular user wants the wifi to be upgraded to the newest version (new drivers etc) without reconfigure all from scratch. is it the case here?

Though you have to start all over, you could consider CAPsMAN (assunming all 4 Tiks are part of the same network).

Posted: **Tue Dec 26, 2023 5:37 pm**

Meanwhile, I wanted to thank Mikrotik for bringing the new wifi drivers to devices like HAP AC2-AC3.

If I can advise developers to reevaluate developing ROS v7 as a single package but instead as multiple packages like ROS v6 that would be perfect. I use the Zerotier package for testing purposes which I will not be able to maintain with the new wifi package on AC2, I will do without Zerotier but sorry.

Question: I have a network with two AC2s, one as a router and one as an access point via ethernet. If I want to finally have roaming between them, do I just need to install the new wifi driver or do I also have to use Capsman?

Do you recommend Capsman for two AC2? (home use)

Posted: **Tue Dec 26, 2023 6:48 pm**

Question: I have a network with two AC2s, one as a router and one as an access point via ethernet. If I want to finally have roaming between them, do I just need to install the new wifi driver or do I also have to use Capsman?

For 802.11k/r/v CAPsMAN is a must.

Do you recommend Capsman for two AC2? (home use)

I do. I use it with ac3 + Audience and it works really nice here.

Posted: **Tue Dec 26, 2023 10:54 pm**

I have a Xiaomi Humidifier, and after upgrade to new CAPsMAN, I see this in log:

 21:38:06 wireless,info 58:B6:23:0A:5B:74@cap-Zal-Sky-IoT connected, signal strength -63
 21:38:06 dhcp,info LAN deassigned 100.64.3.201 for 58:B6:23:0A:5B:74 zhimi-humidifier-ca4_mibt5B74
 21:38:06 dhcp,info LAN assigned 100.64.3.201 for 58:B6:23:0A:5B:74 zhimi-humidifier-ca4_mibt5B74
 21:38:08 wireless,info 58:B6:23:0A:5B:74@cap-Zal-Sky-IoT disconnected, connection lost, signal strength -63
 21:38:21 wireless,info 58:B6:23:0A:5B:74@cap-Zal-Sky-IoT connected, signal strength -62
 21:38:21 dhcp,info LAN deassigned 100.64.3.201 for 58:B6:23:0A:5B:74 zhimi-humidifier-ca4_mibt5B74
 21:38:21 dhcp,info LAN assigned 100.64.3.201 for 58:B6:23:0A:5B:74 zhimi-humidifier-ca4_mibt5B74
 21:38:24 wireless,info 58:B6:23:0A:5B:74@cap-Zal-Sky-IoT disconnected, connection lost, signal strength -62
 21:38:31 wireless,info 58:B6:23:0A:5B:74@cap-Zal-Sky-IoT connected, signal strength -62
 21:38:32 dhcp,info LAN deassigned 100.64.3.201 for 58:B6:23:0A:5B:74 zhimi-humidifier-ca4_mibt5B74
 21:38:32 dhcp,info LAN assigned 100.64.3.201 for 58:B6:23:0A:5B:74 zhimi-humidifier-ca4_mibt5B74
 21:38:34 wireless,info 58:B6:23:0A:5B:74@cap-Zal-Sky-IoT disconnected, connection lost, signal strength -64
 21:38:53 wireless,info 58:B6:23:0A:5B:74@cap-Zal-Sky-IoT connected, signal strength -65
 21:38:53 dhcp,info LAN deassigned 100.64.3.201 for 58:B6:23:0A:5B:74 zhimi-humidifier-ca4_mibt5B74
 21:38:53 dhcp,info LAN assigned 100.64.3.201 for 58:B6:23:0A:5B:74 zhimi-humidifier-ca4_mibt5B74
 21:38:55 wireless,info 58:B6:23:0A:5B:74@cap-Zal-Sky-IoT disconnected, connection lost, signal strength -66
 21:39:03 wireless,info 58:B6:23:0A:5B:74@cap-Zal-Sky-IoT connected, signal strength -64
 21:39:03 dhcp,info LAN deassigned 100.64.3.201 for 58:B6:23:0A:5B:74 zhimi-humidifier-ca4_mibt5B74
 21:39:03 dhcp,info LAN assigned 100.64.3.201 for 58:B6:23:0A:5B:74 zhimi-humidifier-ca4_mibt5B74
 21:39:05 wireless,info 58:B6:23:0A:5B:74@cap-Zal-Sky-IoT disconnected, connection lost, signal strength -64

I can even ping the device for a few seconds when it's connected. And after a few hours, it finally connects and stays connected. Until I change WiFi settings or the device power plug is disconnected and reconnected back. Then "the process" starts again. Looks like Xiaomi Smart Desk Lamp has the same problem. WiFi is set up to use WPA2-PSK, no FT, just like it was on CAPsMAN v1... Any ideas?

Posted: **Wed Dec 27, 2023 1:25 am**

Maybe management-protection=disabled ?
Other parameters that I found are causing troubles between old devices and new drivers; connect-group, connect-priority, disable-pmkid

Posted: **Wed Dec 27, 2023 7:09 am**

Question: I have a network with two AC2s, one as a router and one as an access point via ethernet. If I want to finally have roaming between them, do I just need to install the new wifi driver or do I also have to use Capsman?

Do you recommend Capsman for two AC2? (home use)

There are two good explainatory videos now available for
new Capsman: https://www.youtube.com/watch?v=37aff6d14Xk
Fast Transition: https://www.youtube.com/watch?v=vkWPlsuyuKE

Posted: **Wed Dec 27, 2023 10:05 am**

Maybe management-protection=disabled ?

You're my hero! It worked! Thanks!

Posted: **Wed Dec 27, 2023 2:19 pm**

I'm trying to port my CAPsMAN v1 config to v2 but for whatever reason interfaces are not provisioned, while disabling CAPsMAN and using local configuration works just fine. Can't see any errors in the logs and can confirm that the CAP is joined:

/interface/wifi/radio/print
Flags: L - LOCAL
Columns: CAP, RADIO-MAC, INTERFACE
#   CAP                        RADIO-MAC          INTERFACE
0 L                            08:55:31:69:DA:DB  wifi1
1 L                            08:55:31:69:DA:DC  wifi2
2 L                            08:55:31:69:DA:DD  wifi3
3   RBD25G-LR-01@172.16.86.11  08:55:31:69:DA:DC
4   RBD25G-LR-01@172.16.86.11  08:55:31:69:DA:DB

Following is my config:

/interface wifi channel
add disabled=no frequency=2412,2437,2462 name=2.4ghz-channel width=20mhz
add disabled=no name=5ghz-channel
/interface wifi datapath
add bridge=bridge-local disabled=no name=datapath-cap
/interface wifi security
add authentication-types=wpa-psk,wpa2-psk connect-priority=0 disabled=no name=wifi-local
add authentication-types=wpa-psk,wpa2-psk connect-priority=0 disabled=no name=wifi-iot
add authentication-types=wpa-psk,wpa2-psk connect-priority=0 disabled=no name=wifi-guest
/interface wifi configuration
add channel=2.4ghz-channel country=Poland datapath=datapath-cap disabled=no mode=ap name=2.4ghz-wifi-local security=wifi-local security.connect-priority=0 ssid=Wi-Fi tx-power=10
add channel=5ghz-channel country=Poland datapath=datapath-cap disabled=no mode=ap name=5ghz-wifi-local security=wifi-local security.connect-priority=0 ssid=Wi-Fi tx-power=20
add channel=2.4ghz-channel country=Poland datapath=datapath-cap disabled=no mode=ap name=2.4ghz-wifi-iot security=wifi-iot security.connect-priority=0 ssid=IoT tx-power=10
add channel=5ghz-channel country=Poland datapath=datapath-cap disabled=no mode=ap name=5ghz-wifi-iot security=wifi-iot security.connect-priority=0 ssid="IoT - 5g" tx-power=20
add channel=2.4ghz-channel country=Poland datapath=datapath-cap disabled=no mode=ap name=2.4ghz-wifi-guest security=wifi-guest security.connect-priority=0 ssid="Wi-Fi Durin" tx-power=10
add channel=5ghz-channel country=Poland datapath=datapath-cap disabled=no mode=ap name=5ghz-wifi-guest security=wifi-guest security.connect-priority=0 ssid="Wi-Fi Durin" tx-power=20
/interface wifi
# managed by CAPsMAN
set [ find default-name=wifi1 ] configuration=2.4ghz-wifi-local configuration.manager=capsman-or-local .mode=ap disabled=no security.connect-priority=0
add configuration=2.4ghz-wifi-guest configuration.mode=ap disabled=no mac-address=0A:55:31:69:DA:DC master-interface=wifi1 name=wifi1-guest security.connect-priority=0
add configuration=2.4ghz-wifi-iot configuration.mode=ap disabled=no mac-address=0A:55:31:69:DA:DB master-interface=wifi1 name=wifi1-iot security.connect-priority=0
# managed by CAPsMAN
set [ find default-name=wifi2 ] configuration=5ghz-wifi-local configuration.manager=capsman-or-local .mode=ap disabled=no security.connect-priority=0
add configuration=5ghz-wifi-guest configuration.mode=ap disabled=no mac-address=0A:55:31:69:DA:DE master-interface=wifi2 name=wifi2-guest security.connect-priority=0
add configuration=5ghz-wifi-iot configuration.mode=ap disabled=no mac-address=0A:55:31:69:DA:DD master-interface=wifi2 name=wifi2-iot security.connect-priority=0
/interface wifi cap
set certificate=request discovery-interfaces=br-vlan86 enabled=yes
/interface wifi capsman
set ca-certificate=auto certificate=auto enabled=yes interfaces=br-vlan86 package-path="" require-peer-certificate=no upgrade-policy=suggest-same-version
/interface wifi provisioning
add action=create-dynamic-enabled disabled=no master-configuration=2.4ghz-wifi-local name-format=2G-%I slave-configurations=2.4ghz-wifi-iot,2.4ghz-wifi-guest supported-bands=2ghz-n
add action=create-dynamic-enabled disabled=no master-configuration=5ghz-wifi-local name-format=5G-%I slave-configurations=5ghz-wifi-iot,5ghz-wifi-guest supported-bands=5ghz-ac

Any hints?

Posted: **Wed Dec 27, 2023 2:25 pm**

If you're trying to provision wireless interfaces through capsman running on the same device ... then no, this is not supported any more, local wireless interfaces have to be provisioned "manually". But you can use exactly the same security profiles and sice local interfaces will be handled by the same wifi entity as capsman-provisioned ones, also mobility (802.12 r/k/v) will work fine.

Posted: **Wed Dec 27, 2023 2:58 pm**

First impression is working better in test have better speed, TX and RX rate are more stable.

How much better, the numbers

before update has been around -50 now is -74. Check power it is the maximum like before.

New parameter antenna-gain set to 0

Posted: **Wed Dec 27, 2023 2:59 pm**

If you're trying to provision wireless interfaces through capsman running on the same device ... then no, this is not supported any more, local wireless interfaces have to be provisioned "manually". But you can use exactly the same security profiles and sice local interfaces will be handled by the same wifi entity as capsman-provisioned ones, also mobility (802.12 r/k/v) will work fine.

Yes, those were local ifaces. Thank you for the clarification, I'll try upgrading another device and adding it to the CAPsMAN

Posted: **Wed Dec 27, 2023 3:54 pm**

This is getting annoying for me, it's the same error and reboots I had a few releases ago related with some OVPN issue.

Capture.JPG
Same behavior here - after updating my RB5009 to 7.13 I keep getting 1-2 reboots per day without sup and with "probably power outage" message in the log.
P.S. Running OVPN and Wireguard on this box.

I'm getting the same issue, running OVPN as client with TLS configuration. My RB5009 reboot like 3 time in the morning yesterday, so I just downgrade to 7.12.1 for now. And waiting for the next release to fix it I hope.
Btw the new :deserialize was working like a charm in the 7.13 :) This line reduce my script from 10 to 1 line

$request [:deserialize from=json ([/tool/fetch url=$url http-method=get output=user as-value]->"data")]

Posted: **Wed Dec 27, 2023 5:34 pm**

Something is not right with signal strength, before update has been around -50 now is -74

I have the same issue, but on hap ac3

Posted: **Wed Dec 27, 2023 8:08 pm**

I've set name-format=2G-%I- in the CAPsMAN provisioning, to have my interface names look as follows:

/interface/wifi/print
Flags: M - MASTER; D - DYNAMIC; B - BOUND
Columns: NAME, MASTER-INTERFACE
 #     NAME               MASTER-INTERFACE
 0 MDB 2G-RBD25G-LR-01-
 1  DB 2G-RBD25G-LR-01-2  2G-RBD25G-LR-01-
 2  DB 2G-RBD25G-LR-01-3  2G-RBD25G-LR-01-
 3 MDB 2G-RBcAP-
 4  DB 2G-RBcAP-2         2G-RBcAP-
 5  DB 2G-RBcAP-3         2G-RBcAP-
 6 MDB 5G-RBD25G-LR-01-
 7  DB 5G-RBD25G-LR-01-2  5G-RBD25G-LR-01-
 8  DB 5G-RBD25G-LR-01-3  5G-RBD25G-LR-01-
 9 MDB 5G-RBcAP-
10  DB 5G-RBcAP-2         5G-RBcAP-
11  DB 5G-RBcAP-3         5G-RBcAP-

This makes slave interface names more self-descriptive but also adds this extra hyphen to the master interface. Is there any way I could get rid of that extra hyphen?

Posted: **Wed Dec 27, 2023 8:19 pm**

Possible bug. Mikrotik android pro app do not show firewall filter roules on 7.13.

Posted: **Wed Dec 27, 2023 9:35 pm**

Possible bug. Mikrotik android pro app do not show firewall filter roules on 7.13.

Works on my phone, what Android version are you running?

Posted: **Wed Dec 27, 2023 10:06 pm**

your Android app is up2date? 1.3.32

Posted: **Wed Dec 27, 2023 10:56 pm**

Just got a reboot of my cAP ac

2023-12-27 01:55:10 system,error,critical router was rebooted without proper shutdown, probably kernel failure
2023-12-27 01:55:10 system,error,critical kernel failure in previous boot
2023-12-27 01:55:10 system,error,critical out of memory condition was detected

And autosupout.rif was generated.

It has a default config with CAP enabled. I now turned on Resource Graphing to monitor...

Is this memory usage okay for the wifi-qcom-ac package?..

              free-memory: 33.2MiB
             total-memory: 128.0MiB

Posted: **Wed Dec 27, 2023 11:04 pm**

I got a cAP AC running for 9 days now with qcom-ac package on it.
Free memory is still around 31Mb so your 33Mb looks inline with that.

Posted: **Wed Dec 27, 2023 11:18 pm**

Another cAP ac has uptime of 10 days and 22.4 MiB memory. But it has only a few clients...

Posted: **Wed Dec 27, 2023 11:21 pm**

Possible bug. Mikrotik android pro app do not show firewall filter roules on 7.13.
Works on my phone, what Android version are you running?

Android 14 UI6 Samaung. App is up to date, all in firewall menu show nornal, and all other is show normal, expect firewall filter rules.

Posted: **Thu Dec 28, 2023 11:33 am**

My cap ac xl WiFi leds doesn’t flashing anymore after installing 7.13 and WiFi-qcom-ac driver. Is this a bug or am I have to make setting about it. Capsman running on rb4011

Posted: **Thu Dec 28, 2023 1:28 pm**

My cap ac xl WiFi leds doesn’t flashing anymore after installing 7.13 and WiFi-qcom-ac driver. Is this a bug or am I have to make setting about it. Capsman running on rb4011

Mine is arriving this afternoon, I will let you know.

Posted: **Thu Dec 28, 2023 2:02 pm**

Posted: **Thu Dec 28, 2023 2:09 pm**

...
Is this memory usage okay for the wifi-qcom-ac package?..
Code: Select all
              free-memory: 33.2MiB
             total-memory: 128.0MiB

With wifi-qcom-ac mine lightly used cAP ac now has:

              free-memory: 28.1MiB
             total-memory: 128.0MiB

Which is roughly half of free memory (used to be around 54MiB free) when used with legacy drivers...
I am not sure this is OK, and I am now a bit afraid to upgrade other cAP acs that have much more clients...

Posted: **Thu Dec 28, 2023 2:35 pm**

Wave2 drivers require a lot more memory for buffers etc. so this might be normal.

Posted: **Thu Dec 28, 2023 2:39 pm**

I upgraded 2 x hAP ac2 to ROS 7.13 and wifi-qcom-ac. Both now have like 600KB free flash and around 28-32MB free RAM.

Posted: **Thu Dec 28, 2023 2:56 pm**

Bond interfaces (lacp) being bridge members stopped working (port state: disabled) on CCR on 7.13
Workaround1: disable (R)STP on bridge completely
Workaround2: downgrade to 7.12
Opened ticket SUP-138833

Posted: **Thu Dec 28, 2023 3:12 pm**

I have now upgraded 10+ hAP ac2/ac3 routers to 7.13 with qcom-ac package, all managed by their CAPsMANs (some of them are CAPsMANs, others are CAPs only). The problem is that configuring multiple SSIDs going to multiple bridges (since VLANs are not possible at the moment) is not working for me, no matter what I try.

I tried to follow https://help.mikrotik.com/docs/display/ ... iFiCAPsMAN, qcom-ac part, but it is simply wrong: both master and slave interfaces connected to same VLAN, one Datapath for everything, no (obvious?) connection between slave interfaces and slave configs...

I have also tried to create VLANs, bridges, datapaths, even slave Wlan interfaces manually on CAPs (which defies existence of CAPsMAN, but for testing it's OK), but upon connection to CAPsMAN new interface appears and goes to "default" bridge.

It seems that I don't understand the philosophy of this new CAPsMAN (maybe it is OK with AX devices and VLANs, but I don't have those). Can someone share WORKING configuration (both CAPsMAN and CAP) with two (and more, up to 4) SSIDs, connected to different bridges, for qcom-ac?

Thanks!

Posted: **Thu Dec 28, 2023 3:20 pm**

Have you seen the VLAN configuration example part of the URL you provided:
https://help.mikrotik.com/docs/display/ ... ionexample:

Think you should be able to get it to work by following that tutorial.

Posted: **Thu Dec 28, 2023 3:58 pm**

The modem huawei e3372h-153, like other users, does not work.
Will the bug be fixed in the next version?

Posted: **Thu Dec 28, 2023 3:59 pm**

Just to let everybody knows, I have reported (SUP-128622) a memory leak on version v7.11.2, that continued on v7.12, v7.12.1 and v7.13. It seems to me and my undestandings of the supout files provided data, that it's still DNS resolver related.

I had initially reported a leak, that turned out to be really DNS resolver related, on v7.7 (SUP-105183, 20/January/2023), but it was fixed for the majority of my MK routers with v7.8rc2 and forward. But at least in one case, I'm still experiencing it, while having no real answers from Mikrotik Support Team on the SUP-128622 Support ticket. People just keep asking me to update to latest and provide new supout files, despite no changelog regarding leak or DNS changes.

With no other real options, I'm here asking for some help of the Mikrotik Staff Team that watches this community regarding the ticket SUP-128622

Here's an updated screenshot of memory usage on a RB2011 box with v7.13 over the last 8 (eight) days. IP/DNS is configured to use max of 16MB with cache data, but that amount was clearly not respected and usage is just growing, indefinitely, until the box crashes or I reboot it. The RB2011 is not a big memory box, with 128MB only, thus 25% of memory usage (that is all being used by the resolver process, confirmed by the supout provided data) is about 32MB, far beyond the 16MB configured limit.

PLEASE, HELP
.

mk leak.png

Posted: **Thu Dec 28, 2023 8:28 pm**

With the new wifi-qcom-ac driver my hAP ac2 wireless performance is much better: I got ~ 150 Mbps with old drivers and now with new driver I see ~270 Mbps while running speed test between two cell phones connected to the same AP at 5 GHz. Since that is 50% of what you can get in WLAN <=> LAN scenario, with a gigabit Internet connection (which I don't have yet) I would probably get about 540 Mbps WAN to LAN speed. Moreover the performance at 2.4 GHz has also improved.

The fast roaming between 2.4 GHz radio and 5 GHz works just fine.

As for memory usage my hAP ac2 usually runs with about 30 MB of free memory. When I start speed test between 2 devices free memory drops to 23 MB perhaps due to some buffering and then restores again to ~30 MB. Recently I noticed that there were only 16.5 MB (!) free memory left after 2 days of uptime and the router crashed with "kernel failure" and "out of memory condition" when I started speed test between 2 cell phones. I don't really know what was occupying the memory at that time. There must be a memory leak in some of the services, but I couldn't identify where exactly.

I suspect the root cause is not the new wireless drivers, but something else. I have been getting "kernel failure" since 7.12 every few days and on previous 7.x versions the router was running smoothly. I could not downgrade because I wanted to use OpenVPN over UDP and that was fixed in 7.12...

I use the device as a home wireless router with multiple wireless networks (Home, Guest, IoT), bridge VLAN filtering, some active L2TP, WireGuard and OpenVPN connections, 10 Mangle rules and 22 Filter rules, enabled DNS resolver with NextDNS DoH service.

Unfortunately in 7.13 I had to abandon Zerotier package as it does not fit into flash memory neither with old nor new wireless drivers.

Overall I'm glad that MikroTik has made it possible to use wave2 drivers on old ac devices! Good job, team!

Posted: **Thu Dec 28, 2023 8:58 pm**

Have you seen the VLAN configuration example part of the URL you provided:
https://help.mikrotik.com/docs/display/ ... ionexample:

Think you should be able to get it to work by following that tutorial.

Yes, I was referring exactly to that config. It is wrong, just like someone wrote it from head, instead of exporting REAL, WORKING config.

I first tried to understand it from reading, then to input it into actual routers to check if it might "just work", then to adapt it (fix VLAN membership for example), but nothing could make it working as it should.

Posted: **Thu Dec 28, 2023 10:47 pm**

I've set name-format=2G-%I- in the CAPsMAN provisioning, to have my interface names look as follows:
Code: Select all
/interface/wifi/print
Flags: M - MASTER; D - DYNAMIC; B - BOUND
Columns: NAME, MASTER-INTERFACE
 #     NAME               MASTER-INTERFACE
 0 MDB 2G-RBD25G-LR-01-
 1  DB 2G-RBD25G-LR-01-2  2G-RBD25G-LR-01-
 2  DB 2G-RBD25G-LR-01-3  2G-RBD25G-LR-01-
 3 MDB 2G-RBcAP-
 4  DB 2G-RBcAP-2         2G-RBcAP-
 5  DB 2G-RBcAP-3         2G-RBcAP-
 6 MDB 5G-RBD25G-LR-01-
 7  DB 5G-RBD25G-LR-01-2  5G-RBD25G-LR-01-
 8  DB 5G-RBD25G-LR-01-3  5G-RBD25G-LR-01-
 9 MDB 5G-RBcAP-
10  DB 5G-RBcAP-2         5G-RBcAP-
11  DB 5G-RBcAP-3         5G-RBcAP-
This makes slave interface names more self-descriptive but also adds this extra hyphen to the master interface. Is there any way I could get rid of that extra hyphen?

No, they screwed up CAP interface names on CapsMan. I encountered same issue, was unable to fix it and rolled back, waiting for fixed release…

Posted: **Thu Dec 28, 2023 11:09 pm**

oof, what an unlucky release...

I've noticed that the wifi config keeps on dropping some parameters, so far I think it happened with country and datapath
still unable to run both CAPsMANs on RB4011 so I've added a CHR instance to play as a manager
also noticed that the audience ethernet interface went down at least once, it's connected to CSS610 which has been up for 52 days... keep monitoring

additionally, I have an issue with one of my ESP32 boards which has been having connection issues since 7.13, maybe coincidence but the signal strength for it has dropped significantly since the upgrade

Posted: **Thu Dec 28, 2023 11:43 pm**

I first tried to understand it from reading, then to input it into actual routers to check if it might "just work", then to adapt it (fix VLAN membership for example), but nothing could make it working as it should.

Too bad...it's working like a charm for me.
Can share my config if you want?

Or better...share yours to check.

Posted: **Fri Dec 29, 2023 12:14 am**

Updated LtAP Mini with a simcom 7600g-h modem. The modem does not show up under LTE devices but does show in USB. As such LTE does not work with 7.13.

Posted: **Fri Dec 29, 2023 2:02 am**

Have you seen the VLAN configuration example part of the URL you provided:
https://help.mikrotik.com/docs/display/ ... ionexample:

Think you should be able to get it to work by following that tutorial.
Yes, I was referring exactly to that config. It is wrong, just like someone wrote it from head, instead of exporting REAL, WORKING config.

I first tried to understand it from reading, then to input it into actual routers to check if it might "just work", then to adapt it (fix VLAN membership for example), but nothing could make it working as it should.

The gist is that wifi-qcom-ac does not support VLAN assignment, so you have to add your wifi interfaces to the bridge and assign VLANs manually. slaves-static=yes should help with persisting this config. That said you have to ignore the CAP block in the guide and instead follow the CAPs that support wifi-qcom-ac package.

Posted: **Fri Dec 29, 2023 11:11 am**

I have upgraded my RB4011, hap ac2 and hap ax2 without any issues so far. No reboots, nor memory leaks, all stable. I chose to stay with the legacy drivers for hap ac2 because of limited resources of the machine and because i am too lazy to create all my wifi interfaces from scratch.
It will be convenient if Mikrotik would create a some kind of automation to transfer all the interfaces and settings from old wireless to new Wifi.

Posted: **Fri Dec 29, 2023 11:12 am**

You want to have your cake AND eat it too ?

Posted: **Fri Dec 29, 2023 11:26 am**

It would not be too difficult to make an external program (in a language like Perl or Python) that reads a /export file made when the wireless package was still used, and generates the proper commands to be pasted into a device to migrate the config to the new WiFi after the qcom-ac package has been installed instead. At least for "trivial" access point and station configurations with PSK authentication.
It could even be done as a RouterOS script, although that would be a bit more difficult due to the string handling limitations and error handling in the scripting language.

Posted: **Fri Dec 29, 2023 11:34 am**

You want to have your cake AND eat it too ? :lol:

Laziness is the source of innovation my friend. Lets all of us have a nice 2024!

Posted: **Fri Dec 29, 2023 3:28 pm**

Thank you Mikrotik

Long waiting features ISIS on the way.

Posted: **Sat Dec 30, 2023 1:10 am**

...
I had initially reported a leak, that turned out to be really DNS resolver related, on v7.7 (SUP-105183, 20/January/2023), but it was fixed for the majority of my MK routers with v7.8rc2 and forward. But at least in one case, I'm still experiencing it, while having no real answers from Mikrotik Support Team on the SUP-128622 Support ticket. People just keep asking me to update to latest and provide new supout files, despite no changelog regarding leak or DNS changes.
...

.
Update to all, very interesting changelog entry from v7.14beta4:

*) dns - do not add new entries to cache if "cache-size" is reached;

Posted: **Sat Dec 30, 2023 2:41 am**

When launching export file="$[system identity get name]" commands ROS is adding in underscores for any spaces in the name.
So a device called "this is a test" would generate a file "this_is_a_test.rsc". Is this expected behaviour?

Posted: **Sat Dec 30, 2023 11:32 am**

Is this expected behaviour?

I should think so. Having spaces in file names calls for trouble in many many places.

Posted: **Sat Dec 30, 2023 11:39 am**

Totally agree. Spaces in file names can be a real problem if used (any white-space character, for that matter).
So to be avoided when possible.

Posted: **Sat Dec 30, 2023 11:51 am**

I don't disagree with you, it is however, new behaviour.

Posted: **Sat Dec 30, 2023 12:13 pm**

Totally agree. Spaces in file names can be a real problem if used (any white-space character, for that matter).
So to be avoided when possible.

Maybe make a call to Redmond about that! It has been a nuisance ever since 1995 but they keep doing it...

Posted: **Sat Dec 30, 2023 12:58 pm**

I don't disagree with you, it is however, new behaviour.

Well, it's not universal. So MT (and everybody else) are free not to endorse spaces in file names. And even MS doesn't force anybody to use spaces in file names, they simply allow them (so does linux, but as I wrote before, it causes problems). It's up to you to either try to use spaces everywhere (and live with problems) or use something else (like underscores) instead of spaces on MS as well.

Posted: **Sat Dec 30, 2023 1:26 pm**

Maybe there was a security issue that can be triggered by creating certain file names with spaces (or other special characters?) that has been remedied by replacing them with underscores? Usually there are those "improved stability when using ..." release note lines that point to that, but this time I don't see any. So much for the often made claim that "all changes are in the release notes"...

On MS systems you do not HAVE to use spaces in your own files, but your HAVE to live with their decisions to use spaces in commonly used directory names. So now we have "C:\Program Files (x86)\" and all the time you have to be careful to use quotes. I well remember the error messages like "C:\Program not found" and maybe MikroTik wanted to cut-off that path.

Posted: **Sat Dec 30, 2023 1:29 pm**

When launching export file="$[system identity get name]" commands ROS is adding in underscores for any spaces in the name.
So a device called "this is a test" would generate a file "this_is_a_test.rsc". Is this expected behaviour?

Just read, and understand what are the reserved characters...

*) console - replace reserved characters in file and script names with underscores;

Posted: **Sat Dec 30, 2023 2:24 pm**

As already pointed out... This has been in changelog. There are other characters, that are handled the same, like dollar sign. And I think the changelog is incomplete, IIRC the same goes for scheduler names, and possibly more.

Posted: **Sat Dec 30, 2023 3:10 pm**

Yes, I overlooked it but indeed it is in the change notes.
I have also sometimes had problems when people used special characters in interface names, and some SNMP software would not be able to handle it.
So maybe there it would have to be done as well...

Posted: **Sun Dec 31, 2023 11:56 am**

Just a quick question before saying happy new year...
If i am gonna move to new wifi drivers for my hap ac2 and create all the configuration from scratch, does anyone know if vlans are working on the wifi interfaces with the new drivers?

Posted: **Sun Dec 31, 2023 12:10 pm**

Only CAPsMAN needs a manual trick to make it work. Not sure if you are using that, or if it is just a single hAP ac with VLAN? In case of the latter, just do VLAN filtering on the bridge (which is very well supported with the new driver).

VLAN filtering:
viewtopic.php?t=143620

CAPsMAN with VLAN:
https://help.mikrotik.com/docs/display/ ... ionexample:

Posted: **Sun Dec 31, 2023 12:13 pm**

... if vlans are working on the wifi interfaces with the new drivers?

wifi-qcom-ac driver doesn't support VLANs natively, but you can configure wifi intetfaces as access ports of vlan-enabled bridge. In many cases this is fine as well.

Posted: **Mon Jan 01, 2024 1:02 pm**

My setup is RB5009 (Capsman controller) and three ax2s as CAPs. Upgraded RB5009 to 7.13 and my wi-fi network went down. Connected to RB5009 with ethernet cable and added qcom package. Dodn't help. I still cannot connect to my APs and I cannot ping them even if they are connected as before. What should I do?

Posted: **Mon Jan 01, 2024 1:08 pm**

Remove qcom on rb5009. Not needed since wave 2 is default present in ROS package as of 7.13.

How is capsman upgrade strategy set on your device ?

Maybe best to start separate thread with config of your controller and one of your caps (assuming they are all the same)

Posted: **Mon Jan 01, 2024 1:11 pm**

Well, the first step is already done by posting this problem :-)

Are the hAP ax2's also upgraded? Would it be possible to set it up from scratch? What version where you running?
The qcom package is only required for devices that have wireless interfaces, no need to install it on the RB5009.

Can you share your config:

/export file=anynameyoulike

Post here (or better, create a new topic), remove serial and any other private information and post it in between code tags by using </> button.

Posted: **Mon Jan 01, 2024 4:36 pm**

Thank you all, I managed to resolve my issue but I’ll post a new thread to clarify MikroTik’s logic.

Posted: **Mon Jan 01, 2024 10:59 pm**

One week ago I upgraded to 7.13 the following
RB5009UPr+S+IN
cAP AC
hAP AC2

Today I moved both cAP AC and hAP AC2 to the new wifi-qcom-ac-7.13-arm package and setup them as CAP with the new CAPsMAN (the one under /wifi/interface) however I have an issue.
If access points get rebooted all works fine, after power cycle the CAPs come back, but in case the RB5009 is rebooted then CAPs are not showing up in remote CAP tab. The only way to bring them back is to disable and re-enable CAPsMAN.

To mitigate the issue I added a script to do an off/on of CAPSman at each startup but I wonder if this is a something wrong with my configuration or a bug.

I don't have use cases with RouterOS < 7.13 because until now my AP couldn't get wave2 drivers so until now I used only the old CAPsMAN so I cannot tell if this is something happenning also with previous version and I cannot downgrade to test otherwise I cannot use the new wave2 drivers.

Is someone facing the same issue?

Thanks

**** EDIT - PROBLEM SOLVED ****

I found that this behaviour happens if the CAPs are setup to reach the CAPsMAN using a fixed IP address put in "CAPsMAN address" parameter instead of using discovery interface. I put a fixed IP in my early test from wireless to wifi package and I left the configuration like that as I didn't imagine to have a side effect. Now I moved back to discovery interface and after the reboot of the CAPsMAN the remote CAP are showing up without any problem.

Posted: **Mon Jan 01, 2024 11:14 pm**

Just a quick question before saying happy new year...
If i am gonna move to new wifi drivers for my hap ac2 and create all the configuration from scratch, does anyone know if vlans are working on the wifi interfaces with the new drivers?

It does, I just did it today.
It's just different than before. You don'y have to use datapath but in short for each AP you need to (assuming you are connecting your AP via ether01 and using a management VLAN):

1) create all the WLAN you need (in my case I have 3 SSID on 3vlan so I created 2 virtual WLAN for each master WLAN internface)
2) create a bridge
3) Add to the bridge ether1 and all the WLAN interfaces.Assign the correct VLAN PVID to each WLAN interface
4) create all the VLAN entries under /bridge/vlan
5) Assign bridge and ether1 as tagged and link the appropiate WLAN interface as untagged to the respective VLAN basically you must treat the WLAN as access port)
6) create a VLAN interface under /interface/vlan and setup and ip or a dhcp client (depending on your setup)
7) enable vlan filtering on the bridge
8) setup master WLAN interface to use capsman as manager
9) create a datapath that uses the bridge above as brigde. Do not assign any vlan to the datapath.
10) now you can enable CAP and select "slave static = yes" and slave "datapath = datapath_created_above"

Of course on the other side you must setup the interface that is interconnected to you hap ac2 as tagged for all the VLAN you need to pass, including the management VLAN.

So it's a bit more cumbersome than before with datapath taking care of forwarding but for sure it works.

Posted: **Tue Jan 02, 2024 12:45 am**

Is there a guide on making both CAPSMANs work at the same time on the same MikroTik device?

I've tried but they don't seem to be able to coexist. I suspect that may have to be listening on different interfaces, can't check that right now but would appreciate any advise.

Edit: Tried running them on different VLAN ifaces with no luck - as soon as I enable the new CAPsMAN the old one seem to stop working and I lose all wi-fi connections, CAP interfaces, etc.

Strange.
I'm quite sure I was having both CAPsMAN running during my migration. I decided to move my CAPs one by one and all the old one were working until I didn't reconfigure them.
Of course each CAP can point only to one CAPsMAN instance at time.
I have an old MIPSBE CAP parked somewhere, tomorrow I will bring it back and retest (I still have my old CAPsMAN config as rollback plan since I switched to wave2 only today).

Posted: **Tue Jan 02, 2024 12:48 am**

Loaded 7.13 on a few AX2 units. Fetch from scripts is currently the only one item that stands out with errors compared to 7.12.1.

We have a script that triggers on boot and fetches a few files from our provisioning servers (Basic auth and HTTPS).
On 7.12.1 works every time.

Using 7.13 the first file is saved without issues, but we observe different errors for subsequent files:
Code: Select all
script error: failure: Idle timeout - waiting data
script error: failure: connection timeout
script error: failure: remote disconnected while in HTTP exchange
The entire job is a single script.

Edit the delay does not fix the issue

Hi mate!
have you tried to run the script in terminal?
i have a script that runs a http post to whatsapp api which sends me alerts and after 7.13 netwatch does not run the fetch command however if I copy/paste the same script in terminal, it runs perfectly.

as below:

/tool fetch http-method=post http-header-field="MY_TOKEN_STRING, Content-Type: application/json" http-data="{\"number\":\"my_phone-number\",\"message\":\"the_message_I_wanna_send\"}" url="https://api-whatsapp-I-use.com/bla/bla/bla"

Posted: **Tue Jan 02, 2024 11:08 am**

I upgraded a CRS328 from 7.11 to 7.12 and then to 7.13
SFP flapped permanently, excessive broadcast, duplex mismatch etc...
downgraded to 7.12.1 and problem disappeared.

Posted: **Tue Jan 02, 2024 1:33 pm**

...
1) create all the WLAN you need (in my case I have 3 SSID on 3vlan so I created 2 virtual WLAN for each master WLAN internface)
2) create a bridge
3) Add to the bridge ether1 and all the WLAN interfaces.Assign the correct VLAN PVID to each WLAN interface
4) create all the VLAN entries under /bridge/vlan
5) Assign bridge and ether1 as tagged and link the appropiate WLAN interface as untagged to the respective VLAN basically you must treat the WLAN as access port)
6) create a VLAN interface under /interface/vlan and setup and ip or a dhcp client (depending on your setup)
7) enable vlan filtering on the bridge
8) setup master WLAN interface to use capsman as manager
9) create a datapath that uses the bridge above as brigde. Do not assign any vlan to the datapath.
10) now you can enable CAP and select "slave static = yes" and slave "datapath = datapath_created_above"
...
So it's a bit more cumbersome than before with datapath taking care of forwarding but for sure it works.

I have come to something similar to this. Not "a bit more cumbersome" but "very complicated". Not good at all for deployment of more than a few APs. No automatic configuration. I would not call this "managed AP". CAPsMAN is here only for faster roaming (OK, good thing, and I'm glad it's fnaly here), but not something you could configure once and leave to the customer to add APs at will, as it was possible with old CAPsMAN.
Definitely needs more development.

Posted: **Tue Jan 02, 2024 9:08 pm**

I have come to something similar to this. Not "a bit more cumbersome" but "very complicated". Not good at all for deployment of more than a few APs. No automatic configuration. I would not call this "managed AP". CAPsMAN is here only for faster roaming (OK, good thing, and I'm glad it's fnaly here), but not something you could configure once and leave to the customer to add APs at will, as it was possible with old CAPsMAN.
Definitely needs more development.

Agree and disagree at the same time.
I do agree because it was very handy to set a CAP in CAP mode and provision, and will be great to have it back on AC deviced (I understood that AX can be managed via datapath and vlan tagging)

But I disagree :-) because there is stil a lot that you can manage remotly and deploy at scale
- change SSID configuration
- change security configuration
- change channel configuration
- change access list

So it's not perfect but VLANs are by far things that are less frequently changed. And once you create a standard for your CAP (e.g. always use ether1 to uplink, naming convention for your WLANs, number of WLANs you need) you can prepare a rsc file to be used to configure the device with everything you need without having to spend to much time.

Posted: **Tue Jan 02, 2024 9:21 pm**

Definitely needs more development.

This is only necessary for AC devices, if new devices are AX it won't be a problem.
But I agree AND have trust this will be available in the future.

Posted: **Tue Jan 02, 2024 9:31 pm**

Is there a guide on making both CAPSMANs work at the same time on the same MikroTik device?

I've tried but they don't seem to be able to coexist. I suspect that may have to be listening on different interfaces, can't check that right now but would appreciate any advise.

Edit: Tried running them on different VLAN ifaces with no luck - as soon as I enable the new CAPsMAN the old one seem to stop working and I lose all wi-fi connections, CAP interfaces, etc.

Hi Mazay,
as promised I'm back
I confirm that i succesfully deployed two CAP AC (7.13 on qcom drivers) and one RB951G-2HnD (on 7.13 with old drivers) on the same RB5009 CAPsMAN and obtained an hybrid setup (old and new CAPsMAN).
Both CAPsMAN are using the same management VLAN to connect between CAPs and CAPsMAN

dual_CAPSMAN2.jpg

dual_CAPSMAN3.jpg

dual_CAPSMAN.jpg

Posted: **Tue Jan 02, 2024 10:12 pm**

another qcom-ac feedback: I have a Busch-Jaeger 8240-84 wifi radio. With legacy driver the device could connect once after restart/turn-on but lost connectivity after some time (disconnect in ROS log) and won't reconnect anymore. the device thought it was still connected. Busch support never responded to my inquiries so it was a pita until 7.13.

Now with qcom-ac driver the device is finally working like a charm. Thanks again MT for bringing these (wave2) drivers to us.

Posted: **Wed Jan 03, 2024 12:17 am**

Definitely needs more development.
This is only necessary for AC devices, if new devices are AX it won't be a problem.
But I agree AND have trust this will be available in the future.

Sure, this was only about existing (and new) AC equipment.

I did not mean to be disrespectful for what Mikrotik is doing, actually I LOVE it. It's just that I would like it to be even better.
Old CAPsMAN v2 (anybody remember CAPsMAN v1?) was so easy to configure that I could delegate that to cable installers - even teach them to keep Reset button long enough, but not too long. Now I'll have to visit each AP before it is operational... and I'll do it gladly because of the added features.

Posted: **Wed Jan 03, 2024 2:01 pm**

This night I had another

system,error,critical router was rebooted without proper shutdown, probably kernel failure
system,error,critical kernel failure in previous boot
system,error,critical out of memory condition was detected

And Graphing looks innocent:

Screenshot 2024-01-03 at 15.00.09.png

Hey MikroTik, is it worth sending autosupout to support?..

Posted: **Wed Jan 03, 2024 2:06 pm**

Hey MikroTik, is it worth sending autosupout to support?..

Always a good idea!

What device are you using and how is it configured?
And for how long was it up?

Posted: **Wed Jan 03, 2024 3:40 pm**

There seems to be a typo/discrepancy in the new Wifi documentation's Channel properties section: according to the docs the one of the possible values of the band property is 5ghz-an however on an actual router said property value pair is

band=5ghz-n

.

Posted: **Wed Jan 03, 2024 5:38 pm**

What device are you using and how is it configured?
And for how long was it up?

cAP ac, about 2 weeks uptime (first one rebooted with ~9 days uptime?..)

Will try to send a mail to support, thanks

Posted: **Wed Jan 03, 2024 11:59 pm**

Hi,

Issue spotted with D53G-5HacD2HnD (Chateau LTE 12)

Two things happened with v7.13
Noticed new LTE firmware, downloaded it, and installed firmware, blue led light turned pink, periodically ended up intermittently flashing pink on and off.

Waited for few minutes then rebooted device, it came back up with blue led light on at a constant.

Navigated into Interfaces > LTE, clicked on lte interface and check firmware

lte_firmware_check_v713.png

Posted supout.rif - SUP-139367

Thanks,

Posted: **Thu Jan 04, 2024 1:12 am**

see viewtopic.php?p=1045805

Posted: **Thu Jan 04, 2024 1:53 am**

see viewtopic.php?p=1045805

Cheers for that, hoping MT support look at the supout data to see why the LTE modem failed to initialise after LTE firmware upgrade with AT command failures - SUP-139367.

Posted: **Thu Jan 04, 2024 11:04 am**

see viewtopic.php?p=1045805
Cheers for that, hoping MT support look at the supout data to see why the LTE modem failed to initialise after LTE firmware upgrade with AT command failures - SUP-139367.

SUP-139367 is already fixed and be rolled out in due course

Posted: **Thu Jan 04, 2024 11:23 am**

While your SUP to the apparently same identical problem and newer SUP-number is already addressed, I don't even have an answer on mine (SUP-139163).

edit:
got a response. was just an firmware update-server issue.

Posted: **Thu Jan 04, 2024 5:30 pm**

This night I had another
Code: Select all
system,error,critical router was rebooted without proper shutdown, probably kernel failure
system,error,critical kernel failure in previous boot
system,error,critical out of memory condition was detected
And Graphing looks innocent:

Screenshot 2024-01-03 at 15.00.09.png

Hey MikroTik, is it worth sending autosupout to support?..

Mu both hAP ax2's are crashing at regular intervals, since yesterday, created support ticket.
Log looks the same, sans the "out of memory".

Posted: **Thu Jan 04, 2024 7:17 pm**

CCR1009 update to 7.13 (default rules)
1) Additional options appeared in the general section - Wifi and Wireless :) This router model does not have wifi at all.
2) creating the most ordinary rule to access winbox from the outside world (input chain, dst port 8291, tcp..wan) - no access! Error- incorrect user name or password appears when connecting! What are these jokes?
After downgrading to 7.12 this problem disappeared. There have never been such "jokes" before.
3) unstable download/upload. Directly? When performing speed measurements, there is a very big difference between - upload/download every time. This is not the case with previous versions.
4) L2TP ipsec vpn (road warrior) speed is not higher than 12 Mbit/s (Internet speed is 900 Mbit at both ends of the connection)

A colleague on the RB4011iGS+5HacQ2HnD-IN has exactly the same
I downgraded version 7.13 to 7.12 :(

Posted: **Thu Jan 04, 2024 7:49 pm**

system,error,critical router was rebooted without proper shutdown, probably kernel failure
system,error,critical kernel failure in previous boot
system,error,critical out of memory condition was detected

Why MikroTik have you still not fixed the logging prefix mess?
Are these message above an error message or a critical message?
I have complained about this for at least 6 years!!!

Read more here:
viewtopic.php?t=124291

0 EMERGENCY A "panic" condition - notify all tech staff on call? (Earthquake? Tornado?) - affects multiple apps/servers/sites.
1 ALERT Should be corrected immediately - notify staff who can fix the problem - an example is loss of backup ISP connection.
2 CRITICAL Should be corrected immediately, but indicates failure in a primary system - fix CRITICAL problems before ALERT - an example is loss of primary ISP connection.
3 ERROR Non-urgent failures - these should be relayed to developers or admins; each item must be resolved within a given time.
4 WARNING Warning messages - not an error, but indicated that an error will occur if action is not taken, e.g. file system 85% full - each item must be resolved within a given time.
5 NOTICE Events that are unusual but not error conditions - might be summarized in an email to developers or admins to spot potential problems - no immediate action required.
6 INFORMATIONAL Normal operational messages - may be harvested for reporting, measuring throughput, etc. - no action required.
7 DEBUG Info is useful to developers for debugging the app, not useful during operations.

Posted: **Fri Jan 05, 2024 9:08 am**

Input Accept NLRI bug

It accept some prefix not in the list of prefix allowed to be accepted i stumble this bug in a lab

ss.png

Posted: **Fri Jan 05, 2024 10:57 am**

Input Accept NLRI bug

It accept some prefix not in the list of prefix allowed to be accepted i stumble this bug in a lab

ss.png

Not a bug. You have 0.0.0.0/0 in your list and that means: accept everything. All your other entries don't matter anymore.
As discussed before, that is a design problem. There should be a way to accept the default route without having it in the address list, but there isn't.

Posted: **Fri Jan 05, 2024 11:11 am**

I don't think that's the case i load more than 300K routes and that few /32 slips into crack, if I follow what you say all on that list will be accepted but it's not I think they just made a string match there literally, will going to retest again and remove 0.0.0.0/0 i think I can still reproduce it

Posted: **Fri Jan 05, 2024 11:40 am**

The "Input accept NLRI" checks if the received prefix is "in" the subnets listed in the address list. ALL subnets are ALWAYS in the 0.0.0.0/0 network so once that is in the list, everything is accepted.
This is because there is no prefix-length in an address list item, like there can be in a routing filter. There you can match on prefix length 0 to accept the default route.
So: when you need to accept the default route from the peer, you CANNOT usefully use "Input accept NLRI". Until that problem is fixed, e.g. by having an additional "also accept default route" flag in that "Input accept NLRI" field.

Posted: **Fri Jan 05, 2024 11:42 am**

I think you are right :), I stand corrected this design flaw is really a punch in the gut they should fix this, we are going to do some more pre-flight test otherwise we are going to call off again the deployment :( if you have single peer you can get away with it but multiple peer this will blow out of proportion

Posted: **Fri Jan 05, 2024 11:45 am**

https://stubarea51.net/2016/01/21/put-5 ... r-testing/

This is life saver luckily I was able to save the VM, the tool is not downable anymore :) I hope kevin will re-upload this again

Posted: **Fri Jan 05, 2024 3:23 pm**

Mu both hAP ax2's are crashing at regular intervals, since yesterday, created support ticket.

Damn annoying, wifi is so unstable, due to constant device reboots/crashes :/
Not sure what triggered it, there were no config changes whatsoever.

Posted: **Fri Jan 05, 2024 3:33 pm**

Not sure what triggered it, there were no config changes whatsoever.

There were "other" changes. Any clues in the logging?
Though I might not be representive, I know the hAP ax2 can be rocksolid (I have one running at my parents house).

Have you already shared your config? Anything "exotic" running on the device?

Posted: **Fri Jan 05, 2024 3:42 pm**

There were "other" changes. Any clues in the logging?

Nothing in the logs, except usual:

system,error,critical router was rebooted without proper shutdown, probably kernel failure
system,error,critical kernel failure in previous boot

And no, there has not been any power failures.
What "other" changes you are referring to?

Have you already shared your config? Anything "exotic" running on the device?

Nothing, which I would personally call "exotic", both have "same" config.

/interface bridge
add admin-mac=48:A9:8A:XX:XX:XX auto-mac=no comment=defconf name=bridgeLocal port-cost-mode=short priority=0x4000
/interface ethernet
set [ find default-name=ether1 ] comment=core:ether1 poe-out=off
set [ find default-name=ether2 ] comment=cust:ether2
set [ find default-name=ether3 ] comment=cust:ether3
set [ find default-name=ether4 ] comment=cust:ether4
set [ find default-name=ether5 ] comment=cust:ether5
/interface wifi
# managed by CAPsMAN
# mode: AP, SSID: <removed>, channel: 5180/ax/Ceee
set [ find default-name=wifi1 ] comment=cust:wifi1 configuration.manager=capsman .mode=ap disabled=no security.authentication-types="" .encryption=""
# managed by CAPsMAN
# mode: AP, SSID: <removed>, channel: 2412/ax/Ce
set [ find default-name=wifi2 ] comment=cust:wifi2 configuration.manager=capsman .mode=ap disabled=no security.authentication-types="" .encryption=""
/snmp community
set [ find default=yes ] addresses=XXX.XXX.XXX.XXX/24 encryption-protocol=AES name=<removed> security=private
/system logging action
set 3 bsd-syslog=yes remote=XXX.XXX.XXX.XXX src-address=XXX.XXX.XXX.XXX
/user group
add name=backup policy=ssh,read,!local,!telnet,!ftp,!reboot,!write,!policy,!test,!winbox,!password,!web,!sniff,!sensitive,!api,!romon,!rest-api
/certificate settings
set crl-download=yes crl-use=yes
/interface bridge port
add auto-isolate=yes bridge=bridgeLocal comment=defconf edge=no ingress-filtering=no interface=ether1 internal-path-cost=10 path-cost=10 point-to-point=yes trusted=yes
add auto-isolate=yes bpdu-guard=yes bridge=bridgeLocal comment=defconf edge=yes ingress-filtering=no interface=ether2 internal-path-cost=10 path-cost=10 point-to-point=yes
add auto-isolate=yes bpdu-guard=yes bridge=bridgeLocal comment=defconf edge=yes ingress-filtering=no interface=ether3 internal-path-cost=10 path-cost=10 point-to-point=yes
add auto-isolate=yes bpdu-guard=yes bridge=bridgeLocal comment=defconf edge=yes ingress-filtering=no interface=ether4 internal-path-cost=10 path-cost=10 point-to-point=yes
add auto-isolate=yes bpdu-guard=yes bridge=bridgeLocal comment=defconf edge=yes ingress-filtering=no interface=ether5 internal-path-cost=10 path-cost=10 point-to-point=yes
add auto-isolate=yes bpdu-guard=yes bridge=bridgeLocal comment="simple ap" edge=yes ingress-filtering=no interface=wifi2 internal-path-cost=10 path-cost=10
add auto-isolate=yes bpdu-guard=yes bridge=bridgeLocal comment="simple ap" edge=yes ingress-filtering=no interface=wifi1 internal-path-cost=10 path-cost=10
/ip neighbor discovery-settings
set discover-interface-list=!dynamic
/ipv6 settings
set max-neighbor-entries=8192
/interface ovpn-server server
set auth=sha1,md5
/interface wifi cap
set certificate=request discovery-interfaces=bridgeLocal enabled=yes lock-to-caps-man=yes
/ip cloud
set update-time=no
/ip dhcp-client
add comment=defconf interface=bridgeLocal
/ip service
set telnet disabled=yes
set ftp disabled=yes
set www disabled=yes
set ssh address=XXX.XXX.XXX.XXX/24
set www-ssl address=XXX.XXX.XXX.XXX/24 tls-version=only-1.2
set api disabled=yes
set winbox address=XXX.XXX.XXX.XXX/24
set api-ssl address=XXX.XXX.XXX.XXX/24 disabled=yes tls-version=only-1.2
/ip ssh
set strong-crypto=yes
/ipv6 address
# address pool error: pool not found: ipv6-pool (4)
add address=::1 advertise=no from-pool=ipv6-pool interface=bridgeLocal
/ipv6 dhcp-client
add add-default-route=yes comment="simple ap" disabled=yes interface=bridgeLocal pool-name=ipv6-pool request=prefix
/ipv6 nd
set [ find default=yes ] advertise-dns=no
/snmp
set contact=<removed> enabled=yes location=<removed> trap-version=3
/system clock
set time-zone-name=Europe/Tallinn
/system identity
set name=MFG-AP1
/system logging
add action=remote prefix=system topics=error
add action=remote prefix=system topics=info
add action=remote prefix=system topics=critical
add action=remote prefix=system topics=warning
/system note
set show-at-login=no
/system ntp client
set enabled=yes
/system ntp client servers
add address=XXX.XXX.XXX.XXX
/system routerboard settings
set auto-upgrade=yes
/tool bandwidth-server
set enabled=no
/tool mac-server
set allowed-interface-list=none
/tool mac-server mac-winbox
set allowed-interface-list=static
/tool mac-server ping
set enabled=no
/tool romon
set enabled=yes
/tool romon port
add disabled=no forbid=yes interface=wifi1
add disabled=no forbid=yes interface=wifi2

Weird thing is, after manual reboot they seem to be fine for ~24h and then they start rebooting again.
And won't stop, until I reboot them via WinBox.

Posted: **Fri Jan 05, 2024 3:56 pm**

I'm seeing random router reboots (a CCR2004-16G-2S+) with this ROS version. I have not been able to capture a supout.inf. file

I have a CAKE queue setup on the WAN interface and reboots seem to be triggered when doing upload speed tests.

/queue type
add cake-bandwidth=580.0Mbps cake-diffserv=besteffort cake-nat=yes cake-overhead=4 cake-overhead-scheme=ether-vlan cake-rtt-scheme=internet kind=cake name=cake-wan-up
/queue interface
set if-wan queue=cake-wan-up

Posted: **Fri Jan 05, 2024 4:05 pm**

@donkeyKong I've had random problems using cake with the bandwidth limit set in the cake queue itself, as opposed to setting the max-limit through either a queue tree using cake or a simple queue using cake. I'm not sure if this is a cake issue, a 7.13 issue, or a me issue. Just throwing it out there in case you want to try cake as a queue tree on your upload to see if that gets rid of the reboot issue.

Posted: **Fri Jan 05, 2024 4:40 pm**

I'm seeing random router reboots (a CCR2004-16G-2S+) with this ROS version.

How many of them? When I upgraded to 7.12.1 I have seen two such reboots within a week and made a SUP ticket, they recommended me to attach a terminal to the serial port (I have minicom running on a Linux machine) and capture the output.
But since then (42 days ago) it has not happened again. There may be some condition that triggers these reboots that does not happen often...

Posted: **Fri Jan 05, 2024 5:05 pm**

I'm seeing random router reboots (a CCR2004-16G-2S+) with this ROS version.
How many of them? ...

Once every day for the moment. It has happened during MS Teams calls (call packets have DSCP markings) and while saturating the upload capacity of the WAN link.

Posted: **Fri Jan 05, 2024 5:18 pm**

That looks like what I was seeing, twice the router rebooted (by watchdog) during Teams calls, but not anywhere near capacity of the WAN.
I am not using CAKE but I do use a queue tree with DSCP->Priority->packetmark translations (with pcq-download and wireless-default queues).
After that happened I have (for other reasons) disabled the "download" queues (that were on our internal VLAN interfaces) but the "upload" queues towards the ISP are still present.
Maybe it is related to queueing...

Posted: **Fri Jan 05, 2024 5:31 pm**

I'm seeing random router reboots (a CCR2004-16G-2S+) with this ROS version.
How many of them? When I upgraded to 7.12.1 I have seen two such reboots within a week and made a SUP ticket, they recommended me to attach a terminal to the serial port (I have minicom running on a Linux machine) and capture the output.

I tried attaching a terminal and capturing the output from the serial port but no valuable input was produced (just captured some logs from normal bootup sequence)I am able to reliably have the router reboot by doing speedtests that saturate the upload capacity.

stage2_loader v2.21
SPD I2C Address: 57
Executing next!

-----------------------------------------------------
Stage 3 version: 2.21.0
Commit ID: 5e1dea9
CVOS commit ID: a14387d
HAL commit ID: 7b19d83
Build date: Jan  3 2017 15:34:47
-----------------------------------------------------

agent_wakeup v2.10
EEPROM Revision ID = 39
Device ID = a514
Device Info: v2sil-39-rc1
Loading DT to 01100000 (24973 bytes)...
Board config ID: CCR2004-16G-2S+PC
al_serdes_25g_tx_pll_wa: temperature 40, swing_init 12, swing_adjusted 12
al_serdes_25g_tx_pll_wa: dosc_init 62, dosc_target 63, window_start 58, window_end 66
Serdes25G power up OK (25G mode)
dram_clear: clearing physical memory 0000000002000000 - 00000000c0000000...
dram_clear: clearing physical memory 0000000200000000 - 0000000240000000...
Loading application to 01100000 (62788 bytes)...
Executing application...


RouterBOOT booter 7.13

CCR2004-16G-2S+

CPU frequency: 1200 MHz
  Memory size:   4 GiB
    NAND size: 128 MiB

Press Ctrl+E to enter etherboot mode
Press any key within 2 seconds to enter setup..

loading kernel... OK
setting up elf image... OK
jumping to kernel code
Starting...
Starting services...
MikroTik 7.13 (stable)

MikroTik

v7.13.5 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!

Re: v7.13 [stable] is released!