v7.14.3 [stable] is released!

Thu Feb 29, 2024 4:57 pm

RouterOS version 7.14 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.

What's new in 7.14.3 (2024-Apr-17 15:47):

*) bgp - correctly synchronize input.accept-nlri address list;
*) bridge - use default "edge=auto" for dynamically bridged interfaces (PPP, VPLS, WDS);
*) disk - improved system stability;
*) fetch - fixed slow throughput due to "raw" logging which occurred even when not listening to the topic (introduced in v7.13);
*) queue - improved system stability (introduced in v7.6);
*) wifi-qcom - added configuration.distance setting to enable operation over multi-kilometer distances (CLI only);

What's new in 7.14.2 (2024-Mar-27 09:48):

*) defconf - do not override default DHCP server lease time;
*) defconf - fixed 5ghz-ax channel width for L11, L22 devices;
*) ethernet - fixed interface disable for CRS326-4C+20G+2Q;
*) ethernet - improved port speed downshift functionality for CRS326-4C+20G+2Q;
*) leds - fixed LEDs for L22 device;
*) lte - fixed firmware upgrade not found issue for Chateau LTE12 (introduced in v7.14.1);
*) ssh - require "policy" user policy when adding public key;
*) timezone - updated timezone information from "tzdata2024a" release;
*) traffic-flow - improved system stability;
*) vrf - fixed VRF interfaces being moved to main table after reboot (introduced in v7.14);
*) wifi-qcom - added configuration.distance setting to enable operation over multi-kilometer distances (CLI only);

What's new in 7.14.1 (2024-Mar-08 14:50):

*) bgp-vpn - use VRF interface as gateway for leaked connected routes;
*) chr - fixed Xen and Vultr missing ethernet (introduced in v7.14);
*) chr - fixed bogus messages printed out while booting up the system (introduced in v7.14);
*) console - fixed do/while implementation not working with variables (introduced in v7.14);
*) ethernet - fixed default names for CRS310-8G+2S+ device (introduced in v7.14);
*) lte - fixed R11e-LTE-US modem dial-up;
*) sfp - improved system stability for CR2004-1G-2XS-PCIe (introduced in v7.14);
*) vrf - fixed VRF interfaces being moved to main table after reboot (introduced in v7.14);
*) wireguard - do not attempt to connect to peer without specified endpoint-address;

What's new in 7.14 (2024-Feb-29 09:10):

!) rose-storage - moved SMB service to the RouterOS bundle;
!) smb - removed legacy SMB service (replaced with newer and faster ROSE SMB service, compatible with SMB 2.1, SMB 3.0 and SMB 3.1.1);
*) 6to4 - make "ipsec-secret" sensitive parameter;
*) api - improved REST API stability when processing invalid requests;
*) api - properly return SNMP OIDs when requested;
*) arm - improved system stability when using microSD on RB1100Dx4;
*) arp - added ARP status;
*) bgp - allow to leak routes between local VRFs;
*) bridge - added MLAG support for MSTP bridges;
*) bridge - avoid per-VLAN host flushing on HW offloaded bridge;
*) bridge - fixed auto "path-cost" for bonding interfaces (introduced in v7.13);
*) 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);
*) bridge - improved bridge VLAN configuration validation;
*) bridge - improved configuration speed on large VLAN setups;
*) bridge - improved protocol-mode MSTP functionality;
*) bridge - improved protocol-mode STP and RSTP functionality;
*) bridge - make "point-to-point=yes" default value for non-wireless bridge ports;
*) bridge - removed "mst-config-digest" from MSTI menu;
*) bridge - try to set wireless bridge ports as edge ports automatically;
*) bth - added simple "Back To Home Users" manager under IP/Cloud menu;
*) calea - improved system stability when adding bridge rule without "calea" package installed;
*) certificate - improved certificate validation performance;
*) console - added ":tolf" and ":tocrlf" commands for converting line break to/from LF or CRLF;
*) console - added "show-at-cli-login" option to display a note before telnet login;
*) console - added missing "where" clause for "/ipv6/firewall/filter" table print command;
*) console - do not accept negative or too large values for ":delay" command;
*) console - do not allow to use out-of-range values for time type fields;
*) console - fix configuration export when user does not have a "sniff" policy;
*) console - fixed delayed output from ":grep" command in certain cases;
*) console - fixed incorrect behavior of ":onerror" command in certain cases;
*) console - hint on reset command help that ".rsc file" is required for "run-after-reset" parameter;
*) console - improved editor functionality in full screen mode;
*) console - improved stability when using autocomplete with "export";
*) console - increased maximum file content length that can be managed through command line to 60 KB;
*) console - updated copyright notice;
*) container - improved VETH interface management responsiveness and reliability;
*) container - restrict "/container/shell" menu for users without "write" permissions;
*) defconf - added log about configuration reset due to pressed reset button;
*) defconf - fixed Audience scanning-for-wps-ap timeout;
*) defconf - fixed configuration script on KNOT devices if "ppp-out" interface is removed;
*) defconf - fixed firewall rule for IPv6 UDP traceroute;
*) defconf - fixed wifi configuration if interface MAC address is changed;
*) defconf - improved wifi interface detection after upgrade;
*) defconf - increased LTE interface wait time;
*) defconf - updated health settings on configuration revert;
*) defconf - use "fq_codel" queue as default interface queue for wired ports on LTE devices;
*) dhcpv6-client - install dynamic IPv6 blackhole routes in corresponding routing-table;
*) dhcpv6-client - updated error logging when multiple prefixes received on renew;
*) disk - added exFAT and NTFS mount/read/write support;
*) disk - added global disk "settings" menu;
*) disk - fixed changing settings on some GPT formatted disks;
*) disk - properly unmount disk when it is disconnected;
*) dns - do not add new entries to cache if "cache-size" is reached;
*) dns - fixed domain name lookup resolving for internal services;
*) ethernet - fixed issue with default interface names for CRS310-8G+2S+ in rare cases;
*) ethernet - improved cable-test reliability for hAP ax3 PoE out port;
*) ethernet - resolved minor memory leak while processing packets;
*) fetch - added "head" option for "http-method";
*) fetch - added "patch" option for "http-method";
*) fetch - allow specifying link-local address in FTP mode;
*) fetch - allow to use certificate and check-certificate parameters only in HTTPS mode;
*) 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 execution when unexpected data is received in HTTP payload;
*) fetch - fixed fetch when using "src-path" with HTTP/HTTPS modes (introduced in v7.13);
*) fetch - fixed fetch when using "src-path" with SFTP mode (introduced in v7.13);
*) fetch - fixed incorrect "src-path" error message when "upload=yes";
*) fetch - fixed IPv4 address logging (introduced in v7.13);
*) fetch - improved fetch stability in SFTP mode;
*) fetch - improved file download stability with HTTP/HTTPS modes;
*) fetch - less verbose logging;
*) fetch - print all "Set-Cookies" headers in response;
*) fetch - treat any 2xx HTTP return code as success (introduced in v7.13);
*) filesystem - improved filesystem integrity for several RB3011 units with automatic firmware upgrade;
*) firewall - added "creation-time" parameter for IPv6 address list entries;
*) firewall - fixed underlying CAPsMAN tunnel reusing packet marks of encapsulated packets;
*) firewall - fixed underlying VXLAN/EoIP tunnel reusing packet marks of encapsulated packets;
*) firewall - increased default "udp-timeout" value from 10s to 30s;
*) health - added limited manual control over fans for CCR1016r2, CCR1036r2 devices;
*) health - changed default "fan-min-speed-percent" from 0% to 12%;
*) health - improved fan control on CRS3xx and CCR1016-12S-1S+r2;
*) health - show voltage when powering KNOT R through Micro-USB;
*) health - updated health properties for CCR1016r2, CCR1036r2 devices;
*) iot - added bluetooth whitelist wildcard asterisk support;
*) iot - added LoRa CUPs protocol support;
*) iot - fixed modbus partial frame reception issue;
*) iot - improved LoRa LNS;
*) iot - improved modbus Tx/Rx switching behaviour;
*) iot - improvements to GPIO behavior on boot;
*) iot - improvements to LoRa CUPS;
*) iot - removed bluetooth whitelist maximum entry limit of 8;
*) ipv6 - made "valid" and "lifetime" parameters dynamic for SLAAC IPv6 addresses;
*) isis - show passive interface active levels;
*) l3hw - fixed IPv6 host offloading in certain cases;
*) l3hw - fixed neighbor offloading after link flap;
*) l3hw - preserve offloading for VLANs when bridge ports are down;
*) leds - added "dark-mode" functionality for hAP ax3 and Chateau ax series devices;
*) leds - do not show LTE connection state/mode using RGB power LED from configless LTE modems;
*) leds - fixed "type=on" LED behaviour after reboot;
*) leds - fixed default LTE LED configuration for wAPR-2nD;
*) leds - fixed modem LED indication for SXT LTE 3-7;
*) leds - fixed wireless type of LED triggers for routers using WiFi package;
*) lte - added "at-chat" support for Sierra Wireless EM9293 5G modem;
*) lte - added AT channel support for Quectel EM120K-GL modem;
*) lte - added redial timer when the MBIM modem fails to register or does not receive APN activation notification;
*) lte - don't duplicate primary band in 5G SA mode for chateau 5G;
*) lte - fixed "use-peer-dns" setting for EC200A modem;
*) lte - fixed an issue for EC200A modem that IPv6 address could be added as IPv4 address;
*) lte - fixed APN authentication for FG621-EA modem;
*) lte - fixed MBIM interface enabling for Quectel EC25 modem (introduced in v7.13);
*) lte - fixed Simcom modem support in 0x9000; 0x9002, 0x9002; 0x901a and 0x901b USB compositions;
*) lte - fixed Simcom modem support in 0x9001 USB composition;
*) 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;
*) lte - improved FG621-EA modem firmware upgrade;
*) lte - improved modem recovery after failed IPv4 configuration;
*) lte - improved support for "ACER" and "MSFT" branded EM12-G modems;
*) lte - optimized "at-chat" response reading;
*) lte - refactored AT command control for AT modems;
*) modem - fixed SMS removal (introduced in v7.13);
*) modem - improved stability when performing modem FOTA upgrade;
*) mpls - fixed VPN fragmentation when forwarding IP traffic;
*) netinstall-cli - check package and device architecture before formatting;
*) ovpn - added support for pushing routes;
*) ovpn - improved "push-routes" option handling when large amount of routes is specified;
*) ovpn - improved key-renegotiation process;
*) ovpn - improved OVPN configuration file import process;
*) ovpn - improved system stability when using HW encryption on ARM64 devices (introduced in v7.13);
*) ovpn - limit the maximum length for "push-routes" up to 1400 characters;
*) package - added "size" property;
*) package - reduced "wireless" package size for ARM, ARM64, MIPSBE, MMIPS devices;
*) package - reduced package size for SMIPS;
*) poe-out - driver optimization for AF/AT controlled boards;
*) poe-out - fixed "power-cycle" for CRS354-48P-4S+2Q+ device (introduced in v7.13);
*) poe-out - improved 802.3at classification and measurement accuracy;
*) poe-out - improved cable test for hAP ac3 and hAP ax3 devices;
*) poe-out - improved PoE out reliability on routers with a single PoE out interface;
*) port - fixed support for USB/serial adapters (introduced in v7.13);
*) port - removed bogus serial port on RB750Gr3, RB760iGS and RBM11G devices;
*) ppp - added support for "WISPr-Session-Terminate-Time" RADIUS attribute;
*) ppp - log an error when IPv6 DHCP pool is exhausted;
*) ptp - added "aes67" and "smpte" profiles;
*) ptp - added configurable "domain" and "priority2" parameters;
*) ptp - added support for Management message forwarding in BC;
*) ptp - fixed "default" and "g8275.1" profiles go into "slave" instead of "uncalibrated" state;
*) ptp - fixed default values for "802.1as" profile;
*) ptp - fixed flags in Announce message;
*) ptp - fixed potential error in packet exchange;
*) ptp - make clock go into grandmaster state if slave port goes down;
*) qos-hw - fixed "tx-queue7-packet" counter;
*) route - fixed gateways of locally imported vpnv4 routes;
*) route - improved route print "count-only" process speed;
*) route - improved stability on route table lookup;
*) route-filter - added option to set "isis-ext-metric";
*) route-filter - fixed AS path matchers when input and output chains are used;
*) routerboard - added "reset-button" support for RBwAPR-2nD device;
*) sfp - added support for modules requiring single byte I2C read transactions;
*) sfp - fixed corrupted Tx traffic at 10Gbps rate on CCR2004-16G-2S+ in rare cases;
*) sfp - fixed corrupted Tx traffic at 10Gbps rate on RB4011 in rare cases;
*) sfp - improve high-power SFP module initialization;
*) sfp - improved combo-sfp handling for CRS328-4C-20S-4S+;
*) sfp - improved link establishment for RB4011 devices;
*) smb - added option to specify SMB service mode as "auto";
*) 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;
*) sms - increased SMS read timeout;
*) snmp - added "bgpLocalAs" and "bgpIdentifier" OID reporting;
*) snmp - fixed "bgpPeerFsmEstablishedTime" OID reporting;
*) snmp - hide "MikroTik" in LLDP MIB when branding with hide SNMP option is used;
*) snmp - updated timeout log;
*) ssh - improved SSH performance on ARM, MIPS, MMIPS, SMIPS and TILE devices;
*) ssh - refactored SSH service internal processes;
*) sstp - added support for "aes256-gcm-sha384" encryption;
*) sstp - improved system stability for PPC devices;
*) supout - added PTP section;
*) switch - fixed Ethernet disable/enable for CRS310-8G+2S+ devices;
*) switch - fixed reserved multicast receive on Atheros-8327, QCA8337 switches for R/STP bridge;
*) switch - improved 100G interface stability for 98DX4310 and 98DX8525 switches;
*) switch - minimise potential packet overflows on CRS354;
*) system - changed build time format according to ISO standard;
*) system - expose "lo" and "vrf" interfaces;
*) system - fixed "cpu-frequency" for CRS3xx ARM devices;
*) system - improved memory allocation for ARM64 devices;
*) system - improved RAM allocation for L009UiGS-RM;
*) system - improved system stability when processing packets in FastPath (introduced in v7.13);
*) system - properly assign destination port for HTTP/S connections initiated by the router (introduced in v7.13);
*) system - properly close HTTP/S connections initiated by the router;
*) system - provide more precise "total-memory" value for ARM devices;
*) system - provide more precise "total-memory" value under "System/Resources" menu for L009 and hAP ax lite routers;
*) tftp - improved invalid request processing;
*) timezone - updated timezone information from "tzdata2023d" release;
*) tr069 - don't duplicate cellular info in "X_MIKROTIK_5G" nodes when connected in NR SA mode;
*) tr069 - fixed bandwidth test;
*) tr069-client - show 5G signal info in X_MIKROTIK_5G nodes only for 5G NSA bands;
*) traffic-flow - use 64bit counters for v9 and IPFIX flows;
*) traffic-generator - improved system stability when receiving bogus traffic;
*) usb - show "Supermicro CDC" adapter as Ethernet interface;
*) vlan - fixed non-running VLAN interface after failed MTU change;
*) vrf - prevent VRF interface name collision with interface lists;
*) vxlan - fixed underlying tunnel reusing routing marks of encapsulated packets;
*) webfig - fixed routing table filter under "IP/Routes" menu;
*) webfig - fixed setting the user's password;
*) webfig - fixed showing WireGuard peers;
*) webfig - improved stability when adding new entries under "IP/Routes" menu;
*) wifi - added "station-pseudobridge" interface mode;
*) wifi - fixed issue with setting country profile (introduced in v7.13.1);
*) wifi - improved handling of CAP connections in dual CAPsMAN scenario;
*) wifi - increased value for SAE retransmit period to 3s to improve WPA3 compatibility with IoT client devices;
*) wifi - use "Latvia" as the default value for "country" property;
*) wifi - use correct CAP identity for interface name provisioning after it has been changed by remote-cap/set-identity;
*) wifi-qcom - enable display of regulatory information on L11,L22 devices;
*) wifi-qcom - fixed new connections, when maximum supported number of MAC addresses behind connected station-bridges is reached;
*) wifi-qcom - improve system stability for L11, L22 devices;
*) wifi-qcom - improved memory allocating process;
*) wifi-qcom - improved regulatory compliance for L11, L22 devices;
*) wifi-qcom - improved system stability when using FastPath (introduced in v7.13);
*) winbox - added "accept-protocol-version" parameter to the L2TP server settings;
*) winbox - added "mode-button" and "switch" menus for L41G-2axD&FG621-EA;
*) winbox - added "Name" parameter under "Tools/Netwatch" menu;
*) winbox - added "page-refresh" setting to the Graphing settings;
*) winbox - added "Port Cost Mode" setting under "Bridge" menu;
*) winbox - added "VRF" parameter under "Tools/Ping" menu;
*) winbox - added "x25519" argument for "DH Group" parameter under "IP/IPsec/Profiles" menu;
*) winbox - added missing "Protocol" arguments under "IPv6/Firewall" menu;
*) winbox - added missing monitoring properties under "WireGuard/Peers" menu;
*) winbox - added Preboot Etherboot settings to the System/RouterBOARD/Settings menu;
*) winbox - do not show USB settings for CRS devices that does not need it;
*) winbox - fixed "Bridge Cost" range under "Interfaces/VPLS" menu;
*) winbox - fixed "Password" button under "Quick Set" menu;
*) winbox - improved connection speed and reliability;
*) winbox - improved route table automatic refresh process for static routes;
*) winbox - improved status values under "System/PTP" menu;
*) winbox - improved system stability with large packets;
*) winbox - include "te-tunnel" parameter in VPLS interface monitor;
*) winbox - properly validate "passthrough-subnet-size" in the LTE APN settings;
*) winbox - remove "Root Bridge ID" property under "Bridge/MSTIs" menu;
*) winbox - removed "sfp all" option from combo port settings;
*) winbox - renamed "Wireless Table" menu to "Wifi";
*) winbox - show "routing-table" column under IP/Route menu by default;
*) winbox - show all columns under "Routing/PIM SM/Static RP" menu by default;
*) wireguard - do not allow to use multiple WireGuard interfaces on the same "listen-port";
*) wireguard - optimised and improved WireGuard service logging;
*) x86 - fixed VLAN tagged packet transmit for igb (introduced in v7.12);

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.

