RouterOS version 7.17 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.17 (2025-Jan-16 10:19):

!) device-mode - after upgrade, mode "enterprise" is renamed to "advanced" and traffic-gen, partition (command "repartition"), routerboard and install-any-version features will be disabled;
!) webfig - redesigned HTML, styling and functionality;
*) 6to4 - fixed issue where 6to4 relay would not forward traffic unless destination address is set;
*) adlist - improved logging;
*) adlist - improved system stability;
*) adlist - optimized import on system with low disk space;
*) api - fixed REST API serialization of binary data;
*) arm64 - fixed for bare-metal servers to be able to access more than 2GB RAM;
*) arm64 - show CPU frequency on bare-metal installations;
*) arm64/x86 - added missing PCI id for mlx4 driver;
*) bonding - hide mlag-id property on non-compatible devices;
*) bridge - add HW offload support for active-backup bonds on 98DXxxxx, 88E6393X, 88E6191X and88E6190 switches;
*) bridge - added interface-list support for VLANs;
*) bridge - added message for inactive port reason;
*) bridge - added priority setting to manually elect primary MLAG peer;
*) bridge - correctly display PPP interfaces in VLAN menu;
*) bridge - disallow duplicate static VLAN entries;
*) bridge - disallow multicast MAC address as admin-mac;
*) bridge - enable faster HW offloading when detect-internet is disabled;
*) bridge - fixed first host table response for SNMP;
*) bridge - fixed incorrect HW offloaded port state in certain cases on MSTI add;
*) bridge - fixed missing slave flag on port in certain cases;
*) bridge - fixed MVRP registrar and applicant port options;
*) bridge - fixed port monitor with interface-lists;
*) bridge - fixed port move command;
*) bridge - fixed setting bridge MTU to L2MTU value;
*) bridge - fixed VLAN overlap check;
*) bridge - ignore disabled interfaces when calculating bridge L2MTU;
*) bridge - improved port handling;
*) bridge - improved stability;
*) bridge - prioritize MAC selection from Ethernet interfaces when using auto-mac feature;
*) bridge - re-synchronize MLAG system-id when bridge MAC changes;
*) bridge - removed support for master port config conversion (used before version 6.41);
*) bridge - update dynamic MSTI priority value when changing configuration;
*) bth - improved stability on system time change;
*) certificate - do not download CRL if there is not enough free RAM;
*) certificate - do not show not relevant values for certificate template (CLI only);
*) certificate - fixed handling of capsman-cap certificates (introduced in v7.16);
*) certificate - removed unstructured address field support;
*) chr - added Chelsio VF driver for PCIID 5803;
*) chr/arm64 - fixed kernel crypto use without crypto extensions for RPi CM4;
*) cloud - changed ddns-enabled setting from "no" to "auto" (service is enabled when BTH is enabled);
*) cloud - improved DDNS and VPN state stability;
*) console - added :range command;
*) console - added group-by property for print command;
*) console - added json.no-string-conversion to :serialize;
*) console - added lf/crlf options to :convert transform;
*) console - added more argument definitions for mac-protocol property;
*) console - added password property to "/system/ssh-exec" command;
*) console - added to/from=num option for :convert command;
*) console - allow clearing history for a specific user;
*) console - allow setting width to supout.rif output;
*) console - clear history when removing user;
*) console - disallow autocomplete hints for user without read policy;
*) console - execute :return command without error;
*) console - fixed endless loop when closing input prompt;
*) console - fixed missing arguments in wifi menu in certain cases;
*) console - force print paging when output does not fit terminal width;
*) console - improved printing output in some menus;
*) console - improved scripting system stability;
*) console - increased w60g scan-list size to 6;
*) console - print warning in CLI after enabling protected bootloader;
*) console - removed "chain" names from print parameter list and show all print parameters in "/ipv6/firewall/filter" directory;
*) console - show system-id in export for CHR;
*) console - updated copyright notice;
*) container - allow import from .tar.gz file;
*) container - do not log start, end events unless logging is enabled;
*) container - fixed user and group ID range;
*) container - improved "start-on-boot" stability;
*) container - improved container shell;
*) crypto - improve crypto speeds;
*) crypto - use hardware accelerator for GCM cipher in TLS connection on Alpine CPUs;
*) defconf - changed wireless installation from "indoor" to "any";
*) defconf - disable 5GHz secondary channel on RB4011;
*) defconf - do not add default password for CAP mode configuration on older Audience devices without a password;
*) defconf - fixed new port name recognition;
*) detnet - remove dynamic DHCP client creation;
*) device-mode - added "allowed-versions" list which are allowed to be installed without "install-any-version" mode enabled;
*) device-mode - added "basic" mode;
*) device-mode - added routerboard, install-any-version and partitions features;
*) device-mode - allow feature and mode update on x86 via power button and reboot/shutdown from AWS;
*) device-mode - fixed feature and mode update on ARM64 Hetzner;
*) device-mode - fixed feature and mode update via power-reset on MIPSBE devices;
*) device-mode - limit "/tool/ping-speed" and "/tool/flood-ping" under "traffic-gen" feature;
*) device-mode - limit device-mode update maximum allowed attempt count which can be reset only with reboot or button press;
*) device-mode - provide more precise device-mode update action printout;
*) device-mode - show all features and active restrictions with "print" command;
*) dhcp-relay - added "local-address-as-src-ip" property;
*) dhcp-server - use interface ID for NAS-Port and added interface name to NAS-Port-ID attribute in RADIUS requests;
*) dhcp-server - use single RADIUS accounting session for IPv4 and IPv6 when dual stack is used;
*) dhcpv4-client - correctly handle adding/setting emtpy dhcp-options;
*) dhcpv4-client - fixed crash when releasing disabled DHCP client;
*) dhcpv4-client - respect Renewal-Time (58) and Rebinding-Time (59) options;
*) dhcpv4-server - do not remove options set config when DHCP network is changed;
*) dhcpv4-server - properly detect DHCP server address when underlying interface has multiple IP addresses configured;
*) dhcpv4-server/relay - added additional error messages for DHCP servers and relays;
*) dhcpv4/v6-server - added address-list parameter to which address will be added if the lease is bound;
*) dhcpv6-client - added prefix-address-list parameter;
*) dhcpv6-client - improved system stability when DHCPv6 client is enabled on non-existing interface;
*) dhcpv6-client - log message when response with invalid transaction-id received;
*) dhcpv6-client/server - added support for DHCPv6 reconfigure messages;
*) dhcpv6-server - added IPv6 address delegation support;
*) dhcpv6-server - do not require "prefix-pool" to be specified;
*) dhcpv6-server - fixed DHCPv6 server "address-pool" property showing in command line as "unknown" when real value is "static-only";
*) dhcpv6-server - improved system stability when removing actively used DHCPv6 server;
*) dhcpv6-server - include all existing prefixes (with lifetime 0) in renew reply and new prefix if RADIUS returns different prefix;
*) dhcpv6-server - properly display "static-pool" value in server print output for "prefix-pool" argument;
*) discovery - added support for LLDP DCBX;
*) discovery - use LLDP description field to populate platform, version and board-name;
*) disk - added "type=file" for file-based block devices, useful for using file as a swap, or when having file-based filesystem images (CLI only);
*) disk - added btrfs filesystems list (CLI only);
*) disk - added mount-read-only and mount-filesystem options to allow read-only mounts and prevent mounting device at all (CLI only);
*) disk - added sshfs client to "/disk" menu (CLI only);
*) disk - added support for SWAP, currently allowed on any block device with "set x swap=yes" when container package is installed (CLI only);
*) disk - allow to configure global and per disk mountpoint template - [slot],[model],[serial],[fw-version],[fs-label],[fs-uuid],[fs] variables supported;
*) disk - auto mount iso and squashfs images;
*) disk - fixed managing and cleaning up mount points;
*) disk - fixed raid role auto selection for up to 64 drives;
*) disk - improve slot naming and improvements for visualizing complex hardware topology;
*) disk - improve test to report zero byte iops;
*) disk - improved system stability;
*) disk - read/show exfat filesystem label;
*) disk - recognize virtual sd* interfaces;
*) disk - remove 32 character slot name limit;
*) disk - save raid superblock and raid bitmap superblock on member devices in 1.2 format/location;
*) disk - show detailed mountpoint users when unable to unmount;
*) disk - show usage as percentage (CLI only);
*) disk - try all NFS versions (4.2,4.1,4.0,3,2) when mounting NFS in that order;
*) disk,nvme - show nvme namespaces if configured more than one on a nvme drive;
*) dns - added option to create named DNS servers that can be used as forward-to servers;
*) dns - do not look up local cache when executing ":resolve" command with specified "server" parameter (introduced in v7.16);
*) dns - DoH whitelist support for adlist using static FWD entries;
*) dns - refactored DNS service internal processes;
*) dns - whitelist support for adlist using static FWD entries;
*) ethernet - improved interface stability for RB4011 devices;
*) ethernet - improved linking after reboot for hAP ax lite devices ("/system routerboard upgrade" required);
*) ethernet - improved stability after reboot for Chateau PRO ax;
*) ethernet - improved system stability for CCR2004-1G-2XS-PCIe device;
*) ethernet - log warning only about excessive broadcast (do not include multicast) and reduced log count;
*) fetch - fixed certificate check when provided hostname is IP address;
*) fetch - fixed large file (over 4GB) fetch in HTTP/HTTPS mode;
*) file - correctly identify mounted disks;
*) file - do not needlessly scan large filesystems, could prevent unmounting;
*) file - improved handling of changes to the file system;
*) file - improved service stability when accessing files list from other system services;
*) file - support files over 4GB size;
*) file - update file size before trying to request content;
*) firewall - added none-dynamic and none-static arguments for IPv6 address-list-timout settings;
*) firewall - added support for random external port allocation;
*) firewall - added warning log for TCP SYN flood;
*) firewall - fixed "dst-limit" and "limit" mathers when using zero value for burst argument;
*) firewall - improved matching from deeply nested interface-lists;
*) firewall - removed default mangle passthrough=yes configuration from export;
*) ftp - added VRF support;
*) gps - changed default GPS antenna setting for LtAP mini with internal LTE/GPS combo antenna;
*) graphing - fixed graphing rule removal;
*) graphing - fixed queue graph storing on disk;
*) health - added cpu-overtemp-check on ARM, ARM64 devices (CLI only);
*) health - changed PSU state from "no-ac" to "no-input";
*) health - hide settings in CLI if there is nothing to show;
*) health - removed board-temperature on RB5009UPr+S+IN device;
*) igmp-proxy - refactored IGMP querier;
*) ike2 - improved performance by balancing multicore CPU usage for key exchange calculation also for initiator;
*) iot - added additional debug for LoRa logging;
*) iot - added an option to print out LoRa traffic in CLI (not GUI-only option anymore);
*) iot - added new LoRa traffic FCnt packet counter parameter;
*) iot - added support for USB Bluetooth dongles (LE 4.0+) which enables Bluetooth functionality;
*) iot - bluetooth peripheral device menu now displays correct iBeacon major/minor values;
*) iot - fixed duplicate LoRa payloads in the traffic tab;
*) iot - fixed incorrect LoRa joineui filter export behavior;
*) iot - fixed LoRa behavior, where join eui or dev eui could be incorrectly converted during forwarding;
*) iot - improved system stability for LoRa;
*) iot - improvements to LoRa device's stats tab;
*) iot - LoRa LNS improvement;
*) iot - LoRa traffic tab RSSI now shows proper values for ARM architecture;
*) iot - modbus rework which improves Tx Rx switching behavior;
*) iot - mqtt improvement to support large payloads and gracefully discard payloads above size limit;
*) iot - removed crc-disabled and crc-error options from the LoRa forwarding;
*) iot - removed LoRa pause traffic option/setting;
*) iot - removed some LoRa radio related parameters (e.g. RSSI-OFF and Tx-enabled) that were not meant to be changed;
*) ippool - removed maximum "63 bit" prefix length limitation;
*) ipsec - ike2 improved process for policies;
*) ipv6 - added comment property to "/ipv6/nd/prefix" menu;
*) ipv6 - added IPv6 settings related to stale IPv6 neighbor cleanup;
*) ipv6 - added support for manual link-local address configuration;
*) isis - do not disable fast-path when isis is enabled on an interface;
*) isis - fixed console flags;
*) isis - fixed invalid L2 LSP type;
*) isis - make it work when MTU is larger than 1500;
*) isis - update interface MAC address on change (caused neighbor to stuck in init state);
*) kid-control - use time format according to ISO standard;
*) l3hw - improved system stability;
*) l3hw - rate limit error logging;
*) leds - fixed issue where interface LEDs might not properly disable in some cases;
*) log - added basic validation for "disk-file-name" property;
*) log - added hostname support to remote logging action;
*) log - added regex parameter for log filtering in rules;
*) log - fixed e-mail logging (introduced in v7.16);
*) log - use time format according to ISO standard;
*) lte - added option to check/install modem firmware from early-access/testing channel (CLI only);
*) lte - added provider specific firmware update (FOTA) for Cosmote GR networks on Chateau 5G;
*) lte - disabled ims service for Chateau 5G on operator "3 AT" network (PLMN ID 23205);
*) lte - drop operator selection support for R11e-4G modem as it is unreliable;
*) lte - fixed "default-name" property in export when multiple LTE interfaces are used;
*) lte - fixed "lte monitor" signal reporting for RG520F-EU modem when connected to 5G SA network;
*) lte - fixed "operator" setting for EC200A-EU modem;
*) lte - fixed long "PLMN search in progress" for SXT 3-7;
*) lte - fixed LTE band setting for SXT LTE 3-7;
*) lte - fixed roaming barring (allow-roaming=no) for EC200A-EU modem;
*) lte - fixed signal info reporting for FG621-EA modem in UMTS network;
*) lte - fixed SMS sender parsing;
*) lte - improved modem FW upgrade for Chateau 5G;
*) lte - improved R11eL-EC200A-EU modem firmware upgrade procedure;
*) lte - improved recovery after unexpected modem reboot for Chateau's 5G and 5G R16 series devices;
*) lte - improvements to modem "firmware-upgrade" command;
*) lte - MBIM increased assignable APN profile count up to 8 then modem firmware allows it;
*) lte - modem firmware update (FOTA), added support to install provider specific version;
*) lte - removed trailing "F" symbol from uicc;
*) lte - set "sms-read=no" and "sms-protocol=auto" as default values;
*) lte - set IPv6 address reporting format in modem init for AT modems and MBIM modems with AT channel;
*) mac-server - allow MAC-Telnet access through any bridged port when bridge interface is allowed;
*) mac-telnet - use ASCII DEL as erase/backspace char instead of BS (fixes mac-telnet backspace for WinBox4);
*) macvlan - improved error when trying to create new interface on already busy parent interface;
*) macvlan - updated driver;
*) modem - KNOT BG77 modem, improved handling of modem unexpected restarts;
*) mpls - added fast-path support for VPLS;
*) mpls - added MPLS mangle support;
*) mpls - added support for "ICMP Fragmentation needed";
*) mpls - do no drop LDP peering session on PW deactivation;
*) mpls - do not reconnect VPLS on name or comment changes;
*) netinstall - removed unused "Get key" button;
*) netinstall - save and restore device-mode configuration on format;
*) netinstall-cli - added "-o" option to install devices only once per netinstall run;
*) netinstall-cli - fixed x86 detection;
*) netwatch - added "ignore-initial-up" and "ignore-initial-down" properties;
*) netwatch - fixed multiple variables;
*) netwatch - fixed probe toggle when adding a comment;
*) ospf - fixed memory corruption;
*) ospf - improved stability on configuration update;
*) ovpn - added VRF support to OVPN server (server menu now supports multiple entries and previous server configuration is automatically imported);
*) ovpn - improved system stability;
*) ovpn-client - added tls-crypt, tls-crypt-v2 support;
*) ovpn-server - added "user-auth-method" property and allow mschap2 for RADIUS authentication;
*) pimsm - improved system stability after interface disable;
*) poe-out - added low-voltage-too-low status;
*) poe-out - improved PoE-out configuration handling when doing reset-configuration command;
*) poe-out - upgraded firmware for CRS354-48P-4S+2Q+ device (the update will cause brief power interruption to PoE-out interfaces);
*) poe-out - upgraded firmware for PSE (BT) controlled boards (the update will cause brief power interruption to PoE-out interfaces);
*) port - display a warning when using invalid log-file with the "remote-access" feature;
*) port - more detailed print command output, include in "USED-BY" property channel number(s);
*) ppp - add routes in matching VRF;
*) ppp - added support for bridge-port-pvid configuration via ppp profile;
*) ppp - added support for bridge-port-trusted configuration via ppp profile;
*) ppp - do not print local/remote pool related errors in log when configuration does not require pool usage;
*) ppp - fixed typos in log message;
*) ppp - reuse link-local IPv6 address for static bindings when possible;
*) ppp - set APN/PDN type "IPv4/v6" according assigned PPP profile protocol setting;
*) pppoe - added support for PPPoE server over 802.1Q VLANs;
*) profiler - classify ppp processing;
*) profiler - improved process classification;
*) profiler - renamed radv process to radvd;
*) ptp - added dynamic switch ACL rules in order to trap PTP packets to CPU instead of forwarding;
*) ptp - added option to configure L2 transport with forwardable and non-forwardable MAC destination;
*) ptp - added PTP support for CRS320-8P-8B-4S+ and CRS326-4C+20G+2Q+ devices;
*) ptp - display warning when none of the PTP ports has a link;
*) ptp - fixed DSCP values for IPv4 packets;
*) ptp - fixed packet receive with enabled igmp-snooping;
*) ptp - fixed packet tx/rx when enabling PTP on 1/2.5/100Gbps links for 98CX8410, 98DX8525, 98DX4310 switches (introduced in v7.16);
*) ptp - fixed synchronization on QSFP28 interfaces;
*) ptp - make PTP process more stable and deterministic when applying configuration;
*) ptp - restrict configuring g8275 profile with IPv4 transport;
*) qos-hw - allow to disable/enable profiles, disabled or removed profile gets replaced with the default;
*) qos-hw - enabling PFC on port also requires setting egress-rate-queueN;
*) qos-hw - fixed export when changing default Tx Manager;
*) qos-hw - fixed incorrect port byte-use counter;
*) qos-hw - improved PFC behavior;
*) qos-hw - improved system stability when enabling QoS;
*) qos-hw - improved WRED and ECN behavior;
*) qos-hw - rename pfcN-pause and pfcN-resume to pfcN-pause-threshold and pfcN-resume-threshold;
*) qos-hw - reworked PCP and DSCP mapping (now supports single, multiple and range values, previous configuration with minimal value mapping is converted to a single value);
*) qos-hw - switch-cpu port trust settings are forced to "keep";
*) queue - improved system stability when too many simple queues are added;
*) quickset - added "LTE AP" quickset profile with one wifi interface;
*) rip - improved stability when changing metric;
*) romon - added dynamic switch rules on devices supporting it when enabling the service;
*) romon - added interface-list support;
*) romon - send uptime in discovery;
*) rose-storage - allow to set iscsi-iqn only when type=iscsi and allow nvme-tcp-name only when type=nvme-tcp;
*) rose-storage - do not allow to format exported disks;
*) rose-storage - enable autocomplete for local-path property in "/file/sync" menu;
*) rose-storage - enable more threads for faster RAID sync;
*) rose-storage - ensure unique nvme-tcp-names for nvme-tcp clients;
*) rose-storage - improved error messages;
*) rose-storage - improved system stability;
*) rose-storage,raid - improved stability of degraded arrays on startup;
*) rose-storage,raid - store superblock in 1.2 format, show raid super block info when detected to help with reassembling arrays;
*) route - fixed discourse attribute print;
*) route - fixed minor typo in failure message;
*) route - fixed possible issue with inactive routes after reboot (introduced in v7.16);
*) route - improved stability;
*) route - improved stability with static route configuration;
*) route - increased interface name length limit in log messages;
*) route - removed possibility for IPv6 routes to specify interface in the dst-address;
*) routerboot - fixed boot MAC for devices with Alpine CPU ("/system routerboard upgrade" required);
*) routerboot - fixed boot MAC for MIPSBE CRS3xx and CRS5xx switches ("/system routerboard upgrade" required);
*) routerboot - improved stability for IPQ8072 and IPQ6010 when flash-boot is used ("/system routerboard upgrade" required);
*) routing-filter - fixed subtract and add for numerical values (+x, -x);
*) rsync - fixed when used over ssh and spaces in directory names;
*) sfp - fixed 1Gbps supported rate for RB960 and RB962 devices;
*) sfp - fixed linking with 1Gbps optical modules with "combo-mode=sfp" configuration for CRS312 device;
*) sfp - improved initialization and linking for some SFP modules;
*) sfp - improved initialization for certain SFP modules on CRS309 and CRS317 devices ("/system routerboard upgrade" required);
*) sfp - improved power control configuration for QSFP optical modules according to the EEPROM field;
*) sfp - improved SFP auto-negotiation for L22, L23 devices;
*) sfp - improved SFP28, QSFP28 interface stability using DAC cable for CRS520 switch;
*) smb - stability improvements for client/server;
*) snmp - added wifi fields to MIKROTIK-MIB;
*) socks - fixed comment property for access configuration;
*) ssh - added option to configure SSH ciphers (replaced allow-none-crypto parameter);
*) ssh - do not regenerate host key after update from RouterOS version older than 7.9;
*) ssh - improved logging;
*) ssh - improved speed;
*) ssh - prefer GCM ciphers for arm64 and x86 devices when ciphers=auto;
*) ssl/tls - improved performance;
*) sstp - added pfs=required option to allow only ECDHE during TLS handshake;
*) storage - preserve permissions,owners,attributes when syncing under "/file/sync";
*) storage,rsync - fixed to work with clients passing "-a" option;
*) supout - added BGP advertisements section;
*) supout - added device-mode section;
*) supout - do not create autosupout.rif for second time after system reboot;
*) supout - print non BGP and OSFP routes if route list is too large;
*) supout - reduce minimal RAM required for export to be included;
*) supout - use separate LTE section;
*) switch - added "all" argument for "new-dst-ports" switch rule property for CRS3xx, CRS5xx, CCR2116 and CCR2216 devices;
*) switch - added IPv6 flow label matching in switch rules for CRS3xx, CRS5xx, CCR2116 and CCR2216 devices;
*) switch - allow bond interfaces in switch rules for CRS3xx, CRS5xx, CCR2116 and CCR2216 devices;
*) switch - allow matching network bitmask for IPv4 and IPv6 dst/src-address properties in switch rule;
*) switch - disallow switch-cpu in "ports" and "new-dst-ports" rule properties for CRS3xx, CRS5xx, CCR2116, CCR2216 and RB5009 devices;
*) switch - fixed a potential issue with packet corruption caused by incorrect switch initialization on CRS3xx/5xx devices;
*) switch - fixed L2MTU for 25Gbps ports;
*) switch - fixed RSPAN error message when using mirror-target=cpu;
*) switch - fixed rule disable in certain cases for 98DX224S, 98DX226S, and 98DX3236 switch chips;
*) switch - fixed storm-rate accuracy on 98DX224S, 98DX226S, and 98DX3236 switch chips;
*) switch - force "mac-protocol" when matching IPv4 or IPv6 specific properties;
*) switch - improved CPU performance for CRS328-24P-4S+ switch;
*) switch - improved system stability for RB5009 and CCR2004-16G-2S+ devices;
*) switch - make switch rule "ports" property not required and unsettable (allows matching packets on all switch ports);
*) switch - updated dynamic switch rules when using HW bridge with IGMP snooping (224.0.0.0/24 and ff02::/16 destination addresses are forwarded and copied to CPU);
*) system - improved IPv6 maximum routing table size based on total memory;
*) system - make ICMP error source address selection configurable (icmp-errors-use-inbound-interface-address parameter in ip settings);
*) system - make TCP timestamp handling configurable (tcp-timestamps parameter in ip settings);
*) system - moved "/system/upgrade" to "/system/package/local-update";
*) tftp - improved stability;
*) upnp - rename service description file from gateway_description.xml back to gateway.xml;
*) user-manager - improved stability;
*) vpls - added support for bridge-pvid configuration;
*) vrf - fixed packet handling with enabled queues;
*) vxlan - fixed issue causing to loose IPv6 VTEP address setting;
*) webfig - added search option for settings;
*) webfig - allow download from file details;
*) webfig - allow style.css and script.js in branding packages;
*) webfig - fixed uploading files with Windows style newlines;
*) webfig - hide inherited wifi password;
*) webfig - improved keyboard navigation;
*) webfig - improved screen reader support;
*) webfig - improved system stability when used over many simultaneous sessions;
*) webfig - redirect "/help/license.html" to "/license.txt" for backwards compatibility;
*) webfig - reduce flickering when table is sorted by column with duplicate values;
*) webfig - Skin Designer moved to centralized page;
*) webfig - status page is deprecated, old status page config will work, but can't be updated or created;
*) webfig - support unicode strings;
*) wifi - add information to each interface, showing which CAPsMAN manages it or which CAP hosts it when applicable;
*) wifi - added a debug log entry when switching channel;
*) wifi - added ability to set security.owe-transition-interface to "auto";
*) wifi - added access-list stats (CLI only);
*) wifi - added configuration.installation property to limit use of indoor-only channels;
*) wifi - added debug log messages on station authentication mismatch;
*) wifi - added extra info to CAPsMAN about message;
*) wifi - added last-activity property in registration table;
*) wifi - added multi-passphrase (PPSK) support (CLI only);
*) wifi - added option to reset MAC address (CLI only);
*) wifi - added station-roaming support;
*) wifi - allow IPv6 LL address in caps-man-addresses;
*) wifi - disabled 802.11h on 2.4GHz station;
*) wifi - fixed "disabled" property in certain cases;
*) wifi - fixed failure to resume operation after DFS non-occupancy period has elapsed;
*) wifi - fixed failure with "auto" peer update on the OWE interface;
*) wifi - fixed occasional failure to bring up management frame protection and channel switch capabilities;
*) wifi - fixed the "no available channels" message still being displayed after a setting change has made some channels available;
*) wifi - improved FT roaming with WPA3 for some Apple devices;
*) wifi - indicate radios' ability to perform a channel switch in their "hw-caps" attribute;
*) wifi - indicate which channels are subject to DFS, or are indoor-only in output of "monitor" command;
*) wifi - re-word the "SA Query timeout" log message to "not responding";
*) wifi - show authentication type and wireless standard used by each client in registration table;
*) wifi - show regulatory limits on maximum bandwidth in output of radio/reg-info command;
*) wifi - when operating in station mode, log more information when AP switches to an unsupported channel;
*) wifi-qcom - added Superchannel country profile;
*) wifi-qcom - updated regulatory info for Ukraine, Australia and United States;
*) wifi-qcom-ac - allow use of channel 144 under "Japan" regulatory domain;
*) wifi-qcom-ac - fix possible conflict between radio and USB initialization on hAP ac2;
*) wifi-qcom-ac - improved CPU load balancing and system stability;
*) winbox - added "Copy to Access List" option under "WiFi/Registration" menu;
*) winbox - added "Max Entries" and "Total Entries" properties under "IP/Firewall/Connections/Tracking" menu;
*) winbox - added "Scan" and "Test Disks" features under "System/Disks" menu;
*) winbox - added Enable/Disable buttons under "Tools/Graphing" menus;
*) winbox - added MAC address support for "Group" property under "Bridge/MDB" menu;
*) winbox - added missing "bus" option for compatible devices under "System/RouterBOARD/USB Power Reset" menu;
*) winbox - added missing properties under "IP/Neighbors" menu;
*) winbox - allow to edit Ethernet MAC address;
*) winbox - clear "Value" field when unset under "IP/DNS/Static" menu;
*) winbox - fixed duplicate timezone names;
*) winbox - fixed typo in "System/Reset Configuration" menu;
*) winbox - hide LCD menu for devices without display;
*) winbox - hide LTE "External Antenna" menu for devices without switchable antenna option;
*) winbox - improved stability;
*) winbox - minimal required version is v3.41;
*) winbox - refresh values under "Bridge/VLANs/MVRP Attributes" menu;
*) winbox - renamed and moved "System/Auto Upgrade" to "System/Packages" menu;
*) winbox - renamed wrong invalid interface flag to inactive;
*) winbox - show "FEC" property on status tab for interfaces that use it;
*) winbox - show MLAG settings for CRS326-4C+20G+2Q+ device;
*) winbox - updated properties and behavior under "Switch/QoS" menu;
*) wireguard - do not initiate handshake when peer is configured as responder;
*) wireless - added option to reset MAC address (CLI only);
*) wireless - added vlan-id to registration-table;
*) wireless - allow to set Canada2 country profile when locked with US lock package for CubeG device;
*) wireless - enable all chains by default for RB911 and RB922 series devices;
*) wireless - fixed antenna gain for SXT5ac device;
*) wireless - preserve configured country while using setup-repeater, added "country" argument (CLI only);
*) x86 - Realtek r8169 updated driver;
*) zerotier - added debug logging;
*) zerotier - do not show default settings in export;
*) zerotier - upgraded to version 1.14.0;

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.

