Community discussions

MikroTik App
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1636
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

v7.13.5 [stable] is released!

Fri Dec 15, 2023 11:40 am

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

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

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

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

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

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


What's new in 7.13.5 (2024-Feb-16 19:35):

*) bridge - fixed MLAG connection after peer-link flap (introduced in v7.13);
*) bridge - fixed packet forwarding after changing HW offloaded bridge interface settings in certain cases (introduced in v7.13);
*) dns - do not close connection with DoH server after query execution (introduced in v7.13.3);
*) leds - fixed modem signal strength for RBSXTR&R11e-LTE (introduced in v7.13);
*) sms - increased SMS read timeout;
*) wifi-qcom - improved memory allocating process;
*) wifi-qcom - improved regulatory compliance for L11, L22 devices;
*) wifi-qcom - improved system stability for L11, L22 devices;

What's new in 7.13.4 (2024-Feb-07 11:59):

*) bridge - avoid per-VLAN host flushing on HW offloaded bridge (introduced in v7.13);
*) defconf - fixed firewall rule for IPv6 UDP traceroute;
*) leds - fixed modem LED indication for SXT LTE 3-7 (introduced in v7.13);
*) lte - fixed Simcom modem support in 0x9000; 0x9002, 0x9002; 0x901a and 0x901b USB compositions (introduced in v7.13);
*) ovpn - improved system stability when using HW encryption on ARM64 devices (introduced in v7.13);
*) route-filter - fixed AS path matchers when input and output chains are used;

What's new in 7.13.3 (2024-Jan-24 15:16):

*) dns - fixed DNS service crash when DoH used (introduced in v7.13.1);
*) fetch - fixed fetch when using "src-path" with SFTP mode (introduced in v7.13);
*) fetch - less verbose logging (introduced in v7.13);
*) health - show voltage when powering KNOT R through Micro-USB;
*) lte - fixed Simcom modem support in 0x9001 USB composition;
*) lte - improved SIM PIN unlock event handling for MBIM FG621-EA;
*) poe-out - fixed "power-cycle" for CRS354-48P-4S+2Q+ device (introduced in v7.13);
*) poe-out - improved PoE out reliability on routers with a single PoE out interface;
*) sms - fixed SMS inbox for FG621-EA modem (introduced in v7.13);
*) sms - fixed SMS sending from WinBox and WebFig (introduced in v7.13);
*) sms - improved system stability when working with SMS (introduced in v7.13);
*) system - properly close HTTP/S connections initiated by the router;
*) tftp - improved invalid request processing;
*) wifi-qcom - improved system stability when using FastPath (introduced in v7.13);

What's new in 7.13.2 (2024-Jan-12 11:51):

*) leds - fixed default LTE LED configuration for wAPR-2nD;
*) lte - fixed cases where FG621-EA modem could be missing signal information in "lte monitor" (introduced in v7.13);
*) routerboard - added "reset-button" support for RBwAPR-2nD device;
*) sfp - improved combo-sfp handling for CRS328-4C-20S-4S+;
*) sfp - improved link establishment for RB4011 devices;
*) vlan - fixed non-running VLAN interface after failed MTU change;
*) wifi - fixed issue with setting country profile (introduced in v7.13.1);

What's new in 7.13.1 (2024-Jan-05 15:51):

*) bridge - fixed auto "path-cost" for bonding interfaces (introduced in v7.13);
*) console - updated copyright notice;
*) dns - fixed domain name lookup resolving for internal services;
*) fetch - do not require "content-length" for HTTP (introduced in v7.13);
*) fetch - fixed DNS resolving when domain has only AAAA entries (introduced in v7.13);
*) fetch - fixed fetch when using "src-path" with HTTP/HTTPS modes (introduced in v7.13);
*) fetch - fixed IPv4 address logging (introduced in v7.13);
*) fetch - improved file download stability with HTTP/HTTPS modes;
*) leds - do not show LTE connection state/mode using RGB power LED from configless LTE modems (introduced in v7.13);
*) leds - fixed wireless type of LED triggers for routers using WiFi package (introduced in v7.13);
*) lte - fixed support for config-less modem detection (introduced in v7.13);
*) lte - fixed USB mode switch and initialization race condition for configless USB modems;
*) modem - fixed SMS removal (introduced in v7.13);
*) port - fixed support for USB/serial adapters (introduced in v7.13);
*) switch - improved 100G interface stability for 98DX4310 and 98DX8525 switches;
*) switch - minimise potential packet overflows on CRS354;
*) system - improved system stability when processing packets in FastPath (introduced in v7.13);
*) timezone - updated timezone information from "tzdata2023d" release;
*) tr069 - fixed bandwidth test;
*) wifi - use "Latvia" as default value for "country" property;
*) winbox - renamed "Wireless Table" menu to "Wifi";

What's new in 7.13 (2023-Dec-14 09:24):

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

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

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

Please keep this forum topic strictly related to this particular RouterOS release.
Last edited by holvoetn on Mon Dec 18, 2023 12:05 pm, edited 1 time in total.
 
iustin
just joined
Posts: 21
Joined: Mon Mar 06, 2023 12:11 am

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 12:14 pm

Wohoo! Before the holidays, thank you!
 
BWC
newbie
Posts: 34
Joined: Tue Mar 21, 2006 5:36 pm
Location: Würzburg, Germany
Contact:

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 12:35 pm

It is probably just me, but upgrading from 7.12 to 7.13 on AWS broke the instance again and it does not boot any longer.

I had the same issue upgrading to 7.12 and was forced to recreate the instance.

Isn't there anything I can do to just get the upgrade on AWS working properly?

--Michael
 
holvoetn
Forum Guru
Forum Guru
Posts: 5612
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 12:48 pm

Upgraded RB5009 as main router (DHCP, VLAN, ...) also acting as capsman and AX2/AX3 via capsman coming from 7.13rc4.
So far no issues.
 
ToTheFull
Member Candidate
Member Candidate
Posts: 257
Joined: Fri Mar 24, 2023 3:24 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 12:59 pm

Thanks all updated and working... hAP ax2/cAP ax
 
oskarsk
MikroTik Support
MikroTik Support
Posts: 63
Joined: Mon May 13, 2019 9:41 am

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 1:09 pm

This does not seem version related, send your supout file to support, so we can check what specifics you have there.
It is probably just me, but upgrading from 7.12 to 7.13 on AWS broke the instance again and it does not boot any longer.

I had the same issue upgrading to 7.12 and was forced to recreate the instance.

Isn't there anything I can do to just get the upgrade on AWS working properly?

--Michael
 
User avatar
petardo
newbie
Posts: 30
Joined: Fri Sep 25, 2015 4:06 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 1:10 pm

Question:
Drivers for older wireless and 60GHz interfaces, as well as the wireless management system CAPsMAN, are now part of a separate "wireless" package instead of being a part of the bundle package. This package can be uninstalled if not needed.
How do we know whether a package is needed or not? (We are useing RB951, hAP AC2, hAP AC3, and cAP devices, all of them as simple Access Point - Wisp AP, Home AP)
 
corp9592
just joined
Posts: 12
Joined: Sun May 05, 2019 10:14 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 1:18 pm

I just updated hap ac2 and I have the "wireless" package and "routeros". everything is working as usual, but I wonder how am I supposed to migrate to new WiFi package? Manually?
 
ToTheFull
Member Candidate
Member Candidate
Posts: 257
Joined: Fri Mar 24, 2023 3:24 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 1:20 pm

I just updated hap ac2 and I have the "wireless" package and "routeros". everything is working as usual, but I wonder how am I supposed to migrate to new WiFi package? Manually?
https://www.youtube.com/watch?v=AkBIQxi-VKs
 
oskarsk
MikroTik Support
MikroTik Support
Posts: 63
Joined: Mon May 13, 2019 9:41 am

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 1:22 pm

All needed packages should be downloaded from support and download section, for each product. Now from 7.13 RouterOS current release will have all needed packages listed, you are welcome to check here:
Example for hap_ax_lite_lte6
https://mikrotik.com/product/hap_ax_lit ... -downloads

Question:
Drivers for older wireless and 60GHz interfaces, as well as the wireless management system CAPsMAN, are now part of a separate "wireless" package instead of being a part of the bundle package. This package can be uninstalled if not needed.
How do we know whether a package is needed or not? (We are useing RB951, hAP AC2, hAP AC3, and cAP devices, all of them as simple Access Point - Wisp AP, Home AP)
 
User avatar
Jotne
Forum Guru
Forum Guru
Posts: 3309
Joined: Sat Dec 24, 2016 11:17 am
Location: Magrathean

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 1:23 pm

Pleas post new Announcements so that it show on all places, like under scripting. PS not the first time this has been done wrong.
-
post.png
You do not have the required permissions to view the files attached to this post.
 
nicolap
just joined
Posts: 13
Joined: Mon Sep 09, 2019 12:16 am

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 1:30 pm

This is very confusing: on hAP ac now I have a WiFi menu, completely useless and a Wireless that is the correct one.
Why???
 
User avatar
Jotne
Forum Guru
Forum Guru
Posts: 3309
Joined: Sat Dec 24, 2016 11:17 am
Location: Magrathean

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 1:36 pm

@nicolap Have you read the beta and rc thread? If not read trough them.
viewtopic.php?t=201465
viewtopic.php?t=201989
 
dave3
newbie
Posts: 45
Joined: Mon Feb 07, 2022 8:06 am

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 1:40 pm

Upgraded RB750Gr3. I noticed it lost the /system clock time-zone-name setting after the upgrade; had to add it back.

Is it possible or advisable to remove the new wireless package, since the device has no wireless functionality?
 
User avatar
macgaiver
Forum Guru
Forum Guru
Posts: 1764
Joined: Wed May 18, 2005 5:57 pm
Location: Sol III, Sol system, Sector 001, Alpha Quadrant

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 1:43 pm

This is very confusing: on hAP ac now I have a WiFi menu, completely useless and a Wireless that is the correct one.
Why???
https://www.youtube.com/watch?v=AkBIQxi ... l=MikroTik
 
dimacbz
just joined
Posts: 2
Joined: Sat Jul 02, 2016 11:04 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 1:55 pm

RouterOS-7.13....png
You do not have the required permissions to view the files attached to this post.
 
bamarcant
just joined
Posts: 7
Joined: Wed Nov 20, 2013 11:54 am

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 1:57 pm

--- *) winbox - updated "wireless" and "wifi" menus;---
Please, correct same name in wireless tab; cannot customize old_wireless tab on old devices because on relogging appear the new (wifi) one instead,and if choose the correct one (wireless) customization has not held, but default.
You do not have the required permissions to view the files attached to this post.
 
RafGan
newbie
Posts: 29
Joined: Mon Jun 06, 2011 6:17 pm
Location: Poland / Silesia

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 2:08 pm

RB1100dx4de reboots after few seconds, no supout.rif created, no time needed to do this.
Last edited by RafGan on Fri Dec 15, 2023 2:10 pm, edited 1 time in total.
 
qwertykolea
just joined
Posts: 5
Joined: Wed Aug 30, 2023 2:43 pm
Location: MDA

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 2:08 pm

Hello,
I've just updated my hAP ac^2 to version 7.13, but I can't find where I should set up WPA3?
You do not have the required permissions to view the files attached to this post.
 
nicolap
just joined
Posts: 13
Joined: Mon Sep 09, 2019 12:16 am

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 2:12 pm

@nicolap Have you read the beta and rc thread? If not read trough them.
viewtopic.php?t=201465
viewtopic.php?t=201989
Of course I already read all.
But hAP ac is only WiFi 5 so the WiFi menu is useless. So hide it!!!
And, as someone already noted, in Winbox both windows has the same name!
 
templeos
just joined
Posts: 19
Joined: Mon Aug 26, 2019 3:58 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 2:16 pm

Hello,
I've just updated my hAP ac^2 to version 7.13, but I can't find where I should set up WPA3?
Remove wireless package and install wifi-qcom-ac-7.13-arm.npk from all_packages-arm-7.13.zip
Everything is in the documentation:https://help.mikrotik.com/docs/display/ ... ss'package
 
holvoetn
Forum Guru
Forum Guru
Posts: 5612
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 2:18 pm

Hello,
I've just updated my hAP ac^2 to version 7.13, but I can't find where I should set up WPA3?
You did install wifi-qcom-ac package as well ? This is a manual action to be done afterwards and then you completely need to reconfigure the wifi part.

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

EDIT: someone hit the button a bit faster then I did :lol:
 
BWC
newbie
Posts: 34
Joined: Tue Mar 21, 2006 5:36 pm
Location: Würzburg, Germany
Contact:

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 2:23 pm

Well, as mentioned, it's not booting any longer, so no chance to get the supout anymore.
This does not seem version related, send your supout file to support, so we can check what specifics you have there.
It is probably just me, but upgrading from 7.12 to 7.13 on AWS broke the instance again and it does not boot any longer.

I had the same issue upgrading to 7.12 and was forced to recreate the instance.

Isn't there anything I can do to just get the upgrade on AWS working properly?

--Michael
 
xakep7
just joined
Posts: 1
Joined: Sun Dec 09, 2018 9:06 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 2:25 pm

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

At 7.12 all ok.
 
Reinis
MikroTik Support
MikroTik Support
Posts: 91
Joined: Wed Jan 02, 2019 12:14 pm
Location: Latvia
Contact:

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 2:31 pm

RB1100dx4de reboots after few seconds, no supout.rif created, no time needed to do this.
Does not happen on default config of "RB1100AHx4 Dude Edition" with 7.13. Ensure that there is no netwatch or something else that is rebooting it. Try to generate supout.rif and send it to support@mikrotik.com
 
wvisser
just joined
Posts: 2
Joined: Sat Nov 11, 2023 2:12 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 2:41 pm

DHCP served over a VLAN trunk is still a problem on x86. Rolled back to 7.11.2.

See here, and here (post 99) and SUP-134483.
 
User avatar
herbrico
newbie
Posts: 25
Joined: Mon Dec 31, 2012 4:19 pm
Location: Croatia, Sisak

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 2:46 pm

RB1100dx4de reboots after few seconds, no supout.rif created, no time needed to do this.
Same router, all working ok for me, no issue.
 
Guscht
Member Candidate
Member Candidate
Posts: 241
Joined: Thu Jul 01, 2010 5:32 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 2:52 pm

Works so far:
Screenshot 2023-12-15 134327.jpg

But for clarification regarding "Wireless" and "WiFi":

  • Can I uninstall the old "Wireless" package on devices without WLAN-interface (like Switches), or will this break something (like CAPsMAN-management traffic or something)?
    WiFi is always there, but useless?
  • On devices like the mAP lite, I have now a WiFi button plus a Wireless button. But nothing in the "WiFi" menu.
    There is no additional driver in the MIPSBE-Extra-package. Means WiFi is always there, but useless?
  • Devices without the additional driver ( 'wifi-qcom-ac' or 'wifi-qcom') have to run everything WLAN-related under the old Wireless-Menu?
    Means WiFi is always there, but useless?
You do not have the required permissions to view the files attached to this post.
Last edited by Guscht on Fri Dec 15, 2023 2:54 pm, edited 1 time in total.
 
User avatar
jimmer
just joined
Posts: 19
Joined: Wed Mar 06, 2019 10:06 am
Location: Tasmania, Australia

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 2:54 pm

Have upgraded:

1 x RB3011-iUAS
2 x hAPac2's

All were on 7.12 and all are working perfectly after upgrade, havent tried swapping out the wifi packages yet, using the old wireless one for now.
 
User avatar
merlinthemagic7
Frequent Visitor
Frequent Visitor
Posts: 52
Joined: Fri Sep 16, 2016 8:49 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 3:01 pm

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:
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
Last edited by merlinthemagic7 on Fri Dec 15, 2023 3:18 pm, edited 1 time in total.
 
holvoetn
Forum Guru
Forum Guru
Posts: 5612
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 3:08 pm

  • Can I uninstall the old "Wireless" package on devices without WLAN-interface (like Switches), or will this break something (like CAPsMAN-management traffic or something)?
    WiFi is always there, but useless?
  • On devices like the mAP lite, I have now a WiFi button plus a Wireless button. But nothing in the "WiFi" menu.
    There is no additional driver in the MIPSBE-Extra-package. Means WiFi is always there, but useless?
  • Devices without the additional driver ( 'wifi-qcom-ac' or 'wifi-qcom') have to run everything WLAN-related under the old Wireless-Menu?
    Means WiFi is always there, but useless?
To my understanding:
1- yes.
2- correct, consequence from having (wave2) wifi in base package now.
3- yes. See also 2.
 
Guscht
Member Candidate
Member Candidate
Posts: 241
Joined: Thu Jul 01, 2010 5:32 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 3:13 pm

@Mikrotik, please update the Menu-Name from WiFi Menu to WiFi NOT Wireless!!!!!!!
This is totally confusing o_O

Screenshot 2023-12-15 140941.jpg
You do not have the required permissions to view the files attached to this post.
 
Guscht
Member Candidate
Member Candidate
Posts: 241
Joined: Thu Jul 01, 2010 5:32 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 3:14 pm

To my understanding:
1- yes.
2- correct, consequence from having (wave2) wifi in base package now.
3- yes. See also 2.
Thanks!
 
Simonej
Frequent Visitor
Frequent Visitor
Posts: 59
Joined: Sun Aug 22, 2021 3:34 am

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 3:18 pm

We have a script that triggers on boot and fetches a few files from our provisioning servers (Basic auth and HTTPS).
fetch - require "ftp" user policy;
 
User avatar
rushlife
Member Candidate
Member Candidate
Posts: 246
Joined: Thu Nov 05, 2015 12:30 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 3:20 pm

Is there any wiki for using NEW driver packages for "OLD" devices ? And if so, when I will use NEW drivers from NEW package, can I use just ONE capsman (section) ? For new and also for old devices ?

Or it is just how I thing and there will be always TWO capsmans ( if I have non EX devices also ) in my network... ?
 
whatever
Member
Member
Posts: 356
Joined: Thu Jun 21, 2018 9:29 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 3:24 pm

WiFi is always there, but useless?
It's not useless, it can be used as Capsman to manage devices using new wifi driver.
 
DarkNate
Forum Guru
Forum Guru
Posts: 1065
Joined: Fri Jun 26, 2020 4:37 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 3:27 pm

It's not useless, it can be used as Capsman to manage devices using new wifi driver.
It's confusing, if device A doesn't have wireless chip/features, then "Capsman" should be seperate menu altogether, not "wifi" or "wireless" or "wifiwave2", capsman is just a control plane protocol.
 
Guscht
Member Candidate
Member Candidate
Posts: 241
Joined: Thu Jul 01, 2010 5:32 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 3:30 pm

It's not useless, it can be used as Capsman to manage devices using new wifi driver.
Like on 1 out of 100 devices its useful and on 99 useless? Useless codestuff imho...
 
whatever
Member
Member
Posts: 356
Joined: Thu Jun 21, 2018 9:29 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 3:32 pm

With wifi(wave2) capsman configuration is no longer separate from local wifi configuration. It's only confusing because it used to be different.
 
User avatar
Etz
Member Candidate
Member Candidate
Posts: 178
Joined: Thu Mar 27, 2014 10:09 am
Location: Estonia

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 3:42 pm

