v7.13.5 [stable] is released!

[dalami]

That helps! Thank you.

[anav]

This AM i upgraded my CCR1009 from version 7.12.1 to version 7.13 now getting the following error when running a script

Download from https://view.sentinel.turris.cz/greylist-data/greylist-latest.csv to RAM FAILED: Fetch failed with status 206

The same script was working fine under 7.12.1 and earlier versions

My dear Mozerd, one should know that a 7.X.0 offering will be quickly followed by 7.X.1, as you note you yourself were using 7.12.1,
Never buy the first model year of a car Even smarter folks always wait to .2 LOL

For N.A. raised members, its akin to Charlie Brown believing Lucy is actually going to keep holding the football down for the kick this time!!

[bajodel]

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.

[ppsascha]

Hi all!

I have the same problem with script on CHR after upgrade

Download from https://antifilter.download/list/ip.lst to <nothing> FINISHED
Download from https://antifilter.download/list/ip.lst to RAM FAILED: Fetch failed with status 206

What can i do with this?

https://en.wikipedia.org/wiki/List_of_HTTP_status_codes

206 Partial Content
The server is delivering only part of the resource (byte serving) due to a range header sent by the client. The range header is used by HTTP clients to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams.

Mikrotik has implemented changes to the “fetch” command.

*) fetch - added “http-auth-scheme” parameter, allows to select HTTP basic or digest authentication;
*) fetch - added “http-content-encoding” setting;
*) fetch - added raw logging;
*) fetch - allow to receive HTTP response headers;
*) fetch - require “ftp” user policy;

I’m new to MT scripts so i need help with it; if anyone can do this for me i will be glad.

[anuser]

Has MT an air time fairness implementation at all? Isn’t that something off-standards?

• MT’s own old wireless drivers? => No

• wifiwave2 with chipset vendors driver? => Yes, those driver supports it, but is it enabled by MikroTik for IPQ40xx?

[buset1974]

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.

have a similar experience, report SUP-132127 and no reply ever since.
all topology running well in v6
so upgrading MPLS to v7 still a question

thx

[sch]

I’m observing PoE issue with hAP ax2 and SXT LTE6 kit: when ether1 on hAP ax2 is configured with PoE Out = “auto on”, PoE seems to be reset (during LTE modem init ?) and SXT LTE6 kit is rebooted. This continues in a loop. SXT LTE6 kit could boot on 6 or 7 iterations successfully.
Setting ether1 on hAP ax2 with PoE Out = “forced on” fixes the issue.
It worked fine with PoE Out = “auto on” on firmwares before 7.13 (especially on 7.12 RC4).
Ether1 of SXT LTE6 kit is connected to Ether1 of hAP ax2, hAP ax2 is powered via stock power adapter.

Please send supout file from you both devices to support@mikrotik.com

[emilst]

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.

Please create a support ticket and attach a supout file from both RouterOS versions.
https://help.mikrotik.com/servicedesk/servicedesk

[markatel]

Upgrading from what version?

If stable, 7.12 or 7.12.1, obviously.

@pe1chl, exacly, from 7.12.1.
After enabling bridge VLAN filtering all went working, but it cost us a long journey…

[ivicask]

As mentioned by others bonding stopped working for me on multiple devices after 7.13 update, and one wireless cube with out of box config disappeared need to go check what happend to it after 7.13…
Edit:So 2x CubeG updated same time and same way(automatic check for updates), one update fine, other had missing wireless package for some reason, after adding that 60ghz link established, but still i had NO communication between sites until i killed bonds both sides(5+60ghz)

[rpingar]

we still getting pppoe-server crash on x86 platform, arm64 is stable.
SUP-136050 pppoe server crash 7.13beta3
SUP-97493 pppoe v7 issue
the first ticket was opened more then one year ago.
both tickets are updated with latest autosupout generated on 7.13rc4

we thing it is related to uniquness issue about dynamic interface id.
regards

[pe1chl]

If stable, 7.12 or 7.12.1, obviously.

@pe1chl, exacly, from 7.12.1.
After enabling bridge VLAN filtering all went working, but it cost us a long journey…

Ok but was it enabled on the 7.12.1 config and did it get disabled by the upgrade, or were you running a bridge configured with VLANs but with VLAN filtering not (yet) enabled and did that now fail to work under 7.13?
One thing I have learned to do over time is: prior to upgrade, export the config. Then after upgrade, export it again and “diff” them.
Then you can see what the upgrade has changed in config (interesting anyway) and what you need to focus on when troubleshooting.
When you have upgraded that device from 6.x originally, it is advisable to netinstall and re-import the exported config. Having an upgraded device tends to cause vague problems like this.

[PappaB]

small note outside the version. . . hap ax2 if it had at least USB2 (better USB3.X) it would be an ideal small device and I think its sales would increase several times. . .
This way we have ac2 with USB but little storage space and limited RAM, and ax2 without USB but with lots of RAM and enough storage space.
I don’t know what led MKT to such a failed solution.
(And putting PoeIn and PoeOut on one port, I didn’t understand that either.)
​

I agree 100%.

By the way, another reason for me to hold back relates to the SNMP on Wifiwave2 and changes in the structure.
Using the wireless package, SNMP stats give me (amongst other info) details on every client connected to the Wifi, which on my Grafana dashboard helps me identify devices with poor wifi signals. This allows me to be proactive and move them or improve coverage.

On my HAP AX2 and AX3, that info does not seem to be avaialble. Either that, or I do not have the correct yaml file to interpret it…
See this … http://forum.mikrotik.com/t/wifiwave2-snmp-metrics-missing-hap-ax2/162297/1

If anyone has a fix / workaround, please advise.

[mondychan]

+1
Cube 60Pro ac bonding stopped working after upgrading 7.12 → 7.13

[jacekes]

For me on several 951s and one hap ac2 after the upgrade the “old-gen” wireless package was missing and wifi stopped working.
I needed to install the “wireless” package manually in order to see the interfaces again.

[diamuxin]

Hi, follow this error:

[ ] > :put ([/tool fetch url="https://upgrade.mikrotik.com/routeros/NEWEST7.stable" as-value output=user]->"data")
7.12.1 1700221125

It should report: 7.13 and epoch date: 1702542240 approx.

[jacekes]

All my routers say 7.12.1 1700221125

[optio]

For me on several 951s and one hap ac2 after the upgrade the “old-gen” wireless package was missing and wifi stopped working.
I needed to install the “wireless” package manually in order to see the interfaces again.

Old drivers are no longer bundled in routeros main package, wireless package must be installed with main to use old drivers.
In my case virtual wireless interfaces was not created from 7.12.1 exported configuration for same old drivers, I had to recreate them manually over Winbox.

[dadaniel]

Hi, follow this error:

[ ] > :put ([/tool fetch url="https://upgrade.mikrotik.com/routeros/NEWEST7.stable" as-value output=user]->"data")
7.12.1 1700221125

It should report: 7.13 and epoch date: 1702542240 approx.

AFAIK it will only report 7.12.1 if your current version is below 7.12.1. This is because else the update to 7.13 will likely fail.

[spacex]

+1
Cube 60Pro ac bonding stopped working after upgrading 7.12 → 7.13

Hello, I mentioned the problem above and the same situation happened to me.