MikroTik RouterOS x86 Firmware 6.38.4 Download

Posted at December 22, 2024 by PCI-DB Team

MikroTik RouterOS x86 Firmware 6.38.4 Description

Changes:

- chr - fixed problem when transmit speed was reduced by interface queues;
- dhcpv6-server - require "address-pool" to be specified;
- export - do not show "read-only" IRQ entries;
- filesystem - implemented procedures to verify and restore internal file structure integrity upon upgrading;
- firewall - do not allow to set "time" parameter to 0s for "limit" option;
- hotspot - fixed redirect to URL where escape characters are used (requires newly generated HTML files);
- hotspot - show Host table commentaries also in Active tab and vice versa;
- ike1 - fixed “xauth” Radius login;
- ike2 - also kill IKEv2 connections on proposal change;
- ike2 - always limit empty remote selector;
- ike2 - fixed proposal change crash;
- ike2 - fixed responder subsequent new child creation when PFS is used;
- ike2 - fixed responder TS updating on wild match;
- ipsec - deducted policy SA src/dst address from src/dst address;
- ipsec - do not require "sa-dst-address" if "action=none" or "action=discard";
- ipsec - fixed SA address check in policy lookup;
- ipsec - hide SA address for transport policies;
- ipsec - keep policy in kernel even with bad proposal;
- ipsec - kill ph2 on policy removal;
- ipsec - updated/fixed Radius attributes;
- irq - properly detect all IRQ entries;
- l2tp-client - fixed IPSec policy generation after reboot;
- l2tp-client - require working IPSec encryption if "use-ipsec=yes";
- lcd - show fan2 speed only if it is available;
- profile - classify ethernet driver activity properly in ARM architecture;
- snmp - added SSID to CAPsMAN registration table;
- snmp - fixed "/tool snmp-get" crash on session timeout;
- snmp - fixed CAPsMAN registration table OID print;
- snmp - fixed situation when SNMP could not read "/system health" values after reboot;
- userman - allow access to User Manager users page only through "/user" URL;
- userman - show warning when no users are selected for CSV file generation;
- winbox - do not hide "power-cycle-after" option;
- winbox - hide advertise tab in Hotspot user profile configuration if "transparent-proxy" is not enabled;
- winbox - make "power-cycle-interval" not to depend on "power-cycle-ping-enabled" in PoE settings;
- winbox - properly show BGP communities in routing filters table filter;
- wireless - fixed scan tool stuck in background;
- wireless - improved compatibility with Intel 2200BG wireless card;

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