*) wifi - create first interface without number when using "name-format" provisioning setting;
Is there any way to restore default behaviour, where all CAP interfaces would have number appended?
This is super annoying, do I really have to downgrade to, as my only option, make it work properly again? :(
I really don't want to switch to static interfaces and overcomplicate things.
Last edited by Etz on Fri Dec 15, 2023 3:52 pm, edited 1 time in total.
 
User avatar
merlinthemagic7
Frequent Visitor
Frequent Visitor
Posts: 52
Joined: Fri Sep 16, 2016 8:49 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 3:48 pm

@Simonej

Script has that permission. It looks like it is related to compression. If we instruct the web server to "no-gzip" the download works.
Ill open a ticket when its reproducible.

Edit:
The issue occurs when the http response headers + payload (after being uncompressed) exceeds 65535 bytes.
But what is really odd is that once in awhile it goes through. SUP-137742
Last edited by merlinthemagic7 on Fri Dec 15, 2023 5:19 pm, edited 3 times in total.
 
User avatar
mantouboji
newbie
Posts: 47
Joined: Mon Aug 01, 2022 2:21 pm
Location: Shanghai

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 3:50 pm

RB4011 works well
 
qwertykolea
just joined
Posts: 5
Joined: Wed Aug 30, 2023 2:43 pm
Location: MDA

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 4:03 pm

Remove wireless package and install wifi-qcom-ac-7.13-arm.npk from all_packages-arm-7.13.zip
Everything is in the documentation:https://help.mikrotik.com/docs/display/ ... ss'package
Thank you.

This new 7.13 made my day.
The new driver for hap ac2 increased the maximum speed from 300 Mbps to 500 Mbps on my laptop.
 
User avatar
Etz
Member Candidate
Member Candidate
Posts: 178
Joined: Thu Mar 27, 2014 10:09 am
Location: Estonia

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 4:15 pm

*) wifi - create first interface without number when using "name-format" provisioning setting;
Is there any way to restore default behaviour, where all CAP interfaces would have number appended?
This is super annoying, do I really have to downgrade to, as my only option, make it work properly again? :(
I really don't want to switch to static interfaces and overcomplicate things.
Did not find a way to fix this, so downgraded and waiting for fixed release.
 
ivanfm
newbie
Posts: 48
Joined: Sun May 20, 2012 5:07 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 4:17 pm

It is probably just me, but upgrading from 7.12 to 7.13 on AWS broke the instance again and it does not boot any longer.

I had the same issue upgrading to 7.12 and was forced to recreate the instance.

Isn't there anything I can do to just get the upgrade on AWS working properly?

--Michael
Have you checked this ? viewtopic.php?t=187597

change instance to T2, upgrade and change back to T3, worked for me before, have not tested for this 7.13 yet.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10307
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 4:20 pm

--- *) winbox - updated "wireless" and "wifi" menus;---
Please, correct same name in wireless tab; cannot customize old_wireless tab on old devices because on relogging appear the new (wifi) one instead,and if choose the correct one (wireless) customization has not held, but default.
True!! I reported this in rc thread but it has not been fixed. Please fix that, it is very annoying when using winbox.
 
ela002
Frequent Visitor
Frequent Visitor
Posts: 97
Joined: Tue May 31, 2005 4:19 am

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 4:25 pm

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,
 
pe1chl
Forum Guru
Forum Guru
Posts: 10307
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 4:27 pm

WiFi is always there, but useless?
It's not useless, it can be used as Capsman to manage devices using new wifi driver.
Unfortunately it is not only useless (for those that have no intention to use CapsMAN) but it also causes problems...
When you have configuration in winbox to customize windows, e.g. column layout, it is not handled correctly.
Probably the old and new wifi config windows use the same name or ID or whatever how that is handled in winbox.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10307
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 4:29 pm

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,
hAP ac2 is notorious for lack of space. the best is to netinstall it and restore the backup you made BEFORE the upgrade...
You made a backup, right? It says in the first message above:

Before an upgrade:
1) Remember to make backup/export files before an upgrade and save them on another storage device;
 
User avatar
mkx
Forum Guru
Forum Guru
Posts: 11791
Joined: Thu Mar 03, 2016 10:23 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 4:46 pm

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,
hAP ac2 is notorious for lack of space.
And also consider the fact that wifi-qcom-ac uses around 200kB more flash space than wireless package. So if flash is running tight (and will be, believe me), then the solution might be to stick to wireless.

If one is using ARM ac device as router only (i.e. wireless is not required), then the new arrangement allows to fully uninstall wireless drivers and thus free a few MB of flash (wifi menu is still there as it contains necessary stuff to run CAPsMAN on same device ... but that doesn't require running hardware drivers).
 
massinia
Member Candidate
Member Candidate
Posts: 160
Joined: Thu Jun 09, 2022 7:20 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 4:51 pm

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,
Something else is using the space, I can also install containers and I still have free space.
hap ac2.png
You do not have the required permissions to view the files attached to this post.
 
biomesh
Long time Member
Long time Member
Posts: 567
Joined: Fri Feb 10, 2012 8:25 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 4:51 pm

When updating the firmware on a CCR2004-16G-2S+ the "upgrade firmware" string is different than the version shown under "current firmware" once applied. It looks like there is an extra carriage return in the string - so there always seems to be an update available (even if it has already been applied).
 
User avatar
diamuxin
Member
Member
Posts: 320
Joined: Thu Sep 09, 2021 5:46 pm
Location: Alhambra's City

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 4:52 pm

Hi friends,

In my script this sequence failed:
[ ] > :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.
Last edited by diamuxin on Fri Dec 15, 2023 4:56 pm, edited 2 times in total.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10307
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 4:53 pm

If one is using ARM ac device as router only (i.e. wireless is not required), then the new arrangement allows to fully uninstall wireless drivers and thus free a few MB of flash (wifi menu is still there as it contains necessary stuff to run CAPsMAN on same device ... but that doesn't require running hardware drivers).
Yeah, but as I am locked to the old wireless drivers for now (until the VLAN issues in the new drivers are solved) and I have no intention to use CAPsMAN on that device, I still would prefer to be able to remove the new WiFi package... and keep routeros and wireless on that space-cramped device.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10307
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 4:56 pm

7.12.1 1700221125[/code]

It should report: 7.13 and epoch date
Probably a good thing. It prevents those running auto-upgrade scripts from upgrading in the first couple of hours after release.
The correct version will probably be returned a little later, when there has been no mayhem in this topic.
 
User avatar
msilcher
just joined
Posts: 7
Joined: Mon Mar 09, 2009 9:39 pm
Location: Argentina

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 5:07 pm

Working fine so far on hAP ax2/hAP ac2.

Can we get an updated Zerotier package pleeeeeeeeeeease?
 
rajo
newbie
Posts: 45
Joined: Tue Aug 16, 2011 11:12 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 5:13 pm

It is probably just me, but upgrading from 7.12 to 7.13 on AWS broke the instance again and it does not boot any longer.

I had the same issue upgrading to 7.12 and was forced to recreate the instance.

Isn't there anything I can do to just get the upgrade on AWS working properly?

--Michael
This does not seem version related, send your supout file to support, so we can check what specifics you have there.
It is probably just me, but upgrading from 7.12 to 7.13 on AWS broke the instance again and it does not boot any longer.

I had the same issue upgrading to 7.12 and was forced to recreate the instance.

Isn't there anything I can do to just get the upgrade on AWS working properly?

--Michael
Some additional information relevant to this issue. It actually has nothing to do with upgrading. When I first experienced the same issue I misidentified it as related to licensing. Here is what I now know:

1. Only CHR is affected
2. It occurs when the CHR is rebooted after some extended period of time (weeks maybe?)

#2 is why it is mistaken as an upgrade problem, because you generally aren't going to reboot your router until such time as you need to perform maintenance.

Like BWC, I was unable to obtain debugging info -- especially since Google Compute Engine (GCE) (I suspect the same for AWS) does not output serial console activity during instance disk booting. I probably would have to try on an in-house host to be able to see what's actually happening when it fails. However, GCE (and I believe also AWS) runs on KVM and we use Hyper-V internally; therefore, it's debatable whether I could reproduce the issue in-house. It I get time in the new year (or I'm really bored over the holidays, I might setup an instance to test it out; although results could take weeks or months to achieve. Someone who runs Proxmox in-house would be a better candidate to attempt to reproduce the issue.

In the meantime, I reverted to 6.49.x, because I got tired of having to rebuild the router and it turned out that the automated snapshots also ended up with whatever the corruption is and couldn't be booted.

Hope this info help set MikroTik/others on the right direction to identifying the root cause of this issue.
 
User avatar
merlinthemagic7
Frequent Visitor
Frequent Visitor
Posts: 52
Joined: Fri Sep 16, 2016 8:49 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 5:22 pm

@rajo The issue on AWS likely relates to T3 instances. The Hypervisor is different from T2 (works).

viewtopic.php?p=1027349#p1027349
 
BWC
newbie
Posts: 34
Joined: Tue Mar 21, 2006 5:36 pm
Location: Würzburg, Germany
Contact:

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 5:34 pm

Thanks a bunch, this is crazy, I'll give it a try.
@rajo The issue on AWS likely relates to T3 instances. The Hypervisor is different from T2 (works).

viewtopic.php?p=1027349#p1027349
 
User avatar
mozerd
Forum Veteran
Forum Veteran
Posts: 898
Joined: Thu Oct 05, 2017 3:39 pm
Location: Canada
Contact:

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 5:34 pm

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/greylis ... latest.csv to RAM FAILED: Fetch failed with status 206

The same script was working fine under 7.12.1 and earlier versions

following is script
{
/ip firewall address-list
:local update do={
 :put "Starting import of address-list: $listname"
 :if ($nolog = null) do={:log warning "Starting import of address-list: $listname"}

 :local maxretry 3
 :local retrywaitingtime 120s
 :local retryflag true
 :for retry from=1 to=$maxretry step=1 do={
  :if (retryflag) do={ :set $retryflag false; :set $sounter 0
  :if (retry > 1) do={
   :put "Source file changed. Retrying after a $retrywaitingtime wait..."
   :if ($nolog = null) do={:log warning "Source file changed. Retring after a $retrywaitingtime wait..."}
   :delay $retrywaitingtime  }
  
 :local filesize ([/tool fetch url=$url keep-result=no as-value]->"total")
 :local start 0
 :local maxsize 64000;	        # reqeusted chunk size
 :local end ($maxsize - 1);	# because start is zero the maxsize has to be reduced by one
 :local partnumber	 ($filesize / ($maxsize / 1024)); # how many chunk are maxsize
 :local remainder	 ($filesize % ($maxsize / 1024)); # the last partly chunk 
 :if ($remainder > 0)    do={ :set $partnumber ($partnumber + 1) }; # total number of chunks
 :if ($heirule != null) do={:put "Using as extra filtering: $heirule"} else={:set $heirule "."}
 # remove the current list completely if "erase" is not present (default setting)
  :if ($noerase = null) do={  
   :if ($timeout = null) do={:set $timeout 00:00:00; :do {:foreach i in=[/ip firewall address-list find list=$listname] do={/ip firewall address-list set list=("backup".$listname) $i }} on-error={} } else={
   :do {:foreach i in=[/ip firewall address-list find list=$listname dynamic] do={/ip firewall address-list set list=("backup".$listname) $i }} on-error={} };                
   :put ("Conditional deleting all".$dynamic." entries in address-list: $listname")
   :if ($nolog = null) do={:log warning ("Conditional deleting all".$dynamic." entries in address-list: $listname")}
  } else={:put "Entries not conditional deleted in address-list: $listname"}; # ENDIF ERASE
 :for x from=1 to=$partnumber step=1 do={
   # get filesize to be compared to the orignal one and if changed then retry
   :local comparesize ([/tool fetch url=$url keep-result=no as-value]->"total")
   
#:set $comparesize 5 

   # fetching the chunks from the webserver when the size of the source file has not changed
   # empty array when the source file changed. No processing is done till the next complete retry
   :if ($comparesize = $filesize) do={:set $data ([:tool fetch url=$url http-header-field="Range: bytes=$start-$end" output=user as-value]->"data")} else={:set $data [:toarray ""]; :set $retryflag true}
     #:if ($ownposix = null) do={
  # determining the used delimiter in the list if not provided in the config
   # this only run once and so the impact on the import time is low
    :local ipv4Posix	  "^[0-9]{1,3}\\.[0-9]{1,3}\\.[0-9]{1,3}\\.[0-9]{1,3}"
    :local ipv4rangePosix "^[0-9]{1,3}\\.[0-9]{1,3}\\.[0-9]{1,3}\\.[0-9]{1,3}/[0-9]{1,2}"
    :local domainPosix	  "^.+\\.[a-z.]{2,7}"
    :local sdata $data;     
    :while ([:len $sdata]!=0 && $delimiter = null) do={ # The check on length of $sdata is for if no delimiter is found.
       	:local sline [:pick $sdata 0 [:find $sdata "\n"]]; :local slen [:len $sline];
       	# set posix depending of type of data used in the list
       	:if ($sline ~ $ipv4Posix)	do={:set $posix $ipv4Posix;	 :set $iden "List identified as a IPv4 list"}
       	:if ($sline ~ $ipv4rangePosix)	do={:set $posix $ipv4rangePosix; :set $iden "List identified as a IPv4 with ranges list"}
       	:if ($sline ~ $domainPosix)	do={:set $posix $domainPosix;	 :set $iden "List identified as a domain list"}
       	:if ($sline ~ $posix) do={:put $iden}
      	:if ($sline ~ $posix) do={ # only explore the line if there is match at the start of the line.
	 :do {:if ([:pick $sline 0 ($slen-$send)] ~ ($posix."\$") || $send > $slen) do={
	        :set $delimiter [:pick $sline ($slen-$send) ($slen-($send-1))]; :set $result true} else={:set $send ($send+1)}
	     } while (!$result);
	}; #IF posix
	:set $sdata [:pick $sdata ([:find $sdata "\n"]+1) [:len $sdata]];
	:if ([:len $delimiter] = 0) do={ :set $delimiter "\n" }; # when empty use NewLine 20220529
	:if ($delimiter != null) do={:local sdata [:toarray ""]} ; #Clear array sdata and it is not needed anymore and triggering so the While to end
    }; #WHILE END $sdata
    :local sdata [:toarray ""] 
   #} else={:put "User defind Posix: $ownposix"; :set $posix $ownposix } ; # ENDIF ownposix = null 
   :if ($delimiter = "\n") do={ :set $delimiterShow "New Line" }  else={ :set $delimterShow $delimiter }; #20220529
   :if ($posix = null && $delimiter != null) do={:set $posix "."; :put "Using config-line defined delimiter: \"$delimiterShow\""}; # delimter provided by config line
   :if (!retryflag) do={:put "Reading Part: $x $start - $end"}   
   :if ($timeout = null) do={:local timeout 00:00:00}; # if no timeout is defined make it a static entry.    
   # Only remove the first line only if you are not at the start of list
   
   :if ($start > 0) do={:set $data [:pick $data ([:find $data "\n"]+1) [:len $data]]}
     :while ([:len $data]!=0) do={
       :local line [:pick $data 0 [:find $data "\n"]]; # create only once and checked twice as local variable
       :if ( $line ~ $posix && $line~heirule) do={    
        :do {add list=$listname address=[:pick $data 0 [:find $data $delimiter]] comment=$comment timeout=$timeout; :set $counter ($counter + 1)} on-error={}; # on error avoids any panics        
       }; # if IP address && extra filter if present
      :set $data [:pick $data ([:find $data "\n"]+1) [:len $data]]; # removes the just added IP from the data array
      # Cut of the end of the chunks by removing the last lines...very dirty but it works
      :if ([:len $data] < 256) do={:set $data [:toarray ""]}    
     }; # while

  :set $start (($start-512) + $maxsize); # shifts the subquential start back by 512  
  :set $end (($end-512) + $maxsize); # shift the subquential ends back by 512 to keep the 
  }; # if retryflag
 }; #do for x
 
}; # for retry
 :if ($counter < 1) do={:set $resultline "Import was NOT successfull! Check if the list $listname is still being maintained."} else={:set $resultline "Completed reading $counter items into address-list $listname." } 
 :put $resultline
 :if ($nolog = null) do={:log warning $resultline }
 :if ($counter > 0) do={:do {/ip firewall address-list remove [find where list=("backup".$listname)]} on-error={} } else={
 :do {:foreach i in=[/ip firewall address-list find list=("backup".$listname)] do={/ip firewall address-list set list=$listname $i }} on-error={}
 :put "Restoring backup list: $listname" 
 :if ($nolog = null) do={:log warning "Restoring backup list: $listname"}
 }; # if counter restore on failure and remove on success
}; # do
$update url=https://view.sentinel.turris.cz/greylist-data/greylist-latest.csv listname=turris delimiter=, timeout=1d
}
 
sapin069
just joined
Posts: 3
Joined: Fri Feb 09, 2018 6:34 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 5:37 pm

Hello, I have an issue, How to Upgrade or downgrade to or from Wave2 within 7.13, If a routeur was on wifi5 when upgraded is there a way to upgrade to wave2 within 7.13 or donngrade to Wifi5

Thank you

regards,
 
rajo
newbie
Posts: 45
Joined: Tue Aug 16, 2011 11:12 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 5:42 pm

@rajo The issue on AWS likely relates to T3 instances. The Hypervisor is different from T2 (works).

viewtopic.php?p=1027349#p1027349
As I stated, I experienced the same issue on GCE, which has nothing to do with AWS. I provided the info to help with identifying the actual cause of the issue, if anyone is actually interested in investigating and resolving it.
 
User avatar
diamuxin
Member
Member
Posts: 320
Joined: Thu Sep 09, 2021 5:46 pm
Location: Alhambra's City

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 5:43 pm

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/greylis ... latest.csv to RAM FAILED: Fetch failed with status 206

The same script was working fine under 7.12.1 and earlier versions
Same problem with other scripts:

error ex.
Download from http://::ffff:192.168.8.1/api/webserver/SesTokInfo (::ffff:192.168.8.1) to RAM FAILED: Host is unreachable

versions prior to 7.12.1 there were no problems
 
DeGlucker
just joined
Posts: 14
Joined: Tue Apr 12, 2011 4:35 pm
Location: Moscow, Russia

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 6:00 pm

WiFi on x86 is still broken !!!
Are you going to fix this issue ???
I don't understand what's going on. Why impossible to solve this problem throughout seven ROS releases !?!?!?
 
usx
newbie
Posts: 26
Joined: Sun Oct 27, 2013 7:30 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 6:04 pm

Do I understand it correctly that the WiFi menu/integration is optional?

To go into extremes, I have an Audience and a mAP 2n in my network. I configure the access lists via a Python script which connects via SSH and issues all the commands. Currently all devices are therefore configured via `/interface wireless access-list` commands.

If I were to enable the WiFi menu in the Audience by removing the wireless package and installing the Qualcomm one, I would need to issue different commands to configure that Audience AP with that script, is that correct?

Since I currently do not want to do that change in the script, if I upgrade to 7.13 on the Audience, can I still continue using `/interface wireless access-list` and everything else like before, as long as I don't replace the wireless package with the Qualcomm one?
 
holvoetn
Forum Guru
Forum Guru
Posts: 5612
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 6:10 pm

If I were to enable the WiFi menu in the Audience by removing the wireless package and installing the Qualcomm one, I would need to issue different commands to configure that Audience AP with that script, is that correct?
You would have to do this as well if you were to install the wifiwave2 package under 7.12.
Or on AC3 when installing that same wifiwave2 package.
A bit logical. New features, new menu structure.
Since I currently do not want to do that change in the script, if I upgrade to 7.13 on the Audience, can I still continue using `/interface wireless access-list` and everything else like before, as long as I don't replace the wireless package with the Qualcomm one?
Yes, that should be the case.
 
usx
newbie
Posts: 26
Joined: Sun Oct 27, 2013 7:30 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 6:39 pm

Upgraded without problems:

- RBmAP2n ("mAP 2n") x2
- RBD25G-5HPacQD2HPnD ("Audience")
- 2011UiAS-2HnD
- hAP RB951Ui-2nD ("hAP")
- RB4011iGS
- hEX 750G r3 ("hEX")
 
nemoforum
Frequent Visitor
Frequent Visitor
Posts: 59
Joined: Thu Jan 05, 2017 11:08 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 6:54 pm

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.
Last edited by nemoforum on Fri Dec 15, 2023 7:18 pm, edited 1 time in total.
 
BWC
newbie
Posts: 34
Joined: Tue Mar 21, 2006 5:36 pm
Location: Würzburg, Germany
Contact:

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 7:08 pm

I created a new t3.small instance, deployed 6.44 and updated to 6.49.11 and 7.12.1 after that without issues.
Then I changed instance type to t2.small, updated to 7.13 and changed back to t3.small.

All in all a bit awkward but good to know that there is a way.
Thanks a bunch, this is crazy, I'll give it a try.
@rajo The issue on AWS likely relates to T3 instances. The Hypervisor is different from T2 (works).

viewtopic.php?p=1027349#p1027349
 
User avatar
merlinthemagic7
Frequent Visitor
Frequent Visitor
Posts: 52
Joined: Fri Sep 16, 2016 8:49 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 7:30 pm

@BWC yup the T3 <=> T2 instance change works.

Just dont deploy in regions that dont have any Haswell / Broadwell instances... e.g. eu-south-2

@rajo
We deploy cross platform as well, GCP does not have this issue if you roll your own image that starts out as a V7 instance.
 
valnik
just joined
Posts: 5
Joined: Wed Aug 19, 2020 9:48 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 7:41 pm

Hi, capsman v2 is showing "VLAN-ID CONFIGURED, BUT INTERFACE DOES NOT SUPPORT ASSIGNING VLANS" /cap client is HAP AC2 with wifi-qcom-ac drivers/. Does this has solution or i have some bad config?

Thx.
 
whatever
Member
Member
Posts: 356
Joined: Thu Jun 21, 2018 9:29 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 7:48 pm

Bad config. Wifi-qcom-ac does not support vlan tagging, read the manual.
 
User avatar
merlinthemagic7
Frequent Visitor
Frequent Visitor
Posts: 52
Joined: Fri Sep 16, 2016 8:49 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 7:49 pm

@valnic

802.11n/ac interfaces do not support this type of VLAN tagging under the wifiwave2 package, but they can be configured as VLAN access ports in bridge settings.

https://help.mikrotik.com/docs/pages/vi ... properties
 
onnoossendrijver
Member
Member
Posts: 487
Joined: Mon Jul 14, 2008 11:10 am
Location: The Netherlands

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 8:28 pm

I had to disable/enable the VLAN interface underneath the PPPoE interface to make the PPPoE client work on my RB5009. Am I the only one having this problem?
Last edited by onnoossendrijver on Fri Dec 15, 2023 8:29 pm, edited 1 time in total.
 
User avatar
jvanhambelgium
Forum Guru
Forum Guru
Posts: 1020
Joined: Thu Jul 14, 2016 9:29 pm
Location: Belgium

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 8:28 pm

Upgraded without issues :

RB5009UG+S+
RB3011UiAS
 
fibracapi
just joined
Posts: 9
Joined: Fri Dec 02, 2022 11:52 am

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 9:03 pm

Transferred the 2.4ghz network from capsman to the new 7.13 driver with RB3011 and 2 AP hac ac2. Everything seems to be working correctly.
/interface wifi channel
add band=2ghz-n disabled=no frequency=2412 name="Canales 2,4GHz" width=20/40mhz
/interface wifi datapath
add bridge=HOME disabled=no name=HOME
add bridge=bridge-VLANs disabled=no name=CRISWIFI vlan-id=28
add bridge=bridge-VLANs disabled=no name=DANWIFI vlan-id=24
add bridge=bridge-VLANs disabled=no name=GUEST vlan-id=11
add bridge=bridge-VLANs disabled=no name=IFI-IoT vlan-id=12
/interface wifi security
add authentication-types=wpa2-psk,wpa3-psk disabled=no encryption="" name=WIFI-HOME passphrase=*+password*
add authentication-types=wpa2-psk,wpa3-psk disabled=no encryption="" name=DANWIFI passphrase=++password+
add authentication-types=wpa2-psk,wpa3-psk disabled=no encryption="" name=CRISWIFI passphrase=-+password-
add authentication-types=wpa2-psk,wpa3-psk disabled=no encryption="" name=GUEST passphrase=+password**
add authentication-types=wpa2-psk,wpa3-psk disabled=no encryption="" name=WIFI-IoT passphrase=+password
/interface wifi configuration
add channel="Canales 2,4GHz" datapath=HOME disabled=no mode=ap name=HOME-DYC security=WIFI-HOME ssid="DAN y CRIS"
add channel="Canales 2,4GHz" datapath=DANWIFI disabled=no mode=ap name=DANWIFI security=DANWIFI ssid="WiFi de DAN"
add channel="Canales 2,4GHz" datapath=CRISWIFI disabled=no mode=ap name=CRISWIFI security=CRISWIFI ssid="WiFi de CRIS"
add channel="Canales 2,4GHz" datapath=IFI-IoT disabled=no mode=ap name="WiFi - IoT" security=WIFI-IoT ssid="WiFi - IoT"
add channel="Canales 2,4GHz" datapath=GUEST disabled=no mode=ap name=GUEST security=GUEST ssid="WiFi GUEST"
/interface wifi access-list
add action=accept allow-signal-out-of-range=5s disabled=no interface=any signal-range=-83..120 ssid-regexp=""
add action=reject allow-signal-out-of-range=5s disabled=no interface=any ssid-regexp=""
/interface wifi capsman
set enabled=yes interfaces=all package-path="" require-peer-certificate=no upgrade-policy=none
/interface wifi provisioning
add action=create-dynamic-enabled disabled=no master-configuration=HOME-DYC radio-mac=MIMACADDRESS slave-configurations=\
    "DANWIFI,CRISWIFI,WiFi - IoT,GUEST"
 
User avatar
morphema
just joined
Posts: 6
Joined: Mon May 15, 2023 11:30 am

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 9:05 pm

Is there going to be a tutorial for Audiences setup using wifiwave2?
 
User avatar
Amm0
Forum Guru
Forum Guru
Posts: 3660
Joined: Sun May 01, 2016 7:12 pm
Location: California

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 9:30 pm

*) system - added "rtrace" debugging tool (CLI only);
There are no docs on /system/rtrace. Is its output format the same as linux `strace`, or is there some "reader" tool for it?
 
User avatar
mkx
Forum Guru
Forum Guru
Posts: 11791
Joined: Thu Mar 03, 2016 10:23 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 10:11 pm

Is there going to be a tutorial for Audiences setup using wifiwave2?

What's wrong with this manual?
 
Matta
Member Candidate
Member Candidate
Posts: 116
Joined: Sat Sep 04, 2010 3:13 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 10:51 pm

Is it possible to downgrade LHG XL52 ac from 7.13. to 6.49.11 ?
 
User avatar
mkx
Forum Guru
Forum Guru
Posts: 11791
Joined: Thu Mar 03, 2016 10:23 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 10:56 pm

It's possible to downgrade as low as factory version. This depends on manufacturing date of a particular device.
 
Matta
Member Candidate
Member Candidate
Posts: 116
Joined: Sat Sep 04, 2010 3:13 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 11:21 pm

Apparently I'm doing something wrong. Tried with downgrade option but no success.
 
whatever
Member
Member
Posts: 356
Joined: Thu Jun 21, 2018 9:29 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 11:27 pm

 
User avatar
mkx
Forum Guru
Forum Guru
Posts: 11791
Joined: Thu Mar 03, 2016 10:23 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 11:30 pm

You have to upload npk files to device and then hit the downgrade button. When ROS sees npk file, it tries to install it at reboot ... if it's system package and the version is higher than currently running one (or if it's additional package with version same as running one). But won't install it if version is lower than current one ... unless you hit the downgrade button. But hitting downgrade button will not download older version for you.
 
Matta
Member Candidate
Member Candidate
Posts: 116
Joined: Sat Sep 04, 2010 3:13 pm

Re: v7.13 [stable] is released!

Fri Dec 15, 2023 11:40 pm

I've uploaded routeros-arm-6.49.11.npk, hit downgrade button, LHG reboots with 7.13 version
 
User avatar
JohnTRIVOLTA
Member
Member
Posts: 352
Joined: Sun Dec 25, 2016 2:05 pm
Location: BG/Sofia

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 12:05 am

I've uploaded routeros-arm-6.49.11.npk, hit downgrade button, LHG reboots with 7.13 version
If you have another packet except the main uninstall him first. Then make downgrade procedure!
 
User avatar
morphema
just joined
Posts: 6
Joined: Mon May 15, 2023 11:30 am

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 12:10 am

What's wrong with this manual?
Well, probably nothing wrong from the manual perspective. I'm looking for step-by-step guide for both modes of particular device, which has a bit tricky default config even with old drivers. I'm eager to try new driver but I don't have too much resources for tinkering and guessing the best configuration. There probably should be optimal configs the team used for testing purposes. I see no harm to share them publicly. How do you feel, does it make sense?
 
Matta
Member Candidate
Member Candidate
Posts: 116
Joined: Sat Sep 04, 2010 3:13 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 12:14 am

I've uploaded routeros-arm-6.49.11.npk, hit downgrade button, LHG reboots with 7.13 version
If you have another packet except the main uninstall him first. Then make downgrade procedure!
Thanks m8, that did the trick !
 
Matta
Member Candidate
Member Candidate
Posts: 116
Joined: Sat Sep 04, 2010 3:13 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 12:40 am

By the way, is there likely benefit for PtP link between 2 LHG XL 52ac, to go from 6.49.11 to 7.13, considering wifiwave 2 is available now ?
 
msatter
Forum Guru
Forum Guru
Posts: 2917
Joined: Tue Feb 18, 2014 12:56 am
Location: Netherlands / Nīderlande

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 2:01 am

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/greylis ... latest.csv to RAM FAILED: Fetch failed with status 206

The same script was working fine under 7.12.1 and earlier versions

snip
It can be that they don't support chunking on the moment. However the script can be changed now the file can be downloaded in one go and the then read from disk in chunks of 32KB. Two chunks is 64KB or just double the loops to import the complete file.
 
User avatar
memelchenkov
Member Candidate
Member Candidate
Posts: 202
Joined: Sun Oct 11, 2020 12:00 pm
Contact:

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 2:12 am

Now empty "WiFi" tab in WinBox. And working WiFi tab copied to "Wireless".
 
infabo
Forum Veteran
Forum Veteran
Posts: 810
Joined: Thu Nov 12, 2020 12:07 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 2:25 am

Upgraded D53G-5HacD2HnD successfully. Then I uninstalled wireless package und installed wifi-qcom-ac. LOL, I was astonished as there was not even a default configuration in place for the wifi. Just two disabled interfaces. ROFL, and I had the naive hope that MT transforms my legacy wireless config to the new wifi config. But wasnt that hard to setup manually. I even tried Quick setup out of curiosity to setup some defaults - but that failed hard as a rock. QS created two new interfaces for guest wifi (wlan3/wlan4) but failed to configure wlan1/wlan2. They remained inactive without any configuration. Well played, MT. I was lucky and QS did not destroy anything else according to a export-diff.

One suggestion though: wifi log messages still use the "wireless" prefix. MT should maybe align that so it says wifi there too.
 
jclive
just joined
Posts: 1
Joined: Wed Nov 18, 2015 3:47 am

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 5:30 am

Upgraded a green field RB4011iGS+5HacQ2HnD from 7.12.1. I simply do not have any wireless or for that matter wifi topic logs even with debug enabled.. Which I really need as the 5GHz interface and or config is not working.

Tnx!
 
truefriendcz
newbie
Posts: 39
Joined: Mon Jun 05, 2017 11:07 am

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 5:50 am

I am asking the representatives of Mikrotik to define for me what they mean by the term "stable".
I have a Mikrotik remotely halfway around the world. Once I had to go to a site and install via NetInstall when there was a transition from version 6.x to version 7.x. Now it hasn't even gotten to the 20% newer major next version (8.x) and 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.

Paradoxically, this is an Enterprise environment with a professional range of routers, and I cannot afford downtime for entire companies. Older configurations for LTS versions no longer work, where I am told that it is necessary to upgrade to version 7.x, where the settings and scripts work, but security is not ensured even to the extent that the device does not boot at all after the version update.

I don't know what the problem is anymore. Maybe I'm misunderstanding how the company Mikrtoik interprets the term "stable" version, so I would like it if the engineers from Mikrotik would explain to me how they understand this term. Thank you
And then I want to ask what are the 5 levels of RouterOS test versions for, if this happens in the production version? What is the goal of the test versions?
 
ksteink
Frequent Visitor
Frequent Visitor
Posts: 82
Joined: Thu Mar 31, 2016 6:54 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 6:06 am

I have updated my RB5009 and my CRS326-24G and my scripts for Telegram are not working as expected. I am not getting any message more than the download message with the Chat ID.

I will be rolling back to version 7.12 if this not going to be fixed quickly by Mikrotik
 
ksteink
Frequent Visitor
Frequent Visitor
Posts: 82
Joined: Thu Mar 31, 2016 6:54 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 6:31 am

Another issue: I tried to downgrade to version 7.12.1 and also doesn't work!! I just uploaded the RouterOS 7.12.1 ARM64 into the /files of my RB5009 and went to System --> Packages --> Downgrade and the router refuses to downgrade. Reboots and nothing happens!.

I am so annoyed! and first time I have this kind of behavior. I am getting now messages every min in Telegram with non--sensical messages.
 
sirca
just joined
Posts: 11
Joined: Sun Sep 29, 2019 4:11 am

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 7:01 am

Hi!
I have upgraded from 7.12.1 to 7.13:
CRS326-24G-2S+ X2
CRS317-1G-16S+
CRS305-1G-4S+
CHR (esxi 6.5.0U3)
No issues
 
BluThunder
just joined
Posts: 11
Joined: Fri Aug 18, 2006 1:26 am

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 7:06 am

I have an issue with 7.13 that 7.12.1 didn't have (nor before) - I have a bunch of 1gb SFP's in a CRS328-4C-20S-4S+ switch. None of them will link up auto negotiation at full duplex (they are all fiber). I can hard code both sides of a link and it works full duplex, but with auto negotiation duplex is never picked up and you end up with hundreds of "sfpxx excessive or late collision, link duplex match?" errors and most paths not even passing traffic. Downgrade to 7.12 and it auto negotiates correctly. My 10GB SFP+'s are auto negotiating, only 1GB SFP modules are failing to.
 
kravemir
Frequent Visitor
Frequent Visitor
Posts: 75
Joined: Sun Aug 13, 2023 10:55 am
Location: Slovakia
Contact:

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 8:11 am

I have a Mikrotik remotely halfway around the world. ... and I'll have to fly halfway around the world again to do the Netinstall in person and who knows if it will reinstall.
Who maintains physical hardware halfway around the world - as a sole person / without closer person to perform actions needing aphysical access?

Like, you blame MikroTik, but you've chosen a low-cost platform and at the same time you're going low-cost on people, that you don't even have people nearby the devices you maintain.
 
kalamaja
Member Candidate
Member Candidate
Posts: 114
Joined: Wed May 23, 2018 3:13 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 8:37 am

Paradoxically, this is an Enterprise environment with a professional range of routers, and I cannot afford downtime for entire companies.
MikroTik doesn’t do your business, you do. Even in 10person company no sane person installs version less than 24h old into production. Person who decided that upgrading distant system without test env or local support is a risk for the business.
 
skyhawk
newbie
Posts: 39
Joined: Thu Jan 14, 2016 10:27 am

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 8:50 am

Having package management problems manually updating a hAP ax2 from 7.11.2 -> 7.13

Device has routeros-7.11.2 and wifiwave2-7.11.2 packages installed presently. I dropped routeros-7.13-arm64.npk and wifi-qcom-7.13-arm64.npk onto the device and rebooted, and it came back up still on 7.11.2 with the following error log:

missing package wifiwave2

Do I need to manually update to 7.12 before updating to 7.13?
 
holvoetn
Forum Guru
Forum Guru
Posts: 5612
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 8:53 am

Use normal upgrade procedure.
And yes, you first need to be on 7.12 or 7.12.1 before you can move to 7.13.

Is in the release notes. You may want to read that part first.
 
npero
Member
Member
Posts: 317
Joined: Tue Mar 01, 2005 1:59 pm
Location: Serbia

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 8:54 am

I want to try wifi package outdoor on LHG5 ac. I already try on indoor devices I missing two feature to try outdoor.
First possibility to scan complete list of frequencies not just selected country, because outdoor has lots of devices and some of then, some is maybe wrong word here :) lots of then not comply country regulation or have licenses and want to avoid that frequencies. Sometime they are were close or overlapping some or allowed frequencies.
Second is possible to select some kind of licensed mode or superchannel mode to can select custom frequencies other manufactured allowed that.
If anyone have idea how can to do that ? Thanks.
 
