v6.34 [current] is released!

[Attila]

Sorry guys but why do not you paying attention?
After several months and after a lot of rc release of new major version is full of basic errors. (GRAPH, SNMP, etc.)
It’s not very good…
The RouterOS software version 6.34 is the 34th major release of RouterOS 6.
What’s going on with you?

p.s., Developers can safely take this reproach…

[paoloaga]

@Attila

After several months and after a lot of rc release of new major version is full of basic errors. (GRAPH, SNMP, etc.)

Probably graph counters show less traffic because the code that hides traffic generated by the new backdoor includes also normal packets… (just kidding).

[Genkun]

@Cha0s

Can you be more specific? What exactly isn’t working?

I’ve upgraded 3-4 devices to 6.34 so far and I haven’t got any issues with SNMP (or anything else for that matter) using Cacti, Observium, Dude and custom scripts.

I noticed when upgrading a CCR1036 with V6.34. snmp with cacti shows incorrect data. The Cacti will flatline on a read of 80mbps or whichever for about an hour or so and then update correctly again. When you log into the unit the SNMP data updates correctly immediately.

We noticed as there were large gaps where the data was exactly the same on Cacti and when we logged into the unit, while there was this flatline, the router showed different values. A minute after logging in the Cacti data with synchronize correctly again.

[strods]

Graphing and SNMP related issues are fixed in 6.35rc3 version:
*) interface - show stats properly in bits not bytes;

[pe1chl]

@dadaniel

6.34 WebFig Torch malfunction, showing two lines of incomplete data (after clicking on start it works):

It is the normal behaviour, isn’t it?

[paoloaga]

@strods

Graphing and SNMP related issues are fixed in 6.35rc3 version:
*) interface - show stats properly in bits not bytes;

Is it too much asking for a v6.34.1 with the fix? Using an RC in production environment sounds a bit scary…

[ranpha]

@mariusmotea

Hi!

After i upgrade from 6.30.4 to 6.34 i discover ipv6 was not working anymore. The issue seams to be the ipv6 dhcp client stuck in “Status: searching…”. After i click the “Release” button the status is switching to “Status: bound” and then ipv6 is working fine. I’m using RouterOS in a KVM virtual machine and before the update i made a snaphot. If i revert to snapsot (version 6.30.4) everything is working fine. I try to reconfigure from scatch the version 6.34 to see if the issue is present and it was.
My connection type is pppoe with dhpd-pd

Marius.

I also experience the same problem here, with pppoe +dhcpv6-pd. Reverting to 6.33.5 and everything works again.

[lordcoke]

@strods

We have released 6.34 version.
What’s new in 6.34 (2016-Jan-29 10:25):
*) ipsec - allow my-id address specification in main mode;
*) ipsec - prioritize proposals;
*) ipsec - support multiple DH groups for phase 1;

/ip ipsec peers display problem for enc-algorithm. Peers configured with enc-algorithm=aes-128 are shown with enc-algorithm=aes-256

[paoloaga]

What’s new in 6.34.1 (2016-Feb-02 14:08):

*) interface - fixed stats that were 8x smaller;
*) traffic-monitor - fixed stats that were 8x smaller;
*) smips - properly detect smips boards for winbox & webfig.

Wonderful! Good job Mikrotik!

[easyspot]

RB951Ui-2HnD:
Can’t do web proxy to external disk. Tried USB Flashdisk and USB HDD External, same result. After building cache, running, can’t open anything. Few files entered USB disk but can’t clear cache.
If untick Cache to Disk, everything works normally.

[strods]

Version 6.34.1 has been released:
http://forum.mikrotik.com/t/v6-34-1-current-is-released/95097/1

[mrz]

@lordcoke

@strods

We have released 6.34 version.
What’s new in 6.34 (2016-Jan-29 10:25):
*) ipsec - allow my-id address specification in main mode;
*) ipsec - prioritize proposals;
*) ipsec - support multiple DH groups for phase 1;

/ip ipsec peers display problem for enc-algorithm. Peers configured with enc-algorithm=aes-128 are shown with enc-algorithm=aes-256

It is cosmetic problem. Console shows aes-256 instead of aes-128. Winbox/webfig shows correct value. Will be fixed in one of the next rc builds