Finally! With important and great changes to "wifi" and many other areas. Keep up the great work!

"Wireless" is fine with 7.17, but "wifi-qcom-ac" is crap, unfortunately. I have had long time open memory leak ticket SUP-147911 for hAP ac^2. This ticket has been closed without solution - but it is bullet proof the leak is related to "wifi-qcom-ac", because "wireless" is fine and stable. There is no any willingness on Mikrotik side to do any investigation, only short message - it is old HW. But this old HW IPQ-4019 with exact same amount of RAM memory (256MB) and ROM memory (16MB) is used in Chateau 5G R16. There was visible decrease of RAM free memory 10MB/day starting with 150MB to OOP after roughly 14-21 days - kernel panic memory.

Re: v7.17rc [testing] is released!
Post by CGGXANNX » Thu Jan 16, 2025 12:03 pm

Well it may goes out of memory with SMB, but if wifi-qcom-ac really takes a large chunk of RAM, then OOM might also happen if you run a container (that worked fine with wireless), or if you use adlist with huge lists, etc... If they disable and hide SMB, then should they do that with container and adlist too?

Currently you have to explicitly remove wireless and install wifi-qcom-ac. It is assumed that you read the doc before doing that, and from now on, the doc has the warning about the RAM usage. If your router suffers from OOM, your first thought now would be to revert back to wireless.