massinia · Thu Feb 29, 2024 5:19 pm

Huge changelog, congratulations for the excellent work 👏

rushlife · Thu Feb 29, 2024 5:35 pm

awesome, thx for your hard work

baragoon · Thu Feb 29, 2024 5:37 pm

Yahoooo, thank you

pe1chl · Thu Feb 29, 2024 5:40 pm

Remember this:

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.

Also note that upgrading beyond 7.12.1 can cause issues on ARM devices with "16MB flash", especially for devices that actually have only 15.3MB flash.
So be extra careful when upgrading such a device (e.g. hAP ac2), especially when you cannot easily netinstall it (remote location).

Dish · Thu Feb 29, 2024 5:45 pm

Hi,

I have the following wireguard bth info in the log on a hap ax lite LTE 6 and an RB 5009. With version 7.13
was everything OK. A new configuration of Wiregurad BTH does not bring any changes.

bp0 · Thu Feb 29, 2024 5:55 pm

What causes this message regarding a backup-routerboot upgrade?

Screenshot from 2024-02-29 09-48-58.png

edit: Device is RB960PGS (hEX PoE) r2.

morphema · Thu Feb 29, 2024 5:57 pm

I'm getting endless messages 'Handshake for peer did not complete after 5 seconds, retrying (try 2)' in log.

infabo · Thu Feb 29, 2024 6:22 pm

Note: I spotted several lines in the changelog that where already in 7.13.x releases. So changelog looks longer than it actually is.

Matta · Thu Feb 29, 2024 6:37 pm

*) package - reduced package size for SMIPS

I still cannot ugrade hAP Lite from 7.13 to 7.14 (7.6MiB required, 7.5MiB free, although it's only few kilobytes that are actually missing).
Manual upgrade also won't pass, missing those few kb to upload wireless package.

sszbv · Thu Feb 29, 2024 6:45 pm

Look out when upgrading a CCR2004-1G-2XS-PCIe.
I've got one here that is gone into a reboot loop, even after powering down and up again.
It can be bad luck, but I'm not going to upgrade the rest of them until I know how to get it running again.

Update:

I got the board working again after resetting it to defaults with the reset solder pads.

nmt1900 · Thu Feb 29, 2024 6:55 pm

Also note that upgrading beyond 7.12.1 can cause issues on ARM devices with "16MB flash", especially for devices that actually have only 15.3MB flash.
So be extra careful when upgrading such a device (e.g. hAP ac2), especially when you cannot easily netinstall it (remote location).

Somewhat unbelievably... while 7.13.5 took 14,4 MB of space in hap ac2 - 7.14 has seem to got smaller as used space indicates now 14,3 MB (that with legacy wireless package).
Upgrade took almost 3 minutes which is longest for that device so far...

mirolm · Thu Feb 29, 2024 7:14 pm

Old wireless package got smaller but how it is with wifi-qcom-ac? Anyone knows if it is possible to upgrade to 7.14 and how much flash space will be left free afterwards?

GreySer · Thu Feb 29, 2024 7:16 pm

All ethernet interfaces on the CHR machine on the VDSINA hosting are missing. I checked the installation process twice, the ethernet is always lost. I installed 7.13.5, the ethernet is back.

nmt1900 · Thu Feb 29, 2024 7:17 pm

What causes this message regarding a backup-routerboot upgrade? Screenshot from 2024-02-29 09-48-58.png

What device this is?

Thu Feb 29, 2024 8:26 pm

Hi,

I have the following wireguard bth info in the log on a hap ax lite LTE 6 and an RB 5009. With version 7.13
was everything OK. A new configuration of Wiregurad BTH does not bring any changes.

Since 7.14 there is a lot more verbose logging w.r.t. Wireguard in general, not only BTH.
It's in the change log.

*) wireguard - optimised and improved WireGuard service logging;

But if you ask me, there should also be an 'off' switch for this logging ... haven't found it yet.

Joseph · Thu Feb 29, 2024 8:28 pm

Upgrade done!

I hope it will be better than 7.13... it was a nightmare...
7.13.2 and 7.13.4 has broken file save on NAS. I don't know how and why but I observed that in two different locations.

Thu Feb 29, 2024 8:48 pm

So far upgraded successfully (home and lab gear):
RB5009
AX2
AX3
AX Lite LTE
Map

Minor comment:
log file on AX Lite LTE shows something weird:

19:36:54 script,warning USB device count: 2 >> 3 .id=*1;device=1-0;name=xHCI Host Controller;speed=480;vendor=Linux 5.6.3 xhci-hcd;.id=*2;device=2-0;name=xHCI Host Controller;speed=5000;vendor=
Linux 5.6.3 xhci-hcd;.id=*3;device=1-1;name=FG621 Module;speed=480;vendor=Fibocom
19:37:16 script,warning LTE inteface count: 0 >> 1

But everything works.

w0lt · Thu Feb 29, 2024 8:55 pm

I'm getting endless messages 'Handshake for peer did not complete after 5 seconds, retrying (try 2)' in log.

In Logging, select info, then add wireguard to it, then add the negative sign to wireguard.

Thu Feb 29, 2024 9:08 pm

In Logging, select info, then add wireguard to it, then add the negative sign to wireguard.

Can you elaborate please ? I don't seem to get it right.

BTW same with DNS and NTP logging. It's being SWAMPED now with messages.

Thu Feb 29, 2024 9:13 pm

Hmmm ... there HAS to be a way to SHUT DOWN the verbosity of those logs.
This is NOT practical like it is now.

tom3f · Thu Feb 29, 2024 9:13 pm

Old wireless package got smaller but how it is with wifi-qcom-ac? Anyone knows if it is possible to upgrade to 7.14 and how much flash space will be left free afterwards?

On hapAC2 with wifi-qcom-ac i have 164KiB left. That is very bad :( but it works for now.

Larsa · Thu Feb 29, 2024 9:23 pm

I'm getting endless messages 'Handshake for peer did not complete after 5 seconds, retrying (try 2)' in log.

I've upgraded a couple of lab routers and I'm getting the exact same status flooding from all passive WireGuard peers, ie those defined without endpoint addresses. This applies to both IPv6 and IPv4 peers. And yeah, I know how to mute it but that is beside the point.

rushlife · Thu Feb 29, 2024 9:28 pm

Handshake for peer did not complete after 5 seconds, retrying (try 2)
Handshake for peer did not complete after 5 seconds, retrying (try 2)
Handshake for peer did not complete after 5 seconds, retrying (try 2)

+1, the same by me

Larsa · Thu Feb 29, 2024 9:42 pm

Something fishy is going on with passive WireGuard peers since it seems they are all trying to establish an active connection to the destination address 0.0.0.0, port 0. The WireGuard debug log is flooded with entries like: "wireguard, debug: WG-xxxx: ... Sending handshake initiation to peer (0.0.0.0:0)"

Znevna · Thu Feb 29, 2024 10:04 pm

You have packets flying towards those peers.
Stop the packets, the flooding will stop. Or hide the messages.

Thu Feb 29, 2024 10:21 pm

The comment from w0lt was correct. In order to disable specific topic logs, go to System/Logging and open, for example, "info" topic. Add "!wireguard" to it. All info logs, except WireGuard, will be logged now.

Yes, these are new logs, nothing changed in the WireGuard behavior. Same actions simply were not logged before.

Larsa · Thu Feb 29, 2024 10:24 pm

@strods, what about "Sending handshake initiation to peer (0.0.0.0:0)" from passive peers? Btw, IMO flooding standard "info" with misleading error messages sends wrong signals.

> @Znevna: You have packets flying towards those peers. Stop the packets, the flooding will stop. Or hide the messages.
Nope, totally silent according to the packet sniffer. Also, it logs 'initial handshake,' not 'handshake reply.

gerab · Thu Feb 29, 2024 10:27 pm

In addition to the logs issue, one of a few WG peers lost its public key. The one I found when I started to investigate the loss of connection was not the same one I put there about a week ago.

rushlife · Thu Feb 29, 2024 10:29 pm

System/Logging and open, for example, "info" topic. Add "!wireguard" to it. All info logs, except WireGuard, will be logged now.

Thx, It worked nicely.

Avnn · Thu Feb 29, 2024 10:33 pm

D53G-5HacD2HnD
After updating from 7.13.5 to 7.14, "Loopback" interface appeared in the interface list. I don't see anything about this in changelog...
What is that loopback?

infabo · Thu Feb 29, 2024 10:37 pm

*) system - expose "lo" and "vrf" interfaces;