skyhawk
newbie
Posts: 39
Joined: Thu Jan 14, 2016 10:27 am

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 9:00 am

Use normal upgrade procedure.
And yes, you first need to be on 7.12 or 7.12.1 before you can move to 7.13.

Is in the release notes. You may want to read that part first.
To quote the release notes:
1. When upgrading by using "check-for-updates", all versions earlier than 7.12 will display 7.12 as the latest available version. Upgrade from v7.12 to v7.13 or later versions must be done through 7.12 in order to convert wireless packages automatically. Fresh installation with Netinstall or manual package installation works in the same manner as always.
That reads to me as manual package installation should just work without any special attention.

If manual installation needs to be stepped to 7.12 before stepping beyond that's fine, but the release notes should indicate as such.
 
holvoetn
Forum Guru
Forum Guru
Posts: 5612
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 9:08 am

It says you need to be at 7.12 first.
It does not say how.

Upgrade from v7.12 to v7.13 or later versions must be done through 7.12 in order to convert wireless packages automatically.
 
User avatar
cyrq
just joined
Posts: 6
Joined: Sat Mar 11, 2023 12:19 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 9:33 am

After upgrading my hAP ax^3 to ROS 7.13 everything works fine, but the front WPS button which previously was solid blue, now blinks in red.
Created a ticket (SUP-137799).
 
Matta
Member Candidate
Member Candidate
Posts: 116
Joined: Sat Sep 04, 2010 3:13 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 9:47 am

Another issue: I tried to downgrade to version 7.12.1 and also doesn't work!! I just uploaded the RouterOS 7.12.1 ARM64 into the /files of my RB5009 and went to System --> Packages --> Downgrade and the router refuses to downgrade. Reboots and nothing happens!.

I am so annoyed! and first time I have this kind of behavior. I am getting now messages every min in Telegram with non--sensical messages.
"If you have another packet except the main uninstall him first. Then make downgrade procedure! "
Thanks goes @JohnTRIVOLTA
 
holvoetn
Forum Guru
Forum Guru
Posts: 5612
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 9:54 am

After upgrading my hAP ax^3 to ROS 7.13 everything works fine, but the front WPS button which previously was solid blue, now blinks in red.
Created a ticket (SUP-137799).
No problem here. Normal blue (had to open the closed cabinet to verify :lol: )
 
dcavni
Member Candidate
Member Candidate
Posts: 108
Joined: Sun Mar 31, 2013 6:02 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 10:10 am

By the way, is there likely benefit for PtP link between 2 LHG XL 52ac, to go from 6.49.11 to 7.13, considering wifiwave 2 is available now ?
Tried LHG52 with new drivers and it goes up to 600 Mbps, but that was between LHG52 and a mobile phone. I must buy something to try station bridge mode.
 
User avatar
cyrq
just joined
Posts: 6
Joined: Sat Mar 11, 2023 12:19 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 10:41 am

After upgrading my hAP ax^3 to ROS 7.13 everything works fine, but the front WPS button which previously was solid blue, now blinks in red.
Created a ticket (SUP-137799).
No problem here. Normal blue (had to open the closed cabinet to verify :lol: )
Thanks for checking.
Kinda strange since I have WPS completely disabled and as far as I know, this LED can be controlled only via : system leds settings set all-leds-off=immediate
 
sjmudd
just joined
Posts: 10
Joined: Mon Dec 03, 2018 9:19 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 11:26 am

I have had a mixed reaction to 7.13.

Good:
- several CRS125-24G-1S-2HnD upgraded to 7.13 without incident. I'm not confident on doing this on the one that runs capsman yet.
- map mini upgraded fine to 7.13 which was nice considering how small it is.
- RB5009UG+S+ seemed to upgrade fine to 7.13
- Hex PoE (RB960PGS) upgraded fine to 7.13

Bad:
- cap ac ( RBcAPGi-5acD2nD) had zerotier installed and so did not have enough space to upgrade to 7.13, so rebooted itself back to 7.12.1. I didn't need zerotier here so removed the package, tried again and the upgrade went fine.
- hap ac2 just failed completely. I had to netinstall it and put the configuration back, it's still running 7.12.1 as not sure that upgrading again will not do the same thing. (I see others were successful so maybe it is my configuration that's causing the issue.)

