v6.32 released [version temporarily removed]

Tue Sep 01, 2015 1:48 pm

TEMPORARY DELAY due to Basebox 2 upgrade issue. Version pulled.

==========================================

What's new in 6.32 (2015-Aug-31 14:47):

*) trafflow - added support for IPv6 targets;
*) switch - fixed port flapping on switch ports of RB750, RB750UP, RB751U-2HnD and RB951-2N (introduced in 6.31)
*) ipsec - added compatibility option skip-peer-id-check;
*) flash - fix kernel failure (exposed by 6.31);
*) bridge firewall - add ipv6 src/dst addr, ip protocol, src/dst port matching to bridge firewall;
*) RB911/RB912 - fix SPI bus lock after fast led blink;
*) ipsec - fix potential memory leak;
*) bridge firewall - vlan matchers support service tag - 0x88a8;
*) ippool6 - try to acquire the same prefix if info matches recently freed;
*) crs switch - allow to unset port learn-limit, new default is unset to allow more than 1023 hosts per port;
*) x86 - fixed 32bit multi-cpu kernel support;
*) chr - add hotspot,btest,traffgen support;
*) revised change that caused reboot by watchdog problems introduced in v6.31;
*) ipsec - use local-address for phase 1 matching and initiation;
*) ipsec - fix transport mode ph2 ID ports when policy selects specific ip protocol on initiator;
*) certificates -fixed bug where crl stopped working after a while;
*) ip accounting - fixed kernel crash;
*) snmp - fix system scripts get;
*) hotspot - ignore PoD remote requests if no HotSpot configured;
*) hotspot - fix kernel failure when www plugin aborts on broken html source;
*) torch - add invert filter for src/dst/src6/dst6 addresses ;
*) bonding - add min_links property for 802.3ad mode;
*) snmp - get vlan speed from master interface;
*) hotspot - fix html-directory path on small flash devices;
*) mipsbe - make system shutdown work again;
*) lcd - fixed parallel port LCD display support on multi-cpu x86;
*) bridge - fixed use-ip-firewall-for-vlan in setups with multiple bridges;
*) ipv6 - fixed DHCP-PD client skips some steps when renewing lease;
*) upnp - fixed protocol port selection for upnp protocol comunications;
*) firewall - fixed limit and dst-limit options.
*) winbox - fixed wireless interface l2mtu (VirtualAP and WDS interface creation in winbox)
*) winbox - fixed multiple firewall rule moving in Winbox 2
*) simple queues - restrict all changes in dynamic simple queues

Tue Sep 01, 2015 2:06 pm

Thanks for adding the 802.3ad min_links setting, and all the ipsec improvements.

CyberTod · Tue Sep 01, 2015 2:18 pm

I don't see a fix for loosing management access in some rare occasions after few minutes of uptime (ports are open, but can't login). Is it even reproduced by Mikrotik staff and acknowledged as a bug ?

Tue Sep 01, 2015 2:24 pm

I don't see a fix for loosing management access in some rare occasions after few minutes of uptime (ports are open, but can't login). Is it even reproduced by Mikrotik staff and acknowledged as a bug ?

do you have a ticket number I could check ?

Tue Sep 01, 2015 2:25 pm

I don't see a fix for loosing management access in some rare occasions after few minutes of uptime (ports are open, but can't login). Is it even reproduced by Mikrotik staff and acknowledged as a bug ?

What bug? details? Have you actually written to support? Ticket number?

Over the years i find this type of posts completely useless and annoying in most cases solved by fixing configuration or networking problems

Chupaka · Tue Sep 01, 2015 2:36 pm

*) firewall - fixed limit and dst-limit options.

requesting more details on this =)

WirelessRudy · Tue Sep 01, 2015 2:47 pm

Nothing learned?

Again a new "current" version that is going to be downloaded by many in thinking that because it is "current" it is stable.... A new disaster in the waiting?

6.30.4 is a better candidate for "Current" because it is fixed some times now (4x) without adding new features that might bring new bugs.....

This 6.32 should still be a candidate. Only the first weeks will tell its stable.....

Tue Sep 01, 2015 2:48 pm

WirelessRudy, please read the post about how the releases are done. I see you have not understood the terminology or release method.

CyberTod · Tue Sep 01, 2015 3:15 pm

There were numerous complaints about this in the v6.31 topic. I have not written to support, because I have only 1 affected device. It is not reachable (can't login to make supout) and I can not powercycle it. I am waiting for some power outage so I can log in and upload older or newer fixed routeros.

WirelessRudy · Tue Sep 01, 2015 3:16 pm

WirelessRudy, please read the post about how the releases are done. I see you have not understood the terminology or release method.

Normis, please read all the confusion it has been given to many of us and all the suggestions given to improve the numbering.

The simple fact that a new "current" version is published with many new features that now is going to be 'test' by the ignorants or the 'auto update script' users is every time again creating a disaster. We've just seen it with 3.31......

This version CANNOT be stable only because you guys call it "Current". This is proven over and over again and I don't understand nothing is learned.....

Time will tell but this new 3.32 will probably cause havoc again.....

Tue Sep 01, 2015 3:28 pm

translation of current:

current (adjective; cur·rent \ˈkər-ənt, ˈkə-rənt\)
happening or existing now : belonging to or existing in the present time

example: /current month/

It means the one that is released now. It does not mean best or most stable.

use the bugfix branch and just do not open this topic. ignore it. you are not forced to test the new features

honzam · Tue Sep 01, 2015 3:48 pm

Normis: Release candidate (rc6) od web page is now older than current.
Remove RC from webpage until you have 6.33rc. It's confusing...

vortex · Tue Sep 01, 2015 3:50 pm

And people should not necessarily a expect a 6.31.1 to happen, if 6.31 is so broken.

6.31 should be marked as withdrawn and not be downloadable anymore.

Nova · Tue Sep 01, 2015 4:01 pm

What confuses me is if this version 6.32, has the bug fixes of 6.30.4, or the only way to get that bugs fixed is to stay in 6.30.4 and never ever more update.

Tue Sep 01, 2015 4:05 pm

Normis: Release candidate (rc6) od web page is now older than current.
Remove RC from webpage until you have 6.33rc. It's confusing...

you are right

Tue Sep 01, 2015 4:06 pm

What confuses me is if this version 6.32, has the bug fixes of 6.30.4, or the only way to get that bugs fixed is to stay in 6.30.4 and never ever more update.

yes

6.32 has all the fixes from 6.30.4 + new features

but as you know, sometimes adding new stuff, can introduce unknown issues. this is why you can stay on 6.30.4 if you don't need any particular thing from the above changelog

weissmann · Tue Sep 01, 2015 4:23 pm

Hi everyone!
Just to report a failure with this version. We had a number of Basebox2 with R11e-5HacD daughterboards just waiting to be installed and we thought we would give it a try.
After upgrade, it would not let Winbox in. Http did not work either. Resetting configuration did not help. So we had to rollback to 6.30.4 via netinstall.
Kind regards,
Michael

pbr3000 · Tue Sep 01, 2015 4:30 pm

I don't see a fix for loosing management access in some rare occasions after few minutes of uptime (ports are open, but can't login). Is it even reproduced by Mikrotik staff and acknowledged as a bug ?
do you have a ticket number I could check ?

