MikroTik

Awesome, installing it on a spare 3011. Is there a special version of winbox needed? Or any changelog available?

I can't read that!

Have any special instructions been given?
I see a netinstall and an npk, do you need to use netinstall or is it enough to upload the npk and reboot?
Is it limited to certain ARM devices or can it be used on all of them? (I have an unused LHG ac that I could try it on)

Have any special instructions been given?
I see a netinstall and an npk, do you need to use netinstall or is it enough to upload the npk and reboot?
Is it limited to certain ARM devices or can it be used on all of them? (I have an unused LHG ac that I could try it on)

No other instructions was given. Heard hAP ac² and some other devices mentioned, so I guess there's no restrictions on 4G-5G devices only.

4.14 has longer EOL than 4.19

So instead of a kernel from 2012 we are now going to have a kernel from 2017.
Lets hope they can update this to the 4.19 version soon.

So instead of a kernel from 2012 we are now going to have a kernel from 2017.
Lets hope they can update this to the 4.19 version soon.

Why stop at 4.19 ... MT should go for 5.3 ... ROS 7.0 is beta, and linux kernel 5.3 is RC. With current pace, linux kernel will be at least at 5.8 long term before ROS V7 hits stable...

Maybe I am looking with my nose.. but is there a changelog available?

Maybe I am looking with my nose.. but is there a changelog available?

Maybe I am looking with my nose.. but is there a changelog available?

Currently v7 has v6.45.5 feature set. Main change is a new Linux Kernel, rest of features will gradually come out in next builds as for now we want to ensure that v7 is stable on hAP ac^2 and WAPGR LTE/4G/LTE-US boards mainly (and other boards) to get v7 ready for upcomming 5G products.

When will you include support for MIPSBE?

Maybe I am looking with my nose.. but is there a changelog available?

Currently v7 has v6.45.5 feature set. Main change is a new Linux Kernel, rest of features will gradually come out in next builds as for now we want to ensure that v7 is stable on hAP ac^2 and WAPGR LTE/4G/LTE-US boards mainly (and other boards) to get v7 ready for upcomming 5G products.

after installing this release on CRS317 lost connectivity via SFP
SFP page shows only module present
after downgrading to 46beta38 SFP shows all info, signal strenght but no link

Added ext4 support ?

[admin@MikroTik] > sys reso print 
                   uptime: 2m16s
                  version: 7.0beta1 (development)
               build-time: Sep/05/2019 15:08:48

[admin@MikroTik] /disk> format-drive file-system=
ext3  fat32

I imagine people are going to freak about this

Code: Select all

/interface/ovpn-server/server/set protocol=udp

I lost BGP, but I gained /routing/pimsm and /routing/fantasy,

Some paths are given with "/", some with white space. Is both allowed now?

BGP/MPLS are disabled intentionally, as this is a home router test.

Changelog?

Currently v7 has v6.45.5 feature set. Main change is a new Linux Kernel, rest of features will gradually come out in next builds as for now we want to ensure that v7 is stable on hAP ac^2 and WAPGR LTE/4G/LTE-US boards mainly (and other boards) to get v7 ready for upcomming 5G products.

Whoa! Just installed 7.0beta1 on a hAP ac^2. Wireless/EoIP/VPN all work.
Routing stack seems to have changed quite dramatically though!
I lost BGP, but I gained /routing/pimsm and /routing/fantasy, although I have no clue what that last one does yet.

Have any special instructions been given?
I see a netinstall and an npk, do you need to use netinstall or is it enough to upload the npk and reboot?
Is it limited to certain ARM devices or can it be used on all of them? (I have an unused LHG ac that I could try it on)

Currently running it on a RB3011 so I think it will be all arm devices.

Added ext4 support ?

Code: Select all

[admin@MikroTik] > sys reso print 
                   uptime: 2m16s
                  version: 7.0beta1 (development)
               build-time: Sep/05/2019 15:08:48

[admin@MikroTik] /disk> format-drive file-system=
ext3  fat32

i guess not.

what VPN are you running?

Any reason you can think of to actually upgrade & try this v7 ?
Don't think my RB3011 here will become faster or more stable.

Added ext4 support ?

Code: Select all

[admin@MikroTik] > sys reso print 
                   uptime: 2m16s
                  version: 7.0beta1 (development)
               build-time: Sep/05/2019 15:08:48

[admin@MikroTik] /disk> format-drive file-system=
ext3  fat32

i guess not.

One thing is user-land tool to format drive. Another thing is plugging USB stick already formatted with ext4 ... does ROS recognize it?

So, unless you like to live on the edge (and sometimes slightly over it), then there's no reason to install ROS v7 on your production devices yet.

what VPN are you running?

PPTP- and OpenVPN-clients both work fine. OpenVPN server in UDP mode works as well (just tried it)!

