MikroTik RouterOS Firmware 6.28 RC 14 Download

Posted at December 22, 2024 by PCI-DB Team

MikroTik RouterOS Firmware 6.28 RC 14 Description

Fixes:

- tile - rare situation when CCR devices failed to auto-negotiate ethernet link (introduced in v6.25);
- route - using ldp could cause connected routes with invalid interface nexthop;
- added support for SiS 190/191 PCI Ethernet adapter;
- made metarouter work on boards with 802.11ac support or usb LTE;
- sstp server - allow ADH only when no certificate set;
- make fat32 disk formatting support disks bigger than 134GiB;
- fixed tunnels - could crash when clamp-tcp-mss was enabled;
- added basic counters for ipv4/bridge fast path, also show status weather fast path is active at all;
- console - added 'comment' parameter for '/system script'
- api - return sentences can have property ~.section~ that groups values from commands such as ~monitor~, ~traceroute~, ~print~ (with non-zero 'interval' value);
- cloud - add time zone detection feature ~/system clock time-zone-autodetect~;
- cloud - rename ~/ip cloud enabled~ to ~/ip cloud ddns-enabled~;
- cloud - make ~/ip cloud update-time~ independent from ~/ip cloud ddns-enabled~
- cloud - when setting ~/ip cloud ddns-enabled~ to ~no~ router will send message to server to disable DNS name for this routerboard;
- cloud - ~/ip cloud force-update~ command now will work also when ~/ip cloud ddns-enabled = no~. usefull if user wants to disable DDNS;
- RB4xxGL - improved ethernet throughput (less dropped packets);
- trafflow: - fixed crash on disable;
- pppoe - fixed crash when big ppp packets with were sent over EOIP;
- tilegx - fixed memory leak when queue settings are changed;
- ar9888 - fixed crash when hw reports invalid rate;
- console - fixed "in" operator in console;
- console - make "/system package update print" work again.

  It is highly recommended to always use the most recent driver version available.

Try to set a system restore point before installing a device driver. This will help if you installed an incorrect or mismatched driver. Problems can arise when your hardware device is too old or not supported any longer.

Related MikroTik Drivers