Normis, we can't make the supout file when this happens because the router losts access completely. No ssh, no winbox, telnet, mac-telnet etc. It just responds to pings. I noted that it needs a high usage pattern too. If the router stays on idle most the time this problem could not occur.

juanvi · Tue Sep 01, 2015 4:31 pm

Hi everyone!
Just to report a failure with this version. We had a number of Basebox2 with R11e-5HacD daughterboards just waiting to be installed and we thought we would give it a try.
After upgrade, it would not let Winbox in. Http did not work either. Resetting configuration did not help. So we had to rollback to 6.30.4 via netinstall.
Kind regards,
Michael

Broke 34 basebox2 with r11e too. Netinstall only exit. This can't happen with a non RC release. please help. Hour of hard work for now because capsman2 auto update!

Tue Sep 01, 2015 4:42 pm

Which version did you guys upgrade from ?

madmucho · Tue Sep 01, 2015 4:43 pm

RB912UAG-5GPnD, same behavior after update, cannot access administration using any method.

Please put that version down from mirrors, contains bug

weissmann · Tue Sep 01, 2015 4:48 pm

Which version did you guys upgrade from ?

Mine was 6.29.1 from factory.

juanvi · Tue Sep 01, 2015 4:49 pm

6.31rc10 and 6.32rc6

Tue Sep 01, 2015 4:52 pm

We have removed the v6.32 download for now (some might still see it due to cache) until we investigate

Tue Sep 01, 2015 4:59 pm

Are you all using wireless-fp or wireless-cm2 on those Baseboxes?

bajodel · Tue Sep 01, 2015 5:00 pm

As said already yesterday..

Board: 912UAG-2HPnD
Coming from Ros (netinstall): 6.30.4 or 6.31 (absolutely clean config)

Upgrading to 6.32rc6 or 6.32 (today released & now suspended) the 912UAG-2HPnD cannot be accessed winbox/telnet/mac_telnet/web
Impossibile to generate a supout ..in order to regain access I need to netinstall again.

Netinstalling directly to (bundle) 6.32 ..the board has the same problem.

Tue Sep 01, 2015 5:01 pm

bajodel - do you have a wireless card installed? if yes, which one? which wireless package do you use ?

bajodel · Tue Sep 01, 2015 5:04 pm

As said already yesterday..

Board: 912UAG-2HPnD
Coming from Ros (netinstall): 6.30.4 or 6.31 (absolutely clean config)

Upgrading to 6.32rc6 or 6.32 (today released & now suspended) the 912UAG-2HPnD cannot be accessed winbox/telnet/mac_telnet/web
Impossibile to generate a supout ..in order to regain access I need to netinstall again.

Netinstalling directly to (bundle) 6.32 ..the board has the same problem.

..&.. also netinstalling only system package 6.32 to 912UAG-2HPnD leads to the same problem

P.S.(1) No added wireless card (mPCie) ..only the onboard one
P.S.(2) Normally I enable cm2 package ..but also netinstalling system_only_pck leads to the problem

WirelessRudy · Tue Sep 01, 2015 5:08 pm

translation of current:

current (adjective; cur·rent \ˈkər-ənt, ˈkə-rənt\)
happening or existing now : belonging to or existing in the present time

example: /current month/
It means the one that is released now. It does not mean best or most stable.

use the bugfix branch and just do not open this topic. ignore it. you are not forced to test the new features

Fine, so you acknowledge the fact that "current" means not 'most stable' (=unstable)? And still you guys give this version as the only option for auto update or newbee updates from the website. This is serious a policy mistake. No wonder why the competition grows ten fold compared to MT..... you guys are selling inferior products to your user and pull new users off by the same.....

One more time;
auto update scripts look for "current" version, as will do any non experience MT user.
If MT put a "current" version on a website 99% of the people will consider this to be a stable version.
100% of automated scripts will see this version and start auto upgrading.
This is the worst policy I have seen in years....

We 'die hards' already know we are beta testers... newbees will quickly find out they are too.....

New posts already showing I am right, only 4 hours after the initiation....... pfffff

juanvi · Tue Sep 01, 2015 5:09 pm

all basebox2 with R11e-5HnD cm2 package

rajo · Tue Sep 01, 2015 5:58 pm