I just discovered one bug. On Upgrade the timezone gets unset. It is now UTC instead of Europe/Vienna. "/export" is missing this line which was there in 7.16.2:
edit: seems like this line from export is added or removed by the Cloud feature. After a reboot for firmware upgrade I saw the following log entry and suddenly "/system clock set time-zone-name=Europe/Vienna" was there again.
Sry, not a bug.

"v7 stable"

NOT STABLE.
viewtopic.php?t=198736

"Wireless" is fine with 7.17, but "wifi-qcom-ac" is crap, unfortunately. I have had long time open memory leak ticket SUP-147911 for hAP ac^2. This ticket has been closed without solution - but it is bullet proof the leak is related to "wifi-qcom-ac", because "wireless" is fine and stable. There is no any willingness on Mikrotik side to do any investigation, only short message - it is old HW. But this old HW IPQ-4019 with exact same amount of RAM memory (256MB) and ROM memory (16MB) is used in Chateau 5G R16. There was visible decrease of RAM free memory 10MB/day starting with 150MB to OOP after roughly 14-21 days - kernel panic memory.

This is most probably a configuration related issue. I have cap ac with only 128MB system memory running wifi-qcom-ac and it reached quite 4 weeks uptime on 7.16.2 before I upgraded it to 7.17 today. It reported ~28mb of free memory before I upgraded the system.

