v6.13 released!

[jsahoka]

@normis

@jsahoka

Maybe its just me,

I am on 6.13 and every time I click Quick Set in winbox it shows my passwords in plain text even though the “Hide Passwords” option is checked in winbox, the “hide” box next to the WiFi Passwords keeps getting unchecked and the password is shown in plaintext.

Looks like a bug, I can repeat

Hey Normis,
Thanks for the reply, do i need to submit an official bug report to try and get it fixed or is this sufficient?

[normis]

@jsahoka

@normis

@jsahoka

Maybe its just me,

I am on 6.13 and every time I click Quick Set in winbox it shows my passwords in plain text even though the “Hide Passwords” option is checked in winbox, the “hide” box next to the WiFi Passwords keeps getting unchecked and the password is shown in plaintext.

Looks like a bug, I can repeat

Hey Normis,
Thanks for the reply, do i need to submit an official bug report to try and get it fixed or is this sufficient?

I have already submitted a bug report, so you don’t need to do that

[jsahoka]

@normis

I have already submitted a bug report, so you don’t need to do that

Thanks !

[wa4zlw]

what about the OSPF/IPSec issues which also seem to be in 5.26?

[klaparp]

@klaparp

After upgrade to 6.13 i get “ERROR: Internal Server Error” when trying to log in.

I have tested on 2 different routers. one 750 and onte 2011 with same result. ’

Suggestions?

Get same problem with both webgui and winbox.

2-3 restarts solved the problem on my testing router, I´ll get back later tonight if it works for the production router.

/HW

[Beeski]

@normis

Everything in the last RC is included in the final release.

Which wireless improvements do you mean? This is the official changelog:

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;

is wireless-fp included in the official 6.13 release?
I am guessing no based on comments in the thread below:

http://forum.mikrotik.com/t/new-wireless-package/76487/1

[jarda]

No it isn’t. You have to download it separately. But it is obvious on download webpage…

[jondavy]

I did upgrade from the menu /system upgrade and were not installed some packages defaults as MPLS, then I had to manually reinstall the MPLS package

[patrickmkt]

Something I just noticed after updating two routers to 6.13:

When I connect via SSTP from one ROS client to one ROS Server, the firewall rule associated with this SSTP connection stays red on the server after connection.
It was working before on previous versions. Is there a new parameter that I didn’t see in the update that I need to change or is it a regression?

[rextended]

I know that is off-topic but please someone of MikroTik staff, or another one ingeneer, reply on this post:

http://forum.mikrotik.com/t/is-this-168-km-wirelesse-link-possible/77227/16

[brosky]

@skillful

@panevdd

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?

I confirm this issue on RB1200.

Simple queues are gone in both winbox and webfig. Sometimes the queue are there but frozen in time. After a reboot, simple queues display properly in winbox for sometime before freezing or disappearing. This appears to be a display issue because the simple queues are still functional and limiting clients though.

Same here, 6.13 on RB1100AHx2, queues are not displayed and if I restore from backup they are displayed for a while and then they are missing again.

How can I downgrade to a previous version ? Where is a repository with older versions ?

[Chupaka]

@jondavy

I did upgrade from the menu /system upgrade and were not installed some packages defaults as MPLS, then I had to manually reinstall the MPLS package

check /log

[DjM]

@patrickmkt

Something I just noticed after updating two routers to 6.13:

When I connect via SSTP from one ROS client to one ROS Server, the firewall rule associated with this SSTP connection stays red on the server after connection.
It was working before on previous versions. Is there a new parameter that I didn’t see in the update that I need to change or is it a regression?

Try to double-click on firewall rule, reselect again the same sstp-server interface, clisk OK and it should be fine. It seems that there were some changes in sstp-server interface indexing in 6.13 .

[klaparp]

@klaparp

@klaparp

After upgrade to 6.13 i get “ERROR: Internal Server Error” when trying to log in.

I have tested on 2 different routers. one 750 and onte 2011 with same result. ’

Suggestions?

Get same problem with both webgui and winbox.

2-3 restarts solved the problem on my testing router, I´ll get back later tonight if it works for the production router.

/HW

Didnt help on the production router so I downgraded to 5.26. Also noticed that BCP wont work on 6.12 or 6.13 so its pretty useless. Something major is broken I think.

[dg8ngn]

@lorsungcu

dg8ngn - can you go into more detail about what is broken with BCP in 6.13? I need to upgrade (apparently L2TP is broken in 6.12, which is half the reason I upgraded…), but rely pretty heavily on BCP.

Yes, on the L2TP-Server side the packets are not bridged anymore. Downgrade to 6.12 fixed it.

[rdhw]

@dg8ngn

on the L2TP-Server side the packets are not bridged anymore. Downgrade to 6.12 fixed it.

Yes, I see the same server-side BCP failure over PPTP. Client-side BCP OK on 6.13, but server-side BCP did not work at 6.13 and required to be down-graded to 6.12.

[Clauu]

@bysard

@samotoka

winbox still crash when conected via pptp

Same here.

Same..

[patrickmkt]

@DjM

@patrickmkt

Something I just noticed after updating two routers to 6.13:

When I connect via SSTP from one ROS client to one ROS Server, the firewall rule associated with this SSTP connection stays red on the server after connection.
It was working before on previous versions. Is there a new parameter that I didn’t see in the update that I need to change or is it a regression?

Try to double-click on firewall rule, reselect again the same sstp-server interface, clisk OK and it should be fine. It seems that there were some changes in sstp-server interface indexing in 6.13 .

I already did that but still same behavior on the next reconnection. The firewall rule stays red and I have to reselect it manually again.

[DjM]

In this case I can see two options:

1. Wait for 6.14 release, there are also some SSTP bug fixes
2. Generate support file and send it to MK support

The third possible option can be selecting a different interface in firewall rule, apply configuration, then select back the sstp-server interface and apply configuration. I haven’t tested this step so I’m not sure if it will help, but you can share you experience

[skibi82]

I think 6.13 is as good firmware.

1. Do Not hangs when l2tp/sstp/pptp all versions greater than 6.7 unfortunately had fucked implementations of these tunnels (with 200 tunnels and a large movement of the device had to August reboot using the watchdog)
   Apart from the odd behavior of a process and a higher load mgnt far knock on wood work

2. IPSEC for me is ok about 300 tunnels after the upgrade works correct

I can honestly say I see a light in the tunnel