There were numerous complaints about this in the v6.31 topic. I have not written to support, because I have only 1 affected device. It is not reachable (can't login to make supout) and I can not powercycle it. I am waiting for some power outage so I can log in and upload older or newer fixed routeros.

Do you have another MikroTik router on the same LAN as the one you cannot reach? If you do, you could try /tool mac-telnet

rajo · Tue Sep 01, 2015 6:05 pm

By the way, dragging and dropping multiple items (e.g. firewall, NAT, and mangle rules) in Winbox is broken since probably 6.30.

You can select multiple items, but when you drag and drop, only the item you clicked to drag gets moved.

tri · Tue Sep 01, 2015 6:27 pm

493G upgraded via web interface System / Packages from 6.31 to 6.32 went to reboot loop and had to be recovered via netinstall. Now running 6.30.4 and works again.

105547111 · Tue Sep 01, 2015 6:48 pm

No issues on:

1 x CCR1016-12G
5 x RB951G
2 x CRS125-24G-RM
1 x RB751G
1 x RB532A
1 x RB951U
1 x RB751U

But my question is the 6.32 that everyone's downloaded before it was removed, will this then remain 6.32 or become 6.32.1 but current not bugfix.........

bradg · Tue Sep 01, 2015 7:31 pm

There were numerous complaints about this in the v6.31 topic. I have not written to support, because I have only 1 affected device. It is not reachable (can't login to make supout) and I can not powercycle it. I am waiting for some power outage so I can log in and upload older or newer fixed routeros.
Do you have another MikroTik router on the same LAN as the one you cannot reach? If you do, you could try /tool mac-telnet

I have a PowerBox (RB750Pr2) experiencing this issue right now, upgraded from 6.32rc5. Two others have been upgraded without issue - one came from 6.32rc5, one came from 6.31. All three units are being used as 10/100 PoE switches, no routing/ACL/FW functionality used. Only DHCP, system, and security packages enabled. RouterBoot was current (3.24 IIRC).

MAC telnet does not work, presented with a login/password prompt, and the session was immediately closed. Does not respond to IP ping, does respond to MAC ping.

I have not power cycled this unit yet, and probably will not do so until I am in a position to replace the unit if it cannot be recovered remotely.

neophyte · Tue Sep 01, 2015 8:40 pm

After upgrade to 6.32 /interface wireless print output is empty,wifi dont work.
X86 with dlink DWA-520
Wireless (Atheros AR5213)
/system resource pci print
Atheros AR5001X+ Wireless Network Adapter (rev: 1)

and
lcd - fixed parallel port LCD display support on multi-cpu x86;
6.32.rc6 work! 6.32 dont work..... o_0

robertkjonesjr · Tue Sep 01, 2015 8:44 pm

493G upgraded via web interface System / Packages from 6.31 to 6.32 went to reboot loop and had to be recovered via netinstall. Now running 6.30.4 and works again.

This is happening to me on my 493G. However, netinstall is not able to recover - it's never seen in the Routers window. My RB450G shows up just fine, so I know it's not a 'turn off your firewall' fix.

Troubleshooting, I can stop the boot with serial and boot from Ethernet. Running netinstall, I see the 493G get an IP through bootp, then a kernel from tftp. But that's it...

I see with the 450G the next step is that the board will broadcast UDP to port 5000, and I suspect this is what populates the 'Routers' section. The 493G does not send these broadcast packets, so is there a problem with the kernel it gets via tftp? Can I manipulate this kernel?

patrick7 · Tue Sep 01, 2015 9:05 pm

Upgraded from 6.31. If there is a lot of ipsec traffic, there is a kernel failure and the device reboots. Downgrade to 6.30.4 didn't help.

A lot of traffic = 2x CCR1009-8G-1S-1S+ connected with 1Gbps, IPsec with AES256 / SHA512 + iperf over a time more than 10sec

sep/01/2015 20:01:22 system,error,critical System rebooted because of kernel failure
sep/01/2015 20:01:22 system,error,critical router was rebooted without proper shutdown, probably kernel failure

Lupin · Tue Sep 01, 2015 9:09 pm

*) firewall - fixed limit and dst-limit options.
requesting more details on this =)

I've open a ticket with support on this problem:
http://forum.mikrotik.com/viewtopic.php?f=2&t=99745

also another user has same
http://forum.mikrotik.com/viewtopic.php?f=2&t=99877

Support say me that will fix in next release (6.32)

hatred · Tue Sep 01, 2015 10:28 pm

After upgrading from 6.30.4 to 6.32 all mangle rules have disappeared. Yes, I am looser and no backup exist.
I hate you, MikroTik.

Tue Sep 01, 2015 10:41 pm

Do not touch anything and DOWNGRADE

hatred · Tue Sep 01, 2015 11:00 pm

Unfortunately, I've already downgraded to 6.30.4 through "Check for updates" before posting here.
Don't do as I do.

patrick7 · Tue Sep 01, 2015 11:39 pm

I can confirm that with mangle rules.

Cha0s · Wed Sep 02, 2015 12:16 am

By the way, dragging and dropping multiple items (e.g. firewall, NAT, and mangle rules) in Winbox is broken since probably 6.30.

You can select multiple items, but when you drag and drop, only the item you clicked to drag gets moved.

I confirm that. I also have mentioned it on a previous release topic (I think it was 6.30).
Someone confirmed it as well on that topic.

planetcoop · Wed Sep 02, 2015 2:49 am

Mangle rules have gone missing after 6.32rc5 to rc6. I have confirmed this bug is also in the posted 6.32 final today as well. and ipv4 migration i have done to 6.32rc5 to rc6 has resulted in mangle rules missing. A restore from backup does not help and i have to past back in the missing rules.

I have confirmed this behavior on: ccr1036, ccr1016, rb951,rb953

105547111 · Wed Sep 02, 2015 4:46 am

Okay mangle rules gone from MT751g, but not a CCR1016-12G, but I noticed this only recently on 6.31 so its been around since then..

Wed Sep 02, 2015 7:10 am

I am more and more convinced that mikrotik offloads the testing to users and administrators. I wonder what specific reason makes each of you who installed 6.31 or 6.32 to do so. I did the fault with 6.31 also and lost some time with my testing devices uselessly, but I am not going to repeat it again. Without specific reason none should install these nightly builds.

Wed Sep 02, 2015 8:54 am

As for issue with RB911/912 with ac cards - we are working on fix for this issue. It is reproduce in our lab.

tri, bradg, neophyte, robertkjonesjr, patrick7 - can you please write to support@mikrotik.com and send your supout.rif file? Please refer to this forum post and we will try to reproduce this issue
hatred, patrick7, planetcoop, 105547111 - with simple Mangle rules we are not being able to reproduce issue so far. Can you please send to support@mikrotik.com list of your mangle rules (send supout.rif file)

Wed Sep 02, 2015 9:53 am

rajo - Issue with drag & drop is fixed already. 6.32 is now removed form downloads page but fix will be back in next version. I did test it myself and it works with Winbox 2 and Winbox 3.

*) winbox - fixed multiple firewall rule moving in Winbox 2

By the way - it will never work if rules are not ordered by ID.

Tonda · Wed Sep 02, 2015 10:56 am

but as you know, sometimes adding new stuff, can introduce unknown issues. this is why you can stay on 6.30.4 if you don't need any particular thing from the above changelog