> *) bridge - added interface-list support for VLANs;

What does this mean?

Is possible now to add interface-list as tagged or untagged interface.

NOT STABLE.
In general, the problem of LOST SIGNAL has not been completely solved, and it is strange that Microtic don't pay due attention to this.

Seems that you have not read previous post about the same.
Stable enough to release.
Any code out there have bugs. Some more, some less. There are no perfect software.

Also going from RC to Stable will make more user try the image and more error will be found and fixed.
I do not install a 0 version in production.

"Wireless" is fine with 7.17, but "wifi-qcom-ac" is crap, unfortunately. I have had long time open memory leak ticket SUP-147911 for hAP ac^2. This ticket has been closed without solution - but it is bullet proof the leak is related to "wifi-qcom-ac", because "wireless" is fine and stable. There is no any willingness on Mikrotik side to do any investigation, only short message - it is old HW. But this old HW IPQ-4019 with exact same amount of RAM memory (256MB) and ROM memory (16MB) is used in Chateau 5G R16. There was visible decrease of RAM free memory 10MB/day starting with 150MB to OOP after roughly 14-21 days - kernel panic memory.

Re: v7.17rc [testing] is released!
Post by CGGXANNX » Thu Jan 16, 2025 12:03 pm

Well it may goes out of memory with SMB, but if wifi-qcom-ac really takes a large chunk of RAM, then OOM might also happen if you run a container (that worked fine with wireless), or if you use adlist with huge lists, etc... If they disable and hide SMB, then should they do that with container and adlist too?

Currently you have to explicitly remove wireless and install wifi-qcom-ac. It is assumed that you read the doc before doing that, and from now on, the doc has the warning about the RAM usage. If your router suffers from OOM, your first thought now would be to revert back to wireless.

I have same problem with cap-ac (simple AP mode), SUP-160401 .

NOT STABLE.
...

STABLE != free of bugs
As far as I understand, during beta ( eh 7.18 betaX); Mikrotik "Adds" new code ( fixes for long standing bugs, new features, porting from routeros 6....)
once in RC, they only fix bug in the code added during the betas.
-> if you don't see a a fix for an issue appearing in the changelog of the beta, there is little chance to see in the changelog of the RC.

Is possible now to add interface-list as tagged or untagged interface.

Oh, that's pretty good.

Super-stable 7.17 is unable to install on RB450Gx4 450Gx4 has 512 MB storage space and only 25% of it is used. What is going on??? Other devices with 16 MB storage updated without problems...

P. S. It seems to be an overlooked problem from rc stage -> viewtopic.php?p=1119444

Here my update on the "free-memory" topic for those interested and also managing 16MB devices. Before/after of 2 devices I just upgraded. td;dr: free space decreased.
and

We are speaking about RAM issue, not ROM. ROM has been solved roughly in 7.15, what I remember.

Here my update on the "free-memory" topic for those interested and also managing 16MB devices. Before/after of 2 devices I just upgraded. td;dr: free space decreased.

Code: Select all

[user@router] > /system/resource/print 
                  version: 7.16.2 (stable)
           free-hdd-space: 556.0KiB
          total-hdd-space: 16.0MiB
               board-name: D53G-5HacD2HnD
                 platform: MikroTik

[user@router] > /system/resource/print        
                  version: 7.17 (stable)         
           free-hdd-space: 272.0KiB           
          total-hdd-space: 16.0MiB       
               board-name: D53G-5HacD2HnD     
                 platform: MikroTik

and

Code: Select all

[user@cap] > /system/resource/print 
                  version: 7.16.2 (stable)
           free-hdd-space: 760.0KiB
          total-hdd-space: 16.0MiB
               board-name: cAP ac
                 platform: MikroTik

[user@cap] > /system/resource/print       
                  version: 7.17 (stable)                   
           free-hdd-space: 480.0KiB           
          total-hdd-space: 16.0MiB                   
               board-name: cAP ac             
                 platform: MikroTik

@Edpa
1. *) bridge - added interface-list support for VLANs;

Does this mean we can now list the bridge as an interface list member and this will include all vlans attached to the bridge?

2. *) bridge - enable faster HW offloading when detect-internet is disabled;

Will faster HW offloading also occur when detect-internet is set to NONE? ( or only disabled? )

Well, what kind of traffic you have? IPv4+IPv6? Or only IPv4? What amount of traffic? 100GB/day?

Regarding "configuration issue", what is wrong on this?
Rest is exactly the same for "wireless.apk", which is without any observable memory leak.

"Wireless" is fine with 7.17, but "wifi-qcom-ac" is crap, unfortunately. I have had long time open memory leak ticket SUP-147911 for hAP ac^2. This ticket has been closed without solution - but it is bullet proof the leak is related to "wifi-qcom-ac", because "wireless" is fine and stable. There is no any willingness on Mikrotik side to do any investigation, only short message - it is old HW. But this old HW IPQ-4019 with exact same amount of RAM memory (256MB) and ROM memory (16MB) is used in Chateau 5G R16. There was visible decrease of RAM free memory 10MB/day starting with 150MB to OOP after roughly 14-21 days - kernel panic memory.

This is most probably a configuration related issue. I have cap ac with only 128MB system memory running wifi-qcom-ac and it reached quite 4 weeks uptime on 7.16.2 before I upgraded it to 7.17 today. It reported ~28mb of free memory before I upgraded the system.

@anav

1. You can use interface-list for "tagged", "untagged" properties under the /interface/bridge/vlan menu.
https://help.mikrotik.com/docs/spaces/R ... rfacelists

2. /interface/detect-internet/set detect-interface-list=none

Dude client is failing to update as well

indeed, dude client fails to upgrade

"Wireless" is fine with 7.17, but "wifi-qcom-ac" is crap, unfortunately. I have had long time open memory leak ticket SUP-147911 for hAP ac^2. This ticket has been closed without solution - but it is bullet proof the leak is related to "wifi-qcom-ac", because "wireless" is fine and stable. There is no any willingness on Mikrotik side to do any investigation, only short message - it is old HW. But this old HW IPQ-4019 with exact same amount of RAM memory (256MB) and ROM memory (16MB) is used in Chateau 5G R16. There was visible decrease of RAM free memory 10MB/day starting with 150MB to OOP after roughly 14-21 days - kernel panic memory.

Re: v7.17rc [testing] is released!
Post by CGGXANNX » Thu Jan 16, 2025 12:03 pm

Well it may goes out of memory with SMB, but if wifi-qcom-ac really takes a large chunk of RAM, then OOM might also happen if you run a container (that worked fine with wireless), or if you use adlist with huge lists, etc... If they disable and hide SMB, then should they do that with container and adlist too?

Currently you have to explicitly remove wireless and install wifi-qcom-ac. It is assumed that you read the doc before doing that, and from now on, the doc has the warning about the RAM usage. If your router suffers from OOM, your first thought now would be to revert back to wireless.

I'm surprised they managed to make the propietary QCOM drivers run on a board with 128MB of RAM, back then when I had the ac2 it OOM'd even on OpenWrt running the "small buffers" ath10k driver.

Have a small bug. On my CCR1009, when I right click Interfaces --> Interface --> any interface --> Detail Mode in winbox3.41 just closed.
https://imgur.com/a/Ompf5pA

