As title says, RouterOS 6.10 has been released for development testing. No changelog so far.
I will keep this thread updated, as a changelog appears.

Update:

What's new in 6.10 (2014-Feb-06 12:44):

*) ipv6 pool - fix dynamic prefix disappearing which may influence large VPNs with IPv6;
*) ssh client - fix key agreement when sometimes wrong DH algorithm was selected;
*) bgp - multipath eBGP now does not propagate BGP nexthop unless
forced in configuration;

When the cell copying feature (http://forum.mikrotik.com/viewtopic.php?f=1&t=79209) will?

any known problems with eoip? 6.9 was working fine but after the switch to 6.10 it isn't passing traffic.

this is over a pptp connection, eoip is building and keeping a connection but no packets passed "other then keep alive"

What's new in 6.10 (2014-Feb-06 10:57):

*) ssh client - fix key agreement when sometimes wrong DH algorithm was selected;
*) bgp - multipath eBGP now does not propagate BGP nexthop unless
forced in configuration;

where download 6.10?

Write MikroTik support for development access to RouterOS.

any known problems with eoip? 6.9 was working fine but after the switch to 6.10 it isn't passing traffic.

this is over a pptp connection, eoip is building and keeping a connection but no packets passed "other then keep alive"

Well all is working for me just fine in EOIP over PPTP that is bridged on both sides with Ethernet.
Just check if EOIP mac addresses are different on both tunnel end also - check what MAC addresses bridge is using.
If no write to support with supout.rif files from both ends.

the 6.10 build 2.6.2014 fixed eoip

Why name is 6.10 ?
It is pre-release for testing. It should be 6.10rc1

Anything about fixing routing marks in 6.10 (broken in 6.9, works in 6.7)?

Is anyone seeing any better throughput with Nv2 PtP's with this?

Please, fix it in 6.10: http://forum.mikrotik.com/viewtopic.php ... 14#p407914

Why name is 6.10 ?
It is pre-release for testing. It should be 6.10rc1

Because their naming makes no sense.

Sent from my SCH-I545 using Tapatalk

Anything about fixing routing marks in 6.10 (broken in 6.9, works in 6.7)?

Works fine here

I upgraded again to 6.9 to check again:
- connection mark works ok
- routing mark in firewall works (at least rule counts packets, doing 2 different marks, based on connection mark and mangle rules)
- route shows up inactive and does not work, even if gateway says reachable, as if the interface is visible only from the main table, but not from other routing tables (outgoing interfaces are PPPoE and sstp server binding).
So it doesn't work.

A simple downgrade to 6.7 fixes everything.

6.7 to 6.9 broke pptp connections on several of our systems in production. It actually works fine, however after upgrade security profiles were not working/applied ... showing <unknown> instead of the configured profile (we always set new profiles rather than "default-profile")

6.7 to 6.9 broke pptp connections on several of our systems in production. It actually works fine, however after upgrade security profiles were not working/applied ... showing <unknown> instead of the configured profile (we always set new profiles rather than "default-profile")

could you please clarify where exactly you saw "unknown"? I just upgraded a PPTP server running 6.7 to 6.9 and my 'pofile1' still says 'profile1'

6.7 to 6.9 broke pptp connections on several of our systems in production. It actually works fine, however after upgrade security profiles were not working/applied ... showing <unknown> instead of the configured profile (we always set new profiles rather than "default-profile")

could you please clarify where exactly you saw "unknown"? I just upgraded a PPTP server running 6.7 to 6.9 and my 'pofile1' still says 'profile1'

Screenshot 2014-02-10 10.01.55.png

It happens when the 6.7 version was running the experimental PPP package. At least everywhere i got this problem, the 6.7 experimental PPP package was installed and after upgrade all PPP settings/profiles/interfaces were gone.

What's new in 6.10 (2014-Feb-10 15:11):

*) ovpn client - remove cipher=any & auth=any options, protocol does not support them;
*) pptp - fixed where Windows & MacOS clients were disconnecting all the time;
*) sstp - make it work with Windows client with AES encryption;
*) ipv6 pool - fix dynamic prefix disappearing which may influence large VPNs with IPv6;
*) ssh client - fix key agreement when sometimes wrong DH algorithm was selected;
*) bgp - multipath eBGP now does not propagate BGP nexthop unless forced in configuration;