A question. I have config collector configured to run export on each router I own, but that does not retain the user credentials or certificates so does not provide a full configuration. What's the correct way to pull the COMPLETE config of a router, and then to restore the COMPLETE config back from one that has for example the default configuration setup? I may have missed this so please point me at the docs and also in the notes you provide at the top of the posts about new releases provide links to the docs.
- ideally I'd like a way to restore using netinstall providing the required ROS version and config, or
- have a way to restore the config and boot back to it in a simple operation.

Netinstall (I run on linux so could only use the netinstall-cli) looks good but only works (I think) if you have the netinstall-cli configured on the same layer 2 network where the router is running. At least in my network that's not possible. So having documentation on how to use netinstall if possible (with some helper functionality / firewall port forwarding etc) would be good and allow me to use this from any router when the netinstall-cli is in a different network. That would avoid me unplugging the "broken router" and moving it somehwere where I can do the netinstall and then putting it back in its intended location.
Last edited by sjmudd on Sat Dec 16, 2023 11:42 am, edited 1 time in total.
 
User avatar
Jotne
Forum Guru
Forum Guru
Posts: 3309
Joined: Sat Dec 24, 2016 11:17 am
Location: Magrathean

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 11:37 am

I am asking the representatives of Mikrotik to define for me what they mean by the term "stable".
I have a Mikrotik remotely halfway around the world.
1. What is stable as been answered many times here in the forum.
2. Upgrading a production system just as it has released is just asking for trouble. Wait at leas a week and read all forum threads about it.
3. You should not upgrade remote system without have a 100% equal system (hardware/software) local to test on. If that goes ok, you may test remote system.

So 100% your fault if some goes wrong.

PS this is the same for Cisco and other brand as well.
 
sjmudd
just joined
Posts: 10
Joined: Mon Dec 03, 2018 9:19 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 11:59 am

I'd tend to agree about running any new "stable" version: If this is for production usage don't try it where you care about failure scenarios.

I work in a large database environment where generally people are very conservative, but I have a setup where I often do test new versions and run bleeding edge even in production. I tend to do testing/evaluation of new versions where I can handle the failure and revert or workaround the problem easily. That's good for the vendor as I can provide upstream feedback about issues they have not seen and wait for or get a custom fix if that's needed. Doing this on more important systems could cause more pain so is often best done later. In the meantime you're getting familiar with the new functionality/features/performance.

That does not mean of course that you won't find bugs. All vendors try to test and avoid causing their customers issues but in the end they don't have the resources to test OUR setups so things will slip through.

What's most important is having an easy way back and that includes having a "good backup" and a "good restore procedure". And like any any of these things you MUST test the "restore procedure". If it doesn't work the backup is not worth anything .... I know my amateur/home setup is not as good in this respect as it could be hence the comment for how to do it better earlier, but for people running this as a business even on routers backups/restores are critical.
 
whatever
Member
Member
Posts: 356
Joined: Thu Jun 21, 2018 9:29 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 12:02 pm

Updated
3x hap ac²
1x RB4011+RM
all coming from ROS 6.49.10 long-term via 7.12.1 to 7.13 successfully. I replaced the wireless package with wifi-qcom-ac on all hap ac²s afterwards.
1x hap ax² update was also fine, but it obviously was on ROS 7 already.

Finally made the move to ROS 7 everywhere, so I can now enjoy all the shiny new features, and so far it's looking great. Had to disable multicast package on RB4011 before being able to upgrade to ROS 7, but apart from some unused default objects popping up in OSPF configuration, the automated config migration was fine.

Wifi experience was great as soon as I figured out the security connect-priority=0/1 option and managed to work around the VLAN limitation.
Now I'm just hoping that VLAN tagging will find its way back into wifi-qcom-ac driver to restore the flexibility it provides.
 
User avatar
Smoerrebroed
Frequent Visitor
Frequent Visitor
Posts: 75
Joined: Mon Feb 12, 2018 10:21 am

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 12:09 pm

No issues upgrading for me among CRS328, RB5009, cAP ac, wAP ac, cAP ax, hAP ax²/ax³ - CAPsMAN works like a charm now in a homgeneous fashion.

A couple things I noticed though:

  • It's not possible to set 2 GHz band to ax AND n, so in a mixed (ac and ax) setup, you either need to allow all bands or define separate channels.
  • You need to provide all upgrade packages for download if CAPsMAN automatic upgrade is supposed to work. Otherwise not even the base package gets upgraded.
  • With CAPsMAN on 7.13 and CAP on 7.12.1, it wasn't possible to set 2472 MHz as a channel frequency (error). After bringing CAP to 7.13 the error disappeared.

All in all: Nice work, MikroTik! I'm happy and ready for Xmas. :-) Enjoy the holidays!
Last edited by Smoerrebroed on Sat Dec 16, 2023 6:25 pm, edited 1 time in total.
 
paxon
just joined
Posts: 7
Joined: Sat Apr 04, 2020 11:30 am

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 1:17 pm

Updated cAP ac, Hap ac, and hap AX^3 (C53UiG+5HPaxD2HPaxD)
Seems to be working fine apart from hap AX^3
Upgraded it to 7.13 then installed container package, after that tried to install wireless package ( to have capsman).
After reboot wireless is in disabled state, when i try to enable it wifi_qcom package gets disabled not sure why.
Screenshot 2023-12-16 at 12.25.06.png
Afrer enabling wireless and reboot, WiFi is not accessible and i have both WiFi and Wireless :
Screenshot 2023-12-16 at 13.23.06.png
You do not have the required permissions to view the files attached to this post.
Last edited by paxon on Sat Dec 16, 2023 2:25 pm, edited 1 time in total.
 
User avatar
mkx
Forum Guru
Forum Guru
Posts: 11791
Joined: Thu Mar 03, 2016 10:23 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 1:38 pm

... installed wifi-qcom-ac. LOL, I was astonished as there was not even a default configuration in place for the wifi.

This is how always has been for packages installed seoarately. Default config is only applied when config is reset to factory default config.

But you can always see default config by executing /system/default-configuration/print inside terminal window (IIRC you need admin privileges).
 
User avatar
Chaosphere64
Frequent Visitor
Frequent Visitor
Posts: 94
Joined: Wed Aug 10, 2016 10:19 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 1:39 pm

I noticed this error after upgrading my hAP ax3 from 7.12:
SCR-20231216-lcle.png
Similar did not happen on my RB5009UPr+S+IN.
You do not have the required permissions to view the files attached to this post.
 
User avatar
Ca6ko
Long time Member
Long time Member
Posts: 500
Joined: Wed May 04, 2022 10:59 pm
Location: Kharkiv, Ukraine

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 2:34 pm

Hap ac2 got a cyclic reboot after upgrading from 7.12 to 7.13. The device boots up and after 30-40 sec goes into reboot. Supout file does not allow downloading the reboot occurs before downloading.
I have not found anything in the logs. At the moment of availability I reset the config. After manual settings works.

Installed packages routeros and wireless. Dude not install
 
holvoetn
Forum Guru
Forum Guru
Posts: 5612
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 2:52 pm

Maybe netinstall that device and see how it behaves then ?
It's the only way to clear the hidden dungeons of left over config etc.
 
Shadeofspirit
Member Candidate
Member Candidate
Posts: 203
Joined: Fri May 27, 2016 12:15 am
Location: Minsk
Contact:

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 2:53 pm

Crs326 - bonding stop working after update to 7.13
Disabling/enabling bonding interface, recreation doesn't help.
Traffic is just stop going after update. (Synology nas is in the other end)
 
urknall
newbie
Posts: 36
Joined: Fri Aug 22, 2014 3:27 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 3:26 pm

I have an issue with 7.13 that 7.12.1 didn't have (nor before) - I have a bunch of 1gb SFP's in a CRS328-4C-20S-4S+ switch. None of them will link up auto negotiation at full duplex (they are all fiber). I can hard code both sides of a link and it works full duplex, but with auto negotiation duplex is never picked up and you end up with hundreds of "sfpxx excessive or late collision, link duplex match?" errors and most paths not even passing traffic. Downgrade to 7.12 and it auto negotiates correctly. My 10GB SFP+'s are auto negotiating, only 1GB SFP modules are failing to.
I also have problems with a Mikrotik S+RJ10 Module and CRS326-24G-2S+RM:

it says link ok, but i cannot connect to the server that is connected via ethernet 10G. Had to netinstall 7.12.1 to get the connection working again...
 
ghassan73
just joined
Posts: 1
Joined: Sun May 03, 2020 9:01 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 3:54 pm

Thanks, however, HAP AC3 (RBD53iG-5HacD2HnD) central led now flashing red. I believe this central LED is related to lte / wps?
Up until version 7.12.1 it was solid blue.
Please advise.
Last edited by ghassan73 on Sat Dec 16, 2023 4:24 pm, edited 2 times in total.
 
Matta
Member Candidate
Member Candidate
Posts: 116
Joined: Sat Sep 04, 2010 3:13 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 4:11 pm

Upgraded two LHG XL52 ac (PtP setup), settings were intact, no issue with signal (-42), devices register themselves on one another (both 2GHz and 5GHz), but can't see other LHG via Winbox.
Any clues ?

EDIT: on 7.12.1 was working perfectly.
 
wfburton
Frequent Visitor
Frequent Visitor
Posts: 83
Joined: Mon Apr 10, 2023 1:09 am

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 4:39 pm

Updated CRS309-1G-8S+

Working

TIA
 
User avatar
JohnTRIVOLTA
Member
Member
Posts: 352
Joined: Sun Dec 25, 2016 2:05 pm
Location: BG/Sofia

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 4:46 pm

Upgraded two LHG XL52 ac (PtP setup), settings were intact, no issue with signal (-42), devices register themselves on one another (both 2GHz and 5GHz), but can't see other LHG via Winbox.
Any clues ?

EDIT: on 7.12.1 was working perfectly.
Are you using the new wifi package? If yes, it does not support station bridge mode yet with old devices/old driver! I use bridge and eoip over wifi link for extending the L2 segment
Last edited by JohnTRIVOLTA on Sat Dec 16, 2023 4:50 pm, edited 1 time in total.
 
mike7
just joined
Posts: 12
Joined: Sun Oct 28, 2018 12:20 am

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 4:47 pm

CCR1016 after updating to 7.13 not show lte interface anymore.
But in USB list it showing.
Image
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.
 
mike7
just joined
Posts: 12
Joined: Sun Oct 28, 2018 12:20 am

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 4:52 pm

After upgrading my hAP ax^3 to ROS 7.13 everything works fine, but the front WPS button which previously was solid blue, now blinks in red.
Created a ticket (SUP-137799).
Do you have usb modem attached? I've got red blinks right after modem connection.
 
dcavni
Member Candidate
Member Candidate
Posts: 108
Joined: Sun Mar 31, 2013 6:02 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 4:53 pm

Upgraded two LHG XL52 ac (PtP setup), settings were intact, no issue with signal (-42), devices register themselves on one another (both 2GHz and 5GHz), but can't see other LHG via Winbox.
Any clues ?

EDIT: on 7.12.1 was working perfectly.
Are you using the new wifi package? If yes, it does not support station bridge mode yet with old devices/old driver! I use bridge and eoip over wifi link for extending the L2 segment
There is station bridge mode in new drivers. Tried it just yesterday on LHG52.
 
holvoetn
Forum Guru
Forum Guru
Posts: 5612
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 4:57 pm

Yup, already in beta versions. Tested it as well.
 
User avatar
krafg
Forum Guru
Forum Guru
Posts: 1024
Joined: Sun Jun 28, 2015 7:36 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 5:03 pm

Updated all my devices without issues.

Regards.
 
Matta
Member Candidate
Member Candidate
Posts: 116
Joined: Sat Sep 04, 2010 3:13 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 5:04 pm

Yup, already in beta versions. Tested it as well.
I know it's a guessing game, but I cannot find what seems to be the problem. I have 2 pairs of PtP link, similar setup (apart for SSID names etc). Both pairs were on 6.49.11. I've upgraded both pairs to 7.12.1 and both were working. Now I upgraded one pair to 7.13 and have above issues. I checked all settings but cannot find the cause.
 
holvoetn
Forum Guru
Forum Guru
Posts: 5612
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 5:06 pm

Start separate thread with export of config.
 
eguun
Frequent Visitor
Frequent Visitor
Posts: 83
Joined: Fri Apr 10, 2020 10:18 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 5:09 pm

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/greylis ... latest.csv to RAM FAILED: Fetch failed with status 206

The same script was working fine under 7.12.1 and earlier versions
Same problem with other scripts:

error ex.
Download from http://::ffff:192.168.8.1/api/webserver/SesTokInfo (::ffff:192.168.8.1) to RAM FAILED: Host is unreachable

versions prior to 7.12.1 there were no problems
+1, report the same error:
- fetch with ipv4 url are automatically "translated" into ipv6 by being prefixed with "::ffff:"
- This results in either host unreachable or data content = null

Had to roll back to 7.12.1
 
dcavni
Member Candidate
Member Candidate
Posts: 108
Joined: Sun Mar 31, 2013 6:02 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 5:34 pm

Yup, already in beta versions. Tested it as well.
I know it's a guessing game, but I cannot find what seems to be the problem. I have 2 pairs of PtP link, similar setup (apart for SSID names etc). Both pairs were on 6.49.11. I've upgraded both pairs to 7.12.1 and both were working. Now I upgraded one pair to 7.13 and have above issues. I checked all settings but cannot find the cause.
When i upgraded LHG52 to 7.13 first in didn't even see wireless intefaces even if wireless package was installed (checked). Probably because there was also Zerotier package on it and something went wrong with the instalation (to little space for all those packages).
I just deleted it and installed qcom ac package and everything seems fine.
 
User avatar
cyrq
just joined
Posts: 6
Joined: Sat Mar 11, 2023 12:19 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 5:42 pm

After upgrading my hAP ax^3 to ROS 7.13 everything works fine, but the front WPS button which previously was solid blue, now blinks in red.
Created a ticket (SUP-137799).
Do you have usb modem attached? I've got red blinks right after modem connection.
Yes!
Just tested this and your're right. After connecting the USB modem the LED starts flashing red.
Unplugging it doesn't change it's behavior. You need to reboot the whole router with the modem unplugged. Plugging it back makes the LED starts blinking red again.
EDIT: disabling the dynamic lte1 interface also restores the LED back to normal (static blue).
Last edited by cyrq on Sat Dec 16, 2023 7:34 pm, edited 1 time in total.
 
kravemir
Frequent Visitor
Frequent Visitor
Posts: 75
Joined: Sun Aug 13, 2023 10:55 am
Location: Slovakia
Contact:

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 5:52 pm

Wifi experience was great as soon as I figured out the security connect-priority=0/1 option and managed to work around the VLAN limitation.
Why is that needed? In my WifiWave2/WiFi CAPsMAN setup I don't use this, and devices connect and roam successfully.
Now I'm just hoping that VLAN tagging will find its way back into wifi-qcom-ac driver to restore the flexibility it provides.
Me too. It would make CAP more controlled - better provisioned without a need to manually set bridge ports and VLANs for wifi interfaces on each CAP.
 
mike7
just joined
Posts: 12
Joined: Sun Oct 28, 2018 12:20 am

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 5:55 pm



Do you have usb modem attached? I've got red blinks right after modem connection.
Yes!
Just tested this and your're right. After connecting the USB modem the LED starts flashing red.
Unplugging it doesn't change it's behavior. You need to reboot the whole router with the modem unplugged. Plugging it back makes the LED starts blinking red again.
My modem is useless with 7.13 (
lte interface just disappeared )
 
User avatar
diamuxin
Member
Member
Posts: 320
Joined: Thu Sep 09, 2021 5:46 pm
Location: Alhambra's City

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 6:02 pm

+1, report the same error:
- fetch with ipv4 url are automatically "translated" into ipv6 by being prefixed with "::ffff:"
- This results in either host unreachable or data content = null

Had to roll back to 7.12.1
Indeed that is the problem, you have explained it better than me ;)
Let's see what solution they give us.

TESTs:
======
# Imput CLI:
{
:local urlSesTokInfo "http://192.168.8.1/api/webserver/SesTokInfo"
:put ([/tool fetch $urlSesTokInfo output=user as-value]->"data")
}

# Log message v7.13:
Download from http://::ffff:192.168.8.1/api/webserver/SesTokInfo (::ffff:192.168.8.1) to RAM FINISHED

# Log message v7.12.1:
No message (ok)

Why do more messages appear in the log like fetch, stp, debug, etc?
Last edited by diamuxin on Sat Dec 16, 2023 6:37 pm, edited 3 times in total.
 
whatever
Member
Member
Posts: 356
Joined: Thu Jun 21, 2018 9:29 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 6:07 pm

Why is that needed? In my WifiWave2/WiFi CAPsMAN setup I don't use this, and devices connect and roam successfully.
At least with FT disabled, the default connect-priority setting delays roaming to a new AP until a client has disconnected from its previous AP. With my Android phone this caused several seconds of delay when roaming.

Setting connect-priority=0/1 ensures connections to a new AP are immediately accepted and the old AP connection is dropped automatically. When using PSK authentication, this allows seamless roaming even without FT.
 
ppsascha
just joined
Posts: 5
Joined: Mon Apr 18, 2022 10:31 am

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 6:54 pm

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?
 
jhbarrantes
Frequent Visitor
Frequent Visitor
Posts: 56
Joined: Wed Aug 21, 2019 2:56 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 7:58 pm

Why migrated configurations (upgrade from 7.12.x to 7.13) has setup non default values for port-cost-mode=short at the bridge, as well as defining internal-path-cost + path-cost at ports?

Thanks!
 
User avatar
diamuxin
Member
Member
Posts: 320
Joined: Thu Sep 09, 2021 5:46 pm
Location: Alhambra's City

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 8:03 pm

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?
The fetch command has incorporated new features, check the parameters of your "tool/fetch..." script.
https://help.mikrotik.com/docs/display/ROS/Fetch
Last edited by diamuxin on Sat Dec 16, 2023 8:05 pm, edited 2 times in total.
 
zentavr
newbie
Posts: 49
Joined: Tue Nov 05, 2013 2:11 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 8:04 pm

I have RB4011iGS+5HacQ2Hnd and cAp ac at one building.
I'd upgraded both to v7.13. CAPSMAN was installed at 4011. The problem is that wireless interfaces at cAP connected successfully to 4011, but 4011 cannot manage its own interfaces.

The same issue with the standalone router RB2011UiAS-2HnD - it cannot manage own wireless interfaces as well.
 
zentavr
newbie
Posts: 49
Joined: Tue Nov 05, 2013 2:11 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 8:07 pm

Tells me: `CAP did not find suitable CAPsMAN`
CapsMAN setup:
/interface wireless cap
# 
set bridge=bridge-lan caps-man-addresses="" caps-man-certificate-common-names="" \
    caps-man-names="" certificate=none discovery-interfaces=bridge-lan enabled=yes \
    interfaces=wlan1,wlan2 lock-to-caps-man=no static-virtual=no

/caps-man manager
set ca-certificate=none certificate=none enabled=yes package-path="" \
    require-peer-certificate=no upgrade-policy=none
/caps-man manager interface
set [ find default=yes ] disabled=no forbid=no interface=all
add disabled=no forbid=yes interface=bridge-wan
add disabled=no forbid=yes interface=sfp-sfpplus1
add disabled=no forbid=yes interface=ether1
add disabled=no forbid=yes interface=ether2



 
zentavr
newbie
Posts: 49
Joined: Tue Nov 05, 2013 2:11 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 8:14 pm

I had to set up 127.0.0.1 as a CAPsMAN address at the router which should manage itself. It had been worked for years before without that.
 
PappaB
just joined
Posts: 14
Joined: Thu Nov 16, 2023 1:55 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 9:34 pm

I upgraded my HAP AC2 from 7.12.1 to 7.13.
Also upgraded the routerboard to the same version.
Removed wireless from packages
Downloaded the 7.13 ARM Extra packages
Uploaded the wifi-qcom-ac
Rebooted