We are speaking about RAM issue, not ROM. ROM has been solved roughly in 7.15, what I remember.

Thank you for clarifying, Sit75. My earlier post wasn’t intended as a direct response to the RAM issue you mentioned. I’ve been monitoring free memory on RouterOS since version 7.13, and my recent observation of approximately 280KB less free space after upgrading was meant as a general heads-up for the community.

Devices with limited free memory - say, around 200KB on 7.16 - could potentially encounter issues when moving to 7.17. Hopefully, this additional context will help others keep an eye on their device disk space during upgrades.

The Dude upgrade issue acknowledged, we are working on it.

Does this also fix NPT? It is broken in 7.16. I don't see it changelog

MikroTik RB450Gx4 --> 7.16.2 --> 7.17 upgrade failed, free 5 kB of kernel disk space mikrotik

The Dude upgrade issue acknowledged, we are working on it.

Workaround for now is to download 7.17 installer and run it manually. This way update succeeds and client is able to connect to 7.17 Dude server.

For any1 who upgraded to 7.17 pls check if it is still possible to downgrade to 7.14.3 after? Or it is now marked as not "allowed-versions" or whatever device mode forbids

For any1 who upgraded to 7.17 pls check if it is still possible to downgrade to 7.14.3 after? Or it is now marked as not "allowed-versions" or whatever device mode forbids

It should be possible to downgrade to 7.14.3 if I read it right:

Upgrade from 7.16.2 to 7.17 fails on a CCR2004-1G-12S+2XS. ~35MB of flash storage and ~3.8GB RAM available currently. Tried the upgrade multiple times.
Edit: tried to do the update on a second CCR2004-1G-12S+2XS which has a different configuration, got the exact same error.

For any1 who upgraded to 7.17 pls check if it is still possible to downgrade to 7.14.3 after? Or it is now marked as not "allowed-versions" or whatever device mode forbids

It should be possible to downgrade to 7.14.3 if I read it right:

Code: Select all

/system/device-mode/print 
     mode: advanced     
     allowed-versions: 7.13+,6.49.8+
     ...

Thx good man

Dude CHR installs might lose other disk if configured with multiple disks. Made a ticket to support about this as well.

It is probably wise to wait for 7.17.1

hi, neighbors is broken for winbox v3.41 with de last update (7.17)
with winbox v4 is working fine

How do you go about rebranding Webfig?

If you use an old rebranding.dpk it doesn't work. Do I need to regenerate it or do you still have to work on it?

The login page appears customized after loading the branding package but if I enter the credentials while clicking log in it adds /? instead of /webfig after the router address in the address bar and the login fails

dude client upgrade seems fixed !
tnx Mikrotik

Skins still don't work on Winbox 4

"v7 stable"

NOT STABLE.

Remember that "stable" in software releases means: "here you have a version that will remain for a while, we will not release a new version every week or two, so you can install this and won't have to update it immediately". The stability refers to the number of updates.
It does NOT mean that it will work in a stable way, i.e. will not crash or will not have problems with certain functions.

Skins still don't work on Winbox 4

This has nothing to do with ROS 7.17, it is a Winbox 4 issue.

NOT STABLE.

Remember that "stable" in software releases means: "here you have a version that will remain for a while, we will not release a new version every week or two, so you can install this and won't have to update it immediately". The stability refers to the number of updates.
It does NOT mean that it will work in a stable way, i.e. will not crash or will not have problems with certain functions.

Wow... And how about me that, using semantic versioning as a reference, I was thinking that Stable could mean that the software manufacturer should only release as stable code that is free of any known bugs.

I think I'll review a little more about versioning standards.

new webfig is nice, too bad there's still no dark mode in itself :D

Branding all broken here: %host% and %version% are showing as is instead of showing actual ip and ROS version...
it's not showing as breaking change on changelog (branding is not webfig itself), is there documentation about these changes?
(and also, documentation about "allow style.css and script.js in branding packages" would be good since it has potential)

hi, neighbors is broken for winbox v3.41 with de last update (7.17)
with winbox v4 is working fine

It works perfectly for me

hi, neighbors is broken for winbox v3.41 with de last update (7.17)
with winbox v4 is working fine

It works perfectly for me

It was a strange situation, I restarted the PC and it works again

I can't upgrade a CCR2004:
There aren't any non-system files on the disk, and I tried the upgrade following a clean reboot. I've seen another user complaining about the same issue on different hardware:

viewtopic.php?p=1119074&sid=8afa3d3815d ... 4cc46d0daa

For me so far, on CCR2004's, it added a new problem.

I have one at my office - one at my home. I use EOIP (yes, I know I should subnet it, but for now I need it all on the same layer 2) with encryption to link the two locations together.

Version 7.16.2 the best on a 1gb symmetrical connection I could get was 400MB/sec between the two locations.

Version 7.17 made some huge improvements, I'm seeing 700-800MB/sec....

BUT connections are dropping. Not packet loss - connections get closed. You'll be winboxed in and poof - you're disconnected to the remote site.

Roll back to 7.16.2 - my speeds are back to what they were - and it's stable again.

Thoughts anyone?

Wow... And how about me that, using semantic versioning as a reference, I was thinking that Stable could mean that the software manufacturer should only release as stable code that is free of any known bugs.

I think I'll review a little more about versioning standards.

It would be desirable when it was like that, but for software as complex and versatile as RouterOS that simply isn't realistic.
There will always be known bugs, the only criticism on MikroTik with regard to that is that there is no section "known bugs and limitations" in the release notes. Some other manufacturers do that, but a lot of them do not. So they are not alone.

Due to the versatility, there are always users that concern particular bugs as a showstopper, while 99% of other users do not use that feature and do not mind that it is released with that bug.
(good example: the "SMB crashes the router when there is not enough free memory". some have repeatedly claimed that this is a showstopper bug, but I do not care at all because my router is not my fileserver, SMB is always disabled).

Skins still don't work on Winbox 4

skin does not work at all.

Complete rewrite webfig without finish this important feature... I don't understand....

Thoughts anyone?

EoIP is a connectionless protocol, there is no "connection that is closing".
However, as with any tunnel protocol, there is the risk of creating a loop where encapsulated traffic is again encapsulated.
Maybe the circumstances have changed due to the version upgrade, like some change in the bridge handling.

Best approach for now: get rid of the EoIP.

Yeah, need to but re-ip'ing 40 items and making all those changes in home assistant isn't on my top of the to do list. Wonder if doing layer 2 tunneling a different method would be better.

Seems it's more than just that. After looking at wireshark captures it looks like the packets just quit getting responses - like you unplugged the link. Yet other sessions will stay up. So odd. Pings will go with no loss.

Have rolled forward and back twice and it's definitely with 7.17.

Thanks!

Remember that "stable" in software releases means: "here you have a version that will remain for a while, we will not release a new version every week or two, so you can install this and won't have to update it immediately". The stability refers to the number of updates.
It does NOT mean that it will work in a stable way, i.e. will not crash or will not have problems with certain functions.

Wow... And how about me that, using semantic versioning as a reference, I was thinking that Stable could mean that the software manufacturer should only release as stable code that is free of any known bugs.

I think I'll review a little more about versioning standards.

And why is Microsoft releasing versions for Windows then ?
You believe they are bug free ? Surely you are aware of Patch Tuesday mishaps ?
Stable being bug free ... I wish.

new webfig is nice, too bad there's still no dark mode in itself :D

Branding all broken here: %host% and %version% are showing as is instead of showing actual ip and ROS version...
it's not showing as breaking change on changelog (branding is not webfig itself), is there documentation about these changes?
(and also, documentation about "allow style.css and script.js in branding packages" would be good since it has potential)

With Beta and RC I reported CSS issues and it got Fixed before Final Realse

All good with my heavily modified Brading Packge

The new web interface is interesting. Maybe I will get used to it, but just in terms of being easy to read, I think the old interface is "clearly" better. The new one just seems softer and less distinct. I'm sure I will find some benefits to it after using it, but I would certainly like it more if it were as easy to see and read as the old one.

Yeah the custom font that MikroTik insist on using for WinBox 4 and the new WebFig is not very high quality and completely unoptimized for display on non-hiDPI display at non-huge sizes. Whoever produced that font did not spend proper effort with hinting. It's a blurry mess at smaller size, not properly snapping to pixel boundaries or supporting Clear Type. The system fonts are much better, at least on Windows.

Also, the two woff2 font files must be stored on the router and consume 38KB of valuable flash storage on devices like the hAP ac². Just look at how horrible "memory" and "interface" look with the MT font compared to WinBox 3 (zoomed out screenshot):

WebFig:
WinBox 3:
WinBox 4:

Lot of work on WebUI.
But still no way to easily disable quickset, have an empty user name on login, re-login on page refresh and graphs are still 1998 style instead the webui...

Both of my devices (RB5009UG+S+ and RBwAPGR-5HacD2HnD) lost same part of configuration, likely related to changes 7.17 introduced around these parts, but this should absolutely never result in such a loss of configuration, especially near neighbor discovery which after upgrade started leaking out of every interface instead of previously configured set).

Sadly, I do not have ability to generate support ticket for these as I have noticed this change after second reboot to upgrade RouterBOOT, but leaving it here for others to verify their own configs.

---

Additionally, RBwAPGR-5HacD2HnD is showing non-printable characters for current RouterBOOT version:

Having an issue with my Active-Backup interface. Giving a RX looped packet error and crashing the interface. SUP-176645.

I spent 2h this night going about the shop to switch off all the devices after updating the 'device-mode', I still have 2 other sites to update (they will wait some time so that 7.17 is better tested here). I undestand what it is for, but I cannot imagine those that have lots of devices in the fields as I used to .. good luck.

BTW.. so far so good, all my lab office's devices are on 7.17 and they work as expected.