could you please clarify where exactly you saw "unknown"? I just upgraded a PPTP server running 6.7 to 6.9 and my 'pofile1' still says 'profile1'

What shiny said, although we were not running "ppp experimental' package.
All profiles were missing in Winbox and webfig, present in the cli, but not recognized in the PPTP interface .
Re-entering the security profiles fixed the issue. Sorry I can't seem to replicate the issue downgrading to 6.7 then upgrading to 6.9.

you should remove the ppp test package before upgrading to v6.9 or later. there is nothing else that can be done, unfortunately

What's new in 6.10 (2014-Feb-10 15:11):
*) ovpn client - remove cipher=any & auth=any options, protocol does not support them;

When OVPN start working on UDP?

we have released a new pre-release build for v6.10, please test for remaining issues. most of the reported things in v6.9 have been fixed already

What's new in 6.10 (2014-Feb-11 11:05):

*) fix autosupout.rif generation after kernel panic;
*) ovpn - make it work again;
*) ovpn client - remove cipher=any & auth=any options,
protocol does not support them;
*) pptp - fixed where Windows & MacOS clients were disconnecting all the time;
*) sstp - make it work with Windows client with AES encryption;
*) ipv6 pool - fix dynamic prefix disappearing which may influence large
VPNs with IPv6;
*) ssh client - fix key agreement when sometimes wrong DH algorithm was selected;
*) bgp - multipath eBGP now does not propagate BGP nexthop unless
forced in configuration;

If using the ppp-v6 package, remove it first, then upgrade

And what about Ticket#2014020366000387, is it fixed or will be?

And what about Ticket#2014020366000387, is it fixed or will be?

it is fixed already

And what about Ticket#2014020366000387, is it fixed or will be?

it is fixed already

I asked beacuse there is no info in changelog

Any other improvements in ppp?

Fixed.

Send a supout to support and also specify what client you are using and what client config.

What about using MRRU parameter in ppp-server (l2tp/pptp) configuration on RB 1100AHx2? Any fixes?

What about using MRRU parameter in ppp-server (l2tp/pptp) configuration on RB 1100AHx2? Any fixes?

I love these! Like everyone here should knows what you are talking about... What about it, exactly?

Woof in 6.10 build Feb/12/2014 10:52:34

/ip ipsec peer> set local-address=

The first step in the right direction
Now I was left to wait for the rest of the VPN

I'll arrange a test thank you

Regards
J>S

/ip ipsec peer> set local-address=

The first step in the right direction
Now I was left to wait for the rest of the VPN

Very exciting!

Hopefully /ipsec peer set address becomes /ipsec peer set remote-address to keep things consistent and logical.

/ip ipsec peer> set local-address=

The first step in the right direction
Now I was left to wait for the rest of the VPN

Very exciting!

Hopefully /ipsec peer set address becomes /ipsec peer set remote-address to keep things consistent and logical.

Holy crap!

Awesome change!

Please please please MORE IPSec updates!

What about using MRRU parameter in ppp-server (l2tp/pptp) configuration on RB 1100AHx2? Any fixes?

I love these! Like everyone here should knows what you are talking about... What about it, exactly?

Problem is described in two or more post above, but I do it again:

Upgrade: 6.6 -> 6.9
RouterBOARD: RB 1100AHx2
Tested bugs:
а. [L2TP-Server]:
After upgrade router reboots while first l2tp-session established with watchdog exeption message on serial console.
L2tp-server (and router) crash caused by the use of MRRU (value doesn't matter) parameter in /interface l2tp-server server configuration, so multilink-PPP over single link seems to be broken.
b. [Update]:
Client Mikrotik RB 750G with MRRU option enabled.

Ticket#2014021266000146

I'll try to get support.rif (it constantly reboots, so this bit difficult) from router later.

I have same issue as user sdv.

I am worry about upgrading, I don't have time to go to the datacenter when it goes to constantly rebooting again

there is final ROS 6.10
http://forum.mikrotik.com/viewtopic.php?f=2&t=81872