Neither my 2.4 nor 5 GHz interfaces are visible in the Wifi / Menu.
From the Youtube Video (2:39) https://www.youtube.com/watch?v=AkBIQxi-VKs the interfaces should be there, just need to be enabled and configured
However, mine is blank (No interfaces)

I tried with 7.13rc4, and the same situation.
As a last resort I can try to do a facory reset, but I am travelling, and will only be physically close to the router in a week if something goes wrong.

Just to get everyone being able to use the wireless again, I uploaded the wireless-arm.npk, and rebooted. Everything is at least working for the time being.

Any ideas welcome.
 
kalamaja
Member Candidate
Member Candidate
Posts: 114
Joined: Wed May 23, 2018 3:13 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 9:43 pm

I upgraded my HAP AC2 from 7.12.1 to 7.13.
Neither my 2.4 nor 5 GHz interfaces are visible in the Wifi / Menu.
hAP AC2 is quite tight on storage, so check first, if wifi-qcom-ac module is successfully installed and listed in System->Packages? There should be 2: routeros and wifi-qcom-ac.
After getting wifi-qcom-ac installed, by default both wifi interfaces are without configuration and disabled, so use oneliner configuration available in WiFi wikipage.
 
trackersoft
just joined
Posts: 1
Joined: Fri Jan 06, 2023 10:46 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 10:43 pm

Hello guys,
after i upgraded my LTE6 LHG from 7.12 to 7.13 i have problems deleting the sms.
When i click delete in winbox or via command line, my lte connection drops and reconnects.
This happens every time when i delete sms.
I guess it is some kind of bug.
 
User avatar
spacex
Frequent Visitor
Frequent Visitor
Posts: 64
Joined: Sun Aug 19, 2018 6:03 pm

Re: v7.13 [stable] is released!

Sat Dec 16, 2023 11:34 pm

Hello,
Bonding does not work on our Wireless Wire Cube Pro device after 7.13. Those who use this product should be careful. The solution is to disable bonding and add WLAN1 bridge network directly.
 
ksteink
Frequent Visitor
Frequent Visitor
Posts: 82
Joined: Thu Mar 31, 2016 6:54 pm

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 2:53 am

Another issue: I tried to downgrade to version 7.12.1 and also doesn't work!! I just uploaded the RouterOS 7.12.1 ARM64 into the /files of my RB5009 and went to System --> Packages --> Downgrade and the router refuses to downgrade. Reboots and nothing happens!.

I am so annoyed! and first time I have this kind of behavior. I am getting now messages every min in Telegram with non--sensical messages.
"If you have another packet except the main uninstall him first. Then make downgrade procedure! "
Thanks goes @JohnTRIVOLTA
Thx it worked
 
User avatar
dioeyandika
just joined
Posts: 20
Joined: Fri Feb 08, 2019 11:30 am

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 3:26 am

*) 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;

Upgrade sucess in RB750Gr3
My backup script work only for .backup file but dont work with .rsc file, i am confused which part is doesnt work, the rsc file show in sdcard but i cannot see in FTP server, only .backup file and no .rsc file
# script settings
:local saveConfigBackup         true
:local saveSystemBackup         true
:local encryptSystemBackup      false
:local keepRecentLocalBackup    true

# ftp settings
:local ftpUpload                true
:local ftpAddress               "192.168.0.100"
:local ftpPort                  "990"
:local ftpUser                  "****"
:local ftpPassword              "****"
:local ftpDestination           "/NAS/Mikrotik"

# destination directory for local system backup file (.backup)
:local systemBackupDir "/sd1-part1/"

# destination directory for local config backup file (.rsc)
:local configBackupDir "/sd1-part1/"

# filename prefix
:local filePrefix "MikroTik"

#-------------------------------------------------------------------------------------------------------------------------

:log warning message="START: Backup Script"

# system identity
:local systemIdentity ([/system identity get name])

# router os version
:local routerOSVersion ("RouterOS v".[/system package get number=0 value-name=version])

# months array
:local months ("jan","feb","mar","apr","may","jun","jul","aug","sep","oct","nov","dec")

# get current time
:local currentTime [/system clock get time]
:set currentTime ([:pick $currentTime 0 2].[:pick $currentTime 3 5].[:pick $currentTime 6 8])

# get current Date
:local currentDate [/system clock get date]

# convert name of month to number
:local month [ :pick $currentDate 0 3 ]
:local monthNumber ([ :find $months $month -1 ] + 1)
:if ($monthNumber < 10) do={
    :set monthNumber ("0" . $monthNumber)
}

# set $currentDate to format YYYY-MM-DD
:set currentDate ([:pick $currentDate 7 11] .".". $monthNumber .".". [:pick $currentDate 4 6])

# filename for system backup
:local backupFilename ($filePrefix."_".$systemIdentity."_".$routerOSVersion."_".$currentDate."_".$currentTime.".backup")

# filename for config backup
:local configFilename ($filePrefix."_".$systemIdentity."_".$routerOSVersion."_".$currentDate."_".$currentTime.".rsc")

# filename for wildcard filename search
:local wildcardFilename ($filePrefix."_".$systemIdentity."_".$routerOSVersion."_")

# store various error messages
:local errorMessage

# do not modify - this variable is used for error handling
:local scriptError false

# do not modify - this variable is used for error handling
:local exitBackupScript false

# remove all previous local backups
    :foreach backupFile in=[/file find name~"$wildcardFilename"] do={
        :do {
            /file remove $backupFile
        }   on-error={
                :set errorMessage "Backup Script: Error removing/clearing backups"
                :log error message="$errorMessage"
                :set scriptError true
                :set exitBackupScript true
            }
}

# save new system backup
:if (($saveSystemBackup = true) && ($scriptError = false)) do={
    :if (($encryptSystemBackup = true) && ($scriptError = true)) do={
        :do {
            /system backup save name="$systemBackupDir/$backupFilename"
        }   on-error={
                :set errorMessage "Backup Script: Error saving system backup (.backup file)"
                :log error "$errorMessage"
                :set scriptError true
                :set exitBackupScript true
            }
    }
    :if (($encryptSystemBackup = false) && ($scriptError = false)) do={
        :do {
            /system backup save dont-encrypt=yes name="$systemBackupDir/$backupFilename"
        }   on-error={
                :set errorMessage "Backup Script: Error saving encrypted system backup (.backup file)"
                :log error "$errorMessage"
                :set scriptError true
                :set exitBackupScript true
            }
    }
    :log info message="Backup Script: Finished system backup $systemBackupDir/$backupFilename"
}

# save new config backup
:if (($saveConfigBackup = true) && ($scriptError = false)) do={
    :do {
        /export show-sensitive compact file="/$configBackupDir/$configFilename"
        :log info message="Backup Script: Finished config backup $configBackupDir/$configFilename"
    }   on-error={
            :set errorMessage "Backup Script: Error saving config backup (.rsc file)"
            :log error "$errorMessage"
            :set scriptError true
            :set exitBackupScript true
        }
}

# upload to ftp
:if ($ftpUpload = true) do={

    :delay 5

    :if (($saveSystemBackup = true) && ($scriptError = false)) do={
        :if ([:len [/file find name~"$backupFilename"]] > 0) do={
            :do {
                /tool fetch mode=ftp address="$ftpAddress" port="$ftpPort" user="$ftpUser" password="$ftpPassword"\
                src-path="$systemBackupDir/$backupFilename" dst-path="$ftpDestination/$backupFilename" upload=yes
                :log info message="Backup Script: Finished uploading system backup via FTP to $ftpAddress$ftpDestination/$backupFilename"
            }   on-error={
                    :set errorMessage "Backup Script: Error uploading system backup $systemBackupDir/$backupFilename via FTP to $ftpAddress$ftpDestination/$backupFilename"
                    :log error "$errorMessage"
                    :set scriptError true
                    :local exitBackupScript true
                }
        } 
    }

    :delay 5

    :if (($saveConfigBackup = true) && ($scriptError = false)) do={
        :if ([:len [/file find name~"$configFilename"]] > 0) do={
            :do {
                /tool fetch mode=ftp address="$ftpAddress" port="$ftpPort" user="$ftpUser" password="$ftpPassword"\
                src-path="$configBackupDir/$configFilename" dst-path="$ftpDestination/$configFilename" upload=yes
                :log info message="Backup Script: Finished uploading config backup via FTP to $ftpAddress$ftpDestination/$configFilename"
            }   on-error={
                    :set errorMessage "Backup Script: Error uploading config backup $configBackupDir/$configFilename via FTP to $ftpAddress$ftpDestination/$configFilename"
                    :log error "$errorMessage"
                    :set scriptError true
                    :set exitBackupScript true
                }
        }
    }
}
:log warning message="END: Backup Script"
###################################
This is the second script for upload to gmail
######## The destination email address #########
:local mailTo "****@gmail.com"

######## File Preferences #########
:local saveUserDb false
:local saveSysBackup true
:local encryptSysBackup false
:local saveRawExport true

########### Change not anything below this line or shit will break ###########

:local ts [/system clock get time]
:set ts ([:pick $ts 0 2].[:pick $ts 3 5].[:pick $ts 6 8])

:local ds [/system clock get date]
:set ds ([:pick $ds 7 11].[:pick $ds 0 3].[:pick $ds 4 6])

:local identity [/system identity get name]
:local version [/system resource get version]
:local serial [/system routerboard get serial-number]
:local model [/system routerboard get model]

# Extract the RouterBoard model series (up to the first space)
:local modelSeries [:pick $model 0 ([:find $model " "])]

:local fname ("BACKUP-" . $identity . "-" . $version . "-" . $model . "-" . $serial . "-" . $ds . "-" . $ts)
:local sfname ("/" . $fname)

:if ($saveUserDb) do={
  /tool user-manager database save name=($sfname.".umb")
  :log info message="User Manager DB Backup Finished"
}

:if ($saveSysBackup) do={
  :if ($encryptSysBackup) do={
    /system backup save name=($sfname.".backup")
  } else={
    /system backup save dont-encrypt=yes name=($sfname.".backup")
  }
  :log info message="System Backup Finished"
}

if ($saveRawExport) do={
  /export show-sensitive file=($sfname.".rsc")
  :log info message="Raw configuration script export Finished"
}

:local backupFileName

#delay between export (sync). If this is too short backup will not exist for email.
:delay 5s

:foreach backupFile in=[/file find] do={
  :set backupFileName ("/" . [/file get $backupFile name])
  :if ([:typeof [:find $backupFileName $sfname]] != "nil") do={
       :log info message="Sending email of Backup Files"
       :put "Sending email of Backup File - $backupFileName"
       #FML!
       :local pathFileFix
       :for i from=0 to=([:len $backupFileName] - 1) do={
          :local char [:pick $backupFileName $i]
          :if ($char = "/") do={
            :set $char ""
          }
          :set pathFileFix ($pathFileFix . $char)
        }

       /tool e-mail send to=$mailTo subject="$pathFileFix" file="$pathFileFix"

       #delay between message send (sync) and file being deleted. If this is too short, the file will be deleted BEFORE the email is sent. Default 5s
       :delay 10s
       /file remove $backupFile
    }
  }
}
can anyone tell me which part should i change from this script
2.png
Screenshot 2023-12-17 083313.png
You do not have the required permissions to view the files attached to this post.
 
User avatar
nithinkumar2000
Member Candidate
Member Candidate
Posts: 164
Joined: Wed Sep 11, 2019 7:42 am
Location: Coimbatore
Contact:

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 7:20 am

Awsome Mikrotik Team!!!

Waiting for ISIS Features and Documents Update...
 
User avatar
JohnTRIVOLTA
Member
Member
Posts: 352
Joined: Sun Dec 25, 2016 2:05 pm
Location: BG/Sofia

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 9:19 am

Yup, already in beta versions. Tested it as well.
I'm talking about old devices connected to the new ones or with new wave2 drivers. For me work station pseudobridge mode, but in the stationbridge mode does not pass traffic, in station mode pass only L2.
 
infabo
Forum Veteran
Forum Veteran
Posts: 810
Joined: Thu Nov 12, 2020 12:07 pm

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 9:45 am

ao use oneliner configuration available in WiFi wikipage.
where can I find this one liner?

And another OT question because the wifi doc is very cryptic about this command functionality:
/interface/wifi reset wifi1
What is being reset? What can I expect to be reset? I am afraid calling this and then being screwed with an invalid config state...
 
anuser
Long time Member
Long time Member
Posts: 601
Joined: Sat Nov 29, 2014 7:27 pm

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 9:51 am

Thank you very much for new wifi-qcom-ac package and it's included support for cAP ac. Is airtime fairness feature (ATF) enabled by default for IPQ40xx devices? Or is it disabled?
 
PappaB
just joined
Posts: 14
Joined: Thu Nov 16, 2023 1:55 pm

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 10:20 am

I upgraded my HAP AC2 from 7.12.1 to 7.13.
Neither my 2.4 nor 5 GHz interfaces are visible in the Wifi / Menu.
hAP AC2 is quite tight on storage, so check first, if wifi-qcom-ac module is successfully installed and listed in System->Packages? There should be 2: routeros and wifi-qcom-ac.
After getting wifi-qcom-ac installed, by default both wifi interfaces are without configuration and disabled, so use oneliner configuration available in WiFi wikipage.
It is possible that the wifi-qcom-ac is not installing. I only have routeros and zerotier (which I use to remotely manage the router).

Nothing else in files....

Has anyone done it with zerotier still installed on HAP AC2?
 
dcavni
Member Candidate
Member Candidate
Posts: 108
Joined: Sun Mar 31, 2013 6:02 pm

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 10:26 am

It does not work with Zerotier on Hap Ac2. To little storage for qcom and zerotier together.

I think it's missing around 300 - 500 kB of space.
 
whatever
Member
Member
Posts: 356
Joined: Thu Jun 21, 2018 9:29 pm

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 10:28 am

It doesn't fit with any extra packages, you have to remove zerotier before installing wifi-qcom-ac.
 
User avatar
JohnTRIVOLTA
Member
Member
Posts: 352
Joined: Sun Dec 25, 2016 2:05 pm
Location: BG/Sofia

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 11:06 am

Hmm, now i tested 3 modes - station, station bridge and station pseudobridge. I have basebox2 with second 5ghz radio and cAPac, both with last stable 7.13 version.
Basebox2 is connected to the cAPac on main 2ghz radio to cAPac and second 5ghz radio work in AP mode. The two radios /4 gen/ are in the bridge.My laptop is connected to the 5ghz second radio on basebox2.
Station mode - the radio is connected, but no traffic is passing through.
Station bridge mode - the radio does not connect
Station pseudobridge mode - the radio is connected, but no traffic is passing through.
 
infabo
Forum Veteran
Forum Veteran
Posts: 810
Joined: Thu Nov 12, 2020 12:07 pm

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 11:08 am

Thank you very much for new wifi-qcom-ac package and it's included support for cAP ac. Is airtime fairness feature (ATF) enabled by default for IPQ40xx devices? Or is it disabled?
Has MT an air time fairness implementation at all? Isn't that something off-standards?
 
whatever
Member
Member
Posts: 356
Joined: Thu Jun 21, 2018 9:29 pm

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 12:09 pm

Station bridge mode - the radio does not connect
You can't use station bridge mode between old wireless and new wifi driver, it requires the same driver on both sides. This is documented in the manual.
 
User avatar
JohnTRIVOLTA
Member
Member
Posts: 352
Joined: Sun Dec 25, 2016 2:05 pm
Location: BG/Sofia

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 12:31 pm

Station bridge mode - the radio does not connect
You can't use station bridge mode between old wireless and new wifi driver, it requires the same driver on both sides. This is documented in the manual.
OK, but why device with the wifi card /AR9888/ with old drivers on RBM33G, works with a device with new drivers /cAP AC/ in station pseudobridge mode transparently?
 
User avatar
mkx
Forum Guru
Forum Guru
Posts: 11791
Joined: Thu Mar 03, 2016 10:23 pm

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 12:45 pm


You can't use station bridge mode between old wireless and new wifi driver, it requires the same driver on both sides. This is documented in the manual.
OK, but why device with the wifi card /AR9888/ with old drivers on RBM33G, works with a device with new drivers /cAP AC/ in station pseudobridge mode transparently?
Because station-pseudobridge uses standard 802.11 over the air, the "pseudobridge" magic happens entirely inside station device while "bridge" part of station-bridge uses non-standard extensions of 802.11 over the air ... and those extensions are in principle incompatible between different vendors. MT started to use chipset-producer drivers and thus became incompatible with themselves (previously drivers were made by MT). Which makes me believe there willl be another incompatibility if/when MT starts to use wifi chipsets not made by Qualcomm.

The "transparently" part of your question is yet another thing. station-pseudobridge is not truly transparent in sense that L2 properties (MAC addresses) are masked off ... and that causes problems with any services which rely on transparency of L2 (ARP tables, DHCP protocol, etc.).
 
User avatar
JohnTRIVOLTA
Member
Member
Posts: 352
Joined: Sun Dec 25, 2016 2:05 pm
Location: BG/Sofia

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 1:30 pm


OK, but why device with the wifi card /AR9888/ with old drivers on RBM33G, works with a device with new drivers /cAP AC/ in station pseudobridge mode transparently?
Because station-pseudobridge uses standard 802.11 over the air, the "pseudobridge" magic happens entirely inside station device while "bridge" part of station-bridge uses non-standard extensions of 802.11 over the air ... and those extensions are in principle incompatible between different vendors. MT started to use chipset-producer drivers and thus became incompatible with themselves (previously drivers were made by MT). Which makes me believe there willl be another incompatibility if/when MT starts to use wifi chipsets not made by Qualcomm.

The "transparently" part of your question is yet another thing. station-pseudobridge is not truly transparent in sense that L2 properties (MAC addresses) are masked off ... and that causes problems with any services which rely on transparency of L2 (ARP tables, DHCP protocol, etc.).
Thank you @mkx . My question is why BaseBox2 can't connect or can't set station modes with bridge, but other radio can - in this case rbm33g with AR9888 , if we claim that something is not possible with old drivers? Basebox2 can't create station pseudobridge, RBM33G can?
 
User avatar
mkx
Forum Guru
Forum Guru
Posts: 11791
Joined: Thu Mar 03, 2016 10:23 pm

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 1:58 pm

@JohnTRIVOLTA, I think you should focus on getting straight "station" to pass traffic. That's the most straight forward station mode and should work in any case, regardless the vendor and/or driver generation of either AP or station. After you get station working, pseudobridge should be a relatively easy task.

But make sure the other end is not set to "bridge", it has to run either as "AP" or "AP-bridge".
Last edited by mkx on Sun Dec 17, 2023 2:00 pm, edited 1 time in total.
 
PappaB
just joined
Posts: 14
Joined: Thu Nov 16, 2023 1:55 pm

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 1:59 pm

I upgraded my HAP AC2 from 7.12.1 to 7.13.
Neither my 2.4 nor 5 GHz interfaces are visible in the Wifi / Menu.
hAP AC2 is quite tight on storage, so check first, if wifi-qcom-ac module is successfully installed and listed in System->Packages? There should be 2: routeros and wifi-qcom-ac.
After getting wifi-qcom-ac installed, by default both wifi interfaces are without configuration and disabled, so use oneliner configuration available in WiFi wikipage.
You were all correct.
I set up a VPN to my edge router, so I could test the process using a "local" IP instead of Zerotier.
After removing Zerotier, I was able to load wifi-qcom-ac and the interfaces were visible and could be configured.

After all of that I decided to roll back though, as Zerotier is more important (ability to remotely manage) for me at the moment.

I will check in future if there is more unbundling taking place, and whether I will be able to get wifi-qcom-ac and Zerotier running together.
A few of the core components are not really vital to me, as the HAP AC2s I have are just APs, the edge device is an RB5009 where I need full functionality.
It is really a pity that storage is so limited on the HAP AC2, as it is otherwise an excellent device.

I would consider upgrading all my HAP AC2s to HAP AX2s, but the AX2s do not have an USB port, which I use on the AC2s to drive small ESP32 cameras (small enough power requirement to work quite well).
That leaves me with the AX3 as an option, but the size and price difference does not justify it.
If only we had an USB port on the AX2, or a similarly specced device at a similar price point to the AX2 with an USB port.
Mikrotik - consider bringing out a HAP AX2.5-U (AX2 with an USB port and same small size)