Remember that "stable" in software releases means: "here you have a version that will remain for a while, we will not release a new version every week or two, so you can install this and won't have to update it immediately". The stability refers to the number of updates.
It does NOT mean that it will work in a stable way, i.e. will not crash or will not have problems with certain functions.

Wow... And how about me that, using semantic versioning as a reference, I was thinking that Stable could mean that the software manufacturer should only release as stable code that is free of any known bugs.

I think I'll review a little more about versioning standards.

Stable in mikrotik standards.

I never think that the existence of errors is unacceptable. The problem is that when there are errors, you spend development resources on ROSE SMB NAS DNS. Is it because these people are not capable of fixing the routeros-core package so they can only develop those features? Why not fire them and hire capable people?

I am a network engineer & Java software engineer from China and also an ordinary user. I have a normal "Stable" cognition no matter what they say.

Lot of work on WebUI.
But still no way to easily disable quickset, have an empty user name on login, re-login on page refresh and graphs are still 1998 style instead the webui...

Well, the situation with the new UI is still not perfect, though some improvements have been made.

• Webfig - only inline comments? This is a complete usability show stopper for me.
• Winbox 4 - login screen - grouping is not about adding just a column, but provide real grouping like with Winbox 3. Difficult to navigate, so I need to resort to filters.
• Winbox 4 - column separators - looks weird imo.
• Winbox 4 - font colors - improved a bit. Darker comments than items themselves? Drags an attention a bit, but hopefully groving on me. All could be solved, if we would be allowed to choose the colors ourselves.
• Winbox 4 - table row padding setting - perfect.
• Winbox 4 - table row alternate color might be handy. Conditional coloring would be cool, but that's probably a little too much :-)

How do I stop my cap from auto updating when I update my router?

*) ovpn-client - added tls-crypt, tls-crypt-v2 support;

Hello
Has anyone checked this? Especially on NordVPN or ProtonVPN services
The problem is that I don't know how to add the tls key, of course I used the import option but the problem still persists and it gives the tls error

*) wifi - added access-list stats (CLI only);

Can we get an example for this ? I could not figure it out myself and there is no documentation for it.

CHR on KVM/QEMU: VirtIO disk after upgrade not detected.
Solution: remove disk from virtual and re-add it, now it is in disk list with new name...

How do I stop my cap from auto updating when I update my router?

/interface/wifi/capsman/upgrade-policy

• none - do not perform upgrade
• require-same-version - CAPsMAN suggests to upgrade the CAP RouterOS version and, if it fails it will not provision the CAP. (Manual provision is still possible)
• suggest-same-version - CAPsMAN suggests to upgrade the CAP RouterOS version and if it fails it will still be provisioned

I would expect it to be set on require-same-version currently? Set it to none to prevent updating.

https://help.mikrotik.com/docs/spaces/R ... figuration

Nowhere in the documentation does it say that the upgrade is done automatically. It doesn't work for me unless I put the packages in the "Packge path" folder.

For me so far, on CCR2004's, it added a new problem.

I have one at my office - one at my home. I use EOIP (yes, I know I should subnet it, but for now I need it all on the same layer 2) with encryption to link the two locations together.

Version 7.16.2 the best on a 1gb symmetrical connection I could get was 400MB/sec between the two locations.

Version 7.17 made some huge improvements, I'm seeing 700-800MB/sec....

BUT connections are dropping. Not packet loss - connections get closed. You'll be winboxed in and poof - you're disconnected to the remote site.

Roll back to 7.16.2 - my speeds are back to what they were - and it's stable again.

Thoughts anyone?

Install latest testing version and send us supout rif file from the devices.

*) ovpn-client - added tls-crypt, tls-crypt-v2 support;

Hello
Has anyone checked this? Especially on NordVPN or ProtonVPN services
The problem is that I don't know how to add the tls key, of course I used the import option but the problem still persists and it gives the tls error

Please refer to instructions.
https://help.mikrotik.com/docs/spaces/R ... ls-cryptv2

Nowhere in the documentation does it say that the upgrade is done automatically. It doesn't work for me unless I put the packages in the "Packge path" folder.

Here the text can be improved, as "suggests" seems to either "tried" or "performed".

In regards to the packages:

Folder location for the RouterOS packages. For example, use "/upgrade" to specify the upgrade folder from the files section. If an empty string is set, CAPsMAN can use built-in RouterOS packages, note that in this case only CAPs with the same architecture as CAPsMAN will be upgraded.

MikroTik is always open to improvement, feel free to contact them to make an improvement in the documentation. Thanks for noticing (though it is not 7.17 related).

Trying Superchannel on HAP AX3, isnt it supposed to run all channels at max power? But when i set 5180 it runs at (tx-power: 17), i see briefly 60tx and drops to 17, i did try to set manually 28 it doesn't help.
On the other hand if i set United States it does run on max power (tx-power: 28)

Also not related to superchannel but AP keeps dropping power after some time, interface gets enabled, runs at tx-power: 24, all great, but after few hours it drops to tx-power: 17, there is no channel change or anything in logs it just silently drops power, anyone else notice this?

RB912UAG-2HPnD

Can not change silent-bool option after upgrading to 7.17

RB912UAG-2HPnD

Can not change silent-bool option after upgrading to 7.17

Code: Select all

[admin@MT] /system/routerboard/settings> set silent-boot=yes 
failure: not allowed by device-mode

system/device-mode/update routerboard=yes

That was fast!. Indeed. Didn't notice it was changes after upgrade :/

"Wireless" is fine with 7.17, but "wifi-qcom-ac" is crap, unfortunately. I have had long time open memory leak ticket SUP-147911 for hAP ac^2. This ticket has been closed without solution - but it is bullet proof the leak is related to "wifi-qcom-ac", because "wireless" is fine and stable. There is no any willingness on Mikrotik side to do any investigation, only short message - it is old HW. But this old HW IPQ-4019 with exact same amount of RAM memory (256MB) and ROM memory (16MB) is used in Chateau 5G R16. There was visible decrease of RAM free memory 10MB/day starting with 150MB to OOP after roughly 14-21 days - kernel panic memory.

Re: v7.17rc [testing] is released!
Post by CGGXANNX » Thu Jan 16, 2025 12:03 pm

Well it may goes out of memory with SMB, but if wifi-qcom-ac really takes a large chunk of RAM, then OOM might also happen if you run a container (that worked fine with wireless), or if you use adlist with huge lists, etc... If they disable and hide SMB, then should they do that with container and adlist too?

Currently you have to explicitly remove wireless and install wifi-qcom-ac. It is assumed that you read the doc before doing that, and from now on, the doc has the warning about the RAM usage. If your router suffers from OOM, your first thought now would be to revert back to wireless.

We are working towards optimizing wireless-qcom-ac as we try to optimize other packages to be less resource heavy, but it is still a work in progress. As of this moment, wifi-qcom-ac is known and expected to take up more resources (including RAM) than legacy wireless drivers.

HZsolt, osc86, ormandj, nmt1900
Please send supout.rif file from your device to support@mikrotik.com

Code: Select all

/interface/wifi/radio/reg-info country="Superchannel" number=0          
ranges: 2402-2482/60dBm/40MHz 
5170-5895/60dBm/160MHz

Trying Superchannel on HAP AX3, isnt it supposed to run all channels at max power? But when i set 5180 it runs at (tx-power: 17), i see briefly 60tx and drops to 17, i did try to set manually 28 it doesn't help.
On the other hand if i set United States it does run on max power (tx-power: 28)

There is no superchannel in the new wifi-qcom(-ac) drivers, also there is no no_country_set. (BTW, superchannel was a mode, no_country_set was regulatory domain, so you're doing wrong things in the first place.)

The router is probably kicking you back to a default of Latvia, which is at 17.

And yes, I'm also running my wifi as "United States" because of high TX power, despite being in the EU. Isn't that great? :) But the only reason I have that is because I can't remember which South American country is better :D Was it Panama?

Bigger isn't always better...necessity of higher TX Power is an indication that you don't have enough accesspoints.

Code: Select all

/interface/wifi/radio/reg-info country="Superchannel" number=0          
ranges: 2402-2482/60dBm/40MHz 
5170-5895/60dBm/160MHz

Trying Superchannel on HAP AX3, isnt it supposed to run all channels at max power? But when i set 5180 it runs at (tx-power: 17), i see briefly 60tx and drops to 17, i did try to set manually 28 it doesn't help.
On the other hand if i set United States it does run on max power (tx-power: 28)

There is no superchannel in the new wifi-qcom(-ac) drivers, also there is no no_country_set. (BTW, superchannel was a mode, no_country_set was regulatory domain, so you're doing wrong things in the first place.)

The router is probably kicking you back to a default of Latvia, which is at 17.

And yes, I'm also running my wifi as "United States" because of high TX power, despite being in the EU. Isn't that great? :) But the only reason I have that is because I can't remember which South American country is better :D Was it Panama?

What are you even talking about, its literary in changelog of 7.17 update:
) wifi-qcom - added Superchannel country profile;
And it does work for higher channels i just tried like 5500 and 5600 it runs max power and skips DFS check, just not for lower ones for some reason so it seams as a bug..

Why disable firewall rules that are part of VRFs? We use VRFs extensively on every CPE, to separate management interfaces from client traffic interfaces. All client interfaces are subsequently part of a VRF where we then filter forwarded traffic to prevent traffic from a Guest network towards an address list called local (includes 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16). Similarly for CCTV, we want to drop all traffic unless from DVRs or NVRs.

The change recently disables a firewall forward rule when an input interface is part of a VRF. It however works when we create a new interface list add the interface to that list and then adjust the firewall rule to filter the traffic.

NB: The problem here is that we now have to refactor every router's configuration after upgrading. This introduces human error and will invariably result in routers not being upgraded for several weeks/months.