What should I do in this situation, I would like to upgrade firmware with resolved bug regarding port flapping in CRS switches, but it was not backported to 6.30.X, but exists only in screwed 6.31 and 6.32. So currently I have devices with confirmed bug from Mikrotik and have no straight option to upgrade without doing some beta testing.
I would expect Mikrotik will give more priority to bugfix versions in current situation instead of new features and versions. I would also expect bugfix version for 6.31, look to changelog of 6.32 to notices "introduced in 6.31", but instead we have 6.32. So currently Mikrotik should maintain 6.30.X branch, 6.31 and its bugfixes and 6.32 and its bugfixes. I do not believe that they will be able to handle it in this way.

Wed Sep 02, 2015 10:57 am

Ask Support to backport it. It is unlikely that it was not backported, but anything is possible, maybe it was missed

Tonda · Wed Sep 02, 2015 11:10 am

Discussion regarding this topis was in thread regarding bugfix version 6.30.4 One post from strods:

That is why rc versions are released. When they are absolutely tested and we are sure that fix helps and does not break anything else in common configurations, then fix is included in bugfix version. Fix for CRS is relatively new so it is not yet included in bugfix version.

honzam · Wed Sep 02, 2015 11:18 am

TEMPORARY DELAY due to Basebox 2 upgrade issue. Version pulled.

Autoupgrade still offer 6.22.
You should protect customers and AutoUpgrade shut down until the problem is corrected ...

Cha0s · Wed Sep 02, 2015 11:20 am

rajo - Issue with drag & drop is fixed already. 6.32 is now removed form downloads page but fix will be back in next version. I did test it myself and it works with Winbox 2 and Winbox 3.

*) winbox - fixed multiple firewall rule moving in Winbox 2

By the way - it will never work if rules are not ordered by ID.

Does it work ok with Routing filters too?

The same problem was there too.

devnul00 · Wed Sep 02, 2015 11:22 am

Hi,
I have routerboard 911G-5HPnD and today updated to 6.32...
I have a problem because I can't make downgrade....
Do you have any solution?
thanks

marting · Wed Sep 02, 2015 11:29 am

Dynamic Queues are still not editable by Winbox and Web but only by terminal and api.
Ticket No of confirmed bug is 2015082766000678 but as you see with the number it is a quite recent ago reported bug, so I guess it will be solved in some future release.

dadaniel · Wed Sep 02, 2015 11:29 am

What about Ticket #2015082666000269, last message from 28.08 said "Seems that it was not completely fixed"

WirelessRudy · Wed Sep 02, 2015 11:45 am

This tread shows another disaster release, its even pulled according some statements. But the "Check for Updates" in winbox still shows 6.32 as the recommended upgrade.
If you not yet have installed 6.31 which give new channel option all 'old' ROS version users that go for an update will install this disastrous version. As will therefore any that uses automated scripts (Bad idea, it shows...)

MIKROTIK; REMOVE 6.32 as 'current' version. You are putting your customers in harms way!

For the moment only 6.30.4 should be the default 'current' version. Only this one shows not to have too many bugs anymore...
How many times do we need to tell you guys! This tread is filled with bug reports on 6.32, you even 'pulled' it but still offering it to all not aware (yet!) users!

You guys could write a book called; "How to kill your own product; bring your business down in 3 steps...."

Confidence goes by horse, it will only come back on foot.....

kostas22 · Wed Sep 02, 2015 11:46 am

Just upgrade my RouterBoard 750UP from 6.28 to 6.32, after that I make I reset configuration from inside the winbox, from then I cannot access to the RouterBoard from winbox.

Wed Sep 02, 2015 11:47 am

Rudy!
v6.32 was removed minutes after release. If you see v6.32, clear your cache

kostas22 · Wed Sep 02, 2015 11:51 am

v6.32 was removed minutes after release. If you see old one, clear your cache

How I clear the cache ?

Wed Sep 02, 2015 11:54 am

proxy, browser? check this file:

$ curl http://download2.mikrotik.com/routeros/LATEST.6
6.31

kostas22 · Wed Sep 02, 2015 12:01 pm

proxy, browser? check this file:
Code: Select all
$ curl http://download2.mikrotik.com/routeros/LATEST.6
6.31

Sorry Normis, but I don't get you! Where I will run the command you told me ? On the RouterBoard?

Wed Sep 02, 2015 12:09 pm

Sorry, clarification.

RouterOS checks new versions in the following file:
http://download2.mikrotik.com/routeros/LATEST.6
You can click this link and see what is inside.

If you see 6.31 - everything is correct. If you see 6.32, you have proxy cache somewhere in your ISP. Webpage www.mikrotik.com has 6.31 already. We removed 6.32 approximately 20 minutes after first report that it breaks Basebox 2 with 802.ac wireless card.

marting · Wed Sep 02, 2015 12:11 pm

Click check for updates once more. Latest Version for me still 6.31, see screenshot

dadaniel · Wed Sep 02, 2015 12:16 pm

*) firewall - fixed limit and dst-limit options.
requesting more details on this =)

the add-dst-to-address-list - rule got triggered before the dst-limit rule above it. One minute later the count on the dst-limit rule started to rise exactly to the value of the add-dst-to-address-list - rule.
dst-limit rule still is matched even if the given rate is exceeded.

Wed Sep 02, 2015 12:26 pm

Yes, marting, v6.31 is correct!

See posts above. v6.32 is REMOVED for now, because of a problem.

kostas22 · Wed Sep 02, 2015 12:30 pm

Sorry, clarification.

RouterOS checks new versions in the following file:
http://download2.mikrotik.com/routeros/LATEST.6
You can click this link and see what is inside.

If you see 6.31 - everything is correct. If you see 6.32, you have proxy cache somewhere in your ISP. Webpage http://www.mikrotik.com has 6.31 already. We removed 6.32 approximately 20 minutes after first report that it breaks Basebox 2 with 802.ac wireless card.

But my problem is that I have already made the update! And now I cannot access to my RouterBoard 750UP.

Wed Sep 02, 2015 12:48 pm

Netinstall with 6.31 will fix it http://wiki.mikrotik.com/wiki/Manual:Ne ... escription
RouterBOARD 750UP is not affected by the issue described above. is possible you can't access it for some other reason.

