It seems that ROC 6.34rc1 seems to break OSPF “for some reason” in the CRS210-8G-2S+.
Reverting to ROS 6.32.3 corrects the issue.
I have tried this upgrade/downgrade twice. 
6.34rc3 version will be released today:
Changes since 6.34rc1:
*) smb - fixed SMB share crash when connection was cancelled;
*) lcd - fixed LCD crash on fast disable/enable;
*) fastpath - fixed wireless interface fastpath (broken in 6.33);
*) pppoe - fixed compliance to RFC4638 (MTU larger than 1488);
*) webfig - show correctly SFP Tx/Rx;
*) winbox - renamed power-cycle-ping-interval to power-cycle-ping-timeout;
*) CCR1072 - added support for S-RJ01 SFP modules;
*) trafficgen - fixed issue that traffic-generator could not be started twice without reboot;
*) dhcpv4-client - support /32 address assignment;
*) licensing - fix unneeded connection attempts to 169.254.x.x (must be CHR only);
*) dhcpv6-server - replace delay option with preference option;
*) dhcpv6-client - added address acquisition support;
*) dhcpv6 - implement and enable rapid commit by default.
Upgraded from 6.33 to 6.34rc3 and lost my ipv6 dhcp-client config. (no entry)
Reverted to 6.33, but still had to add back the client entry.
CRS210 still does not route correctly using 6.34rc3. Reverting to 6.33 resolves it. This is using a SFP fiber connection to a CRS112 which is successfully running 6.34rc3.
Auto-negotiation on the fiber ports have been disabled. I’m running OSPF.
Remember, 6.33 works perfectly 
, 6.34rc1 or 6.34rc3 doesn’t work 
.
I’ve tried netinstall, no joy. Added a second boot partition so I don’t have to keep reinstalling 6.33 when I try 6.34rc
That’s a pretty slick feature, I might add… Saves a lot of headache !!
we are working on DHCPv6-client, so you might experience some problems with the DHCP-PD client as they are in the same place. If that is important feature you are using for day to day configuration wait at least till rc5 release or newer.
Can you fix RouterOS update from winbox please for multiple internet links router?
It has error “No route to host” even if all routers behind this one have access without problems.
PtDragon - Please send supout file from your device to support@mikrotik.com
6.34rc5 will be released today.
Changes since 6.34rc3:
*) dns - fix for situation when dynamic dns servers could disappear;
*) packages - show version tag when no bundle is installed;
*) vrrp - fix enabling disabled vrrp interface when vrrp program has exited;
*) winbox - do not send any changes on OK button press if nothing has been changed;
*) sfp - fix 10g ports in 1g mode (introduced in 6.34rc1);
*) dhcpv6-client - added DHCPv6-client functionality for current DHCP-PD client;
Curious about the 10 G ports in 1 G mode correction.
Actually there is a problem with 1G SFPs in SFP+ ports, it doesn´t work with autonegotiation enabled. Is it related? A friend has a problem with such a setup.
Can’t seem to find it..
CCR1072 - added support for S-RJ01 SFP modules;
Is it ccr1072 will support sfp-t by all that means?
So it supposed that ccr1072 support for sfp-f 1ge ?
Any body can give me clarification about this?
Hi Guys
Can we please get driver support for the the following Broadcom 4 ports SFP+ card. It uses the Broadcom BCM57840S controller. I have 1 of these cards based on the http://wiki.mikrotik.com/wiki/Supported_Hardware#Ethernet_chipsets page I thought it would be supported.
http://www.supermicro.com/products/accessories/addon/aoc-stg-b4s.cfm
6.34rc5 shows in the tracker page, but is not accessible.
Download still shows 6.34rc3 as the latest.
“Today” have another sense from today
Hi Guys
Can we please get driver support for the the following Broadcom 4 ports SFP+ card. It uses the Broadcom BCM57840S controller. I have 1 of these cards based on the http://wiki.mikrotik.com/wiki/Supported … t_chipsets page I thought it would be supported.
http://www.supermicro.com/products/acce … tg-b4s.cfm
We can’t add drivers. RouterOS drivers come from the used Linux Kernel. We only change kernel in big releases, next change will come in RouterOS v7
Hi Normis
This does not really help as we have been hearing about ROSv7 for a long time but not even seen a alpha or beta version, so this could be another 2 years before we see any ROSv7, and in the meantime all new network interfaces is unusable because of old kernel being used. Broadcom have back ported their drivers to even kernel 2.6.x so I cant see how this can not be injected into the v3 kernel used by ROSv6.
Can you please explain? I’m sure we have other users with similar issues.
Support promised to me ros7 (public alpha) in this year. month and a half left. With interest expect.
Although I believe that ros7 - it is a myth. As an afterlife, for example.
RB433UAH (power 24V 2A) 6.33 ; 6.34rc3, 6.34rc6
After several versions reappeared error USB Flash disk.
Version 6.34rc6 has been released.
Changes since previous rc version:
*) pppoe - fixed compliance to RFC4638 (MTU larger than 1488) again;
*) hotspot - fixed trial-uptime parsing from CLI to Winbox/Webbox;
*) lte - added support for multiple E3372 on the same device;
*) modem - added wpd-600n ppp support;
*) dhcpv6 client - support DAD and decline;
*) dhcpv4 server - fix kernel crash when restoring lease with queue for non-existent server;
*) console - fixed incorrect disabled firewall rule matching to “invalid flag”;
*) ssh - fix key exchange when first kex packet follows.