Let's see what the future holds.
 
User avatar
diamuxin
Member
Member
Posts: 320
Joined: Thu Sep 09, 2021 5:46 pm
Location: Alhambra's City

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 2:13 pm

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;
 
User avatar
JohnTRIVOLTA
Member
Member
Posts: 352
Joined: Sun Dec 25, 2016 2:05 pm
Location: BG/Sofia

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 2:19 pm

@JohnTRIVOLTA, I think you should focus on getting straight "station" to pass traffic. That's the most straight forward station mode and should work in any case, regardless the vendor and/or driver generation of either AP or station. After you get station working, pseudobridge should be a relatively easy task.

But make sure the other end is not set to "bridge", it has to run either as "AP" or "AP-bridge".
Thank you @mkx! Station standalone mode works on both boards /Basebox2 or RBM33G/, but i don't want L3 with EoiP/VPLS for the L2 transparent connectivity! My question is why basebox2 can't work in this mode /station pseduebridge, others modes not works with bridge/ like the RBM33G , both with same ros version and old drivers, if the problem is the old driver only?
 
User avatar
mkx
Forum Guru
Forum Guru
Posts: 11791
Joined: Thu Mar 03, 2016 10:23 pm

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 2:24 pm

If basebox2 works in station mode but not in station-pseudobridge, then it's the pseudobridge function on basebox2 which is broken. Pseudobridge doesn't "offload" anything on the other end if the radio link.
 
jbarbieri
newbie
Posts: 25
Joined: Thu Sep 06, 2018 6:46 pm

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 2:38 pm

Transferred the 2.4ghz network from capsman to the new 7.13 driver with RB3011 and 2 AP hac ac2. Everything seems to be working correctly.
/interface wifi channel
add band=2ghz-n disabled=no frequency=2412 name="Canales 2,4GHz" width=20/40mhz
/interface wifi datapath
add bridge=HOME disabled=no name=HOME
add bridge=bridge-VLANs disabled=no name=CRISWIFI vlan-id=28
add bridge=bridge-VLANs disabled=no name=DANWIFI vlan-id=24
add bridge=bridge-VLANs disabled=no name=GUEST vlan-id=11
add bridge=bridge-VLANs disabled=no name=IFI-IoT vlan-id=12
/interface wifi security
add authentication-types=wpa2-psk,wpa3-psk disabled=no encryption="" name=WIFI-HOME passphrase=*+password*
add authentication-types=wpa2-psk,wpa3-psk disabled=no encryption="" name=DANWIFI passphrase=++password+
add authentication-types=wpa2-psk,wpa3-psk disabled=no encryption="" name=CRISWIFI passphrase=-+password-
add authentication-types=wpa2-psk,wpa3-psk disabled=no encryption="" name=GUEST passphrase=+password**
add authentication-types=wpa2-psk,wpa3-psk disabled=no encryption="" name=WIFI-IoT passphrase=+password
/interface wifi configuration
add channel="Canales 2,4GHz" datapath=HOME disabled=no mode=ap name=HOME-DYC security=WIFI-HOME ssid="DAN y CRIS"
add channel="Canales 2,4GHz" datapath=DANWIFI disabled=no mode=ap name=DANWIFI security=DANWIFI ssid="WiFi de DAN"
add channel="Canales 2,4GHz" datapath=CRISWIFI disabled=no mode=ap name=CRISWIFI security=CRISWIFI ssid="WiFi de CRIS"
add channel="Canales 2,4GHz" datapath=IFI-IoT disabled=no mode=ap name="WiFi - IoT" security=WIFI-IoT ssid="WiFi - IoT"
add channel="Canales 2,4GHz" datapath=GUEST disabled=no mode=ap name=GUEST security=GUEST ssid="WiFi GUEST"
/interface wifi access-list
add action=accept allow-signal-out-of-range=5s disabled=no interface=any signal-range=-83..120 ssid-regexp=""
add action=reject allow-signal-out-of-range=5s disabled=no interface=any ssid-regexp=""
/interface wifi capsman
set enabled=yes interfaces=all package-path="" require-peer-certificate=no upgrade-policy=none
/interface wifi provisioning
add action=create-dynamic-enabled disabled=no master-configuration=HOME-DYC radio-mac=MIMACADDRESS slave-configurations=\
    "DANWIFI,CRISWIFI,WiFi - IoT,GUEST"
That's interesting. When I went to 7.13 it broke my slave configurations. Running on a HAP AC. Took me a bit to troubleshoot then went back to 7.12.1 and had to reload (same) config for it to come back. Debating on trying again today.
 
User avatar
JohnTRIVOLTA
Member
Member
Posts: 352
Joined: Sun Dec 25, 2016 2:05 pm
Location: BG/Sofia

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 2:43 pm

If basebox2 works in station mode but not in station-pseudobridge, then it's the pseudobridge function on basebox2 which is broken. Pseudobridge doesn't "offload" anything on the other end if the radio link.
Basebox2 does not work in any mode and rbm33g only works with station pseudobridge great like station bridge , but why?
@whatever wrote:
"You can't use station bridge mode between old wireless and new wifi driver, it requires the same driver on both sides. This is documented in the manual."
Last edited by JohnTRIVOLTA on Sun Dec 17, 2023 3:10 pm, edited 2 times in total.
 
nostromog
Member Candidate
Member Candidate
Posts: 226
Joined: Wed Jul 18, 2018 3:39 pm

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 2:59 pm

I upgrading my SOHO network from 7.12 (no ax router) and my main hAP ac2 went apparently ok... until next morning when I did another /export and it entered a boot loop

Apparently the "old" capsman configuration was crashing the machine soon after reboot, with a message about a critical program crashing, and I had to reset the configuration to get it back to live.
Now I'm re-doing the configuration carefully. Still have not re-joined the two capman "slaves", and I'm afraid it will enter the loop again.

I'm using the wireless package. Is there any known problem with "old" capsman config in 7.13?
 
peich1
just joined
Posts: 5
Joined: Mon Dec 11, 2017 9:43 am

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 4:07 pm

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

At 7.12 all ok.
I've got the same problem with a Huawei E3372h-153. I've also got a E3372h-320 that seems to work fine.

But the E3372h-153 just disappears. It goes up for a split second and then goes down. Tried in a RB5009 and a AX3. I've also tried with a RB2011 and it works for a few seconds after restart, but then RX/TX stays at 0 mbps. I ended up downgrading to 7.12 and works fine again. There's definitely something broken in 7.13.

Also, after upgrading +30 devices, I've got a problem with a CRS328: interfaces didn't go up after upgrade. I had to connect using the console cable and observed there were 0 bytes left. After deleting some files and the wireless package, it booted correctly.
 
User avatar
mkx
Forum Guru
Forum Guru
Posts: 11791
Joined: Thu Mar 03, 2016 10:23 pm

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 4:30 pm

Basebox2 does not work in any mode
Well, make up your mind, you wrote in your previous post that ...
Station standalone mode works on both boards /Basebox2 or RBM33G/
 
User avatar
JohnTRIVOLTA
Member
Member
Posts: 352
Joined: Sun Dec 25, 2016 2:05 pm
Location: BG/Sofia

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 5:01 pm

Basebox2 does not work in any mode
Well, make up your mind, you wrote in your previous post that ...
Station standalone mode works on both boards /Basebox2 or RBM33G/
Make a difference between wifi station mode alone and wifi station mode as a bridgeport in the bridge!
 
whatever
Member
Member
Posts: 356
Joined: Thu Jun 21, 2018 9:29 pm

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 5:04 pm

Why would you add a station mode interface to a bridge? This makes no sense at all and cannot produce any usable result.
 
User avatar
JohnTRIVOLTA
Member
Member
Posts: 352
Joined: Sun Dec 25, 2016 2:05 pm
Location: BG/Sofia

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 5:06 pm

Why would you add a station mode interface to a bridge? This makes no sense at all and cannot produce any usable result.
Тo try to somehow get l2 connectivity working.
Leave this modе aside, the question isn't about it.
Why station pseudobridge work with old drivers on RBM33G, but not with basebox2 ? This is my question!
 
User avatar
mkx
Forum Guru
Forum Guru
Posts: 11791
Joined: Thu Mar 03, 2016 10:23 pm

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 5:11 pm

IMO wifi interface in straight station mode is useless as bridge port by definition. Because only that particular device (as an L3 entity) can communicate via wireless in station mode.
 
User avatar
mkx
Forum Guru
Forum Guru
Posts: 11791
Joined: Thu Mar 03, 2016 10:23 pm

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 5:16 pm

Why station pseudobridge work with old drivers on RBM33G, but not with basebox2 ? This is my question!

As I already wrote: it is probably a bug ... either in ROS on basebox2 or in config applied to basebox2. If you suspect a bug in ROS (I guess you do), then make supout.rif of non-working basebox2 (and preferably of the working vasebox2 running 7.12.1 for a refrence) and send them to Mikrotik to investigate.
 
User avatar
JohnTRIVOLTA
Member
Member
Posts: 352
Joined: Sun Dec 25, 2016 2:05 pm
Location: BG/Sofia

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 5:21 pm

IMO wifi interface in straight station mode is useless as bridge port by definition. Because only that particular device (as an L3 entity) can communicate via wireless in station mode.
Focus on the question that interests me please! I tested again with a different board/NetMetal 5/ and with the old driver work in station pseudobridge mode too. If the driver incompatibility old/new was a problem, why some boards can work, other not?
Last edited by JohnTRIVOLTA on Sun Dec 17, 2023 5:26 pm, edited 1 time in total.
 
User avatar
JohnTRIVOLTA
Member
Member
Posts: 352
Joined: Sun Dec 25, 2016 2:05 pm
Location: BG/Sofia

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 5:25 pm

Why station pseudobridge work with old drivers on RBM33G, but not with basebox2 ? This is my question!

As I already wrote: it is probably a bug ... either in ROS on basebox2 or in config applied to basebox2. If you suspect a bug in ROS (I guess you do), then make supout.rif of non-working basebox2 (and preferably of the working basebox2 running 7.12.1 for a refrence) and send them to Mikrotik to investigate.
Thank you ! I will make some more tests with another models.
 
kurio
newbie
Posts: 25
Joined: Sun Dec 22, 2013 6:15 pm

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 6:30 pm

You were all correct.
I set up a VPN to my edge router, so I could test the process using a "local" IP instead of Zerotier.
After removing Zerotier, I was able to load wifi-qcom-ac and the interfaces were visible and could be configured.

After all of that I decided to roll back though, as Zerotier is more important (ability to remotely manage) for me at the moment.

I will check in future if there is more unbundling taking place, and whether I will be able to get wifi-qcom-ac and Zerotier running together.
A few of the core components are not really vital to me, as the HAP AC2s I have are just APs, the edge device is an RB5009 where I need full functionality.
It is really a pity that storage is so limited on the HAP AC2, as it is otherwise an excellent device.
Yes, if i knew that 16 MB devices are crap, i would not buy AC2.
Normally, when you upgrade with zerotier, you don't have space even for wireless package, so the upgrade fails and you are left on 12.1.
You can only have 13 with zerotier, if you remove all configuration, upgrade, install wireless (no new wifi-qcom-ac), and then install zerotier. And you have to know how to upload it correctly (not to flash, but to RAM). But you will end up with 0% free space. So, you risk to lock up your device, if put lots of config on it, or if it generates over 100-200 kilobytes of files.
I am sure that we will never see the room for extra packages on 16MB devices. Their obsolescence was programmed, and has arrived. This is called "efficient management based on effective marketing".
Because zerotier is very important for me, i had to downgrade to 12.1, and will never upgrade until i would never need zerotier anymore.
Many enthusiasts will now have to spend more money on their expensive toys.
 
mike7
just joined
Posts: 12
Joined: Sun Oct 28, 2018 12:20 am

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 6:31 pm

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

At 7.12 all ok.
I've got the same problem with a Huawei E3372h-153. I've also got a E3372h-320 that seems to work fine.

But the E3372h-153 just disappears. It goes up for a split second and then goes down. Tried in a RB5009 and a AX3. I've also tried with a RB2011 and it works for a few seconds after restart, but then RX/TX stays at 0 mbps. I ended up downgrading to 7.12 and works fine again. There's definitely something broken in 7.13.

Also, after upgrading +30 devices, I've got a problem with a CRS328: interfaces didn't go up after upgrade. I had to connect using the console cable and observed there were 0 bytes left. After deleting some files and the wireless package, it booted correctly.
Looks like 7.13 breaks E3372h-153 somehow, after downgrade ROS to 7.12 I can't use HiLink API for sms and I can't send sms from modem either. I tried to reflash, upgrade modem and reset to factory, still have an issue with sms. May be something happened with sim card, but can only check in the next year (
 
optio
Forum Veteran
Forum Veteran
Posts: 709
Joined: Mon Dec 26, 2022 2:57 pm

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 6:48 pm

Regarding 16MB flash devices, to have possibility in future to install any new ROS versions and any supported packages for device architecture maybe MT needs to consider feature to extend system partition with external drive or even possibility to completely use external drive partition as system root. Some 16MB devices have enough other resources (cpu/ram) that serves user's purpose. Why forcing to buy new device just for more system storage? (rhetorical question).
Also 7.12.x can be set as long term release due to changes in 7.13, because some cannot upgrade to that version with some packages combinations due device storage limitation. In this case 7.12 must receive patches for major/security issues.
 
jirinovak
just joined
Posts: 6
Joined: Fri Oct 22, 2010 1:45 pm

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 7:13 pm

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.
 
lubomirs
just joined
Posts: 5
Joined: Tue Feb 05, 2019 4:07 pm

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 8:04 pm

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.)
Last edited by lubomirs on Sun Dec 17, 2023 8:33 pm, edited 1 time in total.
 
User avatar
diamuxin
Member
Member
Posts: 320
Joined: Thu Sep 09, 2021 5:46 pm
Location: Alhambra's City

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 8:22 pm

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.

+1
 
andriys
Forum Guru
Forum Guru
Posts: 1530
Joined: Thu Nov 24, 2011 1:59 pm
Location: Kharkiv, Ukraine

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 8:30 pm

Setting connect-priority=0/1 ensures connections to a new AP are immediately accepted and the old AP connection is dropped automatically. When using PSK authentication, this allows seamless roaming even without FT.
Thanks for the tip, man. You are a lifesaver!
 
dvoijen
just joined
Posts: 7
Joined: Fri Mar 23, 2018 2:01 pm

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 9:22 pm

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.
Here the same, i have a RB5009UG+S After upgrade it keeps rebooting after 5 á 10 minutes.
 
dvoijen
just joined
Posts: 7
Joined: Fri Mar 23, 2018 2:01 pm

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 9:28 pm

Another issue: I tried to downgrade to version 7.12.1 and also doesn't work!! I just uploaded the RouterOS 7.12.1 ARM64 into the /files of my RB5009 and went to System --> Packages --> Downgrade and the router refuses to downgrade. Reboots and nothing happens!.

I am so annoyed! and first time I have this kind of behavior. I am getting now messages every min in Telegram with non--sensical messages.
Uninstall the Wireless Package before downgrade.
 
markatel
just joined
Posts: 2
Joined: Tue Sep 19, 2023 10:53 pm

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 9:54 pm

After upgrading to 7.13, the connectivity to CCR1009 router was lost.

After inspection, it seems that Bridge VLAN Filtering behavior has changed and is not correct.

There are all VLANs declared in the Bridge/VLANs table but the VLAN filtering wasn't enabled on the bridge.

Still, the traffic wasn't passing by.

Please be aware. Support ticket opened: SUP-137880
 
User avatar
ahmdzaki18
just joined
Posts: 12
Joined: Fri Oct 06, 2023 7:52 pm
Location: Jakarta, Indonesia
Contact:

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 10:06 pm

Is anyone trying IS-IS cli? is it good?
 
pe1chl
Forum Guru
Forum Guru
Posts: 10307
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 10:48 pm

After upgrading to 7.13, the connectivity to CCR1009 router was lost.
Upgrading from what version?
 
pe1chl
Forum Guru
Forum Guru
Posts: 10307
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 10:51 pm

Regarding 16MB flash devices, to have possibility in future to install any new ROS versions and any supported packages for device architecture maybe MT needs to consider feature to extend system partition with external drive or even possibility to completely use external drive partition as system root.
Has been suggested before, e.g. when the hAP ac2 could not run wifiwave2 due to space restrictions, but that model has USB.
No meaningful reaction, so I presume they "just don't want to do that" for whatever reason.
 
holvoetn
Forum Guru
Forum Guru
Posts: 5612
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: v7.13 [stable] is released!

Sun Dec 17, 2023 10:52 pm

After upgrading to 7.13, the connectivity to CCR1009 router was lost.
Upgrading from what version?
If stable, 7.12 or 7.12.1, obviously.
 
zdiv
just joined
Posts: 7
Joined: Thu Sep 01, 2011 12:06 pm

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 12:02 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.
I have same behavior with CCR1036-8G-2S+,CCR1009-7G-1C-1S+ and CCR2004-1G-12S+2XS.
Getting Log messages (CLI):
rebooted without proper shutdown by watchdog timer
or
router was rebooted without proper shutdown, probably kernel failure

After returning to 7.12.1 everything seams to be stable
 
giannici
newbie
Posts: 28
Joined: Thu May 11, 2017 4:17 pm

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 12:09 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.
Here the same, i have a RB5009UG+S After upgrade it keeps rebooting after 5 á 10 minutes.
We experience that too!
An RB4011 crashed after a few minutes or half an hour, it seems it depends on the amount of traffic.
A CCR2216 crashed after a few hours.

Every other router without VPLS have no problem.
 
optio
Forum Veteran
Forum Veteran
Posts: 709
Joined: Mon Dec 26, 2022 2:57 pm

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 12:11 am

No meaningful reaction, so I presume they "just don't want to do that" for whatever reason.
My guess is they don't want additional development cost to sell less devices.
 
dalami
Member Candidate
Member Candidate
Posts: 155
Joined: Mon Dec 12, 2011 9:18 am

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 1:10 am

Is there a list of devices that require/support the "wifi-qcom-ac" package? Should the "wireless" package be uninstalled first?
 
templeos
just joined
Posts: 19
Joined: Mon Aug 26, 2019 3:58 pm

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 1:17 am

Is there a list of devices that require/support the "wifi-qcom-ac" package? Should the "wireless" package be uninstalled first?
https://help.mikrotik.com/docs/display/ ... ss'package
https://help.mikrotik.com/docs/display/ ... patibility
Uninstalling is a MUST on everything that is on the compatibility list and has 16MB flash, that is if you want to use wifi-qcom-ac instead of wireless package.
 
dalami
Member Candidate
Member Candidate
Posts: 155
Joined: Mon Dec 12, 2011 9:18 am

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 1:50 am

That helps! Thank you.
 
User avatar
anav
Forum Guru
Forum Guru
Posts: 19848
Joined: Sun Feb 18, 2018 11:28 pm
Location: Nova Scotia, Canada
Contact:

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 2:01 am

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/greylis ... 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!!
 
User avatar
bajodel
Long time Member
Long time Member
Posts: 552
Joined: Sun Nov 24, 2013 8:30 am
Location: Italy

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 3:24 am

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
just joined
Posts: 5
Joined: Mon Apr 18, 2022 10:31 am

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 7:19 am

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
Long time Member
Long time Member
Posts: 601
Joined: Sat Nov 29, 2014 7:27 pm

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 7:58 am

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
Frequent Visitor
Frequent Visitor
Posts: 86
Joined: Wed Sep 13, 2006 12:12 pm
Location: Jakarta

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 8:22 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.
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
 
User avatar
sch
Frequent Visitor
Frequent Visitor
Posts: 76
Joined: Tue Feb 26, 2013 1:05 pm

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 9:02 am

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
MikroTik Support
MikroTik Support
Posts: 21
Joined: Mon Oct 22, 2018 3:25 pm

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 9:26 am