We have never promised multicore BGP routing, by the way.

Some info about upcoming routing:

https://www.youtube.com/watch?v=NbfKplzda7I

Tried twice to install V7 on my hap ac2. Bricked the hell out if it. Thank MikroTik for netinstall...... Wil try beta2

I imagine people are going to freak about this

Code: Select all

/interface/ovpn-server/server/set protocol=udp

We have never promised multicore BGP routing, by the way.

Surely, but keeping in mind your multicore CCRs for such a decent money and mostly stable BGP implementation you have there is no wonder a lot of poor it man still hoping for that.

Labtest beta? I tried the link on the first page. http://mt.lv/v7

We have never promised multicore BGP routing, by the way.

Surely, but keeping in mind your multicore CCRs for such a decent money and mostly stable BGP implementation you have there is no wonder a lot of poor it man still hoping for that.

The "demo" I saw recently (no idea if it was a hoax) showed at least the use of some more cores for BGP, when multiple peers are present.
Not a completely multithreaded version which would use most or all cores on a CCR1072, but at least it is something.
(it appeared to handle each peer's updates in a separate process and then send them to a central process to compute the routing table, which was still single-core)

Thinking about it, I wonder if BGP can be made multithreaded by splitting all routes by prefix length. I would think the recomputation of the routing table can be done separately for each prefix length.
(there should be no interlocks needed between updates of routes of different prefix length)

The "demo" I saw recently (no idea if it was a hoax) showed at least the use of some more cores for BGP, when multiple peers are present.
Not a completely multithreaded version which would use most or all cores on a CCR1072, but at least it is something.
(it appeared to handle each peer's updates in a separate process and then send them to a central process to compute the routing table, which was still single-core)

Thinking about it, I wonder if BGP can be made multithreaded by splitting all routes by prefix length. I would think the recomputation of the routing table can be done separately for each prefix length.
(there should be no interlocks needed between updates of routes of different prefix length)

BGP cannot be split in the way you propose. Filters need to be processed in a "run to completion" fashion. Currently the only way to get a semblence of multi threading is to run a thread/process per BGP peer, process the routing update against the filter set, then push the result up to a conductor process that runs the best path selection algorithm against the routes in the active RIB.

If anyone is having issues installing the beta like I did on a hAP ac2, I had to update the firmware in System>Routerboard before the v7 beta would boot properly.

Try putting your router on latest v6 Stable or Testing release before upgrading to the v7 beta

Labtest beta? I tried the link on the first page. http://mt.lv/v7

Wireless not working?

Wireless not working?

Changelog please

Sent from my SM-A705FN using Tapatalk

Currently v7 has v6.45.5 feature set. Main change is a new Linux Kernel, rest of features will gradually come out in next builds as for now we want to ensure that v7 is stable on hAP ac^2 and WAPGR LTE/4G/LTE-US boards mainly (and other boards) to get v7 ready for upcomming 5G products.

I believe we used the phrasing, much imroved BGP speed, or something like that

I believe we used the phrasing, much imroved BGP speed, or something like that

What is the current version of the kernel?

Has anyone tested version 7 on RB4011(or RB3011) ?

Linux kernel has upgraded from 3.3.5 to 4.14.131.

Cource of this information?

Linux kernel has upgraded from 3.3.5 to 4.14.131.

Cource of this information?

DO NOT install this on production gear. This release is experimental and should be treated accordingly.

Any reason you can think of to actually upgrade & try this v7 ?
Don't think my RB3011 here will become faster or more stable.

More stable definitely not, faster likely not ... according to changelog, kindly published by @krisjanisj, not even more functionalities.

So, unless you like to live on the edge (and sometimes slightly over it), then there's no reason to install ROS v7 on your production devices yet.

When will you include support for MIPSBE?

No current ETA can be given but won't be years...

Linux kernel has upgraded from 3.3.5 to 4.14.131.

Cource of this information?

Unpacked .npk file
V7.png

which program did you use to unzip?

Linux kernel has upgraded from 3.3.5 to 4.14.131.

Cource of this information?

Unpacked .npk file
V7.png

7zip

which program did you use to unzip?

Linux kernel has upgraded from 3.3.5 to 4.14.131.

Cource of this information?

Unpacked .npk file
V7.png

which program did you use to unzip?

7zip

I already read CCR support won’t take years and there is no ETA, but... is it expected to be released in this year or not?

Has anyone tested version 7 on RB4011(or RB3011) ?

Hi,

I've tested 7.0beta1 on a hAP ac² and I was not able to get my configuration with VLANs (used the hw capabilities of the switch chipset) to work. Without VLANs it worked. For the moment I downgraded back to latest stable version.

Best Regards
Tobias

L7 application identification

NV3 is coming?

Hopefully its close to this:

Latest linux release 5.2.11 (29 August 2019)

At least based on 5.x and 4.x

OVPN is not compatible with the previous v6;
v7 ovpn client does not connect to server v6.45 if certificates are used.

Where were the certificates generated?
In my experience, MT generated certificates don't work with the Windows OVPN desktop client (maybe they do now, I haven't tested recently). Maybe, hopefully, if your certificates are MT generated from v6 or older this is an indication that Mikrotik is now using code from the actual OpenVPN project?

Wifi6/802.11ax have TDMA as a part of the specification, so there should be no need to implement any proprietary TDMA protocol for it.
It can even do much more than what supposed NV3 would ever do, like splitting bandwidth into multiple streams for different clients at the same time (at OFDM carrier level, similar to what LTE does).
If the Qualcomm Linux driver and firmware passed WIFI6 certification, all these features should be working "out of the box"...

Where were the certificates generated?
In my experience, MT generated certificates don't work with the Windows OVPN desktop client (maybe they do now, I haven't tested recently).

