RouterOS v7.0 beta1 - when?

RouterOS General
1

Hi,

When RouterOS v7 beta1 is gonna to be released?

2

we all are interested too

3

Same here…we are starting to think v7 is a unicorn :smiley:

4

a magical unicorn :wink:

5

Be patient guys!
I’m sure they work on it but let’s wait for their news.
Don’t pus them, they should work without our pressure to make it good :slight_smile:

6

I wish it was true. Experience says that we will need to betatest and request the connections during next two years after first stable release to get really working ros. Anyway I am looking forward.

7

Hello friends,

Someone had news about the V7 release date?

8

As normis said here

Sometimes versions are released sooner if there is a critical issue that needs to be resolved. Sometimes we work on a bigger change, so version takes longer.

v7 is currently in internal testing, and will be released as beta when it’s stable enough

So no exact date for us.

9

Mikrotik people never give dates as they are not able to fulfil any given date. Their official answer is “when it will be then it will be”. Take it or leave it. I just live with that as with exogenous fact.

10

Really accurate and truthful description :slight_smile:

11

It’s better to not publish a deadline if it’s not sure that it could be honored.

It’s even better to release 7.0 beta 1 tomorrow! :slight_smile: :slight_smile:



(I didn’t know that the maximum amount of smilies allowed in a message is 3).

12

Whats the point of a beta if you don’t release it, beta’s are meant to be unstable. Release the beta, and start getting broad input early.

Not like they’re asking when v7 Final or even RC will be out but beta, for all we know there cud be 900 beta releases before rc1

13

(I didn’t know that the maximum amount of smilies allowed in a message is 3).[/quote]
In that forum we don`t like smiles! :laughing: :laughing: :laughing:

14

We will release a beta, when it will exist. Currently v7 is in alpha stage, many functions are not completed and non functional. Beta needs at least all functions to be somewhat operational.

15

Thanks normis, understood is their a timeline/roadmap for when you guys think you’ll reach feature complete for beta? Or even a feature list for what your planning to implement, i mean right now all the forum seems to be is a wishlist.

Things like proper DHCPv6 with radius and other v6 stuff that don’t match up with the v4 counterparts sort of are forcing some of us into chosing between investing in MT now for large deployments knowing that the v6 features are coming, and just going another way (cisco etc) which i personally would rather not do.

16

Have you got fq_codel working yet in 7.0?

I have done fq_codel backports (where needed) for several manufacturers at this point, and can help out - I also do things like BQL - and I would really like to get some performance numbers out of it + sqm-scripts on your higher end hardware, when your next version of the OS arrives.

We hit a pretty hard shaping limit on a lot of lower end gear at about 60Mbits of HTB, (the fq_codel part is nearly invisible to the cpu, but HTB, oh, my!), and the market, at least in the US, is migrating to 110Mbits of needed inbound shaping on comcast’s deployment to cut inbound latencies from about 600ms to 10ms, under load.

I keep hoping to find an off-the shelf solution for my userbase that works as well as 110mbit as it does at 50mbit.

http://burntchrome.blogspot.com/2014/05/disabling-shaping-in-one-direction-with.html

17

Hey – you wrote one of the RFCs here! :stuck_out_tongue: Awesome!


+1 for fq_codel. This is one of the ~only things significantly holding back our RouterOS userbase.

We have to significantly throttle bandwidth to preserve some highly interactive apps at peak throughput. fq_codel would be of huge benefit to us!

18

I just wish MT was more open with the 7.0 development, i’m really silently praying that MUM March they start to announce some things. I mean even just a “what we have working so far” “whats we want to work” " what we plan to fix in 7" something…

I mean are we looking at mid-late 2015 or 2018 lol

There’s a number of blockers that everyone’s aware of,
1gigabit tcp stream limit due to it being non-threaded
DHCP RADIUS Accounting
fq_codel support
lldp support
ipv6 NAT64/DNS64/6rd/Radius… pretty much everything beyond the basic bare minimum :slight_smile:
Radius COA Support

19

Would like to know as last post.. Mikrotik.. are we talking 4 weeks or 4 years?
Please lets us know any information..

/Markus

20

yes, PLEASE make RouterOS opensource or create quality SDK. I’ll bet there are a lot of good programmers who can help make RouterOS better.