MikroTik RouterOS SMIPS Firmware 6.41 RC 9 Download

Posted at November 22, 2024 by PCI-DB Team

MikroTik RouterOS SMIPS Firmware 6.41 RC 9 Description

Important note!!! Backup before upgrade!

- RouterOS (v6.40rc36-rc40 and) v6.41rc1+ contains new bridge implementation that supports hardware offloading (hw-offload).
- This update will convert all interface "master-port" configuration into new bridge configuration, and eliminate "master-port" option as such.
- Bridge will handle all Layer2 forwarding and the use of switch-chip (hw-offload) will be automatically turned on based on appropriate conditions.
- The rest of RouterOS Switch specific configuration remains untouched in usual menus for now.
- Please, note that downgrading to previous RouterOS versions will not restore "master-port" configuration, so use backups to restore configuration on downgrade.

What's new in 6.41rc9 (2017-Aug-03 12:02):

- certificate - fixed SCEP "get" request URL encoding;
- dhcpv6-client - fixed IA evaluation order;
- l2tp-server - fixed PPP services becoming unresponsive after changes on L2TP server with IPSec configuration;
- lcd - fixed LCD blinking on RB2011 (introduced in 6.40);
- lte - added initial passthrough support for wAP LTE;
- pppoe-client - fixed wrong auto MRU detection over VLAN interfaces;
- pppoe-server - fixed situation when PPPoE servers become invalid on reboot;
- sfp - fixed invalid temperature readings when ambient temperature is below 0C;

Other changes since 6.40:

- bridge - implemented software based vlan-aware bridges;
- https://wiki.mikrotik.com/wiki/Manual:Interface/Bridge#Bridge_VLAN_Filtering
- switch - "master-port" conversion into a bridge with hardware offload "hw" option (CLI only);
- https://wiki.mikrotik.com/wiki/Manual:Switch_Chip_Features#Bridge_Hardware_Offloading
- bridge - general development of hw-offload bridge implementation (introduced in v6.40rc36);
- arp - fixed invalid static ARP entries after reboot on interfaces without IP address;
- bonding - improved relialibility on bonding interface removal;
- bridge - fixed ARP setting (introduced in v6.40rc36);
- bridge - fixed multicast forwarding (introduced in v6.40rc36);
- bridge - implemented dynamic entries for active MST port overrides;
- bridge - implemented software based "igmp-snooping" (CLI only);
- bridge - implemented software based MSTP (CLI only);
- bridge - removed "frame-types" and "ingress-filtering" for bridge interfaces (introduced in v6.40rc36);
- bridge - show "admin-mac" only if "auto-mac=no";
- btest - improved reliability on Bandwidth Test when device`s RAM is almost full;
- certificate - show "Expired" flag when initial CRL fetch fails;
- CRS3xx - switch VLAN configuration integrated within bridge VLAN configuration with hw-offload;
- dhcpv6-client - do not run DHCPv6 client when IPv6 package is disabled;
- e-mail - do not show errors when sending e-mail from script;
- export - fixed export for different parameters where numerical range or constant string is expected;
- firewall - properly remove "address-list" entry after timeout ends;
- hotspot - improved user statistics collection process;
- interface - improved interface state change handling when multiple interfaces are affected at the same time;
- ippool6 - try to assign desired prefix for client if prefix is not being already used;
- ipv6 - fixed IPv6 address request from pool (introduced in 6.41rc1);
- lte - allow to specify the MAC address for passthrough mode;
- lte - fixed LTE not passing any traffic while in running state;
- ovpn-client - fixed incorrect netmask usage for pushed routes;
- ppp - added support for Sierra MC7750, Verizon USB730L;
- pppoe-client - fixed incorrectly formed PADT packet;
- rb2011 - fixed possible LCD blinking along with Ethernet LED;
- rb922 - restored missing wireless interface on some boards;
- sftp - added functionality which imports ".auto.rsc" file or reboots router on ".auto.npk" upload;
- torch - fixed Torch on PPP tunnels (introduced in 6.40);
- trafficgen - fixed "lost-ratio" showing incorrect statistics after multiple sequences;
- winbox - added "none-dynamic" and "none-static" options for "address-list-timeout" parameter under NAT, Mangle and RAW rules;
- winbox - do not show duplicate filter parameters "Published" in ARP list;
- winbox - show warnings under "/system routerboard settings" 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.

Related MikroTik Drivers