Certificates generated by MT CHR, but I won’t say exactly which version, it was a year or two ago. It was definitely version 6.

As no "OpenVPN client" or "OpenVPN server" usage is standardized for certificates, I would expect "tls-client" or "tls-server" to be required, but you have to check.
Also, some clients and servers require a minimum key length and minimum key type (RSA/EC) of the certificate to accept it.

As no "OpenVPN client" or "OpenVPN server" usage is standardized for certificates, I would expect "tls-client" or "tls-server" to be required, but you have to check.
Also, some clients and servers require a minimum key length and minimum key type (RSA/EC) of the certificate to accept it.

This key usage is set correctly and it worked on version 6.
I have
client side certificate: tls client
server side: digital signature, key encipherment, tls server

- removed individual packages, only bundle and extra packages will remain

We would appreciate further compartmentalizing of Router OS features to increase device efficiency and reduce attack surface.

Put SMB, Torrent, and other things that have no place in ISP infrastructure into another package.

Put BGP, MPLS, and other things that have no place in consumer devices into another package.

Put BGP, MPLS, and other things that have no place in consumer devices into another package.

But why this whole bundle package thing is even there to begin with, is completely unclear.

Don't mix up "extra" with "all" packages.
Like I previously said, there will be default bundle + optional extra packages, like user manager, tr069, calea, gps, lcd, ups. I think that's all.

There will be no more system package

Wait, torrent wasn't a joke?

We would appreciate further compartmentalizing of Router OS features to increase device efficiency and reduce attack surface.

Put SMB, Torrent, and other things that have no place in ISP infrastructure into another package.

Put BGP, MPLS, and other things that have no place in consumer devices into another package.

We would appreciate further compartmentalizing of Router OS features to increase device efficiency and reduce attack surface.

Put SMB, Torrent, and other things that have no place in ISP infrastructure into another package.

Put BGP, MPLS, and other things that have no place in consumer devices into another package.

From Russian MUM 2019. Currently available for downloading from http://mt.lv/v7.

another issue... that I created a workaround
ppoe client (to the ISP) connects but the route that it is adding is not working... I had to create and run the following script to add a proper route that works
/ip/route/set [find where comment="pppoe"] gateway=([:pick [/ip/address/print as-value where interface=pppoe-out1] 0]->"network")

of course I added a comment of "pppoe" to the route that I created in order to get updated with the above script

Put SMB, Torrent, and other things that have no place in ISP infrastructure into another package.

i can't stress it any further: IPv6 is a basic stuff now, it shouldn't be a separate package. it is ok if you disable IPv6 forwarding in /ipv6 settings, or we could even have a kill switch for the whole ipv6 protocol stack if one desires (banks, financial institutions and most enterprises are scared ....less), but it must be the part of the basic cocktail, and if you ask me it must be enabled by default.

BTW Wireguard works with 4.14.142

IMO unless a feature/package doesn't have a significant impact on the performance of the device just because it is installed, but has a way to deactivate it in the configuration, it is just fine. why'd anyone bother to uninstall/disable the routing package (BGP or MPLS) if BGP/LDP/MPLS is disabled on its own?

Well, it appears that MikroTik is moving from the small-ISP-backbone world to the home consumer world

It would seem natural to have protocols like BGP, OSPF and MPLS disabled by defauit on such devices, to reduce confusion for daddy who wants to make a small change to the config and should not be distraced by a menu called "Routing" which has nothing to do with what he needs but may sound familiar (it is called a Router, what does it do: Routing, probably I need to set something there).

To me, it appears that routing and mpls should be disabled by default, ipv6 enabled by default.