CCR1016 after updating to 7.13 not show lte interface anymore.
But in USB list it showing.
Image
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
just joined
Posts: 2
Joined: Tue Sep 19, 2023 10:53 pm

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 9:28 am


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
Member
Member
Posts: 427
Joined: Tue Jul 07, 2015 2:40 pm
Location: Croatia, Zagreb

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 10:05 am

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)
Last edited by ivicask on Mon Dec 18, 2023 11:06 am, edited 1 time in total.
 
rpingar
Long time Member
Long time Member
Posts: 593
Joined: Fri May 28, 2004 2:46 pm
Location: Italy

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 10:41 am

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
Forum Guru
Forum Guru
Posts: 10307
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 11:29 am



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
just joined
Posts: 14
Joined: Thu Nov 16, 2023 1:55 pm

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 11:38 am

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 .... viewtopic.php?t=190932

If anyone has a fix / workaround, please advise.
 
mondychan
just joined
Posts: 5
Joined: Wed May 25, 2016 11:10 am

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 12:00 pm

+1
Cube 60Pro ac bonding stopped working after upgrading 7.12 -> 7.13
 
User avatar
jacekes
Member Candidate
Member Candidate
Posts: 167
Joined: Tue Aug 30, 2011 9:34 am
Location: Poznan, Poland
Contact:

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 12:36 pm

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.
 
User avatar
diamuxin
Member
Member
Posts: 320
Joined: Thu Sep 09, 2021 5:46 pm
Location: Alhambra's City

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 12:53 pm

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.
 
User avatar
jacekes
Member Candidate
Member Candidate
Posts: 167
Joined: Tue Aug 30, 2011 9:34 am
Location: Poznan, Poland
Contact:

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 1:31 pm

All my routers say 7.12.1 1700221125
 
optio
Forum Veteran
Forum Veteran
Posts: 709
Joined: Mon Dec 26, 2022 2:57 pm

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 1:49 pm

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
Member Candidate
Member Candidate
Posts: 220
Joined: Fri May 14, 2010 11:51 pm

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 1:59 pm

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.
 
User avatar
spacex
Frequent Visitor
Frequent Visitor
Posts: 64
Joined: Sun Aug 19, 2018 6:03 pm

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 2:08 pm

+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.
 
User avatar
mozerd
Forum Veteran
Forum Veteran
Posts: 898
Joined: Thu Oct 05, 2017 3:39 pm
Location: Canada
Contact:

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 2:36 pm

[ ] > :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.
Yes you are correct .... even through My CCR1009 is on 7.13 your code reports 7.12.1 1700221125
 
xkubus
just joined
Posts: 5
Joined: Sun Dec 11, 2011 7:49 pm

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 2:38 pm

USB LTE is completely broken and I can't downgrade because the wireless package is not present in any old firmware. For example, all_packages-arm-7.13.zip contains the wireless package, but all_packages-arm-7.12.1.zip and older ones do not. Please fix this because LTE is the only internet and the work has completely stopped.
If anyone has wireless-7.12.1-arm.npk please post it.
Last edited by xkubus on Mon Dec 18, 2023 2:46 pm, edited 1 time in total.
 
whatever
Member
Member
Posts: 356
Joined: Thu Jun 21, 2018 9:29 pm

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 2:45 pm

Old ROS 7 versions don't need a separate wireless package, just uninstall wireless and downgrade the main routeros package.
 
User avatar
mozerd
Forum Veteran
Forum Veteran
Posts: 898
Joined: Thu Oct 05, 2017 3:39 pm
Location: Canada
Contact:

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 2:52 pm

on my CCR1009
After upgrade to 7.13 from 7.12.1 when I attempt to downgrade back to 7.12.1 the downgrade fails.
Log file shows
omitting package system-7.12.1: newer package system-7.13 is already installed
I tried 2 methods for the downgrade
1. via terminal
2. via Packages
Both return the same result as shown the above quote ...
 
xkubus
just joined
Posts: 5
Joined: Sun Dec 11, 2011 7:49 pm

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 2:57 pm

Old ROS 7 versions don't need a separate wireless package, just uninstall wireless and downgrade the main routeros package.
Thank you very much, everything works.
 
User avatar
diamuxin
Member
Member
Posts: 320
Joined: Thu Sep 09, 2021 5:46 pm
Location: Alhambra's City

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 3:01 pm

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.
It makes no sense what you say, if I consult that web address (I use it in my scripts) it has to inform you which is the latest stable version that Mikrotik has, just that (it has nothing to do with which router I make the request from).

It should report that the LATEST VERSION available is v7.13. (and not 7.12).
 
User avatar
diamuxin
Member
Member
Posts: 320
Joined: Thu Sep 09, 2021 5:46 pm
Location: Alhambra's City

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 3:08 pm

on my CCR1009
After upgrade to 7.13 from 7.12.1 when I attempt to downgrade back to 7.12.1 the downgrade fails.
Log file shows
omitting package system-7.12.1: newer package system-7.13 is already installed
I tried 2 methods for the downgrade
1. via terminal
2. via Packages
Both return the same result as shown the above quote ...
Hi friend, to downgrade from 7.13 to 7.12.X you only have to have in /system/package the package "routeros" and delete the rest, then the downgrade works.
 
User avatar
diamuxin
Member
Member
Posts: 320
Joined: Thu Sep 09, 2021 5:46 pm
Location: Alhambra's City

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 3:19 pm

Dear Staff, on hAP ac^2 (and lower) with v7.13 equipment the RAM memory available is ridiculous, 128 MB -> 26 or 28 MB available. I think you should improve the wireless packages so that they don't consume so much.

..
 
sinisa
just joined
Posts: 24
Joined: Sun Apr 17, 2011 12:46 am

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 3:34 pm

Just wanted to add that after update to 7.13 bonding does not work on Hex PoE too.
Downgrade fixed the problem...
 
andriys
Forum Guru
Forum Guru
Posts: 1530
Joined: Thu Nov 24, 2011 1:59 pm
Location: Kharkiv, Ukraine

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 3:38 pm

It should report: 7.13 and epoch date: 1702542240 approx.
I suspect that URL was used by RouterOS itself to check for new versions. Now that they mandate the 7.12.x to be an intermediate stop on the upgrade path to 7.13 and newer, I believe they introduced a new URL, and the old one will point to the latest 7.12.x version forever.
 
ksteink
Frequent Visitor
Frequent Visitor
Posts: 82
Joined: Thu Mar 31, 2016 6:54 pm

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 3:52 pm

I confirm downgrading to 7.12.1 fix / restores my issue with Telegram notifications. Don't know the issue but this version (aside of the wireless major change) is a non-go / deal breaker for me with this issue
 
holvoetn
Forum Guru
Forum Guru
Posts: 5612
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 4:08 pm

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.
It makes no sense what you say, if I consult that web address (I use it in my scripts) it has to inform you which is the latest stable version that Mikrotik has, just that (it has nothing to do with which router I make the request from).

It should report that the LATEST VERSION available is v7.13. (and not 7.12).
And still.
You HAVE to pass 7.12 or 7.12.1 before you can go up.
 
User avatar
diamuxin
Member
Member
Posts: 320
Joined: Thu Sep 09, 2021 5:46 pm
Location: Alhambra's City

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 4:25 pm

It should report: 7.13 and epoch date: 1702542240 approx.
I suspect that URL was used by RouterOS itself to check for new versions. Now that they mandate the 7.12.x to be an intermediate stop on the upgrade path to 7.13 and newer, I believe they introduced a new URL, and the old one will point to the latest 7.12.x version forever.
It makes sense what you say. Then I will have to find out what the new web address is.
Thanks.
 
User avatar
diamuxin
Member
Member
Posts: 320
Joined: Thu Sep 09, 2021 5:46 pm
Location: Alhambra's City

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 4:30 pm

And still.
You HAVE to pass 7.12 or 7.12.1 before you can go up.
Maybe I have not explained well, it is not about upgrading, my version before upgrading to 7.13 was version 7.12.1 that I know, that web address I use in some of my scripts to know the last available version 7.X and its upgrade date in epoch format. As @andriys says they may have changed the address.

test code

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

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

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

[ ] > :put ([/tool fetch url="https://upgrade.mikrotik.com/routeros/N ... evelopment" as-value output=user]->"data")
7.12.1 1700221125
Last edited by diamuxin on Mon Dec 18, 2023 4:46 pm, edited 1 time in total.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10307
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 4:34 pm

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.
Did you upgrade by downloading routeros 7.13 and then uploading it to the device?
Instead you need to login to the device and select system->packages->upgrade.
Probably when you want to use the manual upload/reboot method you need to upload wireless 7.13 along with routeros yourself.
 
benkreuter
just joined
Posts: 7
Joined: Mon Nov 29, 2021 1:30 am

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 4:51 pm

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.
I have a similar problem, on devices using MPLS/VPLS I see kernel panics every few hours and a lot of problems with packets not being forwarded or routed properly. I have seen it on an RB4011 (arm), RB5009 (arm64), and CCR1009 (tile). No supout generated, just a log message about the router being improperly rebooted and a suggestion that a kernel panic might be the reason.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10307
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 5:11 pm

In such cases it may be possible to get more info by connecting something to the RS232 console port (e.g. a computer running a terminal program) and see what is sent there at the time of the crash.
 
whatever
Member
Member
Posts: 356
Joined: Thu Jun 21, 2018 9:29 pm

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 5:39 pm

they may have changed the address.
> :put ([/tool fetch url="http://upgrade.mikrotik.com/routeros/NEWESTa7.stable" as-value output=user]->"data")
7.13 1702545848
 
User avatar
mozerd
Forum Veteran
Forum Veteran
Posts: 898
Joined: Thu Oct 05, 2017 3:39 pm
Location: Canada
Contact:

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 5:45 pm

Hi friend, to downgrade from 7.13 to 7.12.X you only have to have in /system/package the package "routeros" and delete the rest, then the downgrade works.
Hi diamuxin
Your suggested fix did not work for me ...
 
User avatar
diamuxin
Member
Member
Posts: 320
Joined: Thu Sep 09, 2021 5:46 pm
Location: Alhambra's City

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 5:48 pm

they may have changed the address.
> :put ([/tool fetch url="http://upgrade.mikrotik.com/routeros/NEWESTa7.stable" as-value output=user]->"data")
7.13 1702545848
thanks a lot!!
 
User avatar
diamuxin
Member
Member
Posts: 320
Joined: Thu Sep 09, 2021 5:46 pm
Location: Alhambra's City

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 5:57 pm

Hi diamuxin
Your suggested fix did not work for me ...
I did it with an RB4011 and it worked for me.

What process did you follow?
 
Z0ltan
newbie
Posts: 35
Joined: Sat Dec 15, 2018 3:07 pm

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 5:57 pm

For all the mixed CAPSMAN users (ac & ax): I have created 2 configurations for each SSID, 1 with data path for ax and 1 without data path for ac. VLAN configuration did not work for ac using the bridge because the CAPSMAN interfaces are dynamic (even with the static slave option set), however I was able to make it work by defining the data path locally on the ac device and assigning the data path to the CAP interface. This sets up the PVID value and VLANs will work, the downside is you have to create all data paths locally on each ac device.
 
User avatar
mozerd
Forum Veteran
Forum Veteran
Posts: 898
Joined: Thu Oct 05, 2017 3:39 pm
Location: Canada
Contact:

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 6:13 pm

What process did you follow?
1st step is copy file routeros-7.12.1-tile.npk to Files except I renamed the file like you suggested routeros
2nd step is via terminal issue /system/package/downgrade

This did not work

The procedure that is outlined in the MikroTiK Docs as follows also did not work for me ...
https://help.mikrotik.com/docs/display/ ... g+RouterOS
 
User avatar
diamuxin
Member
Member
Posts: 320
Joined: Thu Sep 09, 2021 5:46 pm
Location: Alhambra's City

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 6:28 pm

What process did you follow?
1st step is copy file routeros-7.12.1-tile.npk to Files except I renamed the file like you suggested routeros
2nd step is via terminal issue /system/package/downgrade

This did not work

The procedure that is outlined in the MikroTiK Docs as follows also did not work for me ...
https://help.mikrotik.com/docs/display/ ... g+RouterOS
Do not rename the routeros-7.12.1-tile.npk file uploaded to files.

In v7.13 the package "routeros" already exists in System > Package. You have to delete (uninstall) the existing packages except the "routeros" package, then do the downgrade.
 
User avatar
mozerd
Forum Veteran
Forum Veteran
Posts: 898
Joined: Thu Oct 05, 2017 3:39 pm
Location: Canada
Contact:

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 6:57 pm

In v7.13 the package "routeros" already exists in System > Package. You have to delete (uninstall) the existing packages except the "routeros" package, then do the downgrade.
OK followed your suggestion but that did not work ... thanks but now i will wait for 7.13.1 :-)
 
majestic
Frequent Visitor
Frequent Visitor
Posts: 90
Joined: Mon Dec 05, 2016 11:19 am

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 7:06 pm

Upgraded my RB5009UPr+S+ successfully.

However, I am a little hesitant in upgrading my Wireless Wire (which is really two wAP60G). I was wondering if anyone has upgraded these safely?

Thanks in advance.
Last edited by majestic on Mon Dec 18, 2023 7:20 pm, edited 1 time in total.
 
Simonej
Frequent Visitor
Frequent Visitor
Posts: 59
Joined: Sun Aug 22, 2021 3:34 am

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 7:15 pm

*) fetch - require "ftp" user policy;
is policy=ftp necessary in any script now to use Fetch (also when mode=http/s) or just when mode=ftp is used?
 
User avatar
osc86
Member Candidate
Member Candidate
Posts: 197
Joined: Wed Aug 09, 2017 1:15 pm

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 7:39 pm

I don't have the Wireless Wire, but a CubeG-5ac60ad kit. Both have similar hardware.
Updated both units the day 7.13 was released. 60G link has an uptime of over 3 days now.
No issues so far, should be safe to update.
 
majestic
Frequent Visitor
Frequent Visitor
Posts: 90
Joined: Mon Dec 05, 2016 11:19 am

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 7:42 pm

I don't have the Wireless Wire, but a CubeG-5ac60ad kit. Both have similar hardware.
Updated both units the day 7.13 was released. 60G link has an uptime of over 3 days now.
No issues so far, should be safe to update.
Thanks very much, guess its upgrade time, cheers again.
 
majestic
Frequent Visitor
Frequent Visitor
Posts: 90
Joined: Mon Dec 05, 2016 11:19 am

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 8:05 pm

I don't have the Wireless Wire, but a CubeG-5ac60ad kit. Both have similar hardware.
Updated both units the day 7.13 was released. 60G link has an uptime of over 3 days now.
No issues so far, should be safe to update.
I can confirm that Wireless Wire has upgraded successfully. It took approx 3-4 minutes to reboot and upgrade.
 
holvoetn
Forum Guru
Forum Guru
Posts: 5612
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 8:13 pm

In v7.13 the package "routeros" already exists in System > Package. You have to delete (uninstall) the existing packages except the "routeros" package, then do the downgrade.
OK followed your suggestion but that did not work ... thanks but now i will wait for 7.13.1 :-)
You did upload the downgrade package to files before hitting "Downgrade", did you ?
 
User avatar
mozerd
Forum Veteran
Forum Veteran
Posts: 898
Joined: Thu Oct 05, 2017 3:39 pm
Location: Canada
Contact:

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 8:45 pm

You did upload the downgrade package to files before hitting "Downgrade", did you ?
Yes I did upload the downgrade package to Files before hitting the “Downgrade” …

Very annoying that the MikroTik instructions as shown in the link I provided earlier did not work … my only recourse now if I want to downgrade is Netinstall … with the CCR1009 Is quite a rigamarole ….
 
holvoetn
Forum Guru
Forum Guru
Posts: 5612
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 8:51 pm

I hear you, good luck then.

I guess that's a consequence from the upgrade from 7.12 to 7.13 and all the background things they had to foresee for that path to go as smooth as possible.
Not perfect, see reports on mishaps, and apparently not that easy to reverse either.
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1636
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 9:11 pm

If you do try to upgrade/downgrade RouterOS manually, then router do expect 1:1 packages match. If that is not possible (for example, wifi-qcominstalled on 7.13) then on packages menu schedule these packages for uninstall. Uploadpackages that you want to install and execute downgrade command. If that does not work then take a look at the log - it will tell you why did not the upgrade/downgrade work. There is no need for netinstall to re-manage packages.

If that does not work, then please provide detailed example to support@mikrotik.com. We have not seen such case yet. Only rumors :) Upgrad/downgrade is simple package removal and install process. But it starts the process only if there is 1:1 packages match.
 
timnis
just joined
Posts: 9
Joined: Fri Jun 15, 2018 2:03 pm

Re: v7.13 [stable] is released!

Mon Dec 18, 2023 11:43 pm

I have an issue with 7.13 that 7.12.1 didn't have (nor before) - I have a bunch of 1gb SFP's in a CRS328-4C-20S-4S+ switch. None of them will link up auto negotiation at full duplex (they are all fiber). I can hard code both sides of a link and it works full duplex, but with auto negotiation duplex is never picked up and you end up with hundreds of "sfpxx excessive or late collision, link duplex match?" errors and most paths not even passing traffic. Downgrade to 7.12 and it auto negotiates correctly. My 10GB SFP+'s are auto negotiating, only 1GB SFP modules are failing to.
I have same kind of problems with CCR1009. I had a Mikrotik S+85DLC03D 10G SFP+ module (10G fiber link to Unifi SW) and it has worked up to 7.12.1 but now with 7.13 it says link is up but it's not working. If I unplug SFP+ module and plug it back then it works but not if I reboot CCR. I switched Mikrotik S+85DLC03D to Unifi UF-MM-10G module and now its working and also works after reboot.

So looks like that 7.13 has problems with SFP+ modules (only Mikkrotik labeled?)...

EDIT: I think this was my mistake. The 10G link in CCR was set to autonegoation but in Unifi switch it was set to 10G FDX. I changed Unifi switch also to autonegoation and 10G link came up. Need test after work day to swap Mikrotik SFP+ module to CCR and test if it again.
Last edited by timnis on Tue Dec 19, 2023 9:10 am, edited 1 time in total.
 
User avatar
mozerd
Forum Veteran
Forum Veteran
Posts: 898
Joined: Thu Oct 05, 2017 3:39 pm
Location: Canada
Contact:

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 12:00 am

If you do try to upgrade/downgrade RouterOS manually, then router do expect 1:1 packages match. If that is not possible (for example, wifi-qcominstalled on 7.13) then on packages menu schedule these packages for uninstall. Uploadpackages that you want to install and execute downgrade command.
My CCR1009 shows under /system/packages
routeros
wireless

I do not see a match under 7.12.1 in the archive

Plus why would CCR1009 load a wireless package ?
 
Evgeniy29
just joined
Posts: 1
Joined: Wed Aug 12, 2020 6:50 pm
Location: Ukraine

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 12:12 am

I have 20+ hAP ac2 and cAP ac. I upgrade it to 7.13 and use wifi-qcom-ac. I configured the CAPsMAN according to the instructions.
add name=ch-5ghz frequency=5180,5260,5500,5580,5745 width=20/40/80mhz
All APs automatically selected 5500. Now they interfere with each other. Where "Reselect Interval" and "Save Selected"? Maybe it’s possible to somehow use scripts to make the APs one by one do Reselect frequency?
 
User avatar
smyers119
Member Candidate
Member Candidate
Posts: 232
Joined: Sat Feb 27, 2021 8:16 pm
Location: USA

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 12:26 am

After upgrading to 7.12 and 7.13 there seems to be a bug preventing multicast packets coming in on zerotier. I use to have ospf running between hosts over zerotier link that no longer work. when doing a packet capture, the mikrotik does not receive ospf hellos but the other end does. Rulled out firewall issue as #1 this was working on existing config, and #2 i made a input rule accept all protocol ospf.

I rulled out ospf as a problem as I was able to establish a neighbor from another router local to TIK.
This was all working pre 7.12

EDIT:
Enabling Bridging on the Mikrotik seems to fix this issue.

@support please help debug.
 
User avatar
diamuxin
Member
Member
Posts: 320
Joined: Thu Sep 09, 2021 5:46 pm
Location: Alhambra's City

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 12:34 am