Larsa · Thu Feb 29, 2024 11:04 pm

Regarding "wireguard, debug: Sending handshake initiation to peer (0.0.0.0:0)" on passive peers.

This is just pure speculation and I might be completely wrong; but after some troubleshooting it seems that MNDP might trigger passive WireGuard peers to attempt to establish a connection despite the absence of an endpoint address, hence why the dest-addr is set to 0.0.0.0:0.

EDIT:
IMO if it turns out to be the issue, the root cause should be addressed to avoid these (potentially misleading) error messages in the info and debug channels.

braveheartleo · Thu Feb 29, 2024 11:12 pm

I'd like to know, is v7.14rc4 testing and v7.14 stable the same release, except maybe changing the version number and channel? Should I upgrade from v7.14rc4 to this?

fragtion · Thu Feb 29, 2024 11:15 pm

All ethernet interfaces on the CHR machine on the VDSINA hosting are missing. I checked the installation process twice, the ethernet is always lost. I installed 7.13.5, the ethernet is back.

Same problem here. I lost all ethernet devices on one of our CHR after upgrading to 7.14. Provider is running virtualizor

I tested, and v7.13.5 works. 7.14rc1 was the last revision of 7.14rc that sees the nic.

To recover, I had to mount linux livecd and mount /dev/vda2, then create a downgrade directory (mountpoint/disk/downgrade), copy routeros,wireless,container packages to this directory, and then boot back into routeros, enable ftp server, then fetch from download directory to root directory, and finally /system/package/downgrade

mt.png

I presume it's this "RedHat VirtIO Network device"

I'm just glad I found a way to recover this vm...thanks to a combination of my vps provider having the right recovery/console tools, and routeros being linux based and supporting ftpd+fetch
So this one's stuck on 7.14rc1 until we get a fix, hopefully soon :)

Jotne · Thu Feb 29, 2024 11:20 pm

I'd like to know, is v7.14rc4 testing and v7.14 stable the same release, except maybe changing the version number and channel? Should I upgrade from v7.14rc4 to this?

Simple answer yes. RC are not ment for production, do upgrade.

accarda · Thu Feb 29, 2024 11:37 pm

I have noticed an issue with IP tunnel interfaces and VRF.
When creating such interface it does not get instantiated in the proper VRF.
At startup I get an error in the log: failed to set vrf for interface <IP tunnel if>, please check if selected vrf instance is enabled.
VRF is enabled and I have also a VLAN and a L2TP interfaces that are properly working in the same VRF, so it seems more an issue with IP tunnel interfaces and VRF with new Ros 7.14.
Switching back to 7.13.5 solves the issue, all interfaces work fine with the VRF.

bp0 · Thu Feb 29, 2024 11:38 pm

What causes this message regarding a backup-routerboot upgrade? Screenshot from 2024-02-29 09-48-58.png
What device this is?

sorry, RB960PGS (hEX PoE) r2.

usx · Thu Feb 29, 2024 11:46 pm

No immediate problems noticed after upgrading the following from 7.13 (no patch version upgrades applied):

- RBmAP2n ("mAP 2n") x2
- RBD25G-5HPacQD2HPnD ("Audience")
- 2011UiAS-2HnD
- hAP RB951Ui-2nD ("hAP")
- RB4011iGS
- hEX 750G r3 ("hEX")

aindless · Fri Mar 01, 2024 12:26 am

Thanks for the update, amazing memory usage on my ax3 ! With the previous firmware had like 250-300 mb free and now it stays at 500 mb free !!!

sajt · Fri Mar 01, 2024 12:29 am

After upgrading a ccr1009 and a ccr1036 EOIP and IPIP interfaces, tho under the the ip/vrf menu did appear in the correct vrf, in reality the addresses and directly connected networks became part of the "main" vrf.
Downgrading to 7.13.5 solved the issue.

SkyBeam · Fri Mar 01, 2024 1:20 am

Unfortunately I had to downgrade to 7.12.1 again.
After 7.14 installation all my SFP 1G base T (copper) links stayed in non-running state. Same effect as for all 7.13.* revisions. Working just fine again after downgrading to 7.12.1. Interestingly none of my SFP+ modules (1x DAC, 1x LC single-mopde) was affected, they did just run fine.
Device: CRS310-1G-5S-4S+

I was able to get the interface running by disabling auto negotiation as mentioned by somebody else. But would have to set this manually on both ends.

carl0s · Fri Mar 01, 2024 1:34 am

It's a big one. Thank you. I've been waiting for 7.14 to release. I think I am ready to spend some time on wifi-qcom and wifi-qcomac now with capsman

gze100 · Fri Mar 01, 2024 1:44 am

All ethernet interfaces on the CHR machine on the VDSINA hosting are missing. I checked the installation process twice, the ethernet is always lost. I installed 7.13.5, the ethernet is back.

Can confirm this, the bug was introduced with 7.14rc2 and is still there. I opened a support ticket for that. They asked me to create and download a supout.rif file. You may create it, but you cannot download it without ethernet interfaces. So that didn't really help. Will wait for a better idea. Guest tools are also no longer recognized, so that must have been substantial changes between 7.14rc1 and the releases after that. Unfortunately I couldn't find anything in the release notes, that would help for a better understanding of that problem.

infabo · Fri Mar 01, 2024 2:49 am

*) bridge - improved protocol-mode STP and RSTP functionality;

On 7.14 wifi clients can connect to 2.4ghz SSID but DHCP runs into a timeout (and even with static IP no communication possible). Once wifi 5ghz is online (after initial DFS), clients can connect to 5ghz and get IP instantly. But nothing suspicious in the logs.
Then I switched "protocol-mode=rstp" to "protocol-mode=none" on default bridge. Suddenly DHCP and everything else started working on 2ghz as well.

Hmmm

Another observation:
I installed container package yesterday (7.13.5) just for trying the iperf3 container from tangent. ROS reported about 400kb of free disk space on Chateau LTE16 with wifi-qcom-ac and container installed. After the upgrade from 7.13.5 to 7.14 the free space shrinked down to 80kb. I did notice - but did not give much attention. After about 2h running on 7.14 I decided to reboot once again -> BRICKED. Device did not come up again. Netinstall to the rescue. Just ROS with wifi-qcom-ac and no containers, keep configuration. No config lost, device up and running. But 272kb free disk left and I don't even have container package installed this time. I mean WTF. This is getting less on every release.

jordanp123 · Fri Mar 01, 2024 3:48 am

I noticed that on two L009's I have that VRF's quit working. I had a VRF for a Wireguard VPN service and after upgrade it doesn't seem to function anymore. Downgraded back to 7.13.5 and its back to working normally.

own3r1138 · Fri Mar 01, 2024 5:14 am

*) firewall - increased default "udp-timeout" value from 10s to 30s;
It wasn't applied after the update to v17.14.

thedix · Fri Mar 01, 2024 5:22 am

*) arm - improved system stability when using microSD on RB1100Dx4;

I can confirm this is fixed on RB1100AHx4 as well.
On 7.13.5 I had ping losses and reboots when formatting and writing a big file to the microSD slot via Winbox.
On 7.14 I was able to successfully write a file larger than 400 MB.
Thank you!

marcin21 · Fri Mar 01, 2024 5:30 am

Warning!
CCR2004-pcie doesn't come back after upgrade. it's crazy what You do at mikrotik, to release fw *STABLE* that bricks cloud core unit.
looks like boot-loop.

HOW to get it working back on remote location!???

jordanp123 · Fri Mar 01, 2024 5:33 am

I noticed that on two L009's I have that VRF's quit working. I had a VRF for a Wireguard VPN service and after upgrade it doesn't seem to function anymore. Downgraded back to 7.13.5 and its back to working normally.

It seems the issue is that even when the interface of the VPN is added to the VRF via ip->VRF list, the wireguard VPN interface isn't dynamically added to the VRF it was assigned when IP route assignments come up. 7.13.5 It works and behaves as expected, but in this case all wireguard interfaces so matter if they're added to a different VRF or not are dynamically assigned to the main vrf.

thedix · Fri Mar 01, 2024 5:35 am

Code: Select all
*) arm - improved system stability when using microSD on RB1100Dx4;
I can confirm this is fixed on RB1100AHx4 as well.
On 7.13.5 I had ping losses and reboots when formatting and writing a big file to the microSD slot via Winbox.
On 7.14 I was able to successfully write a file larger than 400 MB.
Thank you!

But now on 7.14 the read speed is awful on microSD slot.
About 2-3 Mbps, this is not good.
Could you fix it?

scotth · Fri Mar 01, 2024 5:47 am

MLAG and VRRP still don’t play well together. As aVRRP on an MLAG bridge and when the master changes response on the MLAG up address will fail.

Xand · Fri Mar 01, 2024 6:48 am

Hi, I have hAP ac^2 with wifi-qcom-ac (installed both with netinstall 7.13).
WIFI interfaces are off. I don't keep any files (there is only 1% free free space anyway).
Ever since I upgraded to 7.14 beta the router keeps rebooting with kernel failure (OOM condition detected). Mostly if I try to download / install new version. Sometimes it just happens out of the blue.
Previously, after several reboots on the loop I managed to upgrade to another beta and later rc3. But it just does not want to update to RC4 / stable.
Should I just ditch wifi-qcom-ac? I am not sure what the issue is.

UPD
I disabled wifi-qcom-ac and the router successfully updated to 7.14 stable. Then I enabled again wifi-qcom-ac and rebooted. No kernel issue / OOM so far. Let's see how it will go.

accarda · Fri Mar 01, 2024 7:34 am

In addition to the bug reported about IPIP interfaces not working correctly with VRF, also IP service does not work fine with VRF anymore.
I have IP service www on VRF and does not respond to requests anymore, while all is fine with 7.13.5

Jotne · Fri Mar 01, 2024 7:47 am

HOW to get it working back on remote location!???

Why did you upgrade a remote location, just some hour after a new release?
You should wait 14 days, read the forum, and then you maybe should upgrade.
Also if its a remote location, you should have an equal local device to test it on first.

Rox169 · Fri Mar 01, 2024 8:15 am

ROS 7.14 working on:
HAP AX3
HAP AX2
HAP AC3
HAP AC2
CUBE 60 AC
WAP 60
SXT

Rox169 · Fri Mar 01, 2024 8:19 am

Hi,
could you please explain me why I have new interface lo - Loopback?

Znevna · Fri Mar 01, 2024 8:21 am

Read the changelog.

ccl13 · Fri Mar 01, 2024 8:35 am

Run into issues after upgraded to 7.14 from 7.13.4. The network is not working. WinBox shows all 0 for all interfaces. Switches on the network are all flipping RSTP and it was quite hard to see what actually is happening. Because I need the network working, I downgraded to 7.13.5 and it works fine now. Suspecting similar issue with one of the recent update which screwed up STP too.

gigabyte091 · Fri Mar 01, 2024 8:45 am

RB5009, ax3, CRS310, cAP ax updated without a problem for now, Container and UPS works. CRS310 took 3 and a half minute to upgrade... Other devices minute or so.

Fri Mar 01, 2024 8:55 am

Which version you had on CCR2004-1G-2XS-PCIe, before you did update to 7.14 ?

Fri Mar 01, 2024 9:27 am

*) package - reduced package size for SMIPS

I still cannot ugrade hAP Lite from 7.13 to 7.14 (7.6MiB required, 7.5MiB free, although it's only few kilobytes that are actually missing).
Manual upgrade also won't pass, missing those few kb to upload wireless package.

Those changes are only in the new 7.14 version, but you have the old one. So you don't yet have the smaller package size. You must upgrade using Netinstall. From then on you will no longer have the issues.

Rox169 · Fri Mar 01, 2024 9:37 am

*) system - expose "lo" and "vrf" interfaces;

What is it good for? The lo interface?

sch · Fri Mar 01, 2024 9:47 am

@fragtion
Could you please clarify if your VPS provider has made any updates?

Fri Mar 01, 2024 9:48 am

What is it good for? The lo interface?

Best explanation I could find around here:
viewtopic.php?p=943761#p943761

infabo · Fri Mar 01, 2024 9:58 am

Best explaination is here: https://en.wikipedia.org/wiki/Localhost

Rox169 · Fri Mar 01, 2024 10:01 am

Thank you...until now I did not need it but I have to see it now. It would be better to fix Netwatch/sending notification than add new interface for nothing...

infabo · Fri Mar 01, 2024 10:02 am

*) bridge - improved protocol-mode STP and RSTP functionality;
On 7.14 wifi clients can connect to 2.4ghz SSID but DHCP runs into a timeout (and even with static IP no communication possible). Once wifi 5ghz is online (after initial DFS), clients can connect to 5ghz and get IP instantly. But nothing suspicious in the logs.
Then I switched "protocol-mode=rstp" to "protocol-mode=none" on default bridge. Suddenly DHCP and everything else started working on 2ghz as well.

The SSID is "jupiter" for both wifis. When I only enable 2.4ghz iface, clients connect but receive no IP address (stuck at "obtaining IP address..."). Reproducible on several devices.

Then I change the SSID to "jupiter2". Suddenly all clients connect to AP and can obtain an IP.

Now I am completely clueless.

grusu · Fri Mar 01, 2024 10:03 am

Hi,
I think it's time to rewrite the documentation for the smb service.
Thanks!

morphema · Fri Mar 01, 2024 10:18 am

