6.32.3 version released!

Tue Oct 20, 2015 10:45 am

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

What's new in 6.32.3 (2015-Oct-19 11:13):

*) switch - fixed CRS settings set back to defaults after a reboot;
*) netinstall - include missing RB1200 drivers;
*) firewall - fixed connection-rate matcher;
*) ppp, pptp, l2tp, pppoe: fixed router dead locked if compression was enabled on link;
*) quickset - create proper firewall rules when PPPoE is used for address acquisition;
*) sstp - fixed kernel crash when other party started to fragment ppp packets in the middle;
*) ippool6 - optimize same prefix acquisition;
*) winbox - Shift+Ins & Shift+Del did not work in multi entry fields;
*) winbox - allow to specify ipv6 address in traffic flow target;
*) winbox - allow to specify eap-radius-accounting in CAPsMAN;
*) winbox - allow to enter dns name in email server;
*) ups - fix console oid print;
*) tunnel - fix loopback keepalives on gre and ipip;
*) pptp,l 2tp, sstp, pppoe: do not send data packets before we have negotiated connection with other
side (happens on dial-on-demand interfaces), this brakes when connecting to other party servers;
*) pptp, l2tp, sstp - make it work when add-default-route & dial-on-demand both are enabled;
*) pptp, l2tp, sstp, pppoe clients - fixed problem where they failed to connect
at startup and only reboot helped;
*) nv2 - fixed kernel failure with frame size accounting;
*) ovpn client - fixed crash when ovpn didn't receive it's ip address;
*) lcd - fix slideshow for CCR1072, and possible sign issues for temperatures;
*) winbox - make console notice correct screen size;
*) ssh - allow to specify pass as argument for private key import;
*) winbox - refetch hotspot walled garden hit counter;
*) winbox - added client-connections & server-connections to web proxy status;
*) cerm - fix scep server certificate-reply degenerate PKCS#7 signed-data content;
*) bgp - specific BGP networks were changed to different ones;
*) cerm - allow export for all types except templates;
*) wlan - update brazil-anatel country;
*) winbox - fixed context menu actions to apply to all selected items;

Tue Oct 20, 2015 2:31 pm

Screenshot 2015-10-20 14.08.05.png

Let's open MikroTik.com download page.

current (channel) = new features + fixes*.
bugfix (channel) = fixes.

* - "new features+fixes" means latest tested features and fixes.

Let's have a closer look at 6.32
At the moment current channel is 6.32.3, the previous current version was 6.32.2. There are only bugfixes added to 6.32.3

New features are (will be) added to 6.33, they are already present in 6.33rc (Release candidate channel).

You can discuss version naming in new topic,
http://forum.mikrotik.com/viewtopic.php ... 53#p504153

Please remember this topic is about 6.32.3!

Tue Oct 20, 2015 2:37 pm

Upgraded test network to this version, so far so good.
Thanks, for connection-rate fix.

danielvc · Tue Oct 20, 2015 2:48 pm

Where can I see each country options? Brazil has 4 country options: brazil, brazil direct, brazil-922, brazil-anatel. What?????

kristaps · Tue Oct 20, 2015 2:58 pm

You can get info about channels,

in wire info country-info bra
"brazil direct" brazil brazil-922 brazil-anatel

[admin@Main_GW] > in wire info country-info brazil-anatel
ranges: 2402-2482/b,g,gn20,gn40(20dBm)/passive
5170-5250/a,an20,an40,ac20,ac40,ac80,ac160(10dBm)/passive
5250-5330/a,an20,an40,ac20,ac40,ac80,ac160(10dBm)/passive
5490-5710/a,an20,an40,ac20,ac40,ac80,ac160(15dBm)/passive
5730-5845/a,an20,an40,ac20,ac40,ac80,ac160(15dBm)

[admin@Main_GW] > in wire info country-info brazil-922
ranges: 912-932/b,g,gn20,gn40(30dBm)

[admin@Main_GW] > in wire info country-info "brazil direct"
ranges: 2402-2472/b,g,gn20,gn40(36dBm)/passive
2417-2457/g-turbo(36dBm)
5730-5845/a,an20,an40,ac20,ac40,ac80,ac160(36dBm)
5740-5820/a-turbo(36dBm)

Tue Oct 20, 2015 3:00 pm

nv2 fix was added to fix router occasional reboots in the specific configuration.

Eising · Tue Oct 20, 2015 4:28 pm

*) bgp - specific BGP networks were changed to different ones;

What does this mean?

MetUys · Tue Oct 20, 2015 5:19 pm

*) winbox - allow to enter dns name in email server;

