What's new in 6.8rc1

What’s new in 6.8rc1 (2014-Jan-02 09:46):

*) bgp - don’t show community ‘internet’ in BGP advertisements;
*) ipsec - enable hardware acceleration for aes-cbc-128 + md5|sha1|sha256 aead on tilera cpus;
*) ospf - fixed checksum calculation for OSPFv3 AS-external-LSAs;
*) default configuration - changed dhcp server lease time to 10 minutes;
*) fixed port isolation on CRSs (bug introduced in v6.6);
*) smb - added support for SMB 2.002
*) timezone information updated;
*) ppp - fixed ppp bridging (did not work since v6.6);
*) improved speed of PPP, PPPoE, PPTP & L2TP on multicore routers;
*) address-list - fix crash when adding two identical address list entries (not allowed any more);
*) fixed multicast forwarding on CCRs;

Does anyone tested ipsec on ccr now? I wonder if it will take 1G.

6.8rc1 kills L2TP on CCR for me.

Not sure if perhaps this is a setup issue, but any other version of ROS it works. Move to 6.8rc1, it breaks. Move back 1 version, it works again.

I don’t have time to troubleshoot or produce supout files as this is sadly in production (Stupid me)

Does anyone else notice L2TP issues? Or serious changes over the versions that could cause my config to need to be changed?

Make sure to upgrade to todays build (always)

I can’t risk any more games with this router. It’s in production (Again my stupid mistake)

Please confirm if there was a known L2TP bug between these releases. Simple question.

I did a upgrade + reset on my CRS

Now is all working fine (before only 10mbit if one of the devices was 10 mbit)
Also did a board firmware upgrade

you guys should re-name it to RC2 if there’s a revision. I just re-downloaded it as the same file, same size, just different dates on it. I can’t even tell what was changed from the Jan 2nd and the one released back in December

+1… generally new releases have different version numbers. I have never seen anyone release a new version (different build times, etc) with the same version numbers.

absolutely horrible. I have a PtP I just tested this on. It would link up for about 10-20 seconds, then stay registered, but the rates would drop to 6/162 and not pass any traffic until “-” I minus it off the Master forcing it to re-register, and the process repeats.

if you have any wireless or point-to-points, don’t use this firmware!

+2. Make better naming. RC2, RC3 etc…

+1

I want you to put in the file name, date at least if it is not.

+4

+1

Hi Norman,

Can you assist to check on the following ticket that I’ve report to support team? Being a month already however I did not get any response after which from my correspond to check for update.
http://forum.mikrotik.com/t/any-luck-on-this-ticket-2013120566000115/72822/1

Please at least let me know if someone is looking into this issue to be fix? Do that need more time to check?

The same here. Checked on an Omnitik as AP and a Sextant as client, with an NV2 link between them (actually it is a PtMP link with more clients, but I upgraded only one of them).

It seems to me that the time before the problem kicks in depends heavily on the amount of traffic flowing through the wireless link: more traffic and the link goes down within seconds; less traffic and it can stay on for a day or more.

Downgraded the AP (Omnitik) to 6.7 and it became stable. The Sextant, still on 6.8 rc1, remained unstable. When the latter was also downgraded, the link became stable again.

I wonder if this means that there is some work going on under the hood on the wireless section… :wink:

Try the newest version 6.8RC1(2014-01-08 14:00:28)。
L2TP work fine for me:)

wispwest and nkourtzis, we were able to reproduce this problem. We fixed this problem, you can redownload the v6.8rc1 - Nv2 should work stable
again.

Hey Uldis,

Could you take a look at: http://forum.mikrotik.com/t/test-result-ccr-kernel-panic-6-8rc1-updated-11-01-2014/72927/1
So far every 6.8rc1 build since this year (starting from the 2-1-2014 build), give kernel panics.
Cannot create supouts sadly, because of the reboots the kernel panic issues, it keeps rebooting in a loop.

we fixed this problem, you can redownload the v6.8rc1.

If you changed something to fix it, shouldn’t you really call that v6.8rc2 ? Sort of confusing when you change things or fix something and call it the same release.