In Logging, select info, then add wireguard to it, then add the negative sign to wireguard.

Thank you, it works. Considering how bizarre it works, I'm curious about the reason for enabling this rule by default.

nmt1900 · Fri Mar 01, 2024 10:50 am

deleted

pe1chl · Fri Mar 01, 2024 10:58 am

*) firewall - increased default "udp-timeout" value from 10s to 30s;
It wasn't applied after the update to v17.14.

Defaults are not applied by updates. Once you have made a setting it will be saved and restored at reboot, you need to change it to 30 seconds yourself when you want that. New installations will get the new default.

pe1chl · Fri Mar 01, 2024 11:00 am

Warning!
CCR2004-pcie doesn't come back after upgrade. it's crazy what You do at mikrotik, to release fw *STABLE* that bricks cloud core unit.
looks like boot-loop.

Well, I would call it quite irresponsible to install a freshly released 7.xx version at a remote location within a day after release, especially when the same issue was already reported in the release topic...
Also, as mentioned many times before, the label "stable" refers to the stability of the release process, not to the stability of operation.
When you require stability of operation, always wait for the 7.xx.1 version and do not install it within a week of release.

BWC · Fri Mar 01, 2024 11:05 am

AWS sent me a notification that there is a new ROS Image available, does this mean updates will work now without the Instance type t3 -> t2 -> t3 limbo when freshly deployed?

https://aws.amazon.com/marketplace/pp/p ... gn6js6av54

--Michael

mbovenka · Fri Mar 01, 2024 11:07 am

Defaults are not applied by updates. Once you have made a setting it will be saved and restored at reboot, you need to change it to 30 seconds yourself when you want that. New installations will get the new default.

Interesting. That's not what I am used to (working mostly with the Big C @$dayjob). Defaults do get changed there when upgrading. I guess there is something to be said for both approaches.

bratislav · Fri Mar 01, 2024 11:13 am

What causes this message regarding a backup-routerboot upgrade? Screenshot from 2024-02-29 09-48-58.png

edit: Device is RB960PGS (hEX PoE) r2.

Have you bothered to actually read the page from the link provided?
https://wiki.mikrotik.com/wiki/Manual:R ... bootloader

sszbv · Fri Mar 01, 2024 11:35 am

Which version you had on CCR2004-1G-2XS-PCIe, before you did update to 7.14 ?

It was 7.13 on mine (with 7.8 firmware).
Needed a reset to defaults to get it to work again.

See image for first bootlog

ljb · Fri Mar 01, 2024 11:45 am

I too had an issue with CHR ethernet adapters disappearing after updating from 7.13.5 to 7.14 on a production server times two. 7.14 is supposed to be stable realease? I was prepared with a week old snapshot and suddenly my adapters reappeared.

Chupaka · Fri Mar 01, 2024 11:50 am

Regarding "wireguard, debug: Sending handshake initiation to peer (0.0.0.0:0)" on passive peers.

This is just pure speculation and I might be completely wrong; but after some troubleshooting it seems that MNDP might trigger passive WireGuard peers to attempt to establish a connection despite the absence of an endpoint address, hence why the dest-addr is set to 0.0.0.0:0.

I have Neighbor Discovery enabled on all interfaces, and weird errors stopped appearing for me when I disabled keep-alive on passive peers

Chupaka · Fri Mar 01, 2024 11:52 am

I too had an issue with CHR ethernet adapters disappearing after updating from 7.13.5 to 7.14 on a production server times two. 7.14 is supposed to be stable realease? I was prepared with a week old snapshot and suddenly my adapters reappeared.

You mean, you have a VM and you don't test upgrades by making a copy of your VM before upgrading the router in production? %)

gze100 · Fri Mar 01, 2024 11:54 am

@fragtion
Could you please clarify if your VPS provider has made any updates?

That has nothing to do with the VPS provider, I have the same problem running a selfhosted xcp-ng installation which worked without any problems since 2 two years until the release of 7.14rc2. You can reproduce the issue easily as follows.

Set up an CHR installation up to 7.14rc1 and configure it as you like. Check, that everything is working as intended. Do a snapshot of the vm with the tools of your hypervisor. Do a /system/package/update/install to a newer release, reboot and boom here you are without any ethernet interfaces. Check /interfaces/ethernet. You will probably see nothing. Rollback to your snapshot, that you have preferred before and voilà everything is working again without any issue. The problem is not outside the vm, it is inside of the CHR image. Users have reported problems with KVM based installations, I have XEN running, the problem is just the same.

gze100 · Fri Mar 01, 2024 11:59 am

I too had an issue with CHR ethernet adapters disappearing after updating from 7.13.5 to 7.14 on a production server times two. 7.14 is supposed to be stable realease? I was prepared with a week old snapshot and suddenly my adapters reappeared.

7.14 cannot be considered stable, at least not for the CHR image. I have the same issue with all ethernet interfaces disappearing after updating to 7.14rc2 or newer. I did a rollback to 7.14rc1 in my testing environment. In production I still run 7.13.5.

marcin21 · Fri Mar 01, 2024 12:02 pm

HOW to get it working back on remote location!???
Why did you upgrade a remote location, just some hour after a new release?
You should wait 14 days, read the forum, and then you maybe should upgrade.
Also if its a remote location, you should have an equal local device to test it on first.

its distant but not yet on production. frankly speaking it's because I've got problem on it with tagged VLAN, and according to changelog
that issue was addressed in this release. So if it was placed in

STABLE branch

i thought that it's gone through beta and RC, so it wont blow up but it did.

mikrotik You are really making my effort more interesting that it should be.

marcin21 · Fri Mar 01, 2024 12:05 pm

Which version you had on CCR2004-1G-2XS-PCIe, before you did update to 7.14 ?

7.13.5 as I have on hosting x86.

why you make it so hard to belive stable branch is something that is considered STABLE???

are You testing it on recent devices or just letting ppl like me to be betatester???

infabo · Fri Mar 01, 2024 12:16 pm

On 7.14 wifi clients can connect to 2.4ghz SSID but DHCP runs into a timeout (and even with static IP no communication possible). Once wifi 5ghz is online (after initial DFS), clients can connect to 5ghz and get IP instantly. But nothing suspicious in the logs.
Then I switched "protocol-mode=rstp" to "protocol-mode=none" on default bridge. Suddenly DHCP and everything else started working on 2ghz as well.
The SSID is "jupiter" for both wifis. When I only enable 2.4ghz iface, clients connect but receive no IP address (stuck at "obtaining IP address..."). Reproducible on several devices.

Then I change the SSID to "jupiter2". Suddenly all clients connect to AP and can obtain an IP.

Now I am completely clueless.

Downgrading to 7.13.5 fixes the issue also on SSID "jupiter. But still I don't know what causes this. I would suspect RSTP changes - but how can I pin that out?

jimmer · Fri Mar 01, 2024 12:23 pm

Hi All,

I have upgraded two devices to RouterOS 7.14 one from 7.13 (RB3011iUAS-RM) and the older RB2011iUAS-RM from 7.12

No issues with either per se but the RB2011 MIPSBE based unit reported this in the logs after upgrade:

2024-03-01 14:30:16 system,info,critical Optimal nand stability requires a backup-routerboot upgrade.\r
2024-03-01 14:30:16 system,info,critical Universal package can be found here:\r
2024-03-01 14:30:16 system,info,critical https://wiki.mikrotik.com/wiki/Manual:R ... D_settings

Noticed that it has an escaped character at the end, Routerboot was 7.12 and I upgraded it to 7.14

As seen below:

[jim@bradfield-rb2011-gw] > system/routerboard/print
routerboard: yes
model: RB2011UiAS
serial-number: 763307XXXXX
firmware-type: ar9344
factory-firmware: 3.33
current-firmware: 7.14

What limited information I can find for this alert appears to reference rather confusingly protected mode (which I dont use on anything) and a firmware from 6.4x but nothing relating to 7, I have never seen this pop up on any previous 7 release and the 2011 has been through just about every version from 7.1.5 onwards.

Any thoughts? is this a MIPSBE architecture bug?

infabo · Fri Mar 01, 2024 12:25 pm

The SSID is "jupiter" for both wifis. When I only enable 2.4ghz iface, clients connect but receive no IP address (stuck at "obtaining IP address..."). Reproducible on several devices.

Then I change the SSID to "jupiter2". Suddenly all clients connect to AP and can obtain an IP.

Now I am completely clueless.
Downgrading to 7.13.5 fixes the issue also on SSID "jupiter. But still I don't know what causes this. I would suspect RSTP changes - but how can I pin that out?

After upgrading to 7.14 again - the issue is gone!!! Magic. Pretty speechless.

infabo · Fri Mar 01, 2024 12:27 pm

Here some interesting info for the ones that are interested into "Free HHD Space":

2024-03-01_11-20.png

2024-03-01_11-26.png

ROSE SMB must be really awesome stuff to justify this reduction of free disk space...shrug

DarkNate · Fri Mar 01, 2024 12:36 pm

*) defconf - use "fq_codel" queue as default interface queue for wired ports on LTE devices;

Still not BQL for RouterOS? I still see poor bufferbloat/CPU usage issues under stress testing. Come on MikroTik, just add BQL support already.

Fri Mar 01, 2024 12:57 pm

We can't "Add stuff", we can only "Make stuff"

kalamaja · Fri Mar 01, 2024 1:08 pm

Thank you, Mikrotik, for upgrading AWS CHR image from 6.x to 7.14: https://aws.amazon.com/marketplace/pp/p ... gn6js6av54
Hopefully it has fixed the problem that on T3 instances 7.x upgrades were failing.

DarkNate · Fri Mar 01, 2024 1:12 pm

We can't "Add stuff", we can only "Make stuff"

Then make it, or simply allow official ONIE support on your hardware, we'll flash any OS of choice and get over RouterOS.

Fri Mar 01, 2024 1:16 pm

AWS sent me a notification that there is a new ROS Image available, does this mean updates will work now without the Instance type t3 -> t2 -> t3 limbo when freshly deployed?

https://aws.amazon.com/marketplace/pp/p ... gn6js6av54

--Michael

yes

biomesh · Fri Mar 01, 2024 1:29 pm

Upgraded ccr2004-16g-2s+, rb5009, crs318, crs317, cap ac, crs112 and chr with no real issue. This is from a mixture of 7.13 and 7.14rc versions.

I did see the odd firmware version text display issue I saw with a previous rc to release version on the ccr, but it just seems to be cosmetic.

Everything else was fine.

tommyd · Fri Mar 01, 2024 1:33 pm

What is it good for? The lo interface?
Best explanation I could find around here:
viewtopic.php?p=943761#p943761

On the all routers (from various vendors) I ever configured you can configure as many loopback interfaces you want, attach them to vrfs and use for various things i.e. iBGP. It does not seem to be case there. and What is a VRF interface

Fri Mar 01, 2024 1:35 pm

...and What is a VRF interface

A bit lazy, aren't we ?
https://help.mikrotik.com/docs/pages/vi ... eId=328206

Jotne · Fri Mar 01, 2024 1:38 pm

Thank you...until now I did not need it but I have to see it now. It would be better to fix Netwatch/sending notification than add new interface for nothing...

In large organisation with lots of routers (and switches) its normal to set IP on loop back interface so they are more easy to handle.
A route may have many IP, so what should you use to connect to SSH to it? Setting a range of IP like 10.111.111.0/24, you can access first
router with IP 10.111.111.1, second with 10.111.111.2 etc. Same goes for what IP should be used to send the log from, the loopback IP,
since it always the same and as mention by other always UP.

So for SSH/Telnet/SNMP/Syslog/web access etc loopback IP are nice to have.

wispmikrotik · Fri Mar 01, 2024 1:43 pm

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

What's new in 7.14 (2024-Feb-29 09:10):

Some kind of mechanism to import/export routes from one vrf to another within same router --> Thanks!

baragoon · Fri Mar 01, 2024 1:51 pm

Upgraded 10 CHRs without issue... what I did wrong? :-)

infabo · Fri Mar 01, 2024 1:59 pm

We can't "Add stuff", we can only "Make stuff"
Then make it, or simply allow official ONIE support on your hardware, we'll flash any OS of choice and get over RouterOS.

Are you in love with Mikrotik hardware so much? So there is a thing by Mikrotik you can't complain about? Wow

gze100 · Fri Mar 01, 2024 2:10 pm

Upgraded 10 CHRs without issue... what I did wrong? :-)

I don't know, but maybe you can tell us a little about your environment. That could help microtik narrow down the problem.

baragoon · Fri Mar 01, 2024 2:22 pm

tell us a little about your environment

I don't have detailed HV information, I'm only a client. I only know that some VMs are run on ProxMox (7.3-6, 7.4-17, 7.4-16, 8.1.4) but have no idea about server or NIC models.

Paternot · Fri Mar 01, 2024 2:25 pm

*) firewall - increased default "udp-timeout" value from 10s to 30s;
It wasn't applied after the update to v17.14.

It never is. A new default doesn't overwrite something already set up. This is done on purpose, because the old value worked, and there is a chance the new value will mess with some weird user config.

If someone upgrades to the new version and do a factory reset, the new value will be applied. If someone just upgrades, the old value is kept.

gze100 · Fri Mar 01, 2024 2:41 pm

tell us a little about your environment
I don't have detailed HV information, I'm only a client. I only know that some VMs are run on ProxMox (7.3-6, 7.4-17, 7.4-16, 8.1.4) but have no idea about server or NIC models.