This is only a once off adding in terminal and resolves immediately, not on each use.
it also cannot be set via winbox > tools > email, still only allows IP.

I guess I will have to wait for the RC to release where it has the options amended already.
was just hoping it would be in this version.

Device: RB951G-2HnD with ROS v6.32.3 Firmware v3.24

Knapek · Tue Oct 20, 2015 5:49 pm

nv2 fix was added to fix router occasional reboots in the specific configuration.

Hello, do I have to upgrade AP only or all Clients too for this fix?

Thanks Miroslav

leoktv · Tue Oct 20, 2015 5:52 pm

*) bgp - specific BGP networks were changed to different ones;

What does this mean?

Good qestion? i have not sean this problem in my network.

StubArea51 · Tue Oct 20, 2015 7:48 pm

Thanks MT....Working well on the following so far:

CCR1072-1G-8S+
CCR1036-8G-2S+

freemannnn · Tue Oct 20, 2015 7:56 pm

thanx for connection-rate fix

Tue Oct 20, 2015 7:59 pm

Upgraded test network to this version, so far so good.
Thanks, for connection-rate fix.

+1

thx a lot

darkmanlv · Tue Oct 20, 2015 11:50 pm

after upgrading to 6.32.3 speed of wan is degraded (also on 6.33 rc`s). now i got only ~ 270 MBit/s but with 6.32.2 i had ~330 MBit/s.

tried to downgrade to 6.32.2 and speed got back to 330 MBit/s

routerboard RB951G-2HnD

angboontiong · Wed Oct 21, 2015 9:02 am

any news wireless protocol to be introduce after nv2 ???

Wed Oct 21, 2015 11:40 am

Eising

This fix is for /1 /2 specific networks, in 6.32.2 networks were changed incorrectly.

[admin@rack1_b2] /routing bgp network> add network=0.0.0.0/1
[admin@rack1_b2] /routing bgp network> add network=128.0.0.0/1
[admin@rack1_b2] /routing bgp network> add network=0.0.0.0/2
[admin@rack1_b2] /routing bgp network> add network=64.0.0.0/2
[admin@rack1_b2] /routing bgp network> add network=128.0.0.0/2
[admin@rack1_b2] /routing bgp network> add network=192.0.0.0/2

[admin@rack1_b2] /routing bgp network> print
Flags: X - disabled
# NETWORK SYNCHRONIZE
0 0.0.0.0/25 yes
1 0.0.0.128/25 yes
2 0.0.0.0/26 yes
3 0.0.0.64/26 yes
4 0.0.0.128/26 yes
5 0.0.0.192/26 yes

Once again remember this is a topic about 6.32.3 version release. If you have suggestions about changelog or other features, post it in the appropriate thread.

infused · Thu Oct 22, 2015 1:39 am

So far this new release system is working well.

Good job Mikrotik.

sindudas · Thu Oct 22, 2015 5:42 pm

Certificate got issues. Version 6.32.3, 6.33rc29 and 6.33rc30. Downgrade to 6.30.4 it works.

When try to create CA and self-signed to use in www-ssl, it doesn't work. Can't open Router using www-ssl. If you create on 6.30.4, then upgrade to 6.32.3, it works, you can access to the router by www-ssl.

I create the certificates with this commands:

/certificate add name=ca-template common-name=CA-NAME key-usage=key-cert-sign,crl-sign country=XX days-valid=7300 locality=XXXX organization="XXXX" subject-alt-name=IP:X.X.X.X trusted=yes state=XXXX
/certificate add name=gw-template common-name=GW-CERT days-valid=7299 country=XX locality=XXXX state=XXXX organization="XXXX" subject-alt-name=IP:X.X.X.X trusted=yes

/certificate sign ca-template ca-crl-host=X.X.X.X name=CA-NAME
/certificate sign ca=CA-NAME gw-template name=GW-CERT

/certificate set GW-CERT trusted=yes

sindudas · Thu Oct 22, 2015 5:48 pm

Certificate got issues. Version 6.32.3, 6.33rc29 and 6.33rc30. Downgrade to 6.30.4 it works.

When try to create CA and self-signed to use in www-ssl, it doesn't work. Can't open Router using www-ssl. If you create on 6.30.4, then upgrade to 6.32.3, it works, you can access to the router by www-ssl.

I create the certificates with this commands:

/certificate add name=ca-template common-name=CA-NAME key-usage=key-cert-sign,crl-sign country=XX days-valid=7300 locality=XXXX organization="XXXX" subject-alt-name=IP:X.X.X.X trusted=yes state=XXXX
/certificate add name=gw-template common-name=GW-CERT days-valid=7299 country=XX locality=XXXX state=XXXX organization="XXXX" subject-alt-name=IP:X.X.X.X trusted=yes

/certificate sign ca-template ca-crl-host=X.X.X.X name=CA-NAME
/certificate sign ca=CA-NAME gw-template name=GW-CERT

/certificate set GW-CERT trusted=yes

With a downgrade to 6.30.4, an erase "GW-CERT" en creating again (maintaining the same CA-NAME), it works.

Fri Oct 23, 2015 3:29 pm

sindudas, what RouterBOARD do you use? I tried the same on my CCR board, everything worked fine.

Screenshot 2015-10-23 15.27.48.png

maxspeed · Sat Oct 24, 2015 4:21 am

Hi,

I can't find in the time zone name America/Montreal ... was available before with old firmware could you add it please.

Thank you

sindudas · Sat Oct 24, 2015 12:54 pm

sindudas, what RouterBOARD do you use? I tried the same on my CCR board, everything worked fine.

Screenshot 2015-10-23 15.27.48.png

Tested in hAP lite (smips).

Have you used the CA cert? Or have you used the Cert signed with your CA?

kadosc · Sat Oct 24, 2015 2:57 pm

Device rebooting randomly, I have a CCR-1016 being used as PPPoE concentrator, with about 1000 sessions, running MPLS, VPLS and TE TUNNELS and it just restarts several times during the day, any ideas? Some test that I can do?

Mon Oct 26, 2015 9:45 am

kadosc - Please generate supout file on your router after device has rebooted itself. Send this file to support@mikrotik.com

http://wiki.mikrotik.com/wiki/Manual:Su ... utput_File

Mon Oct 26, 2015 10:01 am

maxspeed - We just upgrade our list according to IANA. You should use Toronto time zone if I am not mistaking.

Mon Oct 26, 2015 12:01 pm

sindudas, Thank you very much for the report. There is an issue with CA signed certificates, that does not have K (or signed). It is already fixed for the next versions.

nas · Fri Oct 30, 2015 2:29 pm

working well on basic config 2011, the only difference is memory usage +4Mb

Basdno · Tue Nov 03, 2015 9:52 pm

No new posts since 30 October, and overall few post at all in this version!!!

I take that as a VERY GOOD sign that this version is working very well !

Am I right in the assumption that ROS 6.32.3 is working nicely and stable?

It has worked nice on the routers I have tested, and am now considering if I should dare to move my production routers ahead to 6.32.3!?

Wed Nov 04, 2015 1:41 am

I think so too. No problems in my lab but will be waiting for some time more and then will be deploying in the waves...

Kraken2k · Wed Nov 04, 2015 1:50 pm

Problem with router cache owerflow caused by sending traffic over IPsec tunnels still persists in this release, despite the fact the Router Cache feature is turned off.

Ticket number #2015081766000633

marcodefreitas · Thu Nov 05, 2015 6:10 am

Device rebooting randomly, I have a CCR-1016 being used as PPPoE concentrator, with about 1000 sessions, running MPLS, VPLS and TE TUNNELS and it just restarts several times during the day, any ideas? Some test that I can do?

Disable compression on PPP Profiles.

timberwolf · Thu Nov 05, 2015 10:22 am

Problem with router cache owerflow caused by sending traffic over IPsec tunnels still persists in this release, despite the fact the Router Cache feature is turned off.

Ticket number #2015081766000633

In which constelation? Pleain IPSec or in combination with L2TP maybe?

Kraken2k · Thu Nov 05, 2015 2:16 pm

Problem with router cache owerflow caused by sending traffic over IPsec tunnels still persists in this release, despite the fact the Router Cache feature is turned off.

Ticket number #2015081766000633
In which constelation? Pleain IPSec or in combination with L2TP maybe?

We do not use L2TP, so plain one. Not sure why is this happening, because this is just problem of the central site with many tunnels - routers on the other ends are ok. On this site however, there are possibly the entries that does not get flushed and stack in the cache (despite the fact, that IP cache is turned off in settings), until the cache overflows and all IPv4 traffic stops to flow until the router is rebooted (cache cannot be flushed manually).

Since there is no way how to see the IP route cache content, I have no idea what causes it, but the other router with the same configuration (used as backup using VRRP) has no problem, when IPsec tunnels are disabled, or there is no traffic over the tunnels - the route cache does not constantly grow in this case.

I opened a ticket some time ago, but after few e-mails and unsuccessful attempts to repair it (like turning off the cache), support stopped to respond.

Basdno · Fri Nov 06, 2015 11:31 pm

And there it got confirmed by Mikrotik!

6.32.3 is new BUGFIX release!

Nice!

Then I can start using it in production envirnoment!

Mikrotik: MEGA KUDOS on the new release system and your VERY nice release notes on latest 6.33 CURRENT version!

Keep up the good work!

PS: BTW maybe an idea to stickynote this thread on top of forum since it is now new BUGFIX Version?!

WirelessRudy · Mon Nov 09, 2015 11:47 am

And there it got confirmed by Mikrotik!

6.32.3 is new BUGFIX release! Nice!

Then I can start using it in production envirnoment!

Mikrotik: MEGA KUDOS on the new release system and your VERY nice release notes on latest 6.33 CURRENT version!

Keep up the good work!

PS: BTW maybe an idea to stickynote this thread on top of forum since it is now new BUGFIX Version?!

So now you can realize why this new naming is wrong:

6.32.3 is according MT now the new BUGFIX version. You can now use it to put as the current version for your network since it probably won't need bugs to be fixed no more.... So I would call this a "Current" version.

6.33 CURRENT is now a release candidate version since it still might have bugs to be fixed. You might also call it BUG FIX version.

And what is now the release candidate version, well, these are just beta......

And by naming this new version 6.33. "Current" and put it as the preferred version on the website etc. again users are being mislead into believing this is a stable version. Well, as long as not proven so it is not.....

But I have the feeling I am fighting a lost battle here...... I think I'd better re-write my dictionary.... pffff

Mon Nov 09, 2015 11:53 am

It is actually called "Bugfixes only" version. It means that any updates in this chain will only contain bugfixes, no features.

Thu Nov 12, 2015 1:58 pm

It is necessary to admit that mikrotik is putting these labels according to their point of view. But we all are looking on it from the opposite side. We, who have some experience with these things can easily understand. So it is not so much important for me what version has what label because I am still taking care what is actual situation. But unfortunately mikrotik is more and more oriented on BFU / SOHO segment. And these are the customers who are going to be disorientated.

Thu Nov 12, 2015 1:59 pm

It is necessary to admit that mikrotik is putting these labels according to their point of view. But we all are looking on it from the opposite side. We, who have some experience with these things can easily understand. So it is not so much important for me what version has what label because I am still taking care what is actual situation. But unfortunately mikrotik is more and more oriented on BFU / SOHO segment. And these are the customers who are going to be disorientated.

WirelessRudy · Fri Nov 13, 2015 1:06 am

It is necessary to admit that mikrotik is putting these labels according to their point of view. But we all are looking on it from the opposite side. We, who have some experience with these things can easily understand. So it is not so much important for me what version has what label because I am still taking care what is actual situation. But unfortunately mikrotik is more and more oriented on BFU / SOHO segment. And these are the customers who are going to be disorientated.

Indeed!

Fri Nov 13, 2015 10:41 am

I was just clarifying to WirelessRudy, who seems to misunderstand how these release chains work:

since it still might have bugs to be fixed. You might also call it BUG FIX version.

Bugfix doesn't mean that there are bugs to be fixed. Bugfix means that only bug fixes can be expected, not features. It is actually the most stable of the release chains.

WirelessRudy · Fri Nov 13, 2015 2:02 pm

Bugfix doesn't mean that there are bugs to be fixed. Bugfix means that only bug fixes can be expected, not features. It is actually the most stable of the release chains.

And therefore should be called "current". That is the only word understood by any new user or less experienced MT users.

If somebody asked me; "What is the current to be used OS version?" I should be able to answer; "The one called "current".
But now my answer will be "The one called "Bugfix". So the cuestionar is now raising his eyebrows and asks; "So it is a bug fix? There were some bugs?"... or he asks; " "Bugfix"? Does that means it still needs to have some bugs fixed?"

Now you need to explain "Bugfix" means that probably all bugs are fixed and the unit is "currently" the best OS version......
So then the same guy asks; "What about that version presently called "current"?" I have to tell him better not to use it if he doesn't need the latest new features in it. Because it is not considered 100% free of bugs yet. So 'currently' it is better not to use it..... It is actually a version should be tested more and you wouldn't depend you business on it....."

So he replies; "Ah, its a 'beta version' or release candidate!" Now I reply; "Well yes, but MT also have even newer version called "release candidate" or 'beta version'.....
Now this persons shakes his head and asks me again; "So, tell me now, which version is best to use on my current system that I can use without problems?" And I reply, the "bugfix" version. NOT the current....."

The guy leaves home, a bit in despair. At home he goes to the MT-website to download a new OS as recommended for first use. He clicks on the download menu and finds a section to download several versions. Since he is so tired now he forgets to read carefully and just clicks on "mipsbe" and gets more questions asked. After reading some he thinks; "I need the 'Main package'" and clicks on the link.....

Since by default the "Current" option is presented, he now downloads a version he should NOT.... Well, he doesn't know, installs it and if he (and thus MT development) is lucky it runs and everybody happy....
If not, it crashes or whatever, he probably gets very irritated and goes to the shop to by another brand router........another client lost forever.......

I don't know how I can explain it any clearer. But the fact this discussion seems to raise questions over and over again means it is not clear.
But whatever, I know what to guard for so I am not affected.....

Fri Nov 13, 2015 2:21 pm

I'm thinking you are overreacting.

We have reached the point in 6.xx version where almost everything works (compare to beginning of 6.x)
If somebody asks what version to use - answer is any that is available on download page.

there are only 2 key differences:

1) version lifespan on site (bugfix - months, current - weeks, RC - days/hours),so when you finally encounter a problem with bugfix there are much less chance that support will ask to upgrade to latest version.

2) how long was the version tested before becoming available in corresponding channel. I was running 6.32.x in one way or another on my network for 2 month and fact that is is moved to bugfix is pleasing, gives me confidence.

This is trade off, all clients everywhere might be devided into 2 groups, ones that need new features, and others that need stability, with just one release it was impossible now ones can try RC others get Bugfix, and current is just a middle stone to get from one to another

WirelessRudy · Fri Nov 13, 2015 2:47 pm

I'm thinking you are overreacting.

Using a lot of text doesn't mean I am overreacting. I am trying to explain why the confusion is still there. Some say there is not, but some other in fact are..... so I try to explain why I can understand the confusion is there. Not overreacting.

We have reached the point in 6.xx version where almost everything works (compare to beginning of 6.x)
If somebody asks what version to use - answer is any that is available on download page.

Well, that argument only goes up to the next disaster that is going to be released. It happened in the past, why should that not happen in the future? I do not agree with this argument. We cannot relay on ANY software development (I mean ANY because it happens with all kinds of programs. Windows, Airbus plane software system, car software etc.). Unless Mikrotik developers are some super humans disasters will happen. We only don't know when....

Fri Nov 13, 2015 3:01 pm

Unless Mikrotik developers are some super humans disasters will happen.

maybe no super human, but they are close, consider that whole company have ~160 employees , all RouterOS is made by 20-30 people max. So My personal opinion , is that having a separate version that lifespan is month are very nice additional, maybe naming is off, but it really doesn't matter how you call them, as long as they provide what you need.

I personally just look at 6.xx and 6.xx.y, choose 6.xx that have all features that you need , and then just upgrade to new y versions, it already eliminates most of upgrading problems from the past.

Fri Nov 13, 2015 3:13 pm

I am trying to explain why the confusion is still there. Some say there is not, but some other in fact are..... so I try to explain why I can understand the confusion is there.

The truth is even if you convince Mikrotik to change their release channel naming conventions the confusion will not disappear. You will probably be satisfied, but there definitely are other people who won't. It's arguable which group is bigger.

Different people may have different opinions about what CURRENT should mean. For me (as a long-term FreeBSD fan) CURRENT means "bleeding edge". YMMV. It will be good if Mikrotik put a brief explanation about their release channel naming conventions right at the top of the download page. Other then that, I don't see why anything should necessarily be changed.

cdemers · Sun Nov 15, 2015 9:47 pm

Maybe a better term for the Bugfix version is Stable.

Sent from my Nexus 5 using Tapatalk

Mon Nov 16, 2015 9:16 am

Yes, Current is like andriys understood it:

current
adjective
1 present-day, present, contemporaneous, ongoing; topical, in the news, live, alive, happening, burning; modern, latest, popular, fashionable, in fashion, in vogue, up to date, up to the minute;

Bugfixes only no longer gets updated with features or major changes. We add bugfixes only.

juanvi · Fri Nov 27, 2015 12:10 pm

Can't kill an OVPN connection. Client is no more connected and his connection is not idle detected for timeout from profile.

Disabled secret and killed active connection from winbox and console and appears again!

If Itry to connect this tunnel again the log says "user xxx is already active" Reboot cloud core is the only solution and cant do it now!

What is happening?

ROS 6.32.3 on CCR 1036 12g-4s and basebox2

Testing MT suggestions.Seems it works fine: Use ovpn server keepalive timeout (seconds) AND idle time of ppp profiles. Must have the two active. Thaks Martins S.

Who is online