MikroTik RouterOS X86 Firmware 7.4 RC 2 Testing

What's new in 7.4beta2:

- api - fixed comma encoding within URL when using the ".proplist" argument;
- bridge - properly process IPsec decapsulated packets through the firewall when the "use-ip-firewall" option is enabled;
- capsman - require a unique name for configuration and configuration pre-sets;
- cloud - print critical log message when system clock gets synchronised;
- console - added ":retry" command;
- console - fixed situation when print output was not consistent;
- dns - convert the domain name to lowercase before matching regex;
- e-mail - added VRF support (CLI only);
- filesystem - fixed repartition on RB5009 series devices;
- firewall - added "srcnat" and "dstnat" flags to IPv6/Firewall/Connection table;
- firewall - added support for IPv6/Firewall/NAT action=src-nat rules (CLI only);
- firewall - fixed IPv6 NAT functionality when processing GRE traffic on TILE devices;
- firewall - fixed IPv6/Firewall/RAW functionality;
- firewall - include "connection-mark", "connection-state", and "packet-mark" when packet logging is enabled;
- firewall - properly handle interface matcher when VRF interface is specified;
- hotspot - fixed ARP resolution for clients when address pool is specified on the server;
- hotspot - fixed Walled Garden entries with action=deny;
- ipv6 - fixed system stability when adding/removing IPv6 address;
- ldp - correctly handle AFI selection for usage on dual-stack peers;
- lte - request connect with the same IP type as in LTE attach status for MBIM;
- lte - fixed Telit AT interface numbering;
- lte - improved LTE interface detection for LtAP-2HnD devices;
- lte - keep MBIM working even if AT channel fails to respond in the initialisation stage;
- mmips - improved USB device detection after system bootup;
- mpls - fixed VPLS functionality when PW peer is an immediate neighbor;
- ovpn - use selected cipher by default when the server does not provide "cipher" option;
- pimsm - improved system stability when changing configuration;
- ppp - properly try to use different authentication algorithms when Conf-Rej is received during the LCP phase;
- quickset - specify the "in-interface-list=WAN" attribute on firewall rules created through "Port Mapping";
- route - added option to join static IGMP and MLD groups (available in "/routing/gmp" menu, CLI only)
- route - fixed false route type detection as blackhole;
- route - provide more detailed information about prefixes when using "discourse" tool;
- routing - moved "/interface bgp vpls" to "/routing bgp vpls" menu;
- routing-filter - fixed regexp community matcher;
- ssh - disable ssh-rsa when strong-crypto=yes and use rsa-sha2-sha256;
- ssh - implemented "server-sig-algs" extension in order to improve rsa-sha2-sha256 support;
- switch - disabled second CPU core for CRS328-24P-4S+ device in order to improve SFP+ link stability;
- vxlan - allow to specify MAC address manually;
- webfig - updated WebFig HTML files with the new MikroTik logo and removed Telnet option from index page;
- webfig - updated link to the WinBox executable;
- webfig - updated link to the documentation;
- wifiwave2 - fixed "frequency-scan" functionality (introduced in v7.3);
- winbox - add a log and log-prefix options to IPv6 firewall NAT and mangle rules;
- winbox - fixed IP/Route and IPv6/Route OSPF type value;
- winbox - removed unused "Apply Changes" button from BGP sessions menu;
- wireguard - fixed system stability when adding/removing WireGuard interface;
- wireless - fixed possible traffic flooding to WDS clients when using Nv2 and multicast helper;
- x86 - fixed keep old configuration functionality during x86 setup installation;
- x86 - improved log warning message on failed downgrade attempt;
- x86 - removed "hdd-model" information from installation screen;

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.