kostas22 · Wed Sep 02, 2015 1:15 pm

Netinstall with 6.31 will fix it http://wiki.mikrotik.com/wiki/Manual:Ne ... escription
RouterBOARD 750UP is not affected by the issue described above. is possible you can't access it for some other reason.

It is possible to make Netinstall without serial port?

Athan · Wed Sep 02, 2015 1:17 pm

RB493G bricked (reboot loop). Back to 6.31 via Netinstall.

Please Mikrotik folks, do some testing before getting out a new release.

Wed Sep 02, 2015 1:18 pm

Netinstall with 6.31 will fix it http://wiki.mikrotik.com/wiki/Manual:Ne ... escription
RouterBOARD 750UP is not affected by the issue described above. is possible you can't access it for some other reason.
It is possible to make Netinstall without serial port?

Of course. Press the reset button, plug the power cord, then wait until Netinstall sees your router. Release the button.

kostas22 · Wed Sep 02, 2015 1:22 pm

Netinstall with 6.31 will fix it http://wiki.mikrotik.com/wiki/Manual:Ne ... escription
RouterBOARD 750UP is not affected by the issue described above. is possible you can't access it for some other reason.
It is possible to make Netinstall without serial port?
Of course. Press the reset button, plug the power cord, then wait until Netinstall sees your router. Release the button.

Thanks for your responses Normis. I will do it.

Wed Sep 02, 2015 1:23 pm

Thanks for your responses Normis. I will do it.

For Netinstall, the PC needs to be connected to port 1 !

pizzulicchio · Wed Sep 02, 2015 4:11 pm

I can confirm this bug on 6.32 on all my RB-SXT .

After some hours i'm not be able to login .( no telnet or ssh or mac-telnet )
At the same time , snmp too is no more working, only ping request are ok... after some more times ( minutes or few hours ) my rb-sxt stop working at all.

I have no problem with mAP 2n... Very strange .

I have updated all my sxt to 6.32 rc6. I hope well!

105547111 · Wed Sep 02, 2015 4:37 pm

As for issue with RB911/912 with ac cards - we are working on fix for this issue. It is reproduce in our lab.

tri, bradg, neophyte, robertkjonesjr, patrick7 - can you please write to support@mikrotik.com and send your supout.rif file? Please refer to this forum post and we will try to reproduce this issue
hatred, patrick7, planetcoop, 105547111 - with simple Mangle rules we are not being able to reproduce issue so far. Can you please send to support@mikrotik.com list of your mangle rules (send supout.rif file)

Hi Strods,

My mangle rules aren't simple there's over 50 of them. It's fast-track as well as pushing certain DST addresses and ports with routing-marks to send them down different routes.

Your post leads me to think there is a problem with more than simple, hence do you need the supout?

WirelessRudy · Wed Sep 02, 2015 4:49 pm

Sorry, clarification.

RouterOS checks new versions in the following file:
http://download2.mikrotik.com/routeros/LATEST.6
You can click this link and see what is inside.

If you see 6.31 - everything is correct. If you see 6.32, you have proxy cache somewhere in your ISP. Webpage http://www.mikrotik.com has 6.31 already. We removed 6.32 approximately 20 minutes after first report that it breaks Basebox 2 with 802.ac wireless card.

Well, this is all new to me.

First of all, this morning while writing the last comment 6.32 was still there on the browser on a freshly started PC. It was 'current' on the website and in several of my routerboards I checked the same....

I don't know where your "cache" is coming from. I am a WISP and I run no proxy caches or whatsoever anywhere. All dns request for any system in my network are directly forwarded to OpenDNS....

But anyway, I just checked again, and now (but only now!) 6.32 seems to be gone....

WirelessRudy · Wed Sep 02, 2015 4:57 pm

And now the latest "current" version is 6.31. I thought that was considered to be a disaster too? Is was so bad 6.32 was pushed too fast and several pre issued rc's were preceding it...