Thanks, that's quite a bit. Do you use any special functions within your CHR routers? How many interfaces do you have connected to them? Can you print the output of the /system/resources/pci section to the thread so we can see what resources are in the VM.

elico · Fri Mar 01, 2024 2:51 pm

The comment from w0lt was correct. In order to disable specific topic logs, go to System/Logging and open, for example, "info" topic. Add "!wireguard" to it. All info logs, except WireGuard, will be logged now.

Yes, these are new logs, nothing changed in the WireGuard behavior. Same actions simply were not logged before.

These logs should be in a debug and not an info level.

elico · Fri Mar 01, 2024 2:56 pm

Thank you...until now I did not need it but I have to see it now. It would be better to fix Netwatch/sending notification than add new interface for nothing...

What notifications and I don't understand if it's sending or not.
As far as I know to send a notification from netwatch you need to write a script, so what exactly is wrong?

elico · Fri Mar 01, 2024 2:58 pm

I too had an issue with CHR ethernet adapters disappearing after updating from 7.13.5 to 7.14 on a production server times two. 7.14 is supposed to be stable realease? I was prepared with a week old snapshot and suddenly my adapters reappeared.

OK what hypervisor? Worked fine on Hyper-V.

/system/resource/pci/print 
Columns: DEVICE, VENDOR, NAME, IRQ
#  DEVICE   VENDOR                 NAME                                                             IRQ
0  00:00.0  Intel Corporation      440BX/ZX/DX - 82443BX/ZX/DX Host bridge (AGP disabled) (rev: 3)    0
1  00:07.0  Intel Corporation      82371AB/EB/MB PIIX4 ISA (rev: 1)                                   0
2  00:07.1  Intel Corporation      82371AB/EB/MB PIIX4 IDE (rev: 1)                                   0
3  00:07.3  Intel Corporation      82371AB/EB/MB PIIX4 ACPI (rev: 2)                                  0
4  00:08.0  Microsoft Corporation  Hyper-V virtual VGA (rev: 0)                                      11

baragoon · Fri Mar 01, 2024 3:00 pm

Thanks, that's quite a bit. Do you use any special functions within your CHR routers? How many interfaces do you have connected to them? Can you print the output of the /system/resources/pci section to the thread so we can see what resources are in the VM.

Columns: DEVICE, VENDOR, NAME
 #  DEVICE   VENDOR             NAME
 0  00:00.0  Intel Corporation  440FX - 82441FX PMC [Natoma] (rev: 2)
 1  00:01.0  Intel Corporation  82371SB PIIX3 ISA [Natoma/Triton II] (rev: 0)
 2  00:01.1  Intel Corporation  82371SB PIIX3 IDE [Natoma/Triton II] (rev: 0)
 3  00:01.2  Intel Corporation  82371SB PIIX3 USB [Natoma/Triton II] (rev: 1)
 4  00:01.3  Intel Corporation  82371AB/EB/MB PIIX4 ACPI (rev: 3)
 5  00:02.0  unknown            unknown (rev: 2)
 6  00:03.0  Red Hat, Inc.      Virtio memory balloon (rev: 0)
 7  00:05.0  Red Hat, Inc.      QEMU PCI-PCI bridge (rev: 0)
 8  00:0a.0  Red Hat, Inc.      Virtio block device (rev: 0)
 9  00:12.0  Red Hat, Inc.      Virtio network device (rev: 0)
10  00:13.0  Red Hat, Inc.      Virtio network device (rev: 0)
11  00:14.0  Red Hat, Inc.      Virtio network device (rev: 0)
12  00:1e.0  Red Hat, Inc.      QEMU PCI-PCI bridge (rev: 0)
13  00:1f.0  Red Hat, Inc.      QEMU PCI-PCI bridge (rev: 0)

Columns: DEVICE, VENDOR, NAME
 #  DEVICE   VENDOR             NAME
 0  00:00.0  Intel Corporation  440FX - 82441FX PMC [Natoma] (rev: 2)
 1  00:01.0  Intel Corporation  82371SB PIIX3 ISA [Natoma/Triton II] (rev: 0)
 2  00:01.1  Intel Corporation  82371SB PIIX3 IDE [Natoma/Triton II] (rev: 0)
 3  00:01.2  Intel Corporation  82371SB PIIX3 USB [Natoma/Triton II] (rev: 1)
 4  00:01.3  Intel Corporation  82371AB/EB/MB PIIX4 ACPI (rev: 3)
 5  00:02.0  unknown            unknown (rev: 2)
 6  00:03.0  Red Hat, Inc.      Virtio memory balloon (rev: 0)
 7  00:05.0  Red Hat, Inc.      QEMU PCI-PCI bridge (rev: 0)
 8  00:12.0  Red Hat, Inc.      Virtio network device (rev: 0)
 9  00:13.0  Red Hat, Inc.      Virtio network device (rev: 0)
10  00:14.0  Red Hat, Inc.      Virtio network device (rev: 0)
11  00:15.0  Red Hat, Inc.      Virtio network device (rev: 0)
12  00:16.0  Red Hat, Inc.      Virtio network device (rev: 0)
13  00:1e.0  Red Hat, Inc.      QEMU PCI-PCI bridge (rev: 0)
14  00:1f.0  Red Hat, Inc.      QEMU PCI-PCI bridge (rev: 0)
15  01:01.0  Red Hat, Inc.      Virtio SCSI (rev: 0)

Columns: DEVICE, VENDOR, NAME
 #  DEVICE   VENDOR             NAME
 0  00:00.0  Intel Corporation  440FX - 82441FX PMC [Natoma] (rev: 2)
 1  00:01.0  Intel Corporation  82371SB PIIX3 ISA [Natoma/Triton II] (rev: 0)
 2  00:01.1  Intel Corporation  82371SB PIIX3 IDE [Natoma/Triton II] (rev: 0)
 3  00:01.2  Intel Corporation  82371SB PIIX3 USB [Natoma/Triton II] (rev: 1)
 4  00:01.3  Intel Corporation  82371AB/EB/MB PIIX4 ACPI (rev: 3)
 5  00:02.0  unknown            unknown (rev: 2)
 6  00:03.0  Red Hat, Inc.      Virtio memory balloon (rev: 0)
 7  00:05.0  Red Hat, Inc.      QEMU PCI-PCI bridge (rev: 0)
 8  00:0a.0  Red Hat, Inc.      Virtio block device (rev: 0)
 9  00:12.0  Red Hat, Inc.      Virtio network device (rev: 0)
10  00:13.0  Red Hat, Inc.      Virtio network device (rev: 0)
11  00:14.0  Red Hat, Inc.      Virtio network device (rev: 0)
12  00:1e.0  Red Hat, Inc.      QEMU PCI-PCI bridge (rev: 0)
13  00:1f.0  Red Hat, Inc.      QEMU PCI-PCI bridge (rev: 0)

Columns: DEVICE, VENDOR
 #  DEVICE   VENDOR
 0  00:00.0  Intel Corporation
 1  00:01.0  Red Hat, Inc.
 2  00:02.0  Red Hat, Inc.
 3  00:02.1  Red Hat, Inc.
 4  00:02.2  Red Hat, Inc.
 5  00:02.3  Red Hat, Inc.
 6  00:02.4  Red Hat, Inc.
 7  00:1f.0  Intel Corporation
 8  00:1f.2  Intel Corporation
 9  00:1f.3  Intel Corporation
10  01:00.0  Red Hat, Inc.
11  02:00.0  Red Hat, Inc.
12  03:00.0  Red Hat, Inc.
13  04:00.0  Red Hat, Inc.

Columns: DEVICE, VENDOR, NAME
 #  DEVICE   VENDOR             NAME
 0  00:00.0  Intel Corporation  440FX - 82441FX PMC [Natoma] (rev: 2)
 1  00:01.0  Intel Corporation  82371SB PIIX3 ISA [Natoma/Triton II] (rev: 0)
 2  00:01.1  Intel Corporation  82371SB PIIX3 IDE [Natoma/Triton II] (rev: 0)
 3  00:01.2  Intel Corporation  82371SB PIIX3 USB [Natoma/Triton II] (rev: 1)
 4  00:01.3  Intel Corporation  82371AB/EB/MB PIIX4 ACPI (rev: 3)
 5  00:02.0  unknown            unknown (rev: 2)
 6  00:03.0  Red Hat, Inc.      Virtio memory balloon (rev: 0)
 7  00:05.0  Red Hat, Inc.      QEMU PCI-PCI bridge (rev: 0)
 8  00:0a.0  Red Hat, Inc.      Virtio block device (rev: 0)
 9  00:12.0  Red Hat, Inc.      Virtio network device (rev: 0)
10  00:1e.0  Red Hat, Inc.      QEMU PCI-PCI bridge (rev: 0)
11  00:1f.0  Red Hat, Inc.      QEMU PCI-PCI bridge (rev: 0)

Columns: DEVICE, VENDOR
 #  DEVICE   VENDOR
 0  00:00.0  Intel Corporation
 1  00:01.0  Intel Corporation
 2  00:01.1  Intel Corporation
 3  00:01.2  Intel Corporation
 4  00:01.3  Intel Corporation
 5  00:02.0  unknown
 6  00:03.0  Red Hat, Inc.
 7  00:04.0  Red Hat, Inc.
 8  00:05.0  Intel Corporation
 9  00:06.0  Red Hat, Inc.
10  00:07.0  Red Hat, Inc.
11  00:08.0  Red Hat, Inc.
12  00:09.0  Red Hat, Inc.
13  00:0a.0  Red Hat, Inc.
14  00:0b.0  Red Hat, Inc.

Columns: DEVICE, VENDOR, NAME
 #  DEVICE   VENDOR             NAME
 0  00:00.0  Intel Corporation  440FX - 82441FX PMC [Natoma] (rev: 2)
 1  00:01.0  Intel Corporation  82371SB PIIX3 ISA [Natoma/Triton II] (rev: 0)
 2  00:01.1  Intel Corporation  82371SB PIIX3 IDE [Natoma/Triton II] (rev: 0)
 3  00:01.2  Intel Corporation  82371SB PIIX3 USB [Natoma/Triton II] (rev: 1)
 4  00:01.3  Intel Corporation  82371AB/EB/MB PIIX4 ACPI (rev: 3)
 5  00:02.0  unknown            unknown (rev: 2)
 6  00:03.0  Red Hat, Inc.      Virtio memory balloon (rev: 0)
 7  00:05.0  Red Hat, Inc.      QEMU PCI-PCI bridge (rev: 0)
 8  00:12.0  Red Hat, Inc.      Virtio network device (rev: 0)
 9  00:13.0  Red Hat, Inc.      Virtio network device (rev: 0)
10  00:1e.0  Red Hat, Inc.      QEMU PCI-PCI bridge (rev: 0)
11  00:1f.0  Red Hat, Inc.      QEMU PCI-PCI bridge (rev: 0)
12  01:01.0  Red Hat, Inc.      Virtio SCSI (rev: 0)

Columns: DEVICE, VENDOR, NAME
 #  DEVICE   VENDOR             NAME
 0  00:00.0  Intel Corporation  440FX - 82441FX PMC [Natoma] (rev: 2)
 1  00:01.0  Intel Corporation  82371SB PIIX3 ISA [Natoma/Triton II] (rev: 0)
 2  00:01.1  Intel Corporation  82371SB PIIX3 IDE [Natoma/Triton II] (rev: 0)
 3  00:01.2  Intel Corporation  82371SB PIIX3 USB [Natoma/Triton II] (rev: 1)
 4  00:01.3  Intel Corporation  82371AB/EB/MB PIIX4 ACPI (rev: 3)
 5  00:02.0  unknown            unknown (rev: 2)
 6  00:03.0  Red Hat, Inc.      Virtio memory balloon (rev: 0)
 7  00:05.0  Red Hat, Inc.      QEMU PCI-PCI bridge (rev: 0)
 8  00:0a.0  Red Hat, Inc.      Virtio block device (rev: 0)
 9  00:12.0  Red Hat, Inc.      Virtio network device (rev: 0)
10  00:13.0  Red Hat, Inc.      Virtio network device (rev: 0)
11  00:1e.0  Red Hat, Inc.      QEMU PCI-PCI bridge (rev: 0)
12  00:1f.0  Red Hat, Inc.      QEMU PCI-PCI bridge (rev: 0)

Columns: DEVICE, VENDOR
 #  DEVICE   VENDOR
 0  00:00.0  Intel Corporation
 1  00:01.0  Intel Corporation
 2  00:07.0  Intel Corporation
 3  00:07.1  Intel Corporation
 4  00:07.3  Intel Corporation
 5  00:07.7  VMware
 6  00:0f.0  VMware
 7  00:11.0  VMware
 8  00:15.0  VMware
 9  00:15.1  VMware
10  00:15.2  VMware
11  00:15.3  VMware
12  00:15.4  VMware
13  00:15.5  VMware
14  00:15.6  VMware
15  00:15.7  VMware
16  00:16.0  VMware
17  00:16.1  VMware
18  00:16.2  VMware
19  00:16.3  VMware
20  00:16.4  VMware
21  00:16.5  VMware
22  00:16.6  VMware
23  00:16.7  VMware
24  00:17.0  VMware
25  00:17.1  VMware
26  00:17.2  VMware
27  00:17.3  VMware
28  00:17.4  VMware
29  00:17.5  VMware
30  00:17.6  VMware
31  00:17.7  VMware
32  00:18.0  VMware
33  00:18.1  VMware
34  00:18.2  VMware
35  00:18.3  VMware
36  00:18.4  VMware
37  00:18.5  VMware
38  00:18.6  VMware
39  00:18.7  VMware
40  03:00.0  VMware
41  0b:00.0  VMware
42  13:00.0  VMware
43  1b:00.0  VMware

