v6.39rc [release candidate] is released

What’s new in 6.39rc4 (2016-Dec-30 07:16):

!) ppp - completely rewritten internal fragmentation algorithm (when MRRU is used), optimized for multicore;
*) capsman - added CAP discovery interface list support;
*) ethernet - renamed “rx-lose” to “rx-loss” in ethernet statistics;
*) health - report fan speed for RB800 and RB1100 when 3-pin fan is being used;
*) led - show warning on print when “modem-signal-threshold” is not available;
*) lte - added error handling for remote AT execute;
*) wAP ac - improved 2.4GHz wireless performance;
*) wireless - added “station-roaming” setting (cli only);
*) wireless - show comment on “security-profile” if it is set (cli only);

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.

Would you be so kind and shed some light on this line in the changelog:

*) wireless - added “station-roaming” setting (cli only);

Here is information about this station-roaming:
http://wiki.mikrotik.com/wiki/Manual:Interface/Wireless#Station_Roaming

Now you can disable station-roaming if you do not want it or, for example, if you have P2P using 802.11 protocol were you don’t have another AP to connect to.

Hi Guys,

Can I please have more info on *) wAP ac - improved 2.4GHz wireless performance;

e.g. under what situations is performance “improved” ?

I ask as we have had issues with the wAP AC’s 2.4Ghz radios and performance to Samsung android devices, as well as WPA group-key issues..

When I installed the firmware 6.39 rc4 was my ovpn connection interrupted.
After back downgrade to 6:36 bugfix everything was ok.
This somehow seems like a bug

“ppp optimized for multicore” - on all platforms?

I forgot to mention that the firmware proved a rb3011.
Mikrotik will have to resolve this isseu. This is a bug.

I hope this one: http://forum.mikrotik.com/t/bad-connection-only-in-channel-6/103910/1

I’ll try the RC and see if it helps.


are there plans to add NAT for IPv6 ?
at home i have dynamic ipv6 from the provider and a static ipv6 net with no flatrate at tunnelprovider.
the simplest solution is to NAT unknown networks und known networks without NAT for static firewall config.

Station Roaming feature is available only for 802.11 wireless protocol. when we use background scan on nv2 and use station roaming. is there any work for nv2.

Please add HTTP POST and HTTP GET to the Dude’s notification feature.
This will allow integration into 3rd-party applications such as Telegram (https://core.telegram.org/bots/api).
Quite important to allow toggling between secure and non-secure connections.

It is clarified in the manual: http://wiki.mikrotik.com/wiki/Manual:Interface/Wireless#Station_Roaming

Version 6.39rc7 has been released.
Changes since previous rc:
*) bridge - fixed MAC address learning from switch master-port;
*) capsman - support for communicating frame priority between CAP and CAPsMAN;
*) dhcpv6-client - fixed dhcpv6 rebind on startup;
*) dns - fixed typo in regexp error message;
*) dude - (changes discussed here: http://forum.mikrotik.com/t/the-dude-v6-39rc-test-builds/104888/1);
*) firewall - nat action “netmap” now requires to-addresses to be specified;
*) ike2 - allow empty selectors to reach policy handler;
*) ike2 - fixed error packet from initiator on responder reply;
*) ike2 - fixed ph1 initial-contact rare desync;
*) ike2 - fixed traffic selector prefix calculation;
*) ike2 - show peer identity of connected peers;
*) ike2 - update also local port when peer changes port;
*) ipsec - fixed flush speed and SAs on startup;
*) ipsec - fixed peer port export;
*) ipsec - port is used only for initiators;
*) leds - added lte modem access technology trigger;
*) log - added warning when winbox/dude sessions was denied;
*) log - improved firewall log messages when NAT has changed only connection ports;
*) mmips - improved general stability;
*) ovpn - fixed address acquisition when ovpn-in interface becomes slave;
*) proxy - fixed “max-cache-object-size” export;
*) proxy - speed-up almost empty disk cache clean-up;
*) rb1100ahx2 - fixed random counter resets for ether12,13;
*) ssh - fixed high memory consumption when transferring file over ssh tunnel;
*) wireless - fixed issue when wireless interfaces might not show up in CAP mode;
*) wireless - fixed occasional crash on interface disabling;

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.

I’ve requested this 2 years ago but the NAT Nazis say “it’s wrong”. Because some IPv6/end2end connectivity ideologists said so.
Those ‘No-NAT-on-IPv6’ people are becoming worse than Apple fanboys :stuck_out_tongue:
http://forum.mikrotik.com/t/feature-request-ipv6-nat66-support/82264/1

And a more comprehensive post about NAT usefulness in IPv6 by ZeroByte http://forum.mikrotik.com/t/ipv6-and-nat-how-i-changed-my-mind/100481/1

Please do not hijack versoin topic with questions which are not related to release itself.

timtasse, deathmagicmedia - You should create new topic with your request and/or write to support.

Hello

!) ppp - completely rewritten internal fragmentation algorithm (when MRRU is used), optimized for multicore;

Can you clarify if this adds any new features for PPP / MRRU? Does this mean that you have added (or will add) PPP Fragmentation reordering / buffering to fix the case where MRRU fragments come in our of order?

–Greg

LED off is only for "Currently “RB cAP 2n” and “RB cAP 2nD” ?

I’ve got the Error on my HAP AC (mipsbe):

[benoga@HAP_AC] > /system leds setting set all-leds-off=immediate
missing values (5)

When HAP AC not support this, then please disable the Setting in CLI and Winbox :slight_smile:
greez

Kalpar - Yes, that is exactly what was done! MRRU works in same way as it did before, but it is now adjusted/updated to multi core age

Rebinding or renewing? And only on startup?
However, the new version solves my problem at least partially.

As I have already described in this thread, DHCPv6 is broken for me since v6.34, If the connection is lost, renewing and rebinding takes 20 minutes. Since v6.39rc this time has been reduced to 10 minutes.

Before v6.34:
PPPoE connected —> status: bound

After v6.34:
PPPoE connected —> status: rebinding —> 10 minutes waiting —> status: renewing —> 10 Minutes waiting —> status: bound

After v6.39rc:
PPPoE connected —> status: rebinding —> 10 minutes waiting — status: bound

http://forum.mikrotik.com/t/v6-38rc-release-candidate-is-released/102037/331

I used this command when I scheduled a PPPoE reconnect: ipv6 dhcp-client release 0;