Can you confirm 6.31 is stable? (Wasn't this the version that did brick the units with PoE-out?)

Wed Sep 02, 2015 4:59 pm

WirelessRudy, did you read any of my responses? If you want stable, use 6.30.4

Wed Sep 02, 2015 5:30 pm

Normis, keeping the 6.31 in your update link to be used by all devices to download and install instead the 6.30.4 is the thing that is really not smart.

WirelessRudy · Wed Sep 02, 2015 6:39 pm

Normis, keeping the 6.31 in your update link to be used by all devices to download and install instead the 6.30.4 is the thing that is really not smart.

Glad I am not the only one that thinks this way.

Normis: "I" know 6.30.4 is last stable. But anyone not familiar with this forum or because he is a robot (script) will now download 6.31 which is just another disaster.....

You simply CANNOT put a version as "current" on the website or as 'upgrade last version' opción while it is not stable.

It is not a matter I am not reading and understanding. I is merely you guys don't understand what is happening and were'd you go wrong....

Normis, I hope you will be in Madrid. Bring your boxing cloves, we are up for a little sparring.....

dadoremix · Wed Sep 02, 2015 7:00 pm

For me last good version is 6.29.1 all other are death for rb

bradg · Wed Sep 02, 2015 7:39 pm

As for issue with RB911/912 with ac cards - we are working on fix for this issue. It is reproduce in our lab.

tri, bradg, neophyte, robertkjonesjr, patrick7 - can you please write to support@mikrotik.com and send your supout.rif file? Please refer to this forum post and we will try to reproduce this issue
hatred, patrick7, planetcoop, 105547111 - with simple Mangle rules we are not being able to reproduce issue so far. Can you please send to support@mikrotik.com list of your mangle rules (send supout.rif file)

Unfortunately, the malfunctioning PowerBox is currently unreachable via IP or MAC, so I'm unable to supply a support file. Although I have remote access to power cycle the unit, I have not rebooted it yet to see if it recovers (I assume that is unlikely given the reports thus far, but please advise if it is possible this would restore normal operation).

This unit is currently functioning as a simple 4 port PoE switch only (powered via barrel power connector at 24VDC, not via eth1 PoE). Right now, all four ports are powered and switch functionality is working normally (as it was configured), so there is enough functionality to configure the hardware to that point at least.

I will be either replacing the unit or doing a netinstall on it in the next few days as time and weather permit. Is there any possibility that this software issue is causing irreparable damage to flash memory, or overheating the CPU to the point where hardware replacement is advised over recovering it via a netinstall?

w0lt · Wed Sep 02, 2015 7:47 pm

Normis, keeping the 6.31 in your update link to be used by all devices to download and install instead the 6.30.4 is the thing that is really not smart.

Glad I am not the only one that thinks this way.

Normis: "I" know 6.30.4 is last stable. But anyone not familiar with this forum or because he is a robot (script) will now download 6.31 which is just another disaster.....

You simply CANNOT put a version as "current" on the website or as 'upgrade last version' opción while it is not stable.

It is not a matter I am not reading and understanding. I is merely you guys don't understand what is happening and were'd you go wrong....

Normis, I hope you will be in Madrid. Bring your boxing cloves, we are up for a little sparring.....

[/quote

After having to Netinstall several backhauls from 6.32rc6 then 6.32 back to 6.30.4, I'm done...
The 6.32 series should be called the MikroFlap edition.

I believe I would agree that 6.30.4 should be the current stable version, as stable as it can be, and everything else higher should be remanded to "Install If You DARE".

It's your business but for my two cents, spend less time working on Cloud Hosted Router and more time on ROS stability.
I'm really not sure what needs to be done whether more regression testing or what but please think seriously about it.

patrick7 · Wed Sep 02, 2015 8:01 pm

Unfortunately I cannot send Supout as I already downgraded. But I can give you my mangle rules:

/ip firewall mangle
add action=mark-connection chain=forward comment="Mark IPsec connections" \
    ipsec-policy=out,ipsec new-connection-mark=ipsec
add action=mark-connection chain=forward ipsec-policy=in,ipsec \
    new-connection-mark=ipsec

bajodel · Wed Sep 02, 2015 9:44 pm

@normis ..for your records:
6.32rc6 was already "killing" my lab rb912uag (as 6.32 "final" did after) ..no management access of kinds
6.31 made some rb750 of mine unstable (ethernet ports stop forwarding traffic after some time)

I'm quite happy with 6.30.4 (even if I'm still more confident on 6.27) but maybe you must backport "upgrade channels" functionality on 6.30.x branch if it will live for some months otherwise bugfix upgrade process will be only manual operation.

Mikorist · Wed Sep 02, 2015 10:04 pm

Bugfix mean stable and Curent is unstable?

Thanks for this precious nformation!

WirelessRudy · Thu Sep 03, 2015 12:33 am

6.27 is rock solid. Have hundreds of units running on it.
We started upgrading to 6.28, 6,29 on new CPE units and an occasional new lesser important router. But they still run fine..
Then we were 'trapped' in using 6.30 because it did do some fastpath improvements on bridges, what we use a lot.
Initial upgrades (some pre 6.27 units I still had were planned to go to 6.29 but suddenly I found myself with 6.30. There was no warning...
Anyway, 6.30 worked fine, it seems, for some days before the problems came. Port flaps, crashing units, completely random. Some units never had issues up to today, others crashed where they were running for months. Even reverting back to 6.27 didn't save these. In hope issues were fixed with 6.30bug fixes we had some ordeal in the fixes but now at least all troubled units run 6.30.4 and are stable again.

By same 'trap' we found ourselves installing 6.31. Yet again initially it worked fine before problems started to surface. Since Normis here advice to go to 6.31 and then to 6.32rc's etc. all over the place, I became very irritated in the knowledge that obviously they are swimming without any direction when it comes to versions; 'current' that are disasters, rc's for versions that are actually bug fixes and advices for new versions (6.32) that should have all bugs fixed and is "stable" (Everybody would agree "current" in the webpage and on the server is the preferred upgrade so it must be stable and tested).

So, after some weeks of havoc it is clear that indeed as 'bajodel' mentioned, the rock solid stable version is 6.27 and 6.30.4 is the latest ROS that has new features and some bug fixed incorporated while at the same time by now shows to be relative stable.

Any other version, including the present 6.31 is just playing russian roulette.

I think MT should really start thinking on their policy again when it comes to what a "current" version means. Actually its a wrong word. They should put a "stable" version on the website and server. And a OS should only get the label "stable" if it has shown as rc for some weeks not to produce major issues amongst users.

Any user that wants to become a 'beta tester' can use any new or rc version and should be rewarded with a free router if they manage to find an important bug that MT did not run across yet. So they can fix it. This way users that want can help MT in finding issues. They will do their best to find bugs. And if not, the OS is maturing?

Only if nobody can find a verified major bug in some weeks (2 months) such a version can be considered "Stable" and be put on the website and server for day to day production environment's upgrades....
This will give serious users that need new features at least a sense that the version they are downloading or upgrading to is "stable" when it is mentioned on the site/server as beiing "stable"

My network (700 units) is kept at 6.27 if no new features are needed and only were bridge fastpath might give me some improvements I am going to 6.30.4 and so far this version seems to work.....

normalcy · Thu Sep 03, 2015 12:49 am

I get the issue that bugfix is not necessarily clear that it means stable. But 'current' is fine for me for the feature branches as this is similar to the FreeBSD release engineering process. There 'current' is the moving target, but they do call their bugfix 'stable' instead.

Ultimately it's all semantics - which is different in various projects. As long as it settles down and is clearly listed somewhere.

Doesn't help that the transition from the versions without release streams (6.30.x) to one with streams (>6.31) has been so rocky.

Hope it doesn't discourage mikrotik, this is the right direction that you're going in!

Just need to get to a bugfix version that has release streams support. Cross fingers it's 6.33 (and then hopefully in the future we won't need to cross our fingers at all on upgrades anymore).

WirelessRudy · Thu Sep 03, 2015 1:48 am

I'm not that much irritated by how the naming of different version is actually maintained. All kinds of suggestions are made and time will tell which one is best.

But on the website, or on the upgrade servers, were scripts, auto upgrade programs or administrators in need of quick router's upgrades are looking, the recommended version should be one that is stable.
What is then stable is to be decided but it can't be a version with new features. It is proven now too many times new features create new bugs. Sometimes minor issues, sometime big.

The name "Current" as Normis states means nothing else than the last version with new features.... nice. But then it should not be the default preferred one if your router by script is asking for a new version. Or when you buy units that come with much older version and you want to upgrade.

I think, and more with me, that a version that is on a website as the preferred download version should be a stable one. If the name "current" doesn't mean "Stable" than the name should be changed and a 'stable' version should be the preferred one...

If my PC by default downloads an update on Windows 10 I don't get Windows 11rc. I get an update on Win10, like it should. .... MT put Win11rc as the new preferred.... wrong.

keema · Thu Sep 03, 2015 8:29 am

And people should not necessarily a expect a 6.31.1 to happen, if 6.31 is so broken.

6.31 should be marked as withdrawn and not be downloadable anymore.

Then they will have to witdraw almost every version released.

Thu Sep 03, 2015 8:55 am

marting - Now you can not change dynamic queues also through CLI. Dynamic items should not be editable.
dadaniel - Issue is not fixed yet. It is reported to developers.
kostas22 - Are you sure that you are not trying to conenct through ether1 through which all incoming connections are blocked by default firewall?
105547111 - Please send supout to support e-mail. We are not being able to reproduce it with simple rules. maybe something else triggered that.

vortex · Thu Sep 03, 2015 9:23 am

And people should not necessarily a expect a 6.31.1 to happen, if 6.31 is so broken.

6.31 should be marked as withdrawn and not be downloadable anymore.
Then they will have to witdraw almost every version released.

I understand 6.31 is forcing quite a few people to Netinstall. I don't think this happens so often.

planetcaravan · Thu Sep 03, 2015 9:57 am

Netinstall with 6.31 will fix it http://wiki.mikrotik.com/wiki/Manual:Ne ... escription
RouterBOARD 750UP is not affected by the issue described above. is possible you can't access it for some other reason.
It is possible to make Netinstall without serial port?
Of course. Press the reset button, plug the power cord, then wait until Netinstall sees your router. Release the button.

I upgrade RB750UP from 6.15 to 6.32 and I did not have any problem. RB750UP is powering up 4 devices (1 RB Metal5, 2 RB912, 1 NetMetal). Do I have to downgrade in any case?

Thu Sep 03, 2015 10:32 am

No, please don't misunderstand me.
If you ignore the new release branches, v6.31 is just another version. We have not made "current" branch versions less stable than any other release before

bugfix - only fixes
current - fixes + features (as 6.29 and any version before it)

marting · Thu Sep 03, 2015 10:43 am

marting - Now you can not change dynamic queues also through CLI. Dynamic items should not be editable.

What???? Why? My whole system relies on this. And it works great, so why do you remove a feature??? It is necessary for me to change rate limit on dynamic pppoe queues as ROS is still not able to change rate limit by CoA with Radius and PPPoE server.
My intention at this bug report was to make the change possible also via Winbox and Web. Not to make it impossible the other way around.
Man, please undo this change. If it´s too much effort to implement it for web and winbox, then leave it with CLI.

Didn´t read anything from this "fix" in the changelog.

Thu Sep 03, 2015 11:05 am

All dynamic features should be fully controlled by their originating settings.

Thu Sep 03, 2015 11:11 am

Dynamic entries can not be changed. That was allowed by mistake.

If you need to change queues, then use static ones. If you need them for dynamic interfaces, then you have to create static interface bindings and assign queues for them.

http://wiki.mikrotik.com/wiki/Manual:In ... PoE_Server

Here is an entry from changelog:
*) simple queues - restrict all changes in dynamic simple queues

