It appeared in v6.34 and is already fixed in v6.35rc. It is just a cosmetic bug that aes-256 is displayed as aes-128

Maybe cosmetic but I have just wasted an hour on it migrating a router and wondering why my scripts dont work.

Same here the other day

I've noticed an issue running 6.34.1 and Winbox 3.1. If I set the email server in Winbox > Tools > Email > Server to either the fqdn or ip of my mail server then try send an email I get an error connecting entry in the logs.

"/tool e-mail print" didn't show a server address entry. "/tool e-mail set" had an address setting option which I set to my mail servers fqdn. This updated the Winbox email server setting and I was able to send emails.

So setting "/tool e-mail set address=fqdn/ip will set Winbox > Tools > Email > Server but not vice versa.

I've noticed a bug in IPIP tunel export. In default compact mode. Parameter "keepalive" is always with exclamation mark.

It works fine with verbose parameter.

We have a problem with the DHCPv6 Server since 6.34
When the lease expires it not automatically binds a new subnet to the client.
When i disconnect the client and reconnect it, a new lease is given to the client.

We have the problem on 2 different Routers (RB2011 and RB3011).

DHCP-Servers:


Bindings before lease expires:


Bindings after lease has expired:

I've noticed an issue running 6.34.1 and Winbox 3.1. If I set the email server in Winbox > Tools > Email > Server to either the fqdn or ip of my mail server then try send an email I get an error connecting entry in the logs.

"/tool e-mail print" didn't show a server address entry. "/tool e-mail set" had an address setting option which I set to my mail servers fqdn. This updated the Winbox email server setting and I was able to send emails.

So setting "/tool e-mail set address=fqdn/ip will set Winbox > Tools > Email > Server but not vice versa.

I have reply from MT: "The problem will be resolved in next RouterOS verions, starting from 6.35rc11"

I've noticed an issue running 6.34.1 and Winbox 3.1. If I set the email server in Winbox > Tools > Email > Server to either the fqdn or ip of my mail server then try send an email I get an error connecting entry in the logs.

"/tool e-mail print" didn't show a server address entry. "/tool e-mail set" had an address setting option which I set to my mail servers fqdn. This updated the Winbox email server setting and I was able to send emails.

So setting "/tool e-mail set address=fqdn/ip will set Winbox > Tools > Email > Server but not vice versa.

I have reply from MT: "The problem will be resolved in next RouterOS verions, starting from 6.35rc11"

Good to know - we reported it as affecting RoS 6.33.5 onwards......

Still having the following Error ( Attachement ) at Mikrotik OVPN - Server, when a non Mikrotik - Client connects.

Can anybody explain, what's going wrong ?
I tested several ( Linux and Windows ) OVPN - Clients,
always the same except the OVPN - Client is a Mikrotik - Router itself !

Manfred

@Manfred please open a new topic for your issue. It is most probably a certificate mismatch or configuration error. Provide both client and server configurations and log output from the client. Or better off, just send requested data to support@mikrotik.com with supout.rif attached.

when 6.34.2 going to release? I am waiting for specific bugfix..

Version 6.34.2 [current] has been released:
http://forum.mikrotik.com/viewtopic.php?f=21&t=105019