Filtering semantics really shouldn't be affected whether or not an interface is part of a VRF. It worked perfectly before upgrading to 7.17 and continues to work if we use the above work around. Sounds to me that the config control is disabling the rule and not actually putting it in to the config based on a filter when it determines that the referenced interface is part of a VRF.

Reference snip:
Reference where others are doing something similar:
viewtopic.php?t=191016

Documentation reference advising that firewall rules associated with a VRF interfaces will now reference the VRF instead:
https://help.mikrotik.com/docs/spaces/R ... ding+-+VRF

Please don't disable the rules, they should work just fine. This should be optional and possibly recommended for many use cases but not when you have a larger single VRF with various VLANs being members and you want to selectively filter traffic ingressing via one of the VRF VLANs.

Ah, terribly sorry, the ax3 is wifi-qcom, I thought it was -ac and wasn't added there as per the changelog. I'm still in the -ac phase after upgrading my Audience so I think everything is -ac.

erlinden: If you can tell me how to place an access point in the basement for my washer and dryer that doesn't involve destroying walls and drilling through 0.4m of reinforced concrete, I'm all ears...

erlinden: If you can tell me how to place an access point in the basement for my washer and dryer that doesn't involve destroying walls and drilling through 0.4m of reinforced concrete, I'm all ears...

Not being erlinden but first thing which comes to mind: powerline.
E,g,:
https://www.devolo.global/products

You don't have to use the wifi variant, you can use the ethernet-only version and use your own AP of choice.
"sender" and "receiver" need to be on the same phase of your electrical installation and presence of solar power installations will reduce throughput drastically if on that same circuit (but I assume for a washer and dryer there is not much bandwidth needed).

Unable to update RB450GX4. After rebooting the ROS version remains 16.2

Unable to update RB450GX4. After rebooting the ROS version remains 16.2

What say LOG?

Smol homenet updated:
Works good so far :)

QUESTIONS:
*) firewall - added support for random external port allocation;
What means this? A bugfix or something we can configure? What is "random" now and what works now what has not worked before?

*) snmp - added wifi fields to MIKROTIK-MIB;
Where can I view the .mib-file? Which OIDs?

*) health - removed board-temperature on RB5009UPr+S+IN device;
WHY?! I used this as OID and it gave good reading!!
You removed it for the RB5009UPr+S+ (not "IN") too :'(

Not being erlinden but first thing which comes to mind: powerline.
E,g,:
https://www.devolo.global/products
You don't have to use the wifi variant, you can use the ethernet-only version and use your own AP of choice.
"sender" and "receiver" need to be on the same phase of your electrical installation and presence of solar power installations will reduce throughput drastically if on that same circuit (but I assume for a washer and dryer there is not much bandwidth needed).

Ah yes, that's nice, except for the fact that I have 3-phase electricity at home :) With wifi-qcom-ac my appliances are just barely holding on, whereas the old wireless package with superchannel and no_country_set was great, and I really have no desire to spend a crapload of extra money just so my wife can get notifications when the laundry is done...

Hi

After upgrading, l2tp client is not connecting. In Webfig all ipsec tabs are empty and an /ip/ipsec/export results on an error.

# 2025-01-17 11:14:14 by RouterOS 7.17
# software id = WZEK-CJNA
#
# model = CCR2004-16G-2S+
# serial number = XXXXXXXXX
#error exporting "/ip/ipsec/policy/group" (timeout)
#error exporting "/ip/ipsec/proposal" (timeout)
#error exporting "/ip/ipsec/mode-config" (timeout)
#error exporting "/ip/ipsec/policy" (timeout)
#error exporting "/ip/ipsec/profile" (timeout)
#error exporting "/ip/ipsec/settings" (timeout)

Any clues?

Smol homenet updated:
Zwischenablage_01-17-2025_02.jpg


Works good so far :)

QUESTIONS:
*) firewall - added support for random external port allocation;
What means this? A bugfix or something we can configure? What is "random" now and what works now what has not worked before?

*) snmp - added wifi fields to MIKROTIK-MIB;
Where can I view the .mib-file? Which OIDs?

*) health - removed board-temperature on RB5009UPr+S+IN device;
WHY?! I used this as OID and it gave good reading!!
You removed it for the RB5009UPr+S+ (not "IN") too :'(

chart.png

Due to a chip issue which reports board temperature MikroTik decided to remove this parameter from health.

Hi

After upgrading, l2tp client is not connecting. In Webfig all ipsec tabs are empty and an /ip/ipsec/export results on an error.

# 2025-01-17 11:14:14 by RouterOS 7.17
# software id = WZEK-CJNA
#
# model = CCR2004-16G-2S+
# serial number = XXXXXXXXX
#error exporting "/ip/ipsec/policy/group" (timeout)
#error exporting "/ip/ipsec/proposal" (timeout)
#error exporting "/ip/ipsec/mode-config" (timeout)
#error exporting "/ip/ipsec/policy" (timeout)
#error exporting "/ip/ipsec/profile" (timeout)
#error exporting "/ip/ipsec/settings" (timeout)

Any clues?

Please send supout rif file.

Due to a chip issue which reports board temperature MikroTik decided to remove this parameter from health.

Sad - it gave me good, plausible and reliable reading.
Opened a ticket (SUP-176683), because I can not relate.

Ok, I have serious problem with DHCP client after upgrade to 7.17, as it drops default route on multiple type of devices (RB4011, SXTsq 5 ac). I experienced this on RCs and betas too. Routers creating autosupout.rif file after dropping def route. I try to figure out what triggers this issue.

"Wireless" is fine with 7.17, but "wifi-qcom-ac" is crap, unfortunately. I have had long time open memory leak ticket SUP-147911 for hAP ac^2. This ticket has been closed without solution - but it is bullet proof the leak is related to "wifi-qcom-ac", because "wireless" is fine and stable. There is no any willingness on Mikrotik side to do any investigation, only short message - it is old HW. But this old HW IPQ-4019 with exact same amount of RAM memory (256MB) and ROM memory (16MB) is used in Chateau 5G R16. There was visible decrease of RAM free memory 10MB/day starting with 150MB to OOP after roughly 14-21 days - kernel panic memory.

Re: v7.17rc [testing] is released!
Post by CGGXANNX » Thu Jan 16, 2025 12:03 pm

Well it may goes out of memory with SMB, but if wifi-qcom-ac really takes a large chunk of RAM, then OOM might also happen if you run a container (that worked fine with wireless), or if you use adlist with huge lists, etc... If they disable and hide SMB, then should they do that with container and adlist too?

Currently you have to explicitly remove wireless and install wifi-qcom-ac. It is assumed that you read the doc before doing that, and from now on, the doc has the warning about the RAM usage. If your router suffers from OOM, your first thought now would be to revert back to wireless.

I can´t confirm that there´s a general problem with wifi-qcom-ac.
There are 4 devices running since 50days without any memory leaks or other problems:

Unable to update RB450GX4. After rebooting the ROS version remains 16.2

What say LOG?

upgrade failed, free 9 kB of kernel disk space

Free Memory: 617.6 MiB Total Memory:1024.0 MiB
Free HDD Space: 409.2 MiB Total HDD Size: 512.0 MiB

What say LOG?

upgrade failed, free 9 kB of kernel disk space

Free Memory: 617.6 MiB Total Memory:1024.0 MiB
Free HDD Space: 409.2 MiB Total HDD Size: 512.0 MiB

MikroTik asked to send supout to them for this. I already netinstalled so can’t, but if you can generate a supout and send it to them as the above post requested, I’m sure they will help them.

HZsolt, osc86, ormandj, nmt1900
Please send supout.rif file from your device to support@mikrotik.com

But the only reason I have that is because I can't remember which South American country is better :D Was it Panama?

Brazil is better than ETSI most of times: 30dBm vs 20dBm on 2.4GHz, 30dBm vs. 14dBm on 5735-5875 MHz ... but not always: ETSI has 30dBm vs. 24dBm on 5490-5730 MHz.

According to reg-info from wAP ax running 7.17, US is the same as Brazil ... but starting with 2025-01-20 I'll like Brazil better than US (regardless nationality of the first lady to be) ;-)

Ok, I have serious problem with DHCP client after upgrade to 7.17, as it drops default route on multiple type of devices (RB4011, SXTsq 5 ac). I experienced this on RCs and betas too. Routers creating autosupout.rif file after dropping def route. I try to figure out what triggers this issue.

Its strange! I using L2TPv2 tunnels, ip,ipv6,mpls over it. Using IGP protocol (RIP or OSPF doesn't matter) to distribute Loopback addresses. MPLS LDP is active on it and using BGP to exchange VPNvX routes. On IPv4 BGP peers I echange VPNv4 routes, on IPv6 BGP peers I exchange VPNv6 routes.
Here comes the strange part. Until only IPv4 BGP peer is active nothing bad happens. When IPv6 BGP peer is comes up or it gets update(?) then it messing up the IPv4 routing table. For example it deleting the DHCP default route so L2TP tunnel goes down.

Due to a chip issue which reports board temperature MikroTik decided to remove this parameter from health.

The questions was "WHY?" What is the chip doing to cause this decision?

What say LOG?

upgrade failed, free 9 kB of kernel disk space

Free Memory: 617.6 MiB Total Memory:1024.0 MiB
Free HDD Space: 409.2 MiB Total HDD Size: 512.0 MiB

First they have to figure out what does this message actually mean...

Due to a chip issue which reports board temperature MikroTik decided to remove this parameter from health.

The questions was "WHY?" What is the chip doing to cause this decision?

Sometimes the reported board temperature is ridiculously high, I have seen that in one of our devices (while others are OK).

[*]*) ppp - add routes in matching VRF;

Still not all routes added to the correct VRF for PPP interfaces added to an interface list (through PPP profile) and interface list added to VRF.
I'll eat a broom if this bug ever gets fixed.

I've sent supout files from two devices to support regarding the 'upgrade failed, free XX kB of kernel disk space' error.

upgrade failed, free 9 kB of kernel disk space
First they have to figure out what does this message actually mean...

