v7.0beta8 [development] is released!

RouterOS RouterOS beta
1

RouterOS version 7.0beta8 has been released in public “development” channel!

What’s new in 7.0beta8 (2020-Jun-4 15:04):

*) fixed CLI dependencies for routing menu;

What’s new in 7.0beta7 (2020-Jun-3 16:31):

!) added Layer3 hardware offloading support for CRS317-1G-16S+RM more info here: https://wiki.mikrotik.com/wiki/Manual:CRS3xx_series_switches#L3_Hardware_Offloading
!) enabled BGP support with multicore peer processing (CLI only);
!) enabled RPKI support (CLI only);
!) ported features and fixes introduced in v6.47;
!) routing updates, complete status report: https://help.mikrotik.com/docs/display/ROS/v7+Routing+Protocol+Status
!) system kernel has been updated to version 5.6.3;
*) other minor fixes and improvements;

All released RouterOS v7 changelogs are available here:
https://mikrotik.com/download/changelogs/development-release-tree

How to report RouterOS v7 bugs:
http://forum.mikrotik.com/t/how-to-report-issues-in-v7-beta/133088/1

2

I expected CAKE or fq-codel queue type since this new kernel already includes it.

Edit: Wireguard is also supported in kernel 5.6.x

3

Please keep this topic related to the problems found in this RouterOS release. This topic is not made for feature requests. For that please create a new topic or contact support@mikrotik.com.

4

I just wanted to say thank you very much for all your hard work.

5

I am simply impressed that you can side stream in improvements from 6.47 into v7.0.

6

DoH is no longer working in 7.0 beta 7, it worked in 6.47
Screenshot_20200604-061002_MikroTik.jpg

7

DoH works fine for me.

Just added

https://1.1.1.1/dns-query

Did not select “Verify DoH Certificate” since this is just a test.

8

The verify certicate option used to work in 6.47, I have the root certicate imported into the router

9

Does it work without certificates? Just to test the DoH to see what is wrong?

10

Seems that the router is unable to resolve the DoH hostname. Post your DNS configuration and make sure you have at least one dynamic or static DNS server configured.

11

I disabled the verify certificate option for testing but it still has resolving errors

/ip dns
set allow-remote-requests=yes servers=1.1.1.1 use-doh-server=\
    https://cloudflare-dns.com/dns-query

EDIT: I resetted the router and the problem with DoH persists, maybe this build requires a netinstall?
Device is hAP AC2

12

What’s new in 7.0beta8 (2020-Jun-4 15:04):

*) fixed CLI dependencies for routing menu;

Unfortunately, v7.0beta7 release did not have all the necessary routing changes for public release, here is a hotfix version of v7.0beta8.

13

DoH is still not working for me in beta8
Captura.PNG

14

Test this instead:

/ip dns
set allow-remote-requests=yes use-doh-server=https://1.1.1.1/dns-query

Looks like your router does not resolve the name for cloudflare-dns.com

15

/export includes this line:
#error exporting /routing/policy/selection

/routing/policy/selection/print shows:
error - contact MikroTik support and send a supout file (3)

Is this already known?

In Winbox, there is no icon for “Routing” (this was true in previous versions as well)
Is there a manual for /routing/bgp ? It appears to be completely different from v6 so I need some directions to be able to test it.

16

It did in 6.47, I can even ping cloudflare-dns.com from the CLI but it’s not working in DoH

Anotación 2020-06-04 082617.png
Anotación 2020-06-04 082617.png755×305 5.15 KB

You updated directly from 6.47 or used Netinstall?

EDIT: Also tried Adguard and Quad9 without luck
EDIT 2: tried https://1.1.1.1/dns-query and it works, but if I want to use another server I can’t do that, because they don’t have a SSL certificate embedded into their IP address like Cloudflare has

17

A basic ibgp configuration :

/routing bgp template
add as=65534 name=lab
/routing bgp connection
add local.role=ibgp remote.address=10.X.X.X template=lab

18

router was rebooted without proper shutdown on RouterOS v7.0 beta 7

When it on RouterOS Beta 5, it’s work well.

I have config some EoIP Tunnels and some IP Tunnels and Bonding Tunnels with EoIP Tunnels.
RouterOS v7 Beta 7.png

19

IPsec Policies say no phase2 on PH2 no phase2

When Upgrade from RouterOS v7.0beta3 and v7.0beta5 to RouterOS v7.0beta7 or v7.0beta8

IPsec Policies say no phase2 on PH2 State
You need goto Identities and remove all and add the Identities for peers again
That’s will make IPsec works again.

When Downgradepgrade from RouterOS v7.0beta7 or v7.0beta8 to RouterOS v7.0beta3 and v7.0beta5

IPsec Policies say no phase2 on PH2 State, too.
You need goto Identities and remove all and add the Identities for peers again
That’s will make IPsec works again.

20

Good work, I just hope that you will do the same effort you’re doing for IPv4 for IPv6 too.