![]() Also, make sure you don’t power off the router or use its buttons during the installation, if you wish avoid any malfunctions. 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. 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. Basically, you must upload the new firmware to the router through its administration page and allow it to upgrade. 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. wireless - reduced load on CPU for high speed wireless links īefore 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.ĭue 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. winbox - removed spare values from "loop-protect" setting for EoIPv6 tunnels winbox - fixed firewall port selection with Winbox v2 winbox - do not allow to open multiple same sub-menus at the same time traffic-flow - fixed IPFIX IPv6 data reporting tile - fixed rare encryption kernel failure when small packets are processed tile - fixed EoIP keepalive when tunnel is made over VLAN interface switch - fixed disabling of MAC learning on CRS1xx/CRS2xx sniffer - fixed VLAN tags when sniffing all interfaces quickset - fixed LTE "signal-strength" graphs queue - fixed queuing when at least one child queue has "default-small" and other/s is/are different (introduced in 6.35) pppoe-server - fixed "one-session-per-host" issue where 2 simultaneous sessions were possible from the same host pppoe-client - removed false warning from client interface if it starts running on non-slave interface pppoe - fixed warning on PPPoE server, when changing interface to non-slave interface ppp - send correct IP address in RADIUS "accounting-stop" messages (introduced in 6.39) ppp - fixed MLPPP over multiple channels/interfaces (introduced in v6.39) ppp - fixed "change-mss" functionality (introduced in 6.39) ![]() ![]() lte - replaced "user-command" with "at-chat" command lte - improved relialibility on SXT LTE lte - improved info channel background polling led - fixed turning off LED when interface is lost ipv6 - fixed address becoming invalid when interface was removed from bridge/mesh ipsec - renamed "remote-dynamic-address" to "dynamic-address" ipsec - fixed peer "my-id" address reset ipsec - fixed generated policy priority ike2 - fixed situation when traffic selector prefix was parsed incorrectly ike2 - fixed rare kernel failure on address acquire ike1 - removed xauth login length limitation firewall - fixed "address-list" entry changing from IP to DNS and vice versa firewall - do not allow to set "rate" value to 0 for "limit" parameter firewall - fixed "address-list" entry "creation-time" adjustment to timezone fetch - fixed "user" and "password" argument parsing from URL for FTP export - removed spare "caller-id-type" value from compact export console - fixed "No such file or directory" warnings on upgrade reboots conntrack - load IPv6 connection tracking independently from IPv4 bridge - fixed connectivity between bridges when "fast-forward" feature is enabled bonding - do not add bonding interface if "could not set MTU" error is received 6to4 - fixed wrong IPv6 "link-local" address generation
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |