MikroTik RouterOS x86 Firmware 6.39 RC 12 Download

Posted at December 3, 2024 by PCI-DB Team

MikroTik RouterOS x86 Firmware 6.39 RC 12 Description

What's new in 6.39rc12

- quickset - configuration changes are now applied only on "OK" and "Apply" (not on mode change);
- winbox - minimal required version is v3.8 (because of new quickset);
- bridge - disallow manual removal of dynamic bridge ports;
- bridge - fixed access loss to device through bridge if master port had a loop (introduced in v6.38);
- bridge - fixed rare conflicts between hardware and software STP (introduced in v6.38);
- certificate - added year cap (invalid-after date will not exceed year 2039);
- certificate - allow CRL address to be specified as DNS name;
- certificate - fixed fail on import from CAPs when both key and name already exist;
- dhcpv6-server - fixed server removal crash if static binding was present;
- fan - improved RPM monitor on CCR1009;
- firewall - fixed import of exported configuration that had updated "limit" setting;
- graphs - fixed graph disappearance after power outage;
- ike1 - fixed ph1 rekey in setups with mode-cfg;
- ike2 - auto-negotiate split nets;
- ike2 - default to tunnel mode in setups without policy;
- ike2 - fixed initiator TS updating;
- ike2 - fixed policy setting for /0 selector with different address families;
- ike2 - fixed split policy active flag;
- ike2 - fixed xauth add check;
- ike2 - include identity in peer address info;
- ike2 - log empty TS payload;
- ike2 - minor logging update;
- ike2 - traffic selector improvements;
- ike2 - use first split net for empty TS;
- ike2 - use standard retransmission timers for DPD;
- ike2 - xauth like auth method with user support;
- ipsec - added ability to kill particular remote-peer;
- ipv6 - added warning about having interface MTU less than minimal IPv6 packet fragment (1280);
- leds - added LTE modem access technology trigger;
- leds - do not update single LED state when it is not changed;
- license - fixed demo license expiration after installation on x86;
- logs - work on false CPU/RAM overclocked alarms;
- mpls - fixed crash on active tunnel loss in MPLS TE setups;
- ppp - fixed rare kernel failure on PPP client connection;
- pppoe - make default keepalive 10s for PPPoE clients;
- profile - classify ethernet driver activity properly in ARM architecture;
- quickset - various small changes;
- rb751u - fixed ethernet LEDs (broken since 6.38rc16);
- tr069-client - added connection request authentication;
- tr069-client - added parameters for DNS client management support;
- tr069-client - generate random connection request target path;
- webfig - allow shorten bytes to k,M,G in firewall "connection-bytes" and "connection-rates";
- webfig - show properly large BGP AS numbers;
- winbox - added "add-relay-info" and "relay-info-remote-id" to DHCP relay;
- winbox - added "group-key-update" to CAPsMAN security settings;
- winbox - added "make-static" to IPv6 DHCP server bindings;
- winbox - added "prefix-pool" to DHCPv6 server binding;
- winbox - added IPsec to radius services;
- winbox - added upstream flag to IGMP proxy interfaces;
- winbox - allow shorten bytes to k,M,G in bridge firewall just like in “/ip firewall”;
- winbox - allow shorten bytes to k,M,G in firewall "connection-bytes" and "connection-rates";
- winbox - allow to change user password to empty one;
- winbox - allow to specify "connection-bytes" & "connection-rate" for any protocol in “/ip firewall” rules;
- winbox - allow to specify "sip-timeout" under ip firewall service-ports;
- winbox - allow to specify certificate type when exporting it;
- winbox - allow to specify interfaces that CAPsMAN can use for management;
- winbox - do not create empty rates.vht-basic/supported-mcs if not specified in CAPsMAN;
- winbox - do not create time field when copying CAPsMAN access list entry;
- winbox - do not try to disable dynamic items from firewall tables;
- winbox - fixed typo in “/system resources pci” list;
- winbox - hide "nat-traversal" setting in IPsec peer if IKEv2 is selected;
- winbox - removed "sfp-rate-select" setting from ethernet interface;
- winbox - show dynamic IPv6 pools properly;
- winbox - show errors on IPv6 addresses ;
- winbox - specify metric for “/ip dns cache-used” setting;
- winbox - updated fan management menu;
- wireless - added "station-roaming" setting;
- wireless - fixed rare wireless ac interface lockup;
- wireless - show comment on "security-profile" if it is set;

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.

Related MikroTik Drivers