RouterOS 6.10 beta

RouterOS General
1

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;

2

When the cell copying feature (http://forum.mikrotik.com/t/feature-request-cell-copying-in-the-winbox/71832/1) will?

3

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”

4

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;

5

where download 6.10?

6

Write MikroTik support for development access to RouterOS.

7

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.

8

the 6.10 build 2.6.2014 fixed eoip

9

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

10

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

11

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

12

Please, fix it in 6.10: http://forum.mikrotik.com/t/6-9-released/73788/161

13

Because their naming makes no sense.

Sent from my SCH-I545 using Tapatalk

14

Works fine here

15

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.

16

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 instead of the configured profile (we always set new profiles rather than “default-profile”)

17

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

18

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.

19

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;

20

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.