v6.21.1 released

What’s new in 6.21.1 (2014-Nov-03 15:20):

*) fixed ugprading from v5;

What’s new in 6.21 (2014-Oct-30 12:34):

*) userman - fix ~Your session has been reset due to inactivity~ error;
*) timezone - updated timezone information to 2014i release;
*) wireless - fixed scanning tool crash for 802.11ac interfaces
*) wireless - fixed Nv2 kernel panic on 802.11ac interfaces
*) quickset - added vpn configuration to Wifi AP %26 Ethernet modes as well;
*) lte - changed device identification for devices which regenerate MAC address,
most likely this will loose device’s configuration;
*) sstp - fixed disconnects on high traffic load;
*) ovpn client - fixed problem where ip address was not added to bridge interface in ethernet mode;
*) webfig - show properly Switch Port configuration;
*) disks - fixed support for MMC/SD cards;
*) winbox - added filtering by dscp to torch;
*) certificate - fix CRL handling in trust chain;
*) fixed 6to4 tunnels having inactive routes;
*) ipsec - fix downgrade problem to v5;
*) ipsec - disallow template-policy-group=none in peer config and set it to ‘default’;
*) metarouter - some metaroutes didn’t have their licenses;
*) torch - possibility to filter by dscp;
*) fixed - master port on AR8327 switches that is put into bridge could sometimes not work properly;
*) fixed queues - could have huge latencies and smaller throughput than specified;
*) interfaces report last link up/down time and link down count;

Click “Check for updates” in QuickSet or Packages menu to get the new version. This time, it should also work for v5 routers, please report if your device found the new release and how the update went.

Is it only me, but ping to Router itself was drastically better in this version ? :slight_smile:
Few of my scripts are now returning significantly lower ping values to localhost.

It’s normal that updates have undocumented features. Maybe this is one of them.

Any news what has changed in RouterBoot Firmware 3.19?

Nothing listed here:

http://wiki.mikrotik.com/wiki/RouterBOOT_changelog

And this is also normal…

Link on download page to 6.22rc is not working.
Remove this link from page if there is no 6.22rc version

sorry, fixed

please fix it also in mikrotik.com Account section - it says ‘Currently there is no available development version!’ :slight_smile:

We need moar info!

Download link fixed. Changelog is not fixed

And also as Chupaka say:

please fix it also in mikrotik.com Account section - it says 'Currently there is no available development version!

Warning!

I just upgrade two CCR1036 to 6.21.1 from v6.20 and lost access to routers. They keep rebooting at each couple of seconds and never go back.
Only netinstall could solve the problem (after hours with consumer complaints).
You guys do not testing before releasing to the public?
Email to support is on the way.

PS: No problem on ppc and mipsbe.
Edit: There is one bonding interface one each router.

Warning!

I just upgrade RB2011UAS-2HnD to 6.21.1 from v6.19 and my router CPU used 100%.
and I turn off all ether Port(ether3 Port is Console) but, Nothing had changed.

I sent a rif file to the mikrotik support email and I waiting for a reply.
Please do sufficient test, before the release.
Photo_2.PNG

Where can you see this interfaces report last link up/down time and link down count?

in Terminal, ‘/interface print detail’

This is crazy…

MT I would rather wait months for updates if you guys would test them properly!

If you need BETA testing, make a different BETA branch for the firmware!

How can think dev build of when such, if from being out in the Stable release a major bug up here,
I want you to care a little more quality control, and you wish me also.

Hey guys, let’s have a simple reality check for a moment.

If you download/upgrade any new ROS and deploy it…You essentially become the “Beta” tester, eh? :astonished:

So far, I don’t believe that MikroTik is requiring anyone to upgrade to a newer version of the software. So if the current version is working, then probably you should leave it alone.
If you want to experiment with newer versions, that’s ok but then you do it at your own risk.
Since MikroTik doesn’t charge for the software, you might conclude that it is worth ever penny you paid for it.. But there are other opinions that might differ at bit.

Rule of thumb should be, to only test new ROS software on a non-essential network and give it enough time to reveal any problems. If someone deploys it on a active network, well then, you have to accept the risks.

-tp

Ever logged a ticket with support? If so you would have seen point number 2


This is an automated reply that will help you to get fastest
possible solution or reply from our support department.

Make sure you have:

  1. attempted to re-set your configuration and started from the beginning, following steps in the documentation
    2) the latest RouterOS version installed on the router
    http://www.mikrotik.com/download.html
  2. attached the supout.rif file from the router in question
    http://wiki.mikrotik.com/wiki/Manual:Support_Output_File
  3. included a precise description of the problem - use network diagrams, screenshots, videos if necessary

If something from above is incomplete in your current email, please, send all additional information as a reply to this email.

lte - changed device identification for devices which regenerate MAC address,
most likely this will loose device’s configuration;

more detailes please

Lost connection to Userman database after upgrading from 6.20 to 6.21.1 :frowning:

Had to set the path to the database and repair it.

/tool user-manager database set db-path=/user-manager1
/tool user-manager database rebuild