no luck with my hap ac2. Tried upgrading from 6.44 and using netinstall. Not a single frame is coming out of this thing on any ethernet port.
Edit: working now. Had to netinstall 6.45.5 only with system + dhcp package, than uploaded 7.0b1 npk and rebooted twice

If anyone is having issues installing the beta like I did on a hAP ac2, I had to update the firmware in System>Routerboard before the v7 beta would boot properly.

Why are people asking for ext4 on mikrotik devices when they should be asking for f2fs?

Out of interest is there an expected release date of new revisions, e.g v7.0beta2 every couple weeks? Or would we only get updates every quarter?

Thanksk

There are no set release schedules for the next beta releases. We will release beta2 once were done fixing current bugs that were found in beta1 and once we expanded the current feature set (and maybe beta on another platform, who knows!).

Thanks, I would presume the beta version of V6 would slow down now and more resources allocated to the v7 dev team. No point in flogging a dead horse essentially.

Out of interest is there an expected release date of new revisions, e.g v7.0beta2 every couple weeks? Or would we only get updates every quarter?

Thanksk

There are no set release schedules for the next beta releases. We will release beta2 once were done fixing current bugs that were found in beta1 and once we expanded the current feature set (and maybe beta on another platform, who knows!).

Even if it's not perfect, we'd love to start testing BGP/MPLS on ARM/Tilera!

Even if it's not perfect, we'd love to start testing BGP/MPLS on ARM/Tilera!

And CHR also, please!!

Any chanfs of the sfp tab on interfaces appear on x86 with this new version? Important information is not reported to sfp card users. What tasks are ready for multiprocessing today in v6? and what happened to be in v7? what is the implementation order for them?

Any chanfs of the sfp tab on interfaces appear on x86 with this new version? Important information is not reported to sfp card users. What tasks are ready for multiprocessing today in v6? and what happened to be in v7? what is the implementation order for them?

Mikrotik can definitely get the SFP information on at least Intel cards, if not all cards that take fibre modules.

Maybe once the v7 beta is out for CHR you could email support@mikrotik.com and request it.

... When you need IPv6, first enable the package, then upgrade your device to latest version...

It doesn't matter if IPv6 was/is enabled/disabled in v6, after upgrading to v7 it will be enabled, and upon executing /system reset-configuration , default IPv6 firewall rules will be added.

Changes in v7beta2

    capsman - improved compatibility between v6 and v7 versions;
    tr069-client - address support of server CA certificates;
    winbox - re-added OSPF menu;
    ppp - fixed "add-default-route" parameter for PPP interfaces;
    ppp - fixed OVPN authentication with client certificates;
    ppp - improved handling for TLS traffic;
    ipsec - enabled EAP client authentication method;
    other minor fixes;

https://mt.lv/v7

This time, we are also including the CHR images for more wide testing possibilities. Please report your findings.

looks like beta2 is out:
viewtopic.php?f=1&t=152003#p752103

This time, we are also including the CHR images for more wide testing possibilities. Please report your findings.

looks like beta2 is out:
viewtopic.php?f=1&t=152003#p752103

Code: Select all

Changes in v7beta2

    capsman - improved compatibility between v6 and v7 versions;
    tr069-client - address support of server CA certificates;
    winbox - re-added OSPF menu;
    ppp - fixed "add-default-route" parameter for PPP interfaces;
    ppp - fixed OVPN authentication with client certificates;
    ppp - improved handling for TLS traffic;
    ipsec - enabled EAP client authentication method;
    other minor fixes;

https://mt.lv/v7

This time, we are also including the CHR images for more wide testing possibilities. Please report your findings.

Updated my hap ac2, and the usb lte interface is not being detected :/
Probably going to have to downgrade.

What kind of modem do you have ?

For anyone who's able to test OpenVPN UDP support in RouterOS 7, is it possible to have the OpenVPN server listening on both UDP and TCP at the same time with a single router?

Are we going to get VTI support or at least a usable implementation of OpenVPN? I say usable because RouterOS sometimes ignores my explicit interface bindings and bring up dynamic OVPN interfaces. That would be all fine and dandy but I'm running OSPF with redundant WAN links. The horrible site to site support is the biggest shortcoming in RouterOS; you essentially cannot make dynamic routing work reliably with a non RouterOS device on the other end of the tunnel.

For anyone who's able to test OpenVPN UDP support in RouterOS 7, is it possible to have the OpenVPN server listening on both UDP and TCP at the same time with a single router?

That isn't possible with stock OpenVPN either! A major omission IMHO.

For anyone who's able to test OpenVPN UDP support in RouterOS 7, is it possible to have the OpenVPN server listening on both UDP and TCP at the same time with a single router?

That isn't possible with stock OpenVPN either! A major omission IMHO.

Yes, but with stock OpenVPN you can just run multiple copies of the daemon process simultaneously on a single server. In RouterOS, that's not an option.