v6.34.6 [bugfix] is released!

Announcements
1

Version 6.34.6 has been released in bugfix channel.

Changes since previous version:
*) discovery - fixed identity discovery (introduced in 6.34.5);
*) log - fixed time zone adjustment (introduced in 6.34.5);
*) snmp - fixed snmp timeout (introduced in 6.34.5);
*) vrrp - fixed missing vrrp interfaces after upgrade (introduced in 6.34.5).

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

2

Route mark working in this version. CCR1009 All seems stable.

3

Good to know, I’ll update soon too. Thanks, much appreciated.

4

hAP lite upgraded 3,5 hrs ago and no issues detected so far.. Timestamps are ok now.

5

Updated from 6.32.3 on 1x RB3011 and 2x RB951. Went smooth and noticeable improvements. Great job MT team! :smiley:

6

Moved ~60 boards (CCRs, hAPs wAPs, CRSes, SXTs mostly) to this version - all solid so far..

P.S. five nice comments in a row about version? - this is WITCHCRAFT!! :slight_smile:

7

3 RB1100ahx2 upgrading all working well so far.

8

6.34.6 is working well on our test CCR’s.

Nice work Mikrotik

9

Upgraded some ipsec endpoints (mostly rb1100) ..all working well.
The new bugfix version seems to have the same quality/stability level of previous.. maybe better.
Well done!

10

Maybe we found a new LTS release…

11

After upgrade to 6.34.6 I encounter some error logs for IPsec when connecting from client machines (Windows 7, Android 6) to Mikrotik L2TP/IPsec server. The IPsec Proposal allows aes-256-cbc, aes-192-cbc, aes-128-cbc, and 3des
If Windows connects (aes-128) there is error
ipsec,error key length mismatched, mine:256 peer:128.
ipsec,error key length mismatched, mine:192 peer:128.
and after that there is a success when MT uses 128 in its 3rd attempt. If I disable aes-256 &192 then Android can not connect

12

that is because more secure algorithms are picked first until supported protocol by client is matched.

13

Thank you on your prompt response, appreciate.
I have solved the problem by choosing the Maximum strength encryption under “Data Encription” in Security Tab of the connection on the Windows client machine.
Now also win client chooses 256 as well as android

14

It does not work Simple Queues.Check it out!

15

Disable Fasttrack

16

Thank you so much!
That helped. Yet it is a bug, or tell how it should be?

17

Not a bug, read documentation.

18

This is probably good example why Dummy simple queue is necessary (similar to dummy firewall rules)

19

traffic engineer not working, had to downgrade and links came up.

20

please send your suppout.rif with your configuration and description to support@mikrotik.com we will test it.