Maybe on some devices there is a separate partition for /boot ?
That used to be required/customary on some Linux filesystems or disk devices, to guarantee that the boot code was always within some area supported by the bootloader.
When for some reason the previous kernel version is not removed after upgrade, a next upgrade may be impossible.
(I know that issue from a server which was installed with a previous Debian version that by default created a "small" boot partition in certain circumstances)

IKEv2 tunnels fail to establish after upgrading to 7.17 (between 7.17<->7.17 and 7.17<->7.16.2). However, 7.17 does establish IKEv2 with Huawei AR (same settings).
Rolling back to 7.16.2 does fix the issue.
Auth method is PSK, 7.17 peer sends "Delete" right after successful IKE_AUTH. Tested on both live RBs and GNS3 lab.

Am I the only one with this issue?

upgrade failed, free 9 kB of kernel disk space
First they have to figure out what does this message actually mean...

Maybe on some devices there is a separate partition for /boot ?
That used to be required/customary on some Linux filesystems or disk devices, to guarantee that the boot code was always within some area supported by the bootloader.
When for some reason the previous kernel version is not removed after upgrade, a next upgrade may be impossible.
(I know that issue from a server which was installed with a previous Debian version that by default created a "small" boot partition in certain circumstances)

On server-space it sounds quite logical, but here we have situation where some of same models succeed and some fail - while using same installation packages and sharing same architecture. It is hard to believe this has anything to do with userspace.

P. S. Even units with same hardware behave differently - hap ac2 with its' 16 MB storage succeeds but RB450Gx4 with 512 MB storage fails while both have essentially same SoC

Ok, I have serious problem with DHCP client after upgrade to 7.17, as it drops default route on multiple type of devices (RB4011, SXTsq 5 ac). I experienced this on RCs and betas too. Routers creating autosupout.rif file after dropping def route. I try to figure out what triggers this issue.

Confirm, I have the same problem on RB5009. I’ve implemented a workaround script to trigger DHCP release once the obtained default route gets missing.

I can confirm this - happened on my hEX Refresh too. Triggered a dhcp release and it went back to normal.

Ok, I have serious problem with DHCP client after upgrade to 7.17, as it drops default route on multiple type of devices (RB4011, SXTsq 5 ac). I experienced this on RCs and betas too. Routers creating autosupout.rif file after dropping def route. I try to figure out what triggers this issue.

Confirm, I have the same problem on RB5009. I’ve implemented a workaround script to trigger DHCP release once the obtained default route gets missing.

It seems, it reinitializes all the IGPs after 5sec: This is totally platform independent, experiencing on CHR too. If I add a static default then where forwarding works, where it doesn't:

What is this field (Netwatch)?

After updating from 7.16.2 to 7.17 yesterday the 5ghz wifi has stopped working.

I have a hAP ax^3 (C53UiG+5HPaxD2HPaxD). The wifi1 interface has all of the configurations that it previously had, but is offline.

Both wifi interfaces are members of Bridge1, Bridge ports show wifi2 (2ghz) is up and running and it transmitting its SSID, whereas wifi1 shows it is not up and is not broadcasting its SSID.

I've looked at the config pre-update and post-update and it has not changed.

I manually uploaded the wifi-qcom package hoping it was just corrupt, that didn't help. I uninstalled the wifi-qcom package and then reinstalled it, no luck.

Any ideas?

Thanks,

Glenn

Hi,

Arggg it seems like there are too many bugs in this version ...

While usual stable release may sometimes be beta-level quality, this endless polishing of device-mode produced a release of alpha-level quality if not even worse...

It might be possible, it is related to some scenarios only. For example: majority of IPv6 traffic, heavy load, traffic handovers between 2,4 and 5 GHz bands, fast BSS transition according IEEE 802.11r etc. etc. If I would know, it would be excellent, but I don't know root cause. Reality is that in my quite simple case and simple config always ending with not only Linux OOPS, but even kernel panic crash and restart with autosupout.rif generated.

All autosupout.rif had been provided to Mikrotik. And result was - nothing, it is fine, old HW, use "wireless.apk". On the other hand "wirelles.apk" works fine. But in this case is big question, why Qualcomm native drivers on Qualcomm HW work so badly in specific cases? And it seems I am not alone. Majority of my connected devices are Apple products and there were more complains from other users about the usage, traffic fluctuation, sudden disconnections and reconnections etc.

I can´t confirm that there´s a general problem with wifi-qcom-ac.
There are 4 devices running since 50days without any memory leaks or other problems:
hc_438.jpg

Thank you Deniss for your effort. I wanted not to be rude, but closing the tickets with kernel crashes without any solution makes me little bit angry. And not only here, in my job (mobile telco industry) too. :-)) Resources are in my case fine, I have 256MB RAM, not only 128MB. I am willing to test it, if you want.

We are working towards optimizing wireless-qcom-ac as we try to optimize other packages to be less resource heavy, but it is still a work in progress. As of this moment, wifi-qcom-ac is known and expected to take up more resources (including RAM) than legacy wireless drivers.

I upgraded to 7.17 on my hAP ax2 and realized that the bridge ports are not shown as "hardware offloaded" anymore. This was always the case on previous versions. Bug?

P.S: Setting "detect interface list" (Detect Internet) to "none" doesn't fix the issue.

IKEv2 tunnels fail to establish after upgrading to 7.17 (between 7.17<->7.17 and 7.17<->7.16.2). However, 7.17 does establish IKEv2 with Huawei AR (same settings).
Rolling back to 7.16.2 does fix the issue.
Auth method is PSK, 7.17 peer sends "Delete" right after successful IKE_AUTH. Tested on both live RBs and GNS3 lab.

Am I the only one with this issue?

Using Mikrotik as spoke (IKEv2 + PSK) to a Cisco Router and it still works fine after upgrading to 7.17.

Arggg it seems like there are too many bugs in this version ...

Yeah and some random guy here dreamed *THIS* will be a long-term, because it took so long... LOL
This is a typical MT point-zero release, 3 steps forward and 5 back... The long-term is as far away as with the v7.0 release.

The issue with WiFi password being shown upon entering HTTPS login screen (even though "Hidden/Hide" is ticked) is still there.

Am going to wait it out, would not be surprised if 7.17.1 or .2 release come out shortly to fix up minor issues.

Try to add wifi1 (5 GHz) on bridge manually. It might help.

After updating from 7.16.2 to 7.17 yesterday the 5ghz wifi has stopped working.

Both wifi interfaces are members of Bridge1, Bridge ports show wifi2 (2ghz) is up and running and it transmitting its SSID, whereas wifi1 shows it is not up and is not broadcasting its SSID.

It continues to be "Offline".

I reset the wifi1 interface and re-configured also, still nothing.

Try to add wifi1 (5 GHz) on bridge manually. It might help.

After updating from 7.16.2 to 7.17 yesterday the 5ghz wifi has stopped working.

Both wifi interfaces are members of Bridge1, Bridge ports show wifi2 (2ghz) is up and running and it transmitting its SSID, whereas wifi1 shows it is not up and is not broadcasting its SSID.

Arggg it seems like there are too many bugs in this version ...

Yeah and some random guy here dreamed *THIS* will be a long-term, because it took so long... LOL
This is a typical MT point-zero release, 3 steps forward and 5 back... The long-term is as far away as with the v7.0 release.

This is because many people wait for the final release to pull the trigger: "omg!!!!! it broke my xyz". instead of evaluating the testing releases ao Mikrotik can fix release specific issues before final version.

There is no superchannel in the new wifi-qcom(-ac) drivers, also there is no no_country_set. (BTW, superchannel was a mode, no_country_set was regulatory domain, so you're doing wrong things in the first place.)

The router is probably kicking you back to a default of Latvia, which is at 17.

And yes, I'm also running my wifi as "United States" because of high TX power, despite being in the EU. Isn't that great? :) But the only reason I have that is because I can't remember which South American country is better :D Was it Panama?

What are you even talking about, its literary in changelog of 7.17 update:
) wifi-qcom - added Superchannel country profile;
And it does work for higher channels i just tried like 5500 and 5600 it runs max power and skips DFS check, just not for lower ones for some reason so it seams as a bug..

Superchannel is working great on my hAP ax3, no DFS and max TX power allowed by the hardware just had to limit the frequency to 5180-5805 and 2412-2462. Otherwise it may pick a channel out of the usable spectrum for most WiFi clients.

I upgraded to 7.17 on my hAP ax2 and realized that the bridge ports are not shown as "hardware offloaded" anymore. This was always the case on previous versions. Bug?

I don't think that the hAP ax²/ax³ have ever had hardware offload support for the bridge. It's stated in the doc since the beginning:

https://help.mikrotik.com/docs/spaces/R ... Offloading

Currently, HW offloaded bridge support for the IPQ-PPE switch chip is still a work in progress. We recommend using, the default, non-HW offloaded bridge (enabled RSTP).

Yeah and some random guy here dreamed *THIS* will be a long-term, because it took so long... LOL
This is a typical MT point-zero release, 3 steps forward and 5 back... The long-term is as far away as with the v7.0 release.

This is because many people wait for the final release to pull the trigger: "omg!!!!! it broke my xyz". instead of evaluating the testing releases ao Mikrotik can fix release specific issues before final version.

@infabo, I know this is well intended.
But as a practical matter, I can't afford to duplicate my network.
MT is slowly killing themselves by dumping testing on the user base.
This is a treadmill where I can't risk upgrading until a 7.xx.2+ version.
Over time fewer and fewer small users will ever touch a 7.xx.0 version.
IMO reliable networking is critical substantially over and above features.
Releasing new features while breaking old ones is beyond a cardinal sin.
Every feature should have an automated test in-place to catch regressions.

do we have any update on [SUP-134566]: BGP-VRF V7?

when that feature will be implemented.
It works perfectly fine on v6