marting · Thu Sep 03, 2015 11:31 am

All dynamic features should be fully controlled by their originating settings.

I would love to do so, but as I mentioned CoA is still not possible.

dadaniel · Thu Sep 03, 2015 12:51 pm

dadaniel - Issue is not fixed yet. It is reported to developers.

Ok, I hope you don't release 6.32 before this is fixed, because RouterOS without working firewall filters is nearly useless

vortex · Thu Sep 03, 2015 11:35 pm

I think in 6.31 the leases page gets eventually emptied. I downgraded to 6.30.4

Thu Sep 03, 2015 11:44 pm

And you did right.

steen · Fri Sep 04, 2015 12:21 pm

Hello Folks!

Issue with CCR1016, after some days of operation suddenly port ether1 at random stop forwarding traffic for intervals and comes back on-line again. There is nothing in the log files or any other logs either, no support file or something like that.

I restarted the CCR1016 and situation calmed down and went back to normal operations.

Ivoshiee · Sat Sep 05, 2015 9:55 am

I am unable to upgrade/downgrade off the broken v6.32 on a RB911 as every attempt to reboot the unit will result with a hard freeze. Is there a way to set the upgrade process to ignore the reboot requirement and be happy with a plain power restore?

hatred · Sat Sep 05, 2015 11:16 am

What's new in 6.33rc3 (2015-Sep-04 11:18):
*) firewall - do not lose firewall mangle rules on start-up (introduced in 6.32);

Genkun · Sat Sep 05, 2015 12:52 pm

Hi Normis

I am trying to update my script. I have upgraded to 6.31 but i do not see any options in the terminal to change channel= "" and it is always on current channel.

Am i missing something?

Genkun · Sat Sep 05, 2015 12:59 pm

I found it

/system package update> set channel=bugfix

But now the upgrade feature works slightly differently.

/system package update check-for-update download

This still reboots automatically just like upgrade command in earlier versions

Noticed that 6.30.4 doesn't support channel feature. So we will have to wait until a new 6.31.x version before implementing channel selection into script upgrades.

Thanks!!

MTeeker · Sun Sep 06, 2015 5:43 am

Unless I missed something, is my recap of Fast Track aspects below correct? Please chime in. Especially Jarda.

FAST TRACK:
Objective: Just to recap the issues in respect to Fast Track feature from 6.29 (from memory).

