v6.13 released!

What is new at 6.13

What’s new in 6.13 (2014-May-15 16:03):

*) console - comments are now accepted where new command can start, that is,
where ‘/’ or ‘:’ characters can be used to start new command, e.g.
/interface { # comment until the end of the line
print
}
*) backup - backups by default are encrypted now (with user password).
To use backup on older versions, you should disable encryption with dont-encrypt
flag when creating it;
*) files with ‘.sensitive.’ in the filename require ‘sensitive’
permission to manipulate;
*) lcd - reduce CPU usage when displaying static screens;
*) l2tp - fixed occasional server lockup;
*) pptp - fixed memory leak;
*) sstp - fixed crashes;

Simply click “Check for updates” in QuickSet, Webfig or Winbox packages menu. If you run v5 or older, download the newest NPK package from our webpage, upload to your router, and reboot: http://www.mikrotik.com/download

NOTE:
We plan to have full release of CAPsMAN for general public in RouterOS v6.14!
Please, make all additional tests and report all persisting problems in wireless-fp package.

STILL EXIST ON 6.13

http://forum.mikrotik.com/t/v6-11-released/75450/1
BUG SIGNALED FROM 6.10 AND STILL NOT FIXED???

Opened another ticket for that: [Ticket#2014041566000226] 6.12 UNFIXED BUG: user-manager profile limitation

I wait again the fix on 6.14…

When we can expect solving of bug “IGMP proxy stop working on upstream interface down/up”? Described in: http://forum.mikrotik.com/t/routeros-6-9-igmp-proxy-stop-working/74143/24

we are working on this issue. no fix yet.

rextended, I will check for the issue, and try to find out why it is not fixed yet.
And we will try to fix it at 6.14 version.

Separate topic is made of OpenVPN bridning.
Please post all your notes there,
http://forum.mikrotik.com/t/ovpn-bridging/77213/1
Thank you very much for the cooperation.

Hi Guys,

Just updated 951-2n to 6.13. I use RIP over a PPTP client interface, and as with every update since probably 6.9 or even earlier, after the first upgrade reboot, RIP routes do not become active. Another reboot of the whole board is required to get the routes back active (even tried disabling/enabling RIP before reboot).

I did report this a few versions ago but only on the forums.

Thanks,
Joe

Just upgraded from 6.12 to 6.13 (x86).

From the Winbox → Queues → Simple Queues - the list is empty.
In the terminal/ssh it’s ok.

Anybody with the same problem?

Hello,

Does v6.13 contain the fix for [Ticket#2014050866000407] ?

[admin@TestPlace] > system clock pr
            time: 14:30:01
            date: may/16/2014
  time-zone-name: Etc/GMT-3
      gmt-offset: +03:00
[admin@TestPlace] >

“-3 is not equal to +3” is still not fixed :slight_smile:

Hey, I see in v6.12 you allow DNS names in a PPTP adapter instead of using a script.

But one thing you should definitely add to the interface, is the ability to select the outgoing interface or route… because in multiple connection scenarios, you still need to update the route/mangle using a script… real bummer, but an easy fix to do it on the interface itself!

I’m new to MT, so maybe it was somethere on the forum…

I got and installed ROS 6.12RC20.
Now after pressed Download and Upgrade it Download and Reboot. After reboot still 6.13RC20.
Download manualy to Files → Reboot. Still 6.13RC20.

How to upgrade to ROS 6.13 final ?

Best

Is it happening only on x86 boxes?
Please contact support@mikrotik.com
If you access the Queue Simple from the Webfig do you see all the simple queue rules?

Very thanks!

it was described at the same place where RCs are available:

NOTE 2:
In some rare cases it might be impossible to do any package managment
(upgrade/downgrade/enable/disable/uninstall/install) in 6.13rc13+ rc versions,
board will simply reboot itself staying on previous version
This is fixed for the release version of 6.13 (2014-May-15 14:33) and newer:
Please, use Netinstall for upgrade/downgrade

Use netinstall.

THIS PROBLEM DO NOT EXIST IN MY TWO x86 MACHINE.

NETINSTALLED <<< (because I can not upgrade from 6.13rc23 to 6.13 final)

Another winbox issue :
interface.png

And where is the issue?
I not see any issue!

Here’s for comparison what it should look like.
interfaces-ok.png