MikroTik RouterOS MMIPS Firmware 6.47 RC 19

MAJOR CHANGES IN v6.47:

- socks - added support for SOCKS5 (RFC 1928);

Changes in this release:

- socks - added support for SOCKS5 (RFC 1928);
- bonding - improved slave interface MAC address handling;
- bonding - prefer primary slave MAC address for bonding interface;
- bridge - added logging message when a host MAC address is learned on a different bridge port;
- chr - improved stability when changing ARP modes on e1000 type adapters;
- console - prevent "flash" directory from being removed (introduced in v6.46);
- console - updated copyright notice;
- crs305 - disable optical SFP/SFP+ module Tx power after disabling SFP+ interface;
- defconf - fixed "caps-mode" not initialized properly after resetting;
- defconf - fixed default configuration loading on RBwAPG-60adkit (introduced in v6.46);
- discovery - do not send CDP and LLDP packets on interfaces that does not have MAC address;
- discovery - do not send discovery packets on inactive bonding slave interfaces;
- discovery - do not send discovery packets on interfaces that are blocked by STP;
- dot1x - added "radius-mac-format" parameter (CLI only);
- health - added "gauges" submenu with SNMP OID reporting;
- lora - added "ru-864-mid" channel plan;
- lora - fixed packet sending when using "antenna-gain" higher than 5dB;
- lora - improved immediate packet delivery;
- lte - do not allow running "scan" on R11e-4G;
- lte - fixed "band" value setting when configuration is reset on R11e-4G;
- lte - fixed "cell-monitor" on R11e-LTE in 3G mode;
- lte - fixed "earfcn" reporting on R11e-LTE6 in UMTS and GSM modes;
- lte - improved all APN session activation after disconnect on R11e-LTE;
- lte - report only valid info parameters on R11e-LTE6;
- lte - use APN from network when blank APN used on R11e-4G;
- ppp - fixed minor typo in "ppp-client" monitor;
- qsfp - do not report bogus monitoring readouts on modules without DDMI support;
- qsfp - improved module monitoring readouts for DAC and break-out cables;
- routerboard - added "mode-button" support for RBcAP2nD;
- sniffer - allow setting port for "streaming-server";
- snmp - added "dot1qTpFdbTable" OID reporting for Q-BRIDGE-MIB;
- snmp - improved OID policy checking and error reporting on "set" command;
- supout - added "dot1x" section to supout files;
- system - correctly handle Generic Receive Offloading (GRO) for MPLS traffic;
- system - fixed ".auto.rsc" file execution (introduced in v6.46);
- system - fixed "check-installation" on PowerPC devices (introduced in v6.46);
- traceroute - improved stability when invalid packet is received;
- traffic-generator - improved memory handling on CHR;
- webfig - allow skin designing without "ftp" and "sensitive" policies;
- webfig - fixed "skins" saving to "flash" directory if it exists (introduced in v6.46);
- winbox - automatically refresh "Packets" table when new packets are captured by "Tools/Packet Sniffer";
- winbox - fixed "Default Route Distance" default value when creating new LTE APN;
- winbox - removed duplicate "join-eui", "dev-eui", "counter", "chain", "size" and "payload" parameters under "Lora/Traffic";

Other changes since v6.46.1:

- crs3xx - fixed "ingress-rate" property on CRS309-1G-8S+, CRS312-4C+8XG, CRS326-24S+2Q+ devices;
- dhcpv6-client - improved error logging when when renewed address differs;
- fetch - fixed "User-Agent" usage if provided by "homepage";
- lte - fixed multiple APN reactivation after deactivation by operator;
- netinstall - removed "Flashfig" from Netinstall;
- netinstall - removed "Make Floppy" from Netinstall;
- netinstall - signed netinstall.exe with Digital Signature;
- snmp - added "dot1qTpFdbTable" OID reporting for Q-BRIDGE-MIB;
- snmp - fixed "dot1dBasePort" index offset for BRIDGE-MIB;
- snmp - improved stability when polling MAC address related OID;
- w60g - use "arp" and "mtu" parameters from master interface when creating a new station;
- winbox - added "auto-erase" option to "Tool/SMS" menu;

About Router Firmware:

Before you consider downloading this firmware, go to the system information page of the router and make sure that the currently installed version isn't either newer or matching this release.

Due to the large variety of router models and different methods for upgrading the device, it is highly recommended that you read and, above all, understand the installation steps before you apply the new firmware, even if you are a power user.

In theory, these steps shouldn't be much of a hassle for anyone, because manufacturers try to make them as easy as possible, even if they don't always succeed. Basically, you must upload the new firmware to the router through its administration page and allow it to upgrade.

If you install a new version, you can expect increased security levels, different vulnerability issues to be resolved, improved overall performance and transfer speeds, enhanced compatibility with other devices, added support for newly developed technologies, as well as several other changes.

If you're looking for certain safety measures, remember that it would be best if you perform the upload using an Ethernet cable rather than a wireless connection, which can be interrupted easily. Also, make sure you don't power off the router or use its buttons during the installation, if you wish avoid any malfunctions.

If this firmware meets your current needs, get the desired version and apply it to your router unit; if not, check with our website as often as possible so that you don't miss the update that will improve your device.

  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.