v7.13.5 [stable] is released!

[mazay]

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? http://forum.mikrotik.com/t/7-13-wireless-package-split-question/172049/1

yes, but this belongs to the docs, thanks

[normis]

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

[diamuxin]

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?username=mE&ghy&l&password=dGMntyhju&type=command&param=udevice&idx=57&nvalue=0&svalue=$temp2”;
/tool fetch keep-result=no url=$url mode=http
(not https)

https://help.mikrotik.com/docs/display/ROS/Fetch#Fetch-Properties

[frank333]

I had already tried but it does not work

[joedoelv]

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.

[holvoetn]

I only run wireguard in mine. No ovpn.

[ksteink]

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

[kevinds]

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,

[mazay]

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.

[dakobg]

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 ?

[dakobg]

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 ?

[andriys]

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.

[eworm]

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?

[kehrlein]

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)

[mazay]

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.

[RafGan]

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.

[Ovic]

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

[Drovan]

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

[hagoyi]

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

Also how to disable this new fetch logging?

[alibloke]

I would also like to disable fetch logging