Columns: DEVICE, VENDOR, NAME, IRQ
#  DEVICE   VENDOR             NAME                                           IR
0  00:00.0  Intel Corporation  440FX - 82441FX PMC [Natoma] (rev: 2)           0
1  00:01.0  Intel Corporation  82371SB PIIX3 ISA [Natoma/Triton II] (rev: 0)   0
2  00:01.1  Intel Corporation  82371SB PIIX3 IDE [Natoma/Triton II] (rev: 0)   0
3  00:01.2  Intel Corporation  82371SB PIIX3 USB [Natoma/Triton II] (rev: 1)  11
4  00:01.3  Intel Corporation  82371AB/EB/MB PIIX4 ACPI (rev: 3)               9
5  00:02.0  unknown            unknown (rev: 2)                                0
6  00:03.0  Red Hat, Inc.      Virtio network device (rev: 0)                 11
7  00:04.0  Red Hat, Inc.      Virtio memory balloon (rev: 0)                 11

all 10 instances, some with single, some with up to 5 ethernet interfaces

Guscht · Fri Mar 01, 2024 3:10 pm

7.14 runs good, but WUS DIS????
Endless log-spam

wireguard.jpg

baragoon · Fri Mar 01, 2024 3:14 pm

WUS DIS????

search this topic...

Fri Mar 01, 2024 3:24 pm

Some default debug filters not being applied to log entries.

I saw them for wireguard, DHCP, DNS, NTP. All silent now.

gze100 · Fri Mar 01, 2024 3:29 pm

Thanks, that's quite a bit. Do you use any special functions within your CHR routers? How many interfaces do you have connected to them? Can you print the output of the /system/resources/pci section to the thread so we can see what resources are in the VM.

It seems that at least one is running under VMware, the others under KVM. Another user reports that Hyper-V is working. Amazon has updated their CHR image as well, as I noted in this thread. I don't know what they are using in their cloud. I'd also appreciate more feedback from other users to see if it's limited to Xen-based VMs or if KVM and XEN both have issues with it. I'm not sure about that yet. With KVM-based installations, there seem to be working and non-functioning ones. There might be an implication to the Linux kernel of the KVM host. Let's see what feedback we get on this.

pe1chl · Fri Mar 01, 2024 3:35 pm

The comment from w0lt was correct. In order to disable specific topic logs, go to System/Logging and open, for example, "info" topic. Add "!wireguard" to it. All info logs, except WireGuard, will be logged now.

Yes, these are new logs, nothing changed in the WireGuard behavior. Same actions simply were not logged before.
These logs should be in a debug and not an info level.

Well, IMHO it is just a bug. When a wireguard interface is passive, and it receives "interesting traffic to send", it should just do nothing.
It appears the code to setup a connection is triggered, even though it is passive. That is just wrong.

pe1chl · Fri Mar 01, 2024 3:38 pm

Some default debug filters not being applied to log entries.

I saw them for wireguard, DHCP, DNS, NTP. All silent now.

Please explain what you mean. Logging for "debug" is disabled by default, and always has been.
Did you create a log rule for "debug" and does it behave different now?

Fri Mar 01, 2024 3:50 pm

Please explain what you mean. Logging for "debug" is disabled by default, and always has been.
Did you create a log rule for "debug" and does it behave different now?

Example which wasn't there before moving from 7.14rc3 to 7.14.
That's debug, isn't it ?

I also saw NTP debug, dns, dns packet (which for me also classifies as debug), ...
All that wireguard info stuff, interesting as it may be for some, is for me also debug info.

I did not have a prior debug rule in log. So it's the system which behaves differently now.

deathandtaxes · Fri Mar 01, 2024 4:33 pm

I'm unable to update my hap ac2 with wifi-qcom-ac package to 7.14 due to disk space. I can uninstall wifi-qcom-ac and upgrade to 7.14, but cannot then add wifi-qcom-ac due to disk space.

I've reverted back to 7.13.5.

mseidler · Fri Mar 01, 2024 4:34 pm

So far so good, but what happens in Webfig when you look for the BTH Wireguard Peers. Page is continously rebuilding the list of peers (every 2 or 5 seconds).

merlinthemagic7 · Fri Mar 01, 2024 4:35 pm

AWS sent me a notification that there is a new ROS Image available, does this mean updates will work now without the Instance type t3 -> t2 -> t3 limbo when freshly deployed?

https://aws.amazon.com/marketplace/pp/p ... gn6js6av54

--Michael
yes

Please clarify if this means ONLY new 7.14 AWS T3 instance can be updated going forward.

We did a few tests:

1) Updating an existing AWS T3 running 7.8 straight to 7.14. Failed with "LoaE01".
2) Created a new AWS T3 7.14 and tried "updating" to 7.14-rc4. Failed with "LoaE01".
3) Changing an existing AWS T3 running 7.8, to T2 then updating straight to 7.14. Works, change back to T3, still works but requires the work around t3<=>t2.

If we need to rebuild all instances that were deployed with <7.14 so be it, but trying to understand why downgrading to the last RC bricks the instance like before. Cant find mention of a fix for the T3 hypervisor in the change log, so i guess it is possible it was added after rc4.

Just trying to understand if we should spend the time and rebuild all our CHR instances now or if there maybe a bug that still needs ironing out.

Kevo · Fri Mar 01, 2024 7:05 pm

I've updated my CHR instance in ProxMox and had no issues with the upgrade so far. I am just using this router as a basic home router with NAT and a couple of containers, so nothing special configured on the ethernet ports. I am running cake as well.

BrateloSlava · Fri Mar 01, 2024 7:13 pm

Good afternoon.

Today, when trying to update one hAP ac2 from 7.13.5 to 7.14, I received this out of memory error.

Screenshot_log_error.png

After which I conducted two experiments with installing ROS via Netinstall.

Two packages are installed on the router:
- routeros-7.14-arm.npk
- wifi-qcom-ac-7.14-arm.npk

In the first case, only the system package was installed via Netinstall, and the WiFi driver package was installed through additional installation into an already installed system.
In the second case, both packages were installed via Netinstall.

Screenshot_ac2-step-2-step.png

Screenshot_ac2-all-at-one.png

Conclusion: if you want to save “more” free space, install all packages via Netinstall.

sbr · Fri Mar 01, 2024 7:27 pm

Hi,

I have the following wireguard bth info in the log on a hap ax lite LTE 6 and an RB 5009. With version 7.13
was everything OK. A new configuration of Wiregurad BTH does not bring any changes.

I just upgraded to 7.14 and got the same. Wireguard is DEAD

DL7JP · Fri Mar 01, 2024 8:48 pm

Updated RB1100AHx4, RB2011iL, CRS125-24G-1S, hAP ac^2 and hAP ac from 7.13.5 to 7.14. w/o problems; the first three run Wireguard, all fine, nothing unusual in the logs.

notanial · Fri Mar 01, 2024 9:02 pm

Hi,

I have the following wireguard bth info in the log on a hap ax lite LTE 6 and an RB 5009. With version 7.13
was everything OK. A new configuration of Wiregurad BTH does not bring any changes.
I just upgraded to 7.14 and got the same. Wireguard is DEAD

A new wg configuration from scratch did the trick. I've deleted peer and wg interface and created new wg interface and peer, reassigned ip and set again interface in fw rules

Lenry · Fri Mar 01, 2024 9:04 pm

my hap ac3 upgraded to 7.14 during the night.
since then a logging rule (wireguard,info) spamming the log about "Handshake for peer did not complete" for a client that doesn't connect. which is fine, but the rule is disabled, has been for a long time. I even deleted it since, but it still spams the log.

t0mm13b · Fri Mar 01, 2024 9:26 pm

Upgraded Chateau LTE12 to v7.14, bit shocked to see the storage size plummet from 420k approx to this.
wifi-qcom-ac and routeros?

chateau_v714.png

Irony was lost when I migrated from wireless package to this wifi-qcom-ac

*) package - reduced "wireless" package size for ARM, ARM64, MIPSBE, MMIPS devices;

pbr3000 · Fri Mar 01, 2024 9:50 pm

my hap ac3 upgraded to 7.14 during the night.
since then a logging rule (wireguard,info) spamming the log about "Handshake for peer did not complete" for a client that doesn't connect. which is fine, but the rule is disabled, has been for a long time. I even deleted it since, but it still spams the log.

Read the first messages from this topic. It's a function, but can be disabled.

Fri Mar 01, 2024 9:59 pm

It should be disabled as default.
So should the other messages spamming the log.

hargen · Fri Mar 01, 2024 10:22 pm

Regarding the "Handshake for peer did not complete" log messages from WireGuard... I confirmed that these were coming from my passive peer entries where I had configured a persistent keepalive. The keepalive configuration was the "trigger". Removing that keepalive stopped the messages. The remote client can still have its own keepalive configured, and should if it is connecting outward and/or inward through a connection-tracking firewall, and the client-side keepalive should be sufficient to keep the connection tracking active.

It could be argued that it is a WireGuard (or MiktoTik) bug to be attempting a keepalive when no endpoint is configured and no connection exists. But removing the keepalive configuration is an easy workaround without disabling the logging of other WireGuard,info events.

Znevna · Fri Mar 01, 2024 10:40 pm

Sounds familiar, Oh wait.
viewtopic.php?p=1059847#p1059847
viewtopic.php?p=1059520#p1059520

One could argue that having keepalive set for what you call "passive peers" is a little ... you know?

Larsa · Fri Mar 01, 2024 10:45 pm

@hargen: I can confirm that it works, but one has to wait for 20 attempts before receiving the message "Handshake for peer did not complete after 20 attempts, giving up," and then it goes silent. If you re-enable "Keep alive" it starts all over again.

Well spotted in finding the root cause. Hopefully, R&D fixes this bug in the next beta. And yeah, I consider it a true bug, especially if a passive node that lacks an endpoint address still attempts to initiate an outbound connection.

Great job!

nmt1900 · Fri Mar 01, 2024 11:19 pm

Regarding the "Handshake for peer did not complete" log messages from WireGuard... I confirmed that these were coming from my passive peer entries where I had configured a persistent keepalive. The keepalive configuration was the "trigger". Removing that keepalive stopped the messages. The remote client can still have its own keepalive configured, and should if it is connecting outward and/or inward through a connection-tracking firewall, and the client-side keepalive should be sufficient to keep the connection tracking active.

It could be argued that it is a WireGuard (or MiktoTik) bug to be attempting a keepalive when no endpoint is configured and no connection exists. But removing the keepalive configuration is an easy workaround without disabling the logging of other WireGuard,info events.

That might explain why I was not seeing this flood while I have passive Wireguard peers configured - I did not have persistent keepalive enabled on them as it did not make sense to me to have keepalive set on "responder" side (even if this kind of configuration is technically possible).

dcbcr · Sat Mar 02, 2024 12:33 am

Hi,

I have the following wireguard bth info in the log on a hap ax lite LTE 6 and an RB 5009. With version 7.13
was everything OK. A new configuration of Wiregurad BTH does not bring any changes.
I just upgraded to 7.14 and got the same. Wireguard is DEAD

Hello dude, escuse me, me too, after install my wireguard connections Dead, i use it for a simple vpn with proton service, but fail after it, are you sure for this think, the error is for the update 7.14?.
Can u help about the solution please, i try to downgrade but is imposible to do it.
U got a solution?

Thanks, good day....

sirbryan · Sat Mar 02, 2024 1:49 am

Regarding the "Handshake for peer did not complete" log messages from WireGuard... I confirmed that these were coming from my passive peer entries where I had configured a persistent keepalive. The keepalive configuration was the "trigger". Removing that keepalive stopped the messages. The remote client can still have its own keepalive configured, and should if it is connecting outward and/or inward through a connection-tracking firewall, and the client-side keepalive should be sufficient to keep the connection tracking active.

It could be argued that it is a WireGuard (or MiktoTik) bug to be attempting a keepalive when no endpoint is configured and no connection exists. But removing the keepalive configuration is an easy workaround without disabling the logging of other WireGuard,info events.
That might explain why I was not seeing this flood while I have passive Wireguard peers configured - I did not have persistent keepalive enabled on them as it did not make sense to me to have keepalive set on "responder" side (even if this kind of configuration is technically possible).

I have passive peers without keepalive configured and I still saw a bunch of these. They weren't incessant, but they randomly came up in clusters. I ended up filtering them in the log settings for now.

Neolo · Sat Mar 02, 2024 2:20 am

Log is flooded with SA Query timeouts. Clients have terrible experience using wifi. What is going on??
Does anyone even work on this long lasting issue? Persists in all versions, including 7.14.

gigabyte091 · Sat Mar 02, 2024 6:51 am

BTH not working after update to 7.14... App keep saying connecting... And I can see handshake timeout error...

Kanzler · Sat Mar 02, 2024 7:43 am

@gigabyte091,
Have you tried deleting BTH and recreating it?

ErfanDL · Sat Mar 02, 2024 8:03 am

This update is full of bugs, I have to reset hAP Lite every 2 hours to reach normal speed.

gigabyte091 · Sat Mar 02, 2024 8:33 am

