v6.39.2 [current]

To upgrade, click “Check for updates” at /system package in your RouterOS configuration interface, or head to our download page: http://www.mikrotik.com/download

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

What’s new in 6.39.2:
*) 6to4 - fixed wrong IPv6 “link-local” address generation;
*) arp - fixed “make-static”;
*) bonding - do not add bonding interface if “could not set MTU” error is received;
*) bridge - fixed connectivity between bridges when “fast-forward” feature is enabled;
*) conntrack - load IPv6 connection tracking independently from IPv4;
*) console - fixed “No such file or directory” warnings on upgrade reboots;
*) export - removed spare “caller-id-type” value from compact export;
*) fetch - fixed “user” and “password” argument parsing from URL for FTP;
*) firewall - fixed “address-list” entry “creation-time” adjustment to timezone;
*) firewall - do not allow to set “rate” value to 0 for “limit” parameter;
*) firewall - fixed “address-list” entry changing from IP to DNS and vice versa;
*) gps - removed duplicate logs;
*) ike1 - fixed crash on xauth message;
*) ike1 - removed xauth login length limitation;
*) ike2 - fixed rare kernel failure on address acquire;
*) ike2 - fixed situation when traffic selector prefix was parsed incorrectly;
*) ipsec - fixed generated policy priority;
*) ipsec - fixed peer “my-id” address reset;
*) ipsec - renamed “remote-dynamic-address” to “dynamic-address”;
*) ipv6 - fixed address becoming invalid when interface was removed from bridge/mesh;
*) led - fixed turning off LED when interface is lost;
*) lte - improved info channel background polling;
*) lte - improved relialibility on SXT LTE;
*) lte - replaced “user-command” with “at-chat” command;
*) ppp - fixed “change-mss” functionality (introduced in 6.39);
*) ppp - fixed MLPPP over multiple channels/interfaces (introduced in v6.39);
*) ppp - send correct IP address in RADIUS “accounting-stop” messages (introduced in 6.39);
*) pppoe - fixed warning on PPPoE server, when changing interface to non-slave interface;
*) pppoe-client - removed false warning from client interface if it starts running on non-slave interface;
*) pppoe-server - fixed “one-session-per-host” issue where 2 simultaneous sessions were possible from the same host;
*) queue - fixed queuing when at least one child queue has “default-small” and other/s is/are different (introduced in 6.35);
*) quickset - fixed LTE “signal-strength” graphs;
*) sniffer - fixed VLAN tags when sniffing all interfaces;
*) snmp - fixed limited walk;
*) switch - fixed disabling of MAC learning on CRS1xx/CRS2xx;
*) tile - fixed EoIP keepalive when tunnel is made over VLAN interface;
*) tile - fixed rare encryption kernel failure when small packets are processed;
*) traffic-flow - fixed IPFIX IPv6 data reporting;
*) winbox - do not allow to open multiple same sub-menus at the same time;
*) winbox - fixed firewall port selection with Winbox v2;
*) winbox - fixed LTE info button;
*) winbox - removed spare values from “loop-protect” setting for EoIPv6 tunnels;
*) wireless - reduced load on CPU for high speed wireless links;

I just popped this on a ccr1009 and it removed all the settings from my main pppoe client interface preventing it from connecting to the internet.

The upgrade auto disabled ipv6 package.

Neither of those things happened on my 1100AHx2 - PPPoE client and IPv6 are still there and enabled.

same here - so far so good.

You, used the bundle package for the upgrade?
On what RouterBOARD you saw this and what RouterOS version you had before?

Same here on an RB850Gx2.

Yes, bundle package.

It happens on CCR1009-8G-1S / RB912UAG-2HPnD / RB912UAG-5HPnD / CRS125-24G-1S. All upgrading from 6.39.1 to 6.39.2.

support.rif sended.

lty1993 - Was bundle installed on device before an upgrade? All devices were running 6.39.1 with bundle package installed and IPv6 package enabled and after upgrade package got disabled? Can you upgrade device, make sure package is disabled, without any reboots in the middle generate supout file and send it to support@mikrotik.com together with explanation of your problem?

We have tested this here locally with same packages, versions and different devices and problem does not appear. Either this is something very specific or actually IPv6 package was scheduled to be disabled after reboot and administrator forgot about it and simply the next reboot was upgrade.

ebreyit - Client is not changed within this version. maybe you did by accident change something in QuickSet?

I don’t use quickset.

original version 6.39.1

upgrade to 6.39.2 via system > packages

on reboot pppoe-client was there but contained no settings as If I had just gone to create new one


Other packages I have installed are NTP and GPS

Updated my RB2011 from 6.39.1 and no issues. I have IPv6 (HLE tunnel broker) and VPNs (using OVPN) working fine.

Nothing about dude in this version? I should post some feature requests to move the dude development forward a bit… Lol.

Upgraded with no problems on RB750Gr2 from 6.39.1 (l2tp/ipsec server, 6to4 broker, pppoe-client, snmp), RB951Ui-2HnD from 6.39.1 (l2tp/ipsec client, simple queue, samba), hAP lite from 6.38.5 and hAP ac lite from 6.39.1.

CCR 1016-12G, 3 x CRS125-24G, 7 x RB951G, 2 x SXT5AC and 3 CHR’s no issue at all. 6.39.1 to 6.39.2

Updated my RB2011 from 6.39.1 and found no issues.

Just upgraded 15 wAP ac and RB751U running in CAP mode from 6.39.1 without any problems.

I have updated 4 CCR1072 units without any problems
PPP accounting-stop was fixed!

CRS125-24G-1S 6.39.2

CISCO 2911 15.5

ip ipsec proposal print
Flags: X - disabled, * - default
0 * name=“default” auth-algorithms=sha1 enc-algorithms=aes-256-cbc lifetime=30m pfs-group=modp1024

Flags: X - disabled, D - dynamic, R - responder
0 address=65.29.2.3/32 auth-method=pre-shared-key secret=“qwwerr” generate-policy=no policy-template-group=default exchange-mode=main
send-initial-contact=yes nat-traversal=no proposal-check=obey hash-algorithm=sha1 enc-algorithm=aes-256 dh-group=modp1024 lifetime=1d dpd-interval=2m
dpd-maximum-failures=5



GRE, ph2
19:46:40 ipsec 65.29.2.2 ignore RESPONDER-LIFETIME notification.
19:46:40 ipsec Expecting IP address type in main mode when using preshared key for authorization (see RFC 2409 section 5.4),but FQDN.
19:46:40 ipsec 65.29.2.2 invalid ID payload
i tried auto, address … not working

how to fix?

Updated:

RB2011 (2 x )
RB962
RB951-2n (2 x )
RB750 Gr3
Omnitik


No issues at all.