How: To speed up subsequent incoming traffic packets ONCE the initial few from SAME source to destination have been already authenticated as legitimate. (I don't think people care about bittorrents not being fast tracked).

Constraints: VoIP queue priorities need to be preserved. Simple reason is that speeding up of packets (by fast tracking) should not render existing VoIP queue priorities useless when bandwidth is full with packets incoming and outgoing. Simply put, Fast Track does not make the size of the bandwidth pipe bigger. It only removes processing at internal 'checkpoint'.

From this angle, it's clearly desirable to preserve the intended working of QoS of VoIP (via queue priorities) for obvious reason. It's why queue priorities were setup in the first place.

Challenges: How to make packets fast tracked STILL subject to queue priority. It's kinda ironic, as I understand it.

Consideration: But what is the benefit in fast tracking normal connections (e.g. downloading a file) while it breaks yous VoIP conversation? It happened on my VoIP line despite having a 100mbps down and 2.4mbps up bandwidth at home. The other party could not hear me properly on the phone when Fast Track was on. I had to turn Fast Track off in the end.

In certain circumstances, Fast Track, while in its early stage of development (still a way to go before reaching maturity), does have its value.

My two cents. With respect.

IntrusDave · Sun Sep 06, 2015 8:24 am

Just an FYI: Using AES with GCM still causes a kernel crash in 6.33rc3

Sun Sep 06, 2015 9:01 am

MTeeker, I am on mobile for couple of days now, so sorry for my short answer. Generally your post should be rather in fasttrack thread then in this version related discussion. But anyway. Fasttrack says not to process selected packets by firewall at all. If the queuing is part of firewall, these packets bypassing queues as well so you cannot calculate the qos at all. The reason for using the fasttrack is to lower the workload of the router and be able to push more thru. So. If your router is not working on the edge before you reach your pipes limits, you don't need to use fasttrack at all. If your router isn't able to pass so much traffic, you can buy more powerful one or spare money and try fasttrack. There are some applications where you can benefit from it. Maybe it isn't your case but you can try to think what kind of traffic you can let pass around the firewall if you need to.

hatred · Sun Sep 06, 2015 9:52 am

I don't think people care about bittorrents not being fast tracked.

Fasttrack reduce CPU load at times (50-70 -> 30) on my RB951G-2HnD while downloading torrents at 100Mbit.

MTeeker · Sun Sep 06, 2015 4:54 pm

Jarda,

I tried to post where Fast Track was discussed but the thread was closed. It crossed my mind that it was somehow a bit odd as your sharp eyes detected it.

.

My VoIP queue tree is based on mangle marking packets at pre-routing chain. And while Fast Track was on, my conversation was broken on the other party's receiver if I initiated the call.

So it seems Fast Track neutralizes my VoIP QoS settings. (With relatives in the US, I need VoIP to contact them without paying an arm and a leg).

I believe your reply basically confirms my understanding of Fast Track. My router is right behind my ISP's modem which is bridged.

I do like Fast Track. It has its usefulness in allowing more incoming traffic passing through.

But I think the real challenge for MikroTik is: Is it possible to have Fast Track features functioning only in the 'remaining nominal bandwidth' therefore RouterOS preserves QoS for VoIP while a VoIP is in progress.

I agree with you that a faster routerboard helps processing packets faster. But I'd also think a faster routerboard also benefits from Fast Track.

Cheers

hatred,
Sure. I was simply making the comparison point that users would be concerned about the breaking up of a VoIP conversation but it would not be critical if bittorrents are not fast tracked.

Mon Sep 07, 2015 8:54 am

Generally I have nothing against the fasttrack itself too. I just do not consider the situation around the counters to be clever enough. I believe that the counters could be corrected so even the qos could be used when fasttracked traffic will be counted into total queues one day. Seems we have pretty close opinions. Now I am fasttracking intersubnet traffic and torrent traffic on some routers in order to be able to utilise the connectivity. Without fasttrack I wouldn't be able to reach the limits.

Ansy · Mon Sep 07, 2015 1:43 pm

I upgrade RB750UP from 6.15 to 6.32 and I did not have any problem. RB750UP is powering up 4 devices (1 RB Metal5, 2 RB912, 1 NetMetal). Do I have to downgrade in any case?

The very same question!

I needed to swap my RB750UP 6.31 (AFAIK) devices due to unexpected huge port flapping/constantly rebooting one nasty morning (after some days worked OK! http://forum.mikrotik.com/viewtopic.php ... 36#p495636)... did not help at all, so I've tried and finally catched a moment between reboots and loaded 6.32rc5 into it... well, it looks stable. Then I've read "*) fix port flapping RB750UP blabla" in changelog (GREAT! Just in time, saving me), but some minutes later I saw "6.32 current" with the same bug fix and installed it too.

Well, my RB750UP works rock solid as PoE, Bridging Firewall with Simple Queues and some NAT rules for 5+ days uptime! But it can't see neither 6.32 nor in 6.32rcX with that magic RB750UP port flapping bugfix (and my special "management process 100% CPU", hanging Bridging Firewall bugfixes http://forum.mikrotik.com/viewtopic.php ... 95#p493595) in MT download area...

So, I use officially unsupported 6.32 as most stable after 6.28 for now. Why that so important bugfixes are not included into 6.30.4? I don't want to destroy all my network by that downgrade.

JFYI, I've firmware 3.25.1, but able to "upgrade" only to 3.24 now -- may be it's important too.

MarkoB · Mon Sep 07, 2015 3:44 pm

marting - Now you can not change dynamic queues also through CLI. Dynamic items should not be editable.
What???? Why? My whole system relies on this. And it works great, so why do you remove a feature??? It is necessary for me to change rate limit on dynamic pppoe queues as ROS is still not able to change rate limit by CoA with Radius and PPPoE server.
My intention at this bug report was to make the change possible also via Winbox and Web. Not to make it impossible the other way around.
Man, please undo this change. If it´s too much effort to implement it for web and winbox, then leave it with CLI.

Didn´t read anything from this "fix" in the changelog.

+1 undo this
we also use pppoe with dynamic queues and IPs, we have scripts that double speeds between 00 and 10 and now this not working

steen · Mon Sep 07, 2015 8:51 pm

Hello Folks!

Usually I stay away from RC versions in production, this time there was no other way out.
RB750 started to flap ports and one CRS fully locked and had to be power cycled.
Only way out was to upgrade to RB6.33rc3, we tried to downgrade to latest stable below 6.31 but it did not help.
Result was a fully outage for 15 minutes at one site and multiple days problems on the site with RB750 till flapping was discovered in some logs.

Tue Sep 08, 2015 9:30 am

New 6.32.1 is out with all important fixes included. It is in the current release chain, Bugfix (Stable) is still v6.30.4
http://forum.mikrotik.com/viewtopic.php?f=21&t=100290

Who is online