@gigabyte091,
Have you tried deleting BTH and recreating it?

No, BTH worked every update until now...

ngalfas · Sat Mar 02, 2024 8:54 am

That might explain why I was not seeing this flood while I have passive Wireguard peers configured - I did not have persistent keepalive enabled on them as it did not make sense to me to have keepalive set on "responder" side (even if this kind of configuration is technically possible).
I have passive peers without keepalive configured and I still saw a bunch of these. They weren't incessant, but they randomly came up in clusters. I ended up filtering them in the log settings for now.

Same here. All peers lack any persistent keepalive setting, all disabled.
The log is full for handshakes did not complete.
I even thought maybe DUDE-snmp is causing peer to be called, disabled some polling. No effect. Still tries to initiate handshakes with peers, with or without endpoints.

erlinden · Sat Mar 02, 2024 9:09 am

What is going on??

In my experience it all comes down (or goes up) with good configuration. Had to do some tweaking, enabling debug logging for wireless did provide a lot of useful information (specifically identifying the iPhone 11 having difficulties with both WPA2-PSK and WPA3-PSK enabled). If you search for SA Query on this forum you will find more information.

Guscht · Sat Mar 02, 2024 10:13 am

The keepalive configuration was the "trigger". Removing that keepalive stopped the messages.

I dont have a Keepalive configured, but a Gateway-Check "Ping" under routes for a few Wireguard-Peers.
Was never a problem till now...

Log is flooded with SA Query timeouts. Clients have terrible experience using wifi. What is going on??

I had to edit the "Connect Priority" thing.. It will make your WiFi vulnerable to the MacStealer'-attack.
MT screwed up the WiFi totally and the network is unuseable with this "security" feature turned on (default). And left you either with an unusable network or a vulnerable network - good job MT... viewtopic.php?t=198228#p1016424

jhbarrantes · Sat Mar 02, 2024 11:29 am

Hi guys,
an error detected with devices using "fash" as disk: command to reset device and then run script with "run-after-reset" option doesn't see flash drive. Autocomplete doesn't work and input the name of the file doesn't work either in 7.14.

/system reset-configuration keep-users=yes run-after-reset=

If anyone confirms, I will open a support ticket.

Thanks!

optio · Sat Mar 02, 2024 11:47 am

Irony was lost when I migrated from wireless package to this wifi-qcom-ac
*) package - reduced "wireless" package size for ARM, ARM64, MIPSBE, MMIPS devices;

I'm using same device as yours, but continued to use "wireless" package and actually gain 36KiB (500KiB -> 536KiB free) after upgrading from 7.13.5 to 7.14.

infabo · Sat Mar 02, 2024 11:51 am

The gain was minimal. The default package increased ins same size as wireless package shrunk down.

t0mm13b · Sat Mar 02, 2024 12:15 pm

The gain was minimal. The default package increased ins same size as wireless package shrunk down.

Ran a wifi scan on 2.4Ghz to check the frequency and compare with between phone and laptop - chateau seized up and had to cut the power as connectivity was lost, replugged into mains again, storage went to 0 so have zero free space - have opened support ticket to find out how to clean up (what I suspect was probably a temp file in /tmp somewhere or a core dump)

urbinek · Sat Mar 02, 2024 12:35 pm

Nice work, but when Capsman and vlans will work in similar fasion as previously?

Mesquite · Sat Mar 02, 2024 1:08 pm

Moral of story, never load up a 7.X.0 version, always at least wait for 7.X.1 or 7.X.2 :-)

optio · Sat Mar 02, 2024 1:55 pm

chateau seized up and had to cut the power as connectivity was lost, replugged into mains again, storage went to 0 so have zero free space - have opened support ticket to find out how to clean up (what I suspect was probably a temp file in /tmp somewhere or a core dump)

Had similar issues with 7.13.x thats why I give up on new ac drivers and continue to use legacy, maybe your configuration is smaller and you are able to use ac on 7.13, but I doubt that as newer ROS releases arrives that you will able to continue to use it on this device unless some changes on ROS are made to offload storage (more packages).

t0mm13b · Sat Mar 02, 2024 2:15 pm

chateau seized up and had to cut the power as connectivity was lost, replugged into mains again, storage went to 0 so have zero free space - have opened support ticket to find out how to clean up (what I suspect was probably a temp file in /tmp somewhere or a core dump)
Had similar issues with 7.13.x thats why I give up on new ac drivers and continue to use legacy, maybe your configuration is smaller and you are able to use ac on 7.13, but I doubt that as newer ROS releases arrives that you will able to continue to use it on this device unless some changes on ROS are made to offload storage (more packages).

I fear, that since the introduction of the wireless package vs wifi-qcom-ac et al, implies that certain 16Mb storage devices with wireless are getting deprecated in favour of the newer drivers, and newer models.

End result is they will get left behind with a version of v7 nd not eligible for newer upgrades. They may well stop dev efforts on the wireless package completely, its going to happen soon.

Unless they do something about the wifi-qcom-ac drivers themselves which chews up more space.

Am looking at a possibility of doing a netinstall to try again from scratch.

markonen · Sat Mar 02, 2024 2:27 pm

7.14 completely disabled my WireGuard-based OOB management network.

The root cause seems to be that all wg interfaces are stuck in the main VRF even if you've specified another VRF for them.

Downgrading to 7.13.5 brought them back to the custom VRF and brought back the network.

pe1chl · Sat Mar 02, 2024 3:20 pm

I fear, that since the introduction of the wireless package vs wifi-qcom-ac et al, implies that certain 16Mb storage devices with wireless are getting deprecated in favour of the newer drivers, and newer models.

End result is they will get left behind with a version of v7 nd not eligible for newer upgrades. They may well stop dev efforts on the wireless package completely, its going to happen soon.

Unfortunately they are not even doing THAT.
The reasonable move would be to declare 7.12.1 to be a long-term version that is supplied with security updates for a year or two, so in the meantime we can replace our 16MB ARM devices.
But no, in the event that a critical security vulnerability is found in 7.12.1 those devices immediately become useless.

arainbow · Sat Mar 02, 2024 3:21 pm

On my CHR system on Vultr, after upgrading from version 7.13.5 to 7.14, the Ethernet card disappeared. This issue had never occurred with previous upgrades, so I didn't have a backup. I had to log in to the console to create a backup, then boot into another Linux CD to copy the backup out. I attempted to downgrade to 7.13.5, trying various methods to incorporate the 7.13.5 npk file, but during the downgrade, it showed that it didn't recognize the installation package. I then tried to install a fresh version of 7.14, but the Ethernet card still didn't appear. Eventually, I had no choice but to reinstall 7.13.5 and restore the configuration.Fortunately, I succeeded.

Matta · Sat Mar 02, 2024 3:34 pm

This update is full of bugs, I have to reset hAP Lite every 2 hours to reach normal speed.

How the hell did you update hAP Lite ? I'm missing few kilobytes to be able to squeeze in ROS and wirless package.

bratislav · Sat Mar 02, 2024 4:00 pm

With some obvious storage space issues and rose storage with btrfs and nfs kernel modules being a separate package, as it should be IMHO, I wonder why other pretty large file system kernel modules such as cifs, smb3, ntfs3 had to be added in the base routeros bundle making install next to impossible on some older but still supported devices...

mirolm · Sat Mar 02, 2024 4:34 pm

I can second that - sure samba and filesystem support is usefull and fun, BUT for me their place is not in the core. Whoever needs them can easily install a package and get the job done.

Package separation is not a bad thing. True it brings complexity in development. For me ROS should have the main router functionality there, and everything that is not needed for a simple router should be a package.

Core + wifi - cap
Core + routing - router
Core + vpn - ....
Core + ntp + filesystems - ...

Get a slim core that can fit in all routers and combine that with packages to enable other functionality would be the best. Maybe it is time to build core depending of the hardware it is used into - i find really strange to have a bunch of stuff in a cap hardware like hap ac2 which people usually use for simple home router and will never touch them. They just stay there and take valuable space.

radio303 · Sat Mar 02, 2024 5:48 pm

I had so much hopes that 'reduced size' in the changelo means that 7.14 will install. But no, not enough disk space, still. Any hope that the default packages will be slimmed down?

osc86 · Sat Mar 02, 2024 6:12 pm

It seems the issue is that even when the interface of the VPN is added to the VRF via ip->VRF list, the wireguard VPN interface isn't dynamically added to the VRF it was assigned when IP route assignments come up. 7.13.5 It works and behaves as expected, but in this case all wireguard interfaces so matter if they're added to a different VRF or not are dynamically assigned to the main vrf.

Confirmed, downgraded back to 7.13.5 for now. Did you file a ticket?
I hope it's limited to only wireguard interfaces.

emunt6 · Sat Mar 02, 2024 7:35 pm

Warning!
CCR2004-pcie doesn't come back after upgrade. it's crazy what You do at mikrotik, to release fw *STABLE* that bricks cloud core unit.
looks like boot-loop.

HOW to get it working back on remote location!???

This is the exact reason why Mikrotik need implement OOB (Out of Band Management - IPMI/Redfish) interface - Its subsystem that independent from main OS, where you can remotely recover/reinstall/reboot the hardware. The same as the SNMP-card in the UPS system.
"Netinstall" is not a solution for "off-site" recovery.

diamuxin · Sat Mar 02, 2024 8:15 pm

Handshake for peer did not complete after 5 seconds, retrying (try 2)
Handshake for peer did not complete after 5 seconds, retrying (try 2)
Handshake for peer did not complete after 5 seconds, retrying (try 2)

+1, the same by me

+1
is very, very annoying especially with road-warrior type wireguard connections.

npeca75 · Sat Mar 02, 2024 8:25 pm

it will be much MUCH better for MT to name this release v8
after all, wireless packages are radically changed, ROS does not fit anymore on old devices, many bugs, etc ...
anybody who work with relative stable 7.12.2, and blindly push update button, will be in big big trouble
so, please MT
move this version to v8

it does not seems right that this version have same V7 name with so many breaking changes

Znevna · Sat Mar 02, 2024 8:38 pm

v7 stable but >90% functional when?

Znevna · Sat Mar 02, 2024 9:04 pm

Handshake for peer did not complete after 5 seconds, retrying (try 2)
Handshake for peer did not complete after 5 seconds, retrying (try 2)
Handshake for peer did not complete after 5 seconds, retrying (try 2)

+1, the same by me
+1
is very, very annoying especially with road-warrior type wireguard connections.

Disable wireguard logging and stop bitching.

infabo · Sat Mar 02, 2024 9:06 pm

move this version to v8

People will still hit the upgrade button YOLO

vsn · Sat Mar 02, 2024 9:37 pm

Hello, after install on hap ac2 7.14 I have no free space. (with 7.13.1 it was about 2%) ; now, when I make some change and restart Mikrotik, the changes miss, even deleting unused FW rules, disabling resource gaphing and queue

MK just should separate some other packages which usually home users dont use (as. dot1X, PPP; MPLS and Radius)

Rox169 · Sat Mar 02, 2024 9:42 pm

it will be much MUCH better for MT to name this release v8
after all, wireless packages are radically changed, ROS does not fit anymore on old devices, many bugs, etc ...
anybody who work with relative stable 7.12.2, and blindly push update button, will be in big big trouble
so, please MT
move this version to v8

it does not seems right that this version have same V7 name with so many breaking changes

+č
I have 10 years old SXT with 7.14 and 3,7MB free

vsn · Sat Mar 02, 2024 10:41 pm

[/quote]
+č
I have 10 years old SXT with 7.14 and 3,7MB free

[/quote]

But its without package qcom-ac , which is only reason for me update to 7.13+

With netistall on different MK (cap ac) its. Also 97% disk used.

ColinSlater · Sun Mar 03, 2024 12:58 am

Can report that I've just upgraded my RB4011 (RB4011iGS+5HacQ2HnD)... everything seems to be working fine.
The upgrade process very kindly installed the WIRELESS package for me (very kindly as this is my home router and therefore, I do use the WiFi function on it).
Will report back again if I find any issues along the way.

doka · Sun Mar 03, 2024 2:33 am

expose "lo" interface
What is it good for? The lo interface?

I guess, you don't need anymore work around "absense" of loopback and create bridge "Loopback" and can assign loopback address directly on the lo interface, i.e.

NOT REQUIRED:
/interface bridge add name=Loopback
/ip address add address=x.x.x.x/32 interface=Loopback

while it will be just enough
/ip/address/add address=x.x.x.x/32 interface=lo

Rox169 · Sun Mar 03, 2024 6:15 am

Hello, after install on hap ac2 7.14 I have no free space. (with 7.13.1 it was about 2%) ; now, when I make some change and restart Mikrotik, the changes miss, even deleting unused FW rules, disabling resource gaphing and queue

MK just should separate some other packages which usually home users dont use (as. dot1X, PPP; MPLS and Radius)

Mine AC2 is OK, do netinstall....

infabo · Sun Mar 03, 2024 6:34 am

vsn runs wifi-qcom-ac on hAP ac2

BBCWatcher · Sun Mar 03, 2024 6:59 am

I've upgraded my hAP ac3 and hAP ac2 from 7.13.5 to 7.14. The hAP ac3 is fine. For the hAP ac2 I used netinstall. Free onboard flash space (with wifi-qcom-ac instead of wireless) is down to about 356 KiB (versus 7.13.5 at around 635 KiB). It was too tight before IMHO and now really too tight. I'm considering reverting the hAP ac2 to 7.13.5 since 356 KiB is so uncomfortably close to the "cliff edge."

