MikroTik RouterOS PPC Firmware 6.42 RC 6 Download

Posted at April 16, 2024 by PCI-DB Team

MikroTik RouterOS PPC Firmware 6.42 RC 6 Description

What's new in 6.42rc6:

- btest - fixed TCP test accuracy when low TX/RX rates are used;
- crs317 - improved transmit performance between 10G and 1G ports;
- dhcpv6-client - added possibility to specify options (CLI only);
- snmp - added w60g support;
- wireless - fixed device becoming unresponsive (introduced in v6.42rc5);

Other changes since 6.41:

- bridge - fixed bridge related settings conversation during upgrade from pre-v6.41 bridge implementation (introduced v6.41);
- bridge - properly update "actual-mtu" after MTU value changes (introduced v6.41);
- capsman - improved CAPsMAN responsiveness on systems with large amount of CAP interfaces;
- detnet - additional work on "detect-internet" implementation;
- detnet - fixed "detect-internet" feature unavailability if router had too long identity (introduced v6.41);
- discovery - fixed discovery related settings conversation during upgrade from pre-v6.41 discovery implementation (introduced v6.41);
- dude - fixed e-mail notifications when default port is not used;
- firewall - fixed "tls-host" firewall matcher (introduced v6.41);
- firewall - limited maximum "address-list-timeout" value to 35w3d13h13m56s;
- ike1 - display error message when peer requests "mode-config" when it is not configured;
- ike1 - fixed “aes-ctr” and “aes-gcm” encryption algorithms (introduced v6.41);
- ike2 - improve half-open connection handling;
- interface - improved interface configuration responsiveness;
- log - properly report bridge interface MAC address changes;
- poe-out - do not show "poe-out-current" on devices which can not determine it;
- rb1100ahx4 - fixed reset button responsiveness when regular firmware is used;
- routerboot - fixed missing upgrade firmware for "ar7240" devices;
- ssh - improved key import error messages;
- tile - added "aes-ctr" hardware acceleration support;
- tile - fixed USB device speed detection after reboot;
- tr069-client - fixed HTTPS authentication process;
- traffic-flow - do not count single extra packet per each flow;
- wireless - fixed nv2 protocol on ARM platform SXTsq devices;
- wireless - improved wireless scan functionality for devices with multiple wireless interfaces;

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