My CCR1009 shows under /system/packages
routeros
wireless

I do not see a match under 7.12.1 in the archive

Plus why would CCR1009 load a wireless package ?
I have explained it to you several times but you don't want to understand.
viewtopic.php?t=202423#p1042842

scheme code

v7.12.1
Packages:  
routeros (core + wifi)

v7.13
Packages:
routeros (core)
wireless (wifi)

To downgrade must be 1:1 means that:

v7.12.1                 v7.13                                      Downgrade now
routeros (1)     :      routeros (1)
                        wireless <- Uninstall and leave only "routeros"

If after this you do not understand it open a support ticket with Mikrotik.
 
User avatar
mozerd
Forum Veteran
Forum Veteran
Posts: 898
Joined: Thu Oct 05, 2017 3:39 pm
Location: Canada
Contact:

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 12:43 am

My CCR1009 shows under /system/packages
routeros
wireless
I do not see a match under 7.12.1 in the archive
Plus why would CCR1009 load a wireless package ?
OK so I finally succeeded downgrading to 7.12.1
I had to uninstall the wireless package then reboot THEN my downgrade worked to 7.12.1. It was as simple s that ...
 
User avatar
mozerd
Forum Veteran
Forum Veteran
Posts: 898
Joined: Thu Oct 05, 2017 3:39 pm
Location: Canada
Contact:

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 12:48 am

If after this you do not understand it open a support ticket with Mikrotik.
@diamuxin, you are correct ... I did not fully comprehend the meaning of your comment "You have to delete (uninstall) the existing packages except the "routeros" package, then do the downgrade."

Please accept my apology ... and Thank You ...
 
User avatar
diamuxin
Member
Member
Posts: 320
Joined: Thu Sep 09, 2021 5:46 pm
Location: Alhambra's City

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 12:55 am

If after this you do not understand it open a support ticket with Mikrotik.
@diamuxin, you are correct ... I did not fully comprehend the meaning of your comment "You have to delete (uninstall) the existing packages except the "routeros" package, then do the downgrade."

Please accept my apology ... and Thank You ...
You are welcome.
No problem.
 
NickOlsen
Member Candidate
Member Candidate
Posts: 131
Joined: Wed Feb 13, 2008 9:30 pm

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 3:33 am

I have an issue with 7.13 that 7.12.1 didn't have (nor before) - I have a bunch of 1gb SFP's in a CRS328-4C-20S-4S+ switch. None of them will link up auto negotiation at full duplex (they are all fiber). I can hard code both sides of a link and it works full duplex, but with auto negotiation duplex is never picked up and you end up with hundreds of "sfpxx excessive or late collision, link duplex match?" errors and most paths not even passing traffic. Downgrade to 7.12 and it auto negotiates correctly. My 10GB SFP+'s are auto negotiating, only 1GB SFP modules are failing to.
Exact same issue here on CRS328-4C-20S-4S+'s. Downgrading to 7.12.1 fixes it. Only an issue with 1G SFP's.
 
User avatar
dioeyandika
just joined
Posts: 20
Joined: Fri Feb 08, 2019 11:30 am

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 4:13 am

after few hours, with the help of chatgpt i modify the backup scripts to
# FTP settings
:local ftpAddress               "192.168.0.100"
:local ftpPort                  "990"
:local ftpUser                  "****"
:local ftpPassword              "***"
:local ftpDestination           "/NAS/Mikrotik"

# System backup settings
:local systemBackupDir "/sd1-part1/"

# Router identity
:local routerOSVersion ("RouterOS_v" . [/system package get number=0 value-name=version])
:local routerBoardModel [/system routerboard get model]

# Clean special characters in model name for filenames
:local cleanedRouterModel [:tostr $routerBoardModel]

# Create backup filenames with timestamp, model, and version
:local currentTime [/system clock get time]
:set currentTime ([:pick $currentTime 0 2] . [:pick $currentTime 3 5])

:local currentDate [/system clock get date]
:set currentDate ([:pick $currentDate 7 11] . [:pick $currentDate 4 6] . [:pick $currentDate 1 3])

:local backupFilenameBackup ($cleanedRouterModel . "_" . $routerOSVersion . "_" . $currentDate . "_" . $currentTime . ".backup")
:local backupFilenameConfig ($cleanedRouterModel . "_" . $routerOSVersion . "_" . $currentDate . "_" . $currentTime . ".rsc")

# Perform system backup for .backup file
/system backup save name=($systemBackupDir . $backupFilenameBackup)

# Export show-sensitive for .rsc file
/export show-sensitive file=($systemBackupDir . $backupFilenameConfig)

# Upload .backup file to FTP
/tool fetch mode=ftp address=$ftpAddress port=$ftpPort user=$ftpUser password=$ftpPassword \
    src-path=($systemBackupDir . $backupFilenameBackup) dst-path=($ftpDestination . "/" . $backupFilenameBackup) upload=yes

# Upload .rsc file to FTP
/tool fetch mode=ftp address=$ftpAddress port=$ftpPort user=$ftpUser password=$ftpPassword \
    src-path=($systemBackupDir . $backupFilenameConfig) dst-path=($ftpDestination . "/" . $backupFilenameConfig) upload=yes
now it works perfectly, i still doesnt now which part before doesnt work with v.7.13
 
User avatar
pekr
Member Candidate
Member Candidate
Posts: 169
Joined: Tue Feb 22, 2005 9:05 pm
Location: Czech Republic
Contact:

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 9:04 am

Upgraded two LHG XL52 ac (PtP setup), settings were intact, no issue with signal (-42), devices register themselves on one another (both 2GHz and 5GHz), but can't see other LHG via Winbox.
Any clues ?

EDIT: on 7.12.1 was working perfectly.
Are you using the new wifi package? If yes, it does not support station bridge mode yet with old devices/old driver! I use bridge and eoip over wifi link for extending the L2 segment
Is this limitation described anywhere? This is crucial information to me, as I have already upgraded hap ac2s to the 7.13, using wireless so far, and will travel soon there to switch to the wave2 package. Well, I could use vxlan tunel probably, or stay with the old wireless package, but was really looking into hassle free station bridge solution :-(
 
User avatar
frank333
Member
Member
Posts: 330
Joined: Mon Dec 18, 2017 12:17 pm
Location: S.Marino Router model: RB3011UiAS-RM+RBM11G

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 10:02 am

I tried 7.13 on RBM11g but the scripts don't work anymore!
I tried uninstalling the wireless package and downgrading to 7.12.1 but it doesn't work .
How did you guys do the downgrade?
Image
You do not have the required permissions to view the files attached to this post.
 
User avatar
Jotne
Forum Guru
Forum Guru
Posts: 3309
Joined: Sat Dec 24, 2016 11:17 am
Location: Magrathean

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 10:41 am

I tried 7.13 on RBM11g but the scripts don't work anymore!
What script?

PS Do add image to the post use Attachements when in full post mode. Link to other site may go away.
 
User avatar
mkx
Forum Guru
Forum Guru
Posts: 11791
Joined: Thu Mar 03, 2016 10:23 pm

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 11:01 am


Are you using the new wifi package? If yes, it does not support station bridge mode yet with old devices/old driver! I use bridge and eoip over wifi link for extending the L2 segment
Is this limitation described anywhere?

Yes, in wifi documentation, read through replacing 'wireless' package section. It's last item in "lost features".
 
peich1
just joined
Posts: 5
Joined: Mon Dec 11, 2017 9:43 am

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 11:26 am

I have a similar problem, on devices using MPLS/VPLS I see kernel panics every few hours and a lot of problems with packets not being forwarded or routed properly. I have seen it on an RB4011 (arm), RB5009 (arm64), and CCR1009 (tile). No supout generated, just a log message about the router being improperly rebooted and a suggestion that a kernel panic might be the reason.
I'm getting 1 or 2 reboots a day in my RB5009 since upgrading 7.13, no sup file creation. Though I don't use VPLS....
 
User avatar
frank333
Member
Member
Posts: 330
Joined: Mon Dec 18, 2017 12:17 pm
Location: S.Marino Router model: RB3011UiAS-RM+RBM11G

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 11:29 am

I have updated my RB5009 and my CRS326-24G and my scripts for Telegram are not working as expected. I am not getting any message more than the download message with the Chat ID.

I will be rolling back to version 7.12 if this not going to be fixed quickly by Mikrotik
It would be interesting to understand what needs to be changed in the scripts to make them work again.
 
User avatar
frank333
Member
Member
Posts: 330
Joined: Mon Dec 18, 2017 12:17 pm
Location: S.Marino Router model: RB3011UiAS-RM+RBM11G

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 11:32 am

I tried 7.13 on RBM11g but the scripts don't work anymore!
What script?

PS Do add image to the post use Attachements when in full post mode. Link to other site may go away.
scripts that include the fetch command for telegram
Last edited by frank333 on Tue Dec 19, 2023 11:41 am, edited 1 time in total.
 
holvoetn
Forum Guru
Forum Guru
Posts: 5612
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 11:35 am

I'm getting 1 or 2 reboots a day in my RB5009 since upgrading 7.13, no sup file creation. Though I don't use VPLS....
No such thing here.
Stable since update last Friday.
 
rb9999
newbie
Posts: 26
Joined: Thu Dec 06, 2018 3:09 pm

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 11:42 am

bonding issue on two CCR2004-16G-2S+... downgrade to 7.12.1 seems to help
 
pe1chl
Forum Guru
Forum Guru
Posts: 10307
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 12:11 pm

Is this limitation described anywhere?
Yes, in wifi documentation, read through replacing 'wireless' package section. It's last item in "lost features".
Also, it is always good to realize that any conversion from "7.13 with routeros+wireless package" to "routeros+wifi_qcom_ac" will always make you lose all configuration of the wifi. There is no attempt to convert even simple configurations like "station connecting to an SSID with a WPA2-PSK password" or "AP with SSID and WPA2-PSK password" into a new configuration after this change.
Of course it would be possible to make a script for that, but it isn't there. So be careful with remote systems or with routers that you manage via WiFi!
 
Simonej
Frequent Visitor
Frequent Visitor
Posts: 59
Joined: Sun Aug 22, 2021 3:34 am

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 12:39 pm

scripts that include the fetch command for telegram
user policy "ftp" is enabled?
 
User avatar
frank333
Member
Member
Posts: 330
Joined: Mon Dec 18, 2017 12:17 pm
Location: S.Marino Router model: RB3011UiAS-RM+RBM11G

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 12:45 pm

scripts that include the fetch command for telegram
user policy "ftp" is enabled?
is enabled.
I get this from the logs:
fetch,info,debug Download from https://api.telegram.org/bot42558852236 ... endMessage to RAM FAILED: Fetch failed with status 400
 
sinisa
just joined
Posts: 24
Joined: Sun Apr 17, 2011 12:46 am

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 1:10 pm

In the "old" wireless, and even in "wifiwave2" there used to be "country info", but I am unable to find it in 7.13 with "qcom-ac" drivers.

Am I missing something?
 
holvoetn
Forum Guru
Forum Guru
Posts: 5612
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 1:18 pm

This ?
[a<some_user>@<some_router>] > interface/wifi/radio reg-info country=Belgium
number: 0
ranges: 2402-2482/20
5170-5250/23/indoor
5250-5330/23/indoor/dfs
5490-5710/30/dfs
 
sinisa
just joined
Posts: 24
Joined: Sun Apr 17, 2011 12:46 am

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 1:39 pm

This ?
[a<some_user>@<some_router>] > interface/wifi/radio reg-info country=Belgium
number: 0
ranges: 2402-2482/20
5170-5250/23/indoor
5250-5330/23/indoor/dfs
5490-5710/30/dfs
Yes, just found it :)
Reading/searching the doc's makes miracles

Thanks!
 
mazay
just joined
Posts: 15
Joined: Thu Aug 08, 2013 9:39 am
Location: Earth
Contact:

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 2:13 pm

Exciting news! :trollface:
The documentation says my Audience is compatible as well as some other my devices. Starting with audience, removing the `wireless` package, rebooting, uploading `wifi-qcom` packages, rebooting and I'm in a boot loop. :)

Netinstall with 7.13 and install of `wifi-qcom` packages on a virgin clean device result in another boot loop, the only way out is another netinstall.

Stick to the old `wireless` package for now...
 
alibloke
Frequent Visitor
Frequent Visitor
Posts: 56
Joined: Fri Jun 03, 2016 12:13 am

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 2:21 pm

Did you install the wifi-qcom or wifi-qcom-ac package?
 
User avatar
rextended
Forum Guru
Forum Guru
Posts: 12047
Joined: Tue Feb 25, 2014 12:49 pm
Location: Italy
Contact:

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 2:27 pm

Did you install the wifi-qcom or wifi-qcom-ac package?
It's already written, just read.

It is obvious that the user wanted to read what he wanted, and installed the packages at random, without logic.
He didn't even read/understand the documentation he linked...
 
mazay
just joined
Posts: 15
Joined: Thu Aug 08, 2013 9:39 am
Location: Earth
Contact:

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 2:42 pm

Did you install the wifi-qcom or wifi-qcom-ac package?
It's already written, just read.

It is obvious that the user wanted to read what he wanted, and installed the packages at random, without logic.
He didn't even read/understand the documentation he linked...
Could you elaborate? I read the doc but I may have missed something. If you know what wouldn't it be more helpful (not only for me but for others coming) to point to the mistakes instead of being... that?
 
mazay
just joined
Posts: 15
Joined: Thu Aug 08, 2013 9:39 am
Location: Earth
Contact:

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 2:45 pm

Did you install the wifi-qcom or wifi-qcom-ac package?
I've installed both, I guess that was my mistake? What's the difference between those?

To my understanding `wifi-qcom` was for 2.4 interfaces while `wifi-qcom-ac` for 5
Last edited by mazay on Tue Dec 19, 2023 2:47 pm, edited 1 time in total.
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 26440
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 2:45 pm

Did you install the wifi-qcom or wifi-qcom-ac package?
wifi-qcom is only for 802.11AX WiFi6 devices. Audience does not support that package.
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 26440
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 2:48 pm

mazay, the documentation clearly says "wifi-qcom-ac package" not wifi-qcom

here is a video too: https://www.youtube.com/watch?v=AkBIQxi-VKs
 
ArtisM
MikroTik Support
MikroTik Support
Posts: 10
Joined: Thu Jun 25, 2020 12:29 pm

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 2:48 pm

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

At 7.12 all ok.
Please report the issue to MikroTik support with Supout.rif files created on v7.13 and v7.12.
https://help.mikrotik.com/servicedesk/servicedesk

And for fellow forum users please post with which version the issue is observed, e3372h's have multiple hardawre nad firmware variants with sufixes -153; -320; -325, so users are aware of which version is affected.
 
mazay
just joined
Posts: 15
Joined: Thu Aug 08, 2013 9:39 am
Location: Earth
Contact:

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 2:48 pm

Did you install the wifi-qcom or wifi-qcom-ac package?
wifi-qcom is only for 802.11AX WiFi6 devices. Audience does not support that package.
Thank you for the clarification. I must say the naming is rather confusing.

The package name should have been `wifi-qcom-ax` to be self-explanatory. At the same time `wifi-qcom-ac` suggests that this is for 5G devices making me think that 2.4 gets lost.
Last edited by mazay on Tue Dec 19, 2023 2:57 pm, edited 1 time in total.
 
mazay
just joined
Posts: 15
Joined: Thu Aug 08, 2013 9:39 am
Location: Earth
Contact:

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 2:50 pm

mazay, the documentation clearly says "wifi-qcom-ac package" not wifi-qcom

here is a video too: https://www.youtube.com/watch?v=AkBIQxi-VKs
You are correct, at the same time the package names are confusing. I'd suggest renaming it or making it bold in the docs.
 
ArtisM
MikroTik Support
MikroTik Support
Posts: 10
Joined: Thu Jun 25, 2020 12:29 pm

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 2:56 pm

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

At 7.12 all ok.
I've got the same problem with a Huawei E3372h-153. I've also got a E3372h-320 that seems to work fine.

But the E3372h-153 just disappears. It goes up for a split second and then goes down. Tried in a RB5009 and a AX3. I've also tried with a RB2011 and it works for a few seconds after restart, but then RX/TX stays at 0 mbps. I ended up downgrading to 7.12 and works fine again. There's definitely something broken in 7.13.

Also, after upgrading +30 devices, I've got a problem with a CRS328: interfaces didn't go up after upgrade. I had to connect using the console cable and observed there were 0 bytes left. After deleting some files and the wireless package, it booted correctly.
Please create and send to support Supout.rif file created after a traffic flow outage has occurred.
https://help.mikrotik.com/servicedesk/servicedesk
 
rb9999
newbie
Posts: 26
Joined: Thu Dec 06, 2018 3:09 pm

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 3:09 pm

Opened a ticket regarding bonding on CCR2004 - SUP-138086. Attached supout.rif
 
peich1
just joined
Posts: 5
Joined: Mon Dec 11, 2017 9:43 am

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 3:32 pm

I'm getting 1 or 2 reboots a day in my RB5009 since upgrading 7.13, no sup file creation. Though I don't use VPLS....
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
You do not have the required permissions to view the files attached to this post.
 
ksteink
Frequent Visitor
Frequent Visitor
Posts: 82
Joined: Thu Mar 31, 2016 6:54 pm

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 4:20 pm


user policy "ftp" is enabled?
is enabled.
I get this from the logs:
fetch,info,debug Download from https://api.telegram.org/bot42558852236 ... endMessage to RAM FAILED: Fetch failed with status 400
I have not changed anything and I use Telegram in NetWatch and also on home based built scripts. After the upgrade I start getting this message:

RouterOS

12-15 22:39:30 Download from https://api.telegram.org/botxxxxxxxxxxx ... d=-yyyyyyy

instead of the text that I have pre-configured for the alert to send. I use the following command with variables to send alerts:

/tool fetch url="https://api.telegram.org/bot$token/send ... t=$Message"

As soon as I roll back everything starts working as expected.
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 26440
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 4:36 pm

mazay, the documentation clearly says "wifi-qcom-ac package" not wifi-qcom

here is a video too: https://www.youtube.com/watch?v=AkBIQxi-VKs
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
 
User avatar
eworm
Forum Guru
Forum Guru
Posts: 1073
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 4:49 pm

No problem here with sending to Telegram... And also every other use of fetch is fine.
 
User avatar
diamuxin
Member
Member
Posts: 320
Joined: Thu Sep 09, 2021 5:46 pm
Location: Alhambra's City

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 4:56 pm

Very interesting...


Image
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 26440
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 4:56 pm

More detailed table viewtopic.php?t=202578
 
User avatar
diamuxin
Member
Member
Posts: 320
Joined: Thu Sep 09, 2021 5:46 pm
Location: Alhambra's City

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 4:59 pm

is enabled.
I get this from the logs:
fetch,info,debug Download from https://api.telegram.org/bot42558852236 ... endMessage to RAM FAILED: Fetch failed with status 400
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.
 
User avatar
pekr
Member Candidate
Member Candidate
Posts: 169
Joined: Tue Feb 22, 2005 9:05 pm
Location: Czech Republic
Contact:

Re: v7.13 [stable] is released!

Tue Dec 19, 2023 5:08 pm


Yes, in wifi documentation, read through replacing 'wireless' package section. It's last item in "lost features".
Also, it is always good to realize that any conversion from "7.13 with routeros+wireless package" to "routeros+wifi_qcom_ac" will always make you lose all configuration of the wifi. There is no attempt to convert even simple configurations like "station connecting to an SSID with a WPA2-PSK password" or "AP with SSID and WPA2-PSK password" into a new configuration after this change.
Of course it would be possible to make a script for that, but it isn't there. So be careful with remote systems or with routers that you manage via WiFi!
Thanks for an advice. I am aware of that, mostly thinking about new wi-fi r/k/v roaming capabilities / a bit more throughput, being worth a slight hassle setting up vxlan tunnel, splitting radios with hidden SSID for the tunnel transport, etc. I still have it with my hap-ax2s, as initially ROS7 did not support station bridge. Hopefully vxlan solution would work with ac driver too.

Who is online

Users browsing this forum: AntennaGain and 12 guests