I appreciate the RouterOS development team's work to expand the support for Wave 2 Wi-Fi to devices such as the hAP ac2. The 802.11r/k/v support is especially appreciated. However, if RouterOS is to grow then it seems vital to keep base RouterOS "skinny" (down around 10MiB) and allow less popular features (particularly those not needed for the boot process itself) to reside in secured/paired USB-attached (and eventually network-attached) storage. That'd solve the space constraint issue on 15.3/16MiB devices for years to come.

macak · Sun Mar 03, 2024 9:38 am

Updated/upgraded inplace (no netinstall) from 13.5 to 14

1. RB 450Gx4 (capsman) + OVPN Server + two Internet interfaces (just ethernet and PPPoE to Orange.pl) + config for Orange TV + VLANS (quite complcated config).
2. CAP AX (x3) (caps)

3. HAP AX2 standalone + OVPN client (max speed close to AP is around 800Mbps over air, over cable around 900Mbps)
4. HAP AC stanalone + OVPN client (I'm thinking about replace)
5. HAP AX Lite LTE + OVPN client

6. mAP 2nd lite. (acting as travel securuty router PC ->mAP -> LTE router over WiFi -> OVPN -> to server, one virtual one static WiFi).

All updates over packages menu without issues. (of course export + backup before!)

So far
OVPN much much more stable! Thanks (Gx4 is'nt ARM64, but over a day stable connection in my case! Thanks).
Other - looks very stable in my case.

Two feature requests:
1. BTH client feature to knock interface before connection.
2. Improve the registration view. Still there is no CAP where user is logged in. So You shoult think radio 12... this is CAP at garden or room.

One hardware request. :-)
1. New mAP lite with AX chipset (same size as Map2nd lite) + normal USB port to connect to the phone will be perfect as emergency/trip gateway.

Thanks
You are the best!.

jhbarrantes · Sun Mar 03, 2024 10:07 am

Indeed, joining to the wish list: mAP Lite AX: usb-c + PoE-IN + gigabit port + 2,4 wifi ax in a modern ARM architecture. And the magnet, don’t forget the magnet!

That will be an amazing swiss knife to carry on with you while traveling.

Regards!

Sun Mar 03, 2024 10:24 am

mAP AX in mAP Lite package, don't think so.
Thermal issues.

mAP package/size, maybe... that would be very sweet.

massinia · Sun Mar 03, 2024 10:48 am

For the hAP ac2 I used netinstall. Free onboard flash space (with wifi-qcom-ac instead of wireless) is down to about 356 KiB (versus 7.13.5 at around 635 KiB).

This is my hap ac2 with wifi-qcom-ac and also docker package:

hap ac2.png

How do you have 356 KiB with only ros and wifi-qcom-ac using netinstall?
Install all packages with netinstall.

t0mm13b · Sun Mar 03, 2024 11:37 am

I fear, that since the introduction of the wireless package vs wifi-qcom-ac et al, implies that certain 16Mb storage devices with wireless are getting deprecated in favour of the newer drivers, and newer models.

End result is they will get left behind with a version of v7 nd not eligible for newer upgrades. They may well stop dev efforts on the wireless package completely, its going to happen soon.
Unfortunately they are not even doing THAT.
The reasonable move would be to declare 7.12.1 to be a long-term version that is supplied with security updates for a year or two, so in the meantime we can replace our 16MB ARM devices.
But no, in the event that a critical security vulnerability is found in 7.12.1 those devices immediately become useless.

Fingers crossed that MT can opensource their code to allow for improvements - or open up the bootloader to allow for likes of openwrt etc to be easily installed on the devices. More likely until hell freezes over :)

pe1chl · Sun Mar 03, 2024 11:51 am

Fingers crossed that MT can opensource their code to allow for improvements - or open up the bootloader to allow for likes of openwrt etc to be easily installed on the devices. More likely until hell freezes over :)

I am not asking for any policy changes, only for long-term support of the 7.12.x version.

Lenry · Sun Mar 03, 2024 11:54 am

+1
is very, very annoying especially with road-warrior type wireguard connections.
Disable wireguard logging and stop bitching.

it IS disabled
now everyone has to explicitly disallow WG logging. Sorry, but I fail to see this as "improve and optimise"

Znevna · Sun Mar 03, 2024 12:49 pm

If you have to disallow it isn't disabled. Logic, right?
Same as dhcp leases info and other random crap that gets logged by default, which, wait for it, YOU CAN DISABLE (hide..).
I'd rather have logs that I can disable instead of no logs at all.
Don't be lazy.
Or bitch to MikroTik to improve the improvement and move it to 'debug' instead of 'info'.

LESHIYODESSA · Sun Mar 03, 2024 4:10 pm

What am I doing wrong? Why does an error occur with NFS.
hAP ax³ (7.14) + rose-storage-7.14-arm64

2024-3-3 16-5-38.png

2024-3-3 16-6-48.png

update Did I understand correctly that they forgot to update the documentation? The code is now like this — /disk set usb1 nfs-sharing=yes

https://help.mikrotik.com/docs/display/ ... rage-iSCSI

Amm0 · Sun Mar 03, 2024 4:36 pm

update Did I understand correctly that they forgot to update the documentation? The code is now like this — /disk set usb1 nfs-sharing=yes

Apparently, my configs with NFS got migrated to nfs-sharing=yes at some point – seem to work as I didn't notice till just now. But doc do show nfs-export=yes...

And docs and CLI's "F1 help" still don't describe the options for ROSE. And docs do not mention the "dynamic /ip/smb" entries created by smb-export=yes smb-sharing=yes in ROSE /disk settingin versions after ROSE SMB being moved to main package. In fact docs now have incorrect information re SMB:

RouterOS also supports older SMB without ROSE package - SMB with legacy protocol support.

fornuftFTW · Sun Mar 03, 2024 5:08 pm

Help, this update broke my containers. I just get "execve: No such file or directory" in the log on both of my containers when I try to start them.

Here are the relevant settings:

The containers are on a USB drive that seems to be working fine. What's the error, how can I get them working again?

splastunov · Sun Mar 03, 2024 5:50 pm

All ethernet interfaces on the CHR machine on the VDSINA hosting are missing. I checked the installation process twice, the ethernet is always lost. I installed 7.13.5, the ethernet is back.

The same problem here.
I have several xcp-ng (XEN) servers with different host OS version running multiple CHRs.
After upgrade to 7.14 CHR can not detect any network interfaces, but in list for IRQs I can see vif0-q0-rx, vif0-q0-tx.
The latest "working" version is 7.13.5.
After rolling back to 7.13.5 and restoring from a backup, the CHR starts working normally

krafg · Sun Mar 03, 2024 5:52 pm

My R11e-LTE-US keeps on boot loop. I Can't upgrade to this version.

This version creates a weird loopback interface that keeps running but LTE2 never boots up.

Downgrading to 7.13.5 problem solved.

LTE firmware is up to date on both LTE interfaces and RouterBOARD firmware keeps on 7.13.5 on all devices.

Tested on LtAP. I also have an RBM33G to do the tests.

Regards.

frank333 · Sun Mar 03, 2024 7:01 pm

log.jpeg

on rbm11 scripts with fetch still do not work, I have reverted to 7.12.1

Amm0 · Sun Mar 03, 2024 7:30 pm

Interesting...

*) lte - added "at-chat" support for Sierra Wireless EM9293 5G modem;

But it's not listed on: https://help.mikrotik.com/docs/display/ROS/Peripherals

Does the Sierra EM9293 support reading RSRQ, RSRP, etc.? Previous generations Sierra modems only support reading "RSSI" via RouterOS.

Chupaka · Sun Mar 03, 2024 7:57 pm

Re: wireguard... Why the heck it's always "try 2"? Not try 3, 4, 5... All 20 attempts are try 2

infabo · Sun Mar 03, 2024 7:58 pm

try 2 connect

zentavr · Sun Mar 03, 2024 8:10 pm

> *) x86 - fixed VLAN tagged packet transmit for igb (introduced in v7.12);
Unfortunately this had not been fixed. My VLANs at IGB and x86 not work at all :(

diamuxin · Sun Mar 03, 2024 8:37 pm

+1
is very, very annoying especially with road-warrior type wireguard connections.
Disable wireguard logging and stop bitching.

That a passive peer (without endpoint) constantly tries to perform a handshake, transmitting data to nothing, just because it has a 0.0.0.0.0/0 in the allowed address, which is what is happening. This behavior is irregular, and is a bug to be fixed.

Znevna · Sun Mar 03, 2024 8:40 pm

Take it up to the wireguard devs. It's not something for MikroTik to fix.

Sun Mar 03, 2024 8:43 pm

Wireguard behavior is not the problem.
The all of a sudden excessive logging is.
This is debug and by default it should be off.
Same with dns, ntp, dhcp... I've seen it all pass by.

jhbarrantes · Sun Mar 03, 2024 8:43 pm

mAP AX in mAP Lite package, don't think so.
Thermal issues.

mAP package/size, maybe... that would be very sweet.

Also good! I'm big fan of these two mini routers. Specially mAP (not mini version) saved me when doing netinstall froma laptop that doesn't have ethernet port. And mAP-Lite was for quite a long time my guests wifi network, and it works flawlesly.

Don't mind ot see these improvements on a mAP either, if thermal issues arise on such a small gadget, regarding mAP-Lite.

Regards!

sajt · Sun Mar 03, 2024 8:56 pm

I hope it's limited to only wireguard interfaces.

No, in my experience it affects eoip and ipip tunnels too.

diamuxin · Sun Mar 03, 2024 10:22 pm

Wireguard behavior is not the problem.
The all of a sudden excessive logging is.
This is debug and by default it should be off.
Same with dns, ntp, dhcp... I've seen it all pass by.

Exactly, I think the same.

monotsc · Sun Mar 03, 2024 10:52 pm

> *) x86 - fixed VLAN tagged packet transmit for igb (introduced in v7.12);
Unfortunately this had not been fixed. My VLANs at IGB and x86 not work at all :(

what kind of NIC you have ? my i350,i210/i211 on 7th gen intel working again after 7.12/7.13 bug

Znevna · Sun Mar 03, 2024 11:03 pm

Disable wireguard logging and stop bitching.
That a passive peer (without endpoint) constantly tries to perform a handshake, transmitting data to nothing, just because it has a 0.0.0.0.0/0 in the allowed address, which is what is happening. This behavior is irregular, and is a bug to be fixed.

Wireguard behavior is not the problem.
The all of a sudden excessive logging is.
This is debug and by default it should be off.
Same with dns, ntp, dhcp... I've seen it all pass by.
Exactly, I think the same.

You seem to be contradicting yourself. Which one is it?

Neolo · Sun Mar 03, 2024 11:11 pm

Log is flooded with SA Query timeouts. Clients have terrible experience using wifi. What is going on??
I had to edit the "Connect Priority" thing.. It will make your WiFi vulnerable to the MacStealer'-attack.
MT screwed up the WiFi totally and the network is unuseable with this "security" feature turned on (default). And left you either with an unusable network or a vulnerable network - good job MT... viewtopic.php?t=198228#p1016424

Connect Priority 0/1 does not help in any way. I set it on all APs and still see those SA timeouts in the log.

Cha0s · Sun Mar 03, 2024 11:41 pm

Wireguard behavior is not the problem.
The all of a sudden excessive logging is.
This is debug and by default it should be off.
Same with dns, ntp, dhcp... I've seen it all pass by.

Can you post an example?
I don't see any difference (besides wireguard) on my logs with v7.14.

What has been annoying to me is the inclusion in the logs of the full edit command of each and every action done via cli/winbox a few versions back (I think in 7.11?).
Especially when editing large scripts, the whole log window can get filled just with one action.

We went from vague and useless logs like this:

device changed by admin

To excessively verbose and practically still useless (who can read this without copying it to notepad - since it doesn't even fit in any screen resolution) like this:

device changed by winbox-3.40/tcp-msg(winbox):admin@x.x.x.x (
/interface set ether9 disabled=no l2mtu=1596 mtu=1500 name=ether9; /interface ethernet set [ find ] 
advertise=10M-baseT-half,10M-baseT-full,100M-baseT-half,100M-baseT-full,1G-baseT-half,1G-baseT-full 
arp=enabled arp-timeout=auto auto-negotiation=yes combo-mode=auto disabled=no fec-mode=off l2mtu=1596 
loop-protect=default loop-protect-disable-time=5m loop-protect-send-interval=5s mtu=1500 
name=ether9 rx-flow-control=off sfp-rate-select=low tx-flow-control=off; /queue interface set ether9
)

(I've added the break lines - it's even worse in the log window in a single line)

Instead of logging the relevant change only so with one glance in the logs you know who did what you get this mess that eventually no one will actually read.

The end result is the same as with the old vague logs. You don't know what the user actually did unless you know by heart every single configuration that has been done previously on the router.
Yes you get the full command run but not the actual change.
Did he change the mtu? the loop-protect? the advertise rate? You cannot know, because it includes every single option instead of only what the user actually changed at that given time.

diamuxin · Sun Mar 03, 2024 11:44 pm

You seem to be contradicting yourself. Which one is it?

I am not contradicting myself (if you had tried it you would understand). I keep insisting that it makes no sense for the passive peer without endpoint to constantly try to handshake, it's a debugging problem not a wireguard interface problem. If you don't understand it is your problem.