Community discussions

MikroTik App
 
User avatar
emils
Forum Veteran
Forum Veteran
Topic Author
Posts: 906
Joined: Thu Dec 11, 2014 8:53 am

v7.1beta3 [development] is released!

Thu Dec 03, 2020 11:59 am

RouterOS version 7.1beta3 has been released in public "development" channel!

What's new in 7.1beta3 (2020-Dec-02 15:59):

!) added support for "Cake" and "FQ_Codel" type queues;
!) added new experimental wireless package "wifiwave2" for ARM devices with more than 256 MB of RAM (CLI only);
*) bgp - template parameters are now exposed in connection;
*) chr - added support for SR-IOV
*) routing - added "route", "routing table", "route rules" and BGP configuration migration from RouterOS v6 after upgrade;
*) routing - renamed "instance" menu to "id";
*) other fixes and improvements;

Information about "wifiwave2" package: https://help.mikrotik.com/docs/display/ROS/WifiWave2

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

How to report RouterOS v7 bugs:
viewtopic.php?f=1&t=152006
 
blingblouw
Member
Member
Posts: 345
Joined: Wed Aug 25, 2010 9:43 am

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 12:08 pm

Wow!!
 
User avatar
Larsa
Forum Guru
Forum Guru
Posts: 1025
Joined: Sat Aug 29, 2015 7:40 pm
Location: The North Pole, Santa's Workshop

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 12:09 pm

Thanks, will try it immediately on our sandboxes! Is WireGuard part of other fixes and improvements?
 
Railander
Frequent Visitor
Frequent Visitor
Posts: 85
Joined: Thu Jun 16, 2016 11:30 pm

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 12:17 pm

!) added support for "Cake" and "FQ_Codel" type queues;
very nice!
 
msatter
Forum Guru
Forum Guru
Posts: 2897
Joined: Tue Feb 18, 2014 12:56 am
Location: Netherlands / Nīderlande

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 12:22 pm

Hope this will also stop the router crashing when you change the MTU of an interface.

Update: I could change de MTU but sadly not the one I wanted to. The PPPoE dropped back to 1480 and manually I could set it to 1492 to a bit be closer to the 1500 that I can use in 6.48.

Routing was changed (expected), routing labels where set main and when I wanted to traceroute there where two routing tables main in the list. Both worked but it is confusing this way. After I corrected all the changed routing marks it still not work and I could only ping/traceroute directly from the router to 8.8.8.8.

My external IP I could not set as preferred source on my PPPoE connection or I had to make my own static routing entry. All my internal routing was also dead so no in fun testing this way.

Looking forward to try 7.1Beta4 somewhere in 2021. For now I am back to 6.48.

Update 2: hanging in there like a pit-bull I tried again. The nexthop in routing displays all unreachable, manually removed the double main next to default dynamic main and the blank one. Exporting to a RSC file does not complete and the last complete section is: /ip service and the next service /system time is not present in the file and also the rest of the export.

I could partly activate the internal routing by setting rules but it still worked only partly.
Last edited by msatter on Thu Dec 03, 2020 5:01 pm, edited 3 times in total.
 
User avatar
SiB
Forum Guru
Forum Guru
Posts: 1888
Joined: Sun Jan 06, 2013 11:19 pm
Location: Poland

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 12:28 pm

LHGR & SXTR works

RouterOS 7 STATUS of ROUTING https://help.mikrotik.com/docs/display/ ... col+Status
Last edited by SiB on Thu Dec 03, 2020 12:41 pm, edited 1 time in total.
 
kalamaja
Member Candidate
Member Candidate
Posts: 112
Joined: Wed May 23, 2018 3:13 pm

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 12:38 pm

NAT64 and/or DNS64 for the beta4, please, and you would be the best router software in the world! :) That would give a huge boost to IPv6-only internal networks and prevent double work for dual-stack management.
 
FezzFest
Frequent Visitor
Frequent Visitor
Posts: 86
Joined: Wed Jun 03, 2015 12:03 am

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 12:41 pm

Lost lte1 interface after upgrade from v7.1beta2 to v7.1beta3. Sierra Wireless MC7430 in wAP R. Log file reports 'reply timeout for: AT E0 V1' (see screenshot).
fq_codel, SR-IOV and 802.11ac Wave2 support are some interesting additions though!
You do not have the required permissions to view the files attached to this post.
 
User avatar
eworm
Forum Guru
Forum Guru
Posts: 1070
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 12:42 pm

Looks like my wireguard tunnel is down after update... Did not check the details, will have to investigate later.
 
madejson
just joined
Posts: 13
Joined: Mon Sep 07, 2020 9:06 pm

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 12:53 pm

Looks like my wireguard tunnel is down after update... Did not check the details, will have to investigate later.
Mine works ok, 2x hap ac2 and 962UiGS-5HacT2HnT looks like work properly.
 
templeos
just joined
Posts: 19
Joined: Mon Aug 26, 2019 3:58 pm

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 1:04 pm

!) added new experimental wireless package "wifiwave2" for ARM devices with more than 256 MB of RAM (CLI only);
What about devices with 16MB storage and 128MB of RAM? This new driver is way too big. 10MB. Does this mean that IPQ4018 devices are left behind?
 
User avatar
FToms
MikroTik Support
MikroTik Support
Posts: 87
Joined: Fri Jul 24, 2020 3:28 pm

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 1:14 pm

What about devices with 16MB storage and 128MB of RAM? This new driver is way too big. 10MB. Does this mean that IPQ4018 devices are left behind?
Unfortunately, reducing the size of the driver and its memory usage further was not found to be feasible at this point. Perhaps when RouterOS 7 and the wifiwave2 package come out of beta, further optimizations can be made.
 
LSan83
Frequent Visitor
Frequent Visitor
Posts: 66
Joined: Fri Aug 10, 2018 11:35 am
Location: Italy

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 1:20 pm

!) added new experimental wireless package "wifiwave2" for ARM devices with more than 256 MB of RAM (CLI only);
What about devices with 16MB storage and 128MB of RAM? This new driver is way too big. 10MB. Does this mean that IPQ4018 devices are left behind?
And the IPQ4019 devices with 16MB storage like HAP AC2 e CHATEAU LTE12??? It's possible to use external memory on usb2 port for the driver?
 
templeos
just joined
Posts: 19
Joined: Mon Aug 26, 2019 3:58 pm

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 1:31 pm

And the IPQ4019 devices with 16MB storage like HAP AC2 e CHATEAU LTE12???
No way this driver would fit without replacing the old driver with the new one. There's barely any space left on hAP ac2. And if by replacing there's still not enough space left then that means there's no point to buy any of the 16MB devices because none of them would get this new driver. Especially if it stays like this and it will be a separate package. Maybe there's debug symbols still left in. After all this is still an experimental driver. People has been asking for a Wave2 driver for ages and in the end they wouldn't be able to get it. If I am wrong please correct me.
 
xrayd78
just joined
Posts: 7
Joined: Sat Apr 30, 2016 12:31 pm

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 1:36 pm

+1!
 
User avatar
Znevna
Forum Guru
Forum Guru
Posts: 1347
Joined: Mon Sep 23, 2019 1:04 pm

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 1:46 pm

Almost every device out there based on ipq4018/4019 has atleast 256MB of RAM.
With a few exceptions, like RT-AC58U which struggles to not throw errors because of the very limited memory available out of the 128MB total.
So I wouldn't keep my hopes up to see it running in the future on lower requirements than the ones posted here today.
This was expected.
 
User avatar
memelchenkov
Member Candidate
Member Candidate
Posts: 202
Joined: Sun Oct 11, 2020 12:00 pm
Contact:

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 2:11 pm

After upgrade Chateau to 7.1b3, right after reboot, I noticed in logs:

lte1 mbim: error: function error: not opened

next lines are:
lte1: IPV4: x.x.x.x, DNS: 2
lte1 link up
 
Florian
Member Candidate
Member Candidate
Posts: 117
Joined: Sun Mar 13, 2016 9:45 am
Location: France

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 2:14 pm

Almost every device out there based on ipq4018/4019 has atleast 256MB of RAM.
With a few exceptions, like RT-AC58U which struggles to not throw errors because of the very limited memory available out of the 128MB total.
So I wouldn't keep my hopes up to see it running in the future on lower requirements than the ones posted here today.
This was expected.
A lot of Hap AC2 have only 128mb of ram (yeah, well done mikrotik by releasing 128 and 256 mb versions "randomly").
 
User avatar
eworm
Forum Guru
Forum Guru
Posts: 1070
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 2:33 pm

Looks like my wireguard tunnel is down after update... Did not check the details, will have to investigate later.
The peer's endpoint-port was set to 0. After setting the correct port everything is back up now.
 
Kindis
Member
Member
Posts: 434
Joined: Tue Nov 01, 2011 6:54 pm
Location: Sweden

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 2:43 pm

Almost every device out there based on ipq4018/4019 has atleast 256MB of RAM.
With a few exceptions, like RT-AC58U which struggles to not throw errors because of the very limited memory available out of the 128MB total.
So I wouldn't keep my hopes up to see it running in the future on lower requirements than the ones posted here today.
This was expected.
True but cAP AC that has 4018 only has 128 MB which sucks at this point as I would argue they where made to be a AP and now they cannot go to Wave 2.
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 2:44 pm

After upgrade, all my OSPF settings disappeared (except of Instance)

And I cannot change it or create a new instance via WinBox setting "version": it saus, incorrect version. If I add a new instance via Terminal, WinBox shows "unknown" under Version
 
User avatar
FToms
MikroTik Support
MikroTik Support
Posts: 87
Joined: Fri Jul 24, 2020 3:28 pm

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 2:49 pm

And the IPQ4019 devices with 16MB storage like HAP AC2 e CHATEAU LTE12??? It's possible to use external memory on usb2 port for the driver?
Unfortunately, it's not. The wifiwave2 package is a preview of the wireless driver and configuration interface being built for future products and an opportunity to provide feedback on it.
Existing products will continue to receive updates for the bundled wireless package.
 
templeos
just joined
Posts: 19
Joined: Mon Aug 26, 2019 3:58 pm

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 2:55 pm

True but cAP AC that has 4018 only has 128 MB which sucks at this point as I would argue they where made to be a AP and now they cannot go to Wave 2.
Not only cAP ac, the new wAP ac (RBwAPG-5HacD2HnD) too with IPQ4018 which was released recently. That's a new product and same 16MB storage and 128MB RAM. We need some clarifications here if Wave2 driver is actually planned for these or we should wait for new products that can benefit from having Wave2 features.
 
huntermic
Member Candidate
Member Candidate
Posts: 111
Joined: Wed Oct 26, 2016 3:42 pm

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 2:56 pm

And the IPQ4019 devices with 16MB storage like HAP AC2 e CHATEAU LTE12??? It's possible to use external memory on usb2 port for the driver?
Unfortunately, it's not. The wifiwave2 package is a preview of the wireless driver and configuration interface being built for future products and an opportunity to provide feedback on it.
Existing products will continue to receive updates for the bundled wireless package.
So can you guys at mikrotik finally agree with all the users here that the choice for 16MB Flash ( and 128MB RAM ) in recent models has been a big mistake?
 
arm920t
Frequent Visitor
Frequent Visitor
Posts: 61
Joined: Sat Aug 03, 2019 8:02 am

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 3:06 pm

X86 not work.Attemped to reinstall by the iso image.System boot up and hunged with " file system corruption".Reinstall with Beta2 works well,but when upgrade to beta3 with npk file.System hung up again
 
onnoossendrijver
Member
Member
Posts: 486
Joined: Mon Jul 14, 2008 11:10 am
Location: The Netherlands

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 3:14 pm

Of course I would really like to have these features..
But come on guys... I believe Mikrotik never promised wave2/mimo support on these devices. Also, never buy hardware for a feature that may or may not be available later.
 
User avatar
osc86
Member Candidate
Member Candidate
Posts: 197
Joined: Wed Aug 09, 2017 1:15 pm

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 3:17 pm

Updated my HAP AC2 from beta2 to beta3 and the device is constantly rebooting at about 1 minute of uptime.
There was only one critical log entry, the device restarted because of a kernel failure. Downgraded back to beta2.
 
templeos
just joined
Posts: 19
Joined: Mon Aug 26, 2019 3:58 pm

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 3:18 pm

Of course I would really like to have these features..
But come on guys... I believe Mikrotik never promised wave2/mimo support on these devices. Also, never buy hardware for a feature that may or may not be available later.
viewtopic.php?t=145047#p713800
 
infabo
Long time Member
Long time Member
Posts: 586
Joined: Thu Nov 12, 2020 12:07 pm

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 3:21 pm

And the IPQ4019 devices with 16MB storage like HAP AC2 e CHATEAU LTE12??? It's possible to use external memory on usb2 port for the driver?
Unfortunately, it's not. The wifiwave2 package is a preview of the wireless driver and configuration interface being built for future products and an opportunity to provide feedback on it.
Existing products will continue to receive updates for the bundled wireless package.
So can you guys at mikrotik finally agree with all the users here that the choice for 16MB Flash ( and 128MB RAM ) in recent models has been a big mistake?
wait a second - gotta grab some popcorn ;)
 
User avatar
FToms
MikroTik Support
MikroTik Support
Posts: 87
Joined: Fri Jul 24, 2020 3:28 pm

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 3:31 pm

Updated my HAP AC2 from beta2 to beta3 and the device is constantly rebooting at about 1 minute of uptime.
There was only one critical log entry, the device restarted because of a kernel failure. Downgraded back to beta2.
Please report this to support@mikrotik.com and attach either a supout file from your device or just a configuration export.
 
blingblouw
Member
Member
Posts: 345
Joined: Wed Aug 25, 2010 9:43 am

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 3:41 pm

Added a simple queue using cake. boot loop RB951
 
R1CH
Forum Guru
Forum Guru
Posts: 1098
Joined: Sun Oct 01, 2006 11:44 pm

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 3:45 pm

Great to finally see some movement on newer wireless drivers, but also disappointing to see that no currently released AP hardware can use them (especially the just-released wAP AC revision). Wave2 has been around for over four years at this point! There should have been plenty of time to evaluate the requirements and not continue releasing hardware with the lowest amounts of flash / RAM possible. I'm worried that by the time we see usable Wave2 hardware the rest of the world will have moved on to 802.11ax.
 
User avatar
mkx
Forum Guru
Forum Guru
Posts: 11381
Joined: Thu Mar 03, 2016 10:23 pm

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 4:15 pm

Of course I would really like to have these features..
But come on guys... I believe Mikrotik never promised wave2/mimo support on these devices. Also, never buy hardware for a feature that may or may not be available later.
viewtopic.php?t=145047#p713800
Where exactly did they promise wawe2 support on existing devices? They mentioned that driver is WIP ... didn't mention which devices they're targeting.
 
guipoletto
Member Candidate
Member Candidate
Posts: 195
Joined: Mon Sep 19, 2011 5:31 am

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 4:27 pm

what about RBcAPGi-5acD2nD (Cap-AC?)

i could live with "on the fly" loading of a driver stored in the CAPsMAN controller.

Not Ideal, but certainly better than nothing.
 
LSan83
Frequent Visitor
Frequent Visitor
Posts: 66
Joined: Fri Aug 10, 2018 11:35 am
Location: Italy

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 5:00 pm

Almost every device out there based on ipq4018/4019 has atleast 256MB of RAM.
With a few exceptions, like RT-AC58U which struggles to not throw errors because of the very limited memory available out of the 128MB total.
So I wouldn't keep my hopes up to see it running in the future on lower requirements than the ones posted here today.
This was expected.
A lot of Hap AC2 have only 128mb of ram (yeah, well done mikrotik by releasing 128 and 256 mb versions "randomly").
The two version have different chipset....
HAP AC2 with 128 MB --> IPQ4018 (like CAP AC, WAP AC v2, WAP AC R)
HAP AC2 with 256 MB --> IPQ4019 (like Chateau LTE12, Hap AC3 LTE, Hap AC3, Audience, Audience LTE)
Only the two Audiences and Hap AC3 have both IPQ4019 and more than 16MB flash.
 
msatter
Forum Guru
Forum Guru
Posts: 2897
Joined: Tue Feb 18, 2014 12:56 am
Location: Netherlands / Nīderlande

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 5:07 pm

 
txpower501
just joined
Posts: 10
Joined: Wed Jan 09, 2013 5:44 pm

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 5:29 pm

Completely borked my CHR 'tik. Can no longer Winbox in, no reply from router. Wiregard tunnel down. DNS not working. Doing config diff now to see whats changing.

EDIT: I'm not able to telnet, ssh, winbox, or ssl to it, Tik isn't sending tcp-reset, just not responding. I can http to it or console via ESX. If I do an export from terminal, it hangs right at DNS config and I have to Control+C it. Downgrading from 7.1beta2 didn't fix. I had to revert config from prior to upgrading to 7.1beta3 and its fixed. Not able to generate a support file, it just hangs. Not sure what info I can provide for devs...
Last edited by txpower501 on Thu Dec 03, 2020 6:22 pm, edited 1 time in total.
 
rpingar
Long time Member
Long time Member
Posts: 592
Joined: Fri May 28, 2004 2:46 pm
Location: Italy

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 5:47 pm

x86 not working either for me:
"ERROR: Your disk file system is corrupted!"

netinstall crashes on passing ip
 
User avatar
herger
newbie
Posts: 49
Joined: Tue Aug 18, 2020 2:48 pm

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 5:49 pm

I'm testing beta3 on my CRS309-1G-8S+, the update went smooth. One thing i instantly noticed is that /export never terminates. Tried to reset to an empty configuration, same thing. When i run /export verbose the last thing that gets displayed is /radius incoming set accept=no port=3799 and then it hangs forever. Anyone else having this behavior?
 
tpedko
just joined
Posts: 23
Joined: Wed May 22, 2019 9:58 am

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 5:49 pm

simple queues still don't work. the router goes into an endless reboot.
router RB4011iGS+5HacQ2HnD-IN
 
chubbs596
Frequent Visitor
Frequent Visitor
Posts: 90
Joined: Fri Dec 06, 2013 6:07 pm

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 6:22 pm

*) routing - added "route", "routing table", "route rules" and BGP configuration migration from RouterOS v6 after upgrade;

How does the BGP related config migration work? Is this done automatically as part of the upgrade process?
 
whatever
Member
Member
Posts: 348
Joined: Thu Jun 21, 2018 9:29 pm

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 6:23 pm

a preview of the wireless driver and configuration interface being built for future products
So the hap ac² will never receive full wave2 support, not even the models with 256 MB RAM?
 
templeos
just joined
Posts: 19
Joined: Mon Aug 26, 2019 3:58 pm

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 6:41 pm

Where exactly did they promise wawe2 support on existing devices? They mentioned that driver is WIP ... didn't mention which devices they're targeting.
That's the point. They choose the words carefully so that you have to ask for more questions and with each reply you start to realize what is going on. At this point we are 100% right about not getting Wave2 support for 16MB with 128MB devices until proven otherwise.
 
guipoletto
Member Candidate
Member Candidate
Posts: 195
Joined: Mon Sep 19, 2011 5:31 am

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 6:47 pm

id they promise wawe2 support on existing devices? They mentioned that driver is WIP ... didn't mention which devices they're targeting.
That's the point. They choose the words carefully so that you have to ask for more questions and with each reply you start to realize what is going on. At this point we are 100% right about not getting Wave2 support for 16MB with 128MB devices until proven otherwise.
Imagine how many cents were saved with all those 16mb devices
 
Sob
Forum Guru
Forum Guru
Posts: 9119
Joined: Mon Apr 20, 2009 9:11 pm

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 6:53 pm

When i run /export verbose the last thing that gets displayed is /radius incoming set accept=no port=3799 and then it hangs forever. Anyone else having this behavior?
I have same behaviour on CHR.

Also all free disk space is gone. Right after update it showed 8kB free, then I deleted two autosupouts to get at least something, but instead ended with nothing:
 free-hdd-space: 0
total-hdd-space: 59.5MiB
 
r00t
Long time Member
Long time Member
Posts: 672
Joined: Tue Nov 28, 2017 2:14 am

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 6:54 pm

Looks like most 802.11ac products will never be able to run this new wireless package. Sad.

I think it might be possible to port it to different architecture than ARM, but memory and especially flash requirements are most limiting.
Getting it to work with 128MB RAM might be doable after some optimization, but it will never fit into 16MB of flash... that's just impossible.
16MBs of flash should have been phased out years ago...

What about using USB for loading these extra modules? I don't care if you encrypt them, digitally sign them or whatever you have to do.
Or what about remote server (TFTP, NFS, some custom protocol...)?

Say you have installation of cAP ACs, it would be perfectly fine if new wifi package was loaded every time on boot from central server/router.
You really made things hard by insisting on "16MB is enough for everybody" for way too long, but at least look into some clever workarounds now...
 
User avatar
herger
newbie
Posts: 49
Joined: Tue Aug 18, 2020 2:48 pm

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 7:09 pm

Also all free disk space is gone. Right after update it showed 8kB free, then I deleted two autosupouts to get at least something, but instead ended with nothing:
Thats actually fine on my side:
 free-hdd-space: 2732.0KiB
total-hdd-space: 15.9MiB
but i did not do any file based operations so far. will keep an eye on it.
 
User avatar
eworm
Forum Guru
Forum Guru
Posts: 1070
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 7:16 pm

Also all free disk space is gone. Right after update it showed 8kB free, then I deleted two autosupouts to get at least something, but instead ended with nothing:
 free-hdd-space: 0
total-hdd-space: 59.5MiB
The CHR images have been 128MB in size for a really long time now. Possibly this is a very old installation?
You should start over with a fresh images, I guess the issue is solved there.
 
andriys
Forum Guru
Forum Guru
Posts: 1526
Joined: Thu Nov 24, 2011 1:59 pm
Location: Kharkiv, Ukraine

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 7:26 pm

I am sure that 16MB flash nonsense is not so much about money as it is about technology. I've recently posted my thoughts about it here. Now I just wanted to add that the reason all Mikrotik devices with SPI flash chips are limited to 16MB might be the relatively old kernel in v6. Though should it be true, it does not explain why Chateau has 16MB of flash while being a v7 only device...

Talking about workarounds, I would not hold my breath too much. All the workarounds proposed have a significant development effort associated with them, while the chances to return the investments are pretty unclear.
 
msatter
Forum Guru
Forum Guru
Posts: 2897
Joined: Tue Feb 18, 2014 12:56 am
Location: Netherlands / Nīderlande

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 7:36 pm

Updated my HAP AC2 from beta2 to beta3 and the device is constantly rebooting at about 1 minute of uptime.
There was only one critical log entry, the device restarted because of a kernel failure. Downgraded back to beta2.
Please report this to support@mikrotik.com and attach either a supout file from your device or just a configuration export.
The export never completes and the last complete section is: /ip service
 
Sob
Forum Guru
Forum Guru
Posts: 9119
Joined: Mon Apr 20, 2009 9:11 pm

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 7:38 pm

Missing CHR disk space was false alarm, the magic "turn it off and on again" fixed it. Now there's 34.6MB free.
 
ib254254
just joined
Posts: 23
Joined: Sat Nov 21, 2020 10:15 pm

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 7:46 pm

It looks good as the new features become.

the band that caught my attention is 802.11-ax

Could you please give us some information about this issue?

here wave2 is not 802.11ac wave2
I guess MikroTik means wireless wireless wave2.

Please give some information about ax.

Is this just a visual without a forward-looking infrastructure?

Or is there a roadmap for ax this year or anytime?

give us information.
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7038
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 8:01 pm

How does the BGP related config migration work? Is this done automatically as part of the upgrade process?
Yes it is part of the upgrade process, but keep in mind that routing filters are not converted yet and some of the config might still be missing. So it is recommended to make a backup of ROSv6 config before upgrading.
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7038
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 8:04 pm

One thing i instantly noticed is that /export never terminates. Tried to reset to an empty configuration, same thing. When i run /export verbose the last thing that gets displayed is /radius incoming set accept=no port=3799 and then it hangs forever.
Export problem is known, /routing menu export is the one that fails.
 
ib254254
just joined
Posts: 23
Joined: Sat Nov 21, 2020 10:15 pm

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 8:50 pm

"band ( 2ghz-g | 2ghz-n | 2ghz-ax | 5ghz-a | 5ghz-ac | 5ghz-an | 5ghz-ax )"

Please give a brief explanation about ax.



dikkatimi çeken grup 802.11-ax.

Bu konuda bize biraz bilgi verebilir misiniz?

Burada wave2 802.11ac wave2 değil
sanırım MikroTik kablosuz wireless wave2 anlamına geliyor.

Lütfen balta hakkında biraz bilgi veriniz.

Bu, ileriye dönük bir altyapısı olmayan bir görsel mi?

Yoksa bu yıl veya herhangi bir zamanda balta için bir yol haritası var mı?

bize bilgi verin.
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 8:58 pm

Apparent OSPFv3 bug in v7.1beta3 - PTP network type is giving "wrong checksum" when trying to establish neighbor with ROS v6 device. OSPFv2 seems to work OK.
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 9:22 pm

After upgrade, all my OSPF settings disappeared (except of Instance)
Yes, this happened to me as well. The issue is the required and optional fields have changed, so the old config tries to apply but fields do not exist anymore or have now been named differently.
 
ib254254
just joined
Posts: 23
Joined: Sat Nov 21, 2020 10:15 pm

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 9:30 pm

For the most important point for wisp why MikroTik is not responding.

Thousands of people read this place.

Is 802.11ax included in wave2 drivers?

Or is it just an image?

why don't you answer Is this a secret?
 
pe1chl
Forum Guru
Forum Guru
Posts: 10183
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 9:38 pm

I upgraded a CHR that I use for some testing from v7.1beta2 to v7.1beta3.
After upgrade, the BGP link that was configured does not come up.
No log messages in either this router or the one it connects to (other than the close of the previous connection at reboot).
The config was very simple:
/routing bgp template
add name=test
/routing bgp connection
add local.role=ibgp remote.address=172.22.16.254 template=test
When I type /export in the updated router's command window it hangs just before the /routing bgp connection line.
I restored the saved disk image with beta2 for now. After boot the BGP comes up as before.
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 9:46 pm

I upgraded a CHR that I use for some testing from v7.1beta2 to v7.1beta3.
After upgrade, the BGP link that was configured does not come up.
Yes, the required BGP fields have changed. If you created BGP config in 7.1beta2, you have to delete it, upgrade to 7.1 beta 3, make sure all BGP config is gone, and re-enter it. If I recall correctly, the new required field was a name field under the connection.

The same thing happened to me, but I can confirm that after upgrading and reconfiguring BGP it works again. Same thing with OSPF.

It seems like MikroTik didn't bother to create conversion code to convert beta2 config style to beta3 so any lines that now have wrong field names or missing required fields are lost completely.
 
thadrumr
newbie
Posts: 32
Joined: Sat Dec 23, 2017 2:02 am

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 10:02 pm

I can confirm on my CHR Hyper-V system that Cake works on my Download simple Queue and on myUpload Queue tree. After the install on my 128MB systems I am using 17.8 MB of 91.2MB.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10183
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 10:06 pm

Talking about workarounds, I would not hold my breath too much. All the workarounds proposed have a significant development effort associated with them, while the chances to return the investments are pretty unclear.
I have been using wave2 AP's from the competitor for quite some time.
Currently it looks like they use about 40MB of the 256MB of flash, and 135MB of the 512MB of available RAM (plus 40MB for buffers).
It looks like with the traditional 128MB of flash, and at least 256MB of RAM (the notes say "more than" but it looks like they mean "at least") it would have worked just fine.
But indeed, there appear to be some technical reasons to limit to 16MB of flash.

As a workaround, I think the suggestion to load software from another device, like the CAPsMAN or some other MikroTik router in the network, would be a nice one.
(just to load the 10MB that the driver apparently takes from that external device into RAM during boot)
It could even be considered to load it from an internet server (at MikroTik or elsewhere). Of course in that case there should be some fallback when it is not available.
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 10:06 pm

RB4011 wifi model - upgraded fine, works
hAP ac (running as cap) - upgraded fine, works
Mikrotik Audience (running as cap) - management hangs about every half hour to hour, going into mac winbox connects but interfaces/wireless menu is empty. Reboot fixes it for another half hour to an hour. Tried resetting the config on it in case it was a config problem brought forward from 7.1beta2 but that did not help. I am probably going to have to downgrade it to 7.1beta2.
 
felixka
Frequent Visitor
Frequent Visitor
Posts: 58
Joined: Mon Oct 19, 2020 4:12 am
Location: Canada

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 10:13 pm

Hope this will also stop the router crashing when you change the MTU of an interface.
I appreciate your test reports as we seem to be having the same issues. I'm with Bell in Canada and they also use baby jumbo frames on a SFP ONT with PPPoE. So I see the same crashing and MTU issues you are seeing.
 
mistry7
Forum Guru
Forum Guru
Posts: 1480
Joined: Tue Oct 13, 2009 11:57 am
Location: Germany

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 10:22 pm

That's the point. They choose the words carefully so that you have to ask for more questions and with each reply you start to realize what is going on. At this point we are 100% right about not getting Wave2 support for 16MB with 128MB devices until proven otherwise.
One reason more not to buy any WiFi device from Mikrotik, until this is clear
 
msatter
Forum Guru
Forum Guru
Posts: 2897
Joined: Tue Feb 18, 2014 12:56 am
Location: Netherlands / Nīderlande

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 10:42 pm

Hope this will also stop the router crashing when you change the MTU of an interface.
I appreciate your test reports as we seem to be having the same issues. I'm with Bell in Canada and they also use baby jumbo frames on a SFP ONT with PPPoE. So I see the same crashing and MTU issues you are seeing.
You missed my update in that same posting. I don't expience the crashing anymore but a MTU of 1500 or even 1508 (rfc4638) is not working. Because 7.1betaX is not working at all with me I don't see the effort of rewiring my fiber to a NTU and connect it to a ether port to see it probally still not working.

The SFP is fine and it has a MTU of 1592.

My previous attempt was worse and now it works much better: viewtopic.php?f=1&t=165248#p812265
 
mada3k
Long time Member
Long time Member
Posts: 682
Joined: Mon Jul 13, 2015 10:53 am
Location: Sweden

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 10:53 pm

Every new 7-beta release brings amazing features. Lets just hope that they eventually become stable as well :)
 
User avatar
SiB
Forum Guru
Forum Guru
Posts: 1888
Joined: Sun Jan 06, 2013 11:19 pm
Location: Poland

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 11:20 pm

Every new 7-beta release brings amazing features. Lets just hope that they eventually become stable as well :)
ROS v6 was stable at my customers at v6.3, v6.4, v6.19 and newer. If I again must wait for ros v7.20 then this will be not good for my business.

That's why, now I test ros7 too as testing rabbit, and try detect bugs and report all problems what I found.
This is only way to start with v7, report all bug and be a tester itself.
 
msatter
Forum Guru
Forum Guru
Posts: 2897
Joined: Tue Feb 18, 2014 12:56 am
Location: Netherlands / Nīderlande

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 11:26 pm

This is still present and had this when enabling/disabling logging in RAW rules.

viewtopic.php?f=1&t=165248#p813064

The first rules counter had a life of their own.
 
shavenne
just joined
Posts: 16
Joined: Wed Dec 11, 2019 4:27 pm

Re: v7.1beta3 [development] is released!

Thu Dec 03, 2020 11:28 pm

Beta 3 on my RB4011iGS+ crashes immediately after boot unfortunately. It runs just for 10-20 seconds and crashes then.
Any spontaneously idea?

I'll post an export when I have more time. Even with hide-sensitive there are way too many ip addresses shown that I don't want to post.
But I actually don't have any special things going on on that router. Just simple things .. some firewall rules, nat, but no queues, no vpn, nothing.

/edit: Ok, had time ;)
/interface bridge
add igmp-snooping=yes name=main_bridge
/interface ethernet
set [ find default-name=ether1 ] advertise=10M-half,10M-full auto-negotiation=no comment="Zum SW_KellerMini"
set [ find default-name=ether2 ] advertise=10M-half,10M-full auto-negotiation=no comment="WAN FTTH"
set [ find default-name=ether9 ] advertise=10M-half,10M-full auto-negotiation=no comment="Server IPMI"
set [ find default-name=ether10 ] advertise=10M-half,10M-full auto-negotiation=no comment="Unifi AP"
set [ find default-name=sfp-sfpplus1 ] advertise=10M-half comment="Zum SW_Keller"
/interface vlan
add arp=local-proxy-arp interface=main_bridge name=DMZ vlan-id=4050
add interface=main_bridge name=FREIFUNK vlan-id=31
add interface=main_bridge name=FREIFUNK_GW vlan-id=30
add interface=main_bridge name=INET_FTTH vlan-id=4001
add interface=main_bridge name=IPV6_ONLY vlan-id=66
add interface=sfp-sfpplus1 name=VOIP vlan-id=21
add interface=main_bridge name=WAN_LTE vlan-id=4010
add interface=ether1 name=WAN_VDSL vlan-id=4005
/interface ethernet switch port
set 0 default-vlan-id=0
set 1 default-vlan-id=0
set 2 default-vlan-id=0
set 3 default-vlan-id=0
set 4 default-vlan-id=0
set 5 default-vlan-id=0
set 6 default-vlan-id=0
set 7 default-vlan-id=0
set 8 default-vlan-id=0
set 9 default-vlan-id=0
set 10 default-vlan-id=0
set 11 default-vlan-id=0
/interface list
add name=LAN
add name=WAN
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/ip vrf
add list=all name=main
/user group
add name=prometheus policy="read,winbox,api,!local,!telnet,!ssh,!ftp,!reboot,!write,!policy,!test,!password,!web,!sniff,!\
    sensitive,!romon,!dude,!tikapp"
/interface bridge port
add bridge=main_bridge interface=ether10
add bridge=main_bridge interface=ether9
add bridge=main_bridge interface=sfp-sfpplus1 internal-path-cost=0 path-cost=5
add bridge=main_bridge interface=ether1 path-cost=15
/interface bridge vlan
add bridge=main_bridge comment=INET_FTTH tagged=sfp-sfpplus1,ether1 vlan-ids=4001
add bridge=main_bridge comment=WAN_VDSL tagged=sfp-sfpplus1,ether1 vlan-ids=4005
add bridge=main_bridge comment=WAN_LTE tagged=sfp-sfpplus1,ether1 vlan-ids=4010
add bridge=main_bridge comment=IPV6_ONLY tagged=sfp-sfpplus1 vlan-ids=66
add bridge=main_bridge comment=FREIFUNK tagged=sfp-sfpplus1,ether1 vlan-ids=30
add bridge=main_bridge comment=FREIFUNK_GW tagged=sfp-sfpplus1,ether1 vlan-ids=31
add bridge=main_bridge comment=DMZ tagged=ether1,sfp-sfpplus1 vlan-ids=4050
/interface list member
add interface=main_bridge list=LAN
add interface=WAN_VDSL list=WAN
add interface=ether2 list=WAN
add interface=VOIP list=LAN
add interface=IPV6_ONLY list=LAN
add interface=WAN_LTE list=WAN
add interface=INET_FTTH list=LAN
add interface=FREIFUNK list=LAN
add interface=FREIFUNK_GW list=LAN
add interface=DMZ list=WAN
/ip address
add address=10.255.0.18/29 interface=WAN_VDSL network=10.255.0.16
add address=192.168.99.1/24 interface=VOIP network=192.168.99.0
add address=192.168.95.11/24 interface=WAN_LTE network=192.168.95.0
add address=10.255.0.1/29 interface=INET_FTTH network=10.255.0.0
add address=192.168.90.1/24 interface=main_bridge network=192.168.90.0
add address=10.200.250.1/28 interface=FREIFUNK_GW network=10.200.250.0
add address=10.200.255.1/28 interface=FREIFUNK network=10.200.255.0
add address=10.250.254.252 interface=DMZ network=10.250.254.252
/ip dhcp-client
add default-route-distance=2 disabled=no interface=ether2
/ip dns
set allow-remote-requests=yes
/ip firewall address-list
add address=103.53.48.0/23 list=Twitch
add address=185.42.204.0/22 list=Twitch
add address=192.108.239.0/24 list=Twitch
add address=192.16.64.0/21 list=Twitch
add address=199.9.248.0/21 list=Twitch
add address=23.160.0.0/24 list=Twitch
add address=45.113.128.0/22 list=Twitch
add address=52.223.192.0/20 list=Twitch
add address=52.223.208.0/21 list=Twitch
add address=52.223.224.0/20 list=Twitch
add address=52.223.240.0/20 list=Twitch
add address=99.181.64.0/20 list=Twitch
add address=99.181.80.0/21 list=Twitch
add address=99.181.88.0/21 list=Twitch
add address=99.181.96.0/19 list=Twitch
add address=192.168.90.81 comment=deep-thought.home list=LoadBalancingSrcs
add address=192.168.90.21 comment=datengrab.home list=LoadBalancingSrcs
add address=192.168.201.0/24 comment=Stallnetz list=NichtUeberGateway
add address=10.200.255.0/28 comment=freifunk-APs list=NichtUeberGateway
add address=10.200.250.0/28 comment=freifunk-GWs list=NichtUeberGateway
add address=192.168.94.0/24 comment=freifunk-Client list=NichtUeberGateway
add address=192.168.99.0/24 comment=VoIP-Netz list=NichtUeberGateway
add address=[IP ADDRESS] comment="[A COMMENT]" list=NichtUeberGateway
add address=[IP ADDRESS] comment="[A COMMENT]" list=NichtUeberGateway
add address=[IP ADDRESS] list=whitelistInvalid
add address=116.203.7.21 list=whitelistInvalid
add address=10.201.111.2 list=whitelistInvalid
add address=10.201.112.2 list=whitelistInvalid
add address=10.201.113.2 list=whitelistInvalid
add address=[IP ADDRESS] list=whitelistInvalid
add address=[IP ADDRESS] list=whitelistInvalid
add address=[IP ADDRESS] comment="[A COMMENT]" list=NichtUeberGateway
add address=[IP ADDRESS] comment="[A COMMENT]" list=NichtUeberGateway
add address=[IP ADDRESS] comment="[A COMMENT]" list=NichtUeberGateway
add address=[IP ADDRESS] list=whitelistInvalid
add address=192.168.201.0/24 list=whitelistInvalid
add address=10.132.101.0/24 comment=VPN list=NichtUeberGateway
add address=10.55.55.11 comment=Stallnetz list=NichtUeberGateway
add address=192.168.90.0/24 list=whitelistInvalid
add address=[IP ADDRESS] list=Freifunk_GWs
add address=[IP ADDRESS] list=Freifunk_GWs
add address=[IP ADDRESS] list=Freifunk_GWs
add address=[IP ADDRESS] list=Freifunk_GWs
add address=[IP ADDRESS] list=Freifunk_GWs
add address=[IP ADDRESS] list=Freifunk_GWs
add address=192.168.1.1 comment=freifunk-Client list=NichtUeberGateway
add address=10.255.0.17 comment=VDSL-Modem list=NichtUeberGateway
/ip firewall filter
add action=accept chain=input comment="defconf: accept ICMP" protocol=icmp
add action=accept chain=output comment="defconf: accept ICMP" log=yes protocol=icmp
add action=accept chain=input comment="defconf: accept established,related,untracked" connection-state=\
    established,related,untracked
add action=drop chain=input comment="defconf: drop invalid" connection-state=invalid
add action=drop chain=input comment="defconf: drop all not coming from LAN" in-interface-list=!LAN log=yes
add action=accept chain=forward comment="defconf: accept established,related, untracked" connection-state=\
    established,related,untracked
add action=drop chain=forward comment="defconf: drop invalid" connection-state=invalid dst-address-list=\
    !whitelistInvalid log-prefix=dropInvalid
add action=drop chain=forward comment="defconf:  drop all from WAN not DSTNATed" connection-nat-state=!dstnat \
    connection-state=new in-interface-list=WAN
/ip firewall mangle
add action=mark-connection chain=prerouting comment="Mark Twitch" connection-mark=no-mark dst-address-list=Twitch \
    dst-address-type=!local in-interface-list=LAN new-connection-mark=Streaming passthrough=yes
add action=mark-routing chain=prerouting comment="Routing Mark Streaming" connection-mark=Streaming in-interface-list=\
    LAN passthrough=no
add action=mark-connection chain=prerouting comment="Mark Freifunk" dst-address-list=Freifunk_GWs new-connection-mark=\
    Freifunk passthrough=yes
/ip firewall nat
add action=masquerade chain=srcnat out-interface-list=WAN
add action=masquerade chain=srcnat comment="NAT bei fritz.box, sonst kein Login m\F6glich" dst-address=192.168.99.13 \
    out-interface=VOIP
/ip route
add check-gateway=ping distance=3 dst-address=0.0.0.0/0 gateway=10.255.0.17 pref-src="" scope=30 target-scope=10 type=\
    unicast
add check-gateway=ping distance=5 dst-address=0.0.0.0/0 gateway=192.168.95.1 type=unicast
add dst-address=192.168.201.0/24 gateway=192.168.90.60 type=unicast
add comment="[A COMMENT]" distance=1 dst-address=[IP ADDRESS] gateway=192.168.90.60 pref-src="" \
    scope=30 target-scope=10 type=unicast
add comment="[A COMMENT]" distance=1 dst-address=[IP ADDRESS] gateway=192.168.90.60 pref-src=\
    "" scope=30 target-scope=10 type=unicast
add comment="[A COMMENT]" distance=1 dst-address=[IP ADDRESS] gateway=192.168.90.60 pref-src="" \
    scope=30 target-scope=10 type=unicast
add comment="[A COMMENT]" distance=1 dst-address=[IP ADDRESS] gateway=192.168.90.60 pref-src="" \
    scope=30 target-scope=10 type=unicast
add comment="[A COMMENT]" distance=1 dst-address=[IP ADDRESS] gateway=192.168.90.60 pref-src="" \
    scope=30 target-scope=10 type=unicast
add distance=1 dst-address=10.201.111.0/24 gateway=192.168.90.60 pref-src="" scope=30 target-scope=10 type=unicast
add distance=1 dst-address=10.201.112.0/24 gateway=192.168.90.60 pref-src="" scope=30 target-scope=10 type=unicast
add distance=1 dst-address=10.201.113.0/24 gateway=192.168.90.60 pref-src="" scope=30 target-scope=10 type=unicast
/ipv6 address
add address=::[SUFFIX] eui-64=yes from-pool=DG interface=IPV6_ONLY
add address=::[SUFFIX] eui-64=yes from-pool=DG interface=VOIP
add address=::[SUFFIX] eui-64=yes from-pool=DG interface=INET_FTTH
/ipv6 dhcp-client
add add-default-route=yes interface=ether2 pool-name=DG request=address,prefix
/ipv6 firewall address-list
add address=::/128 comment="defconf: unspecified address" list=bad_ipv6
add address=::1/128 comment="defconf: lo" list=bad_ipv6
add address=fec0::/10 comment="defconf: site-local" list=bad_ipv6
add address=::ffff:0.0.0.0/96 comment="defconf: ipv4-mapped" list=bad_ipv6
add address=::/96 comment="defconf: ipv4 compat" list=bad_ipv6
add address=100::/64 comment="defconf: discard only " list=bad_ipv6
add address=2001:db8::/32 comment="defconf: documentation" list=bad_ipv6
add address=2001:10::/28 comment="defconf: ORCHID" list=bad_ipv6
add address=3ffe::/16 comment="defconf: 6bone" list=bad_ipv6
add address=::224.0.0.0/100 comment="defconf: other" list=bad_ipv6
add address=::127.0.0.0/104 comment="defconf: other" list=bad_ipv6
add address=::/104 comment="defconf: other" list=bad_ipv6
add address=::255.0.0.0/104 comment="defconf: other" list=bad_ipv6
add address=[AN IPV6 ADDRESS] list=[A HOSTNAME]
/ipv6 firewall filter
add action=accept chain=forward dst-address=[AN IPV6 ADDRESS] dst-port=44201 \
    in-interface-list=WAN out-interface-list=LAN protocol=udp
add action=accept chain=forward in-interface-list=LAN out-interface-list=WAN protocol=udp src-address=\
    [AN IPV6 ADDRESS] src-port=44201
add action=accept chain=forward in-interface-list=LAN out-interface-list=WAN
add action=drop chain=forward connection-state=invalid
add action=drop chain=forward connection-state=new,untracked in-interface-list=WAN
add action=drop chain=input disabled=yes in-interface-list=!LAN log=yes
add action=accept chain=forward dst-port=15151-15153 in-interface-list=WAN out-interface-list=LAN protocol=tcp
add action=accept chain=forward dst-port=15151-15153 in-interface-list=WAN out-interface-list=LAN protocol=udp
add action=accept chain=forward dst-port=5201 in-interface-list=WAN out-interface-list=LAN protocol=tcp
add action=accept chain=forward in-interface-list=LAN out-interface-list=WAN
add action=accept chain=forward connection-state=established,related,untracked disabled=yes
add action=drop chain=forward connection-state=invalid
add action=drop chain=forward connection-state=invalid,new,untracked in-interface-list=WAN out-interface-list=LAN
add action=drop chain=forward connection-state=new,untracked in-interface-list=WAN
add action=drop chain=input disabled=yes in-interface-list=!LAN log=yes
/ipv6 firewall mangle
add action=mark-packet chain=prerouting connection-mark=Stall new-packet-mark=Stal
add action=mark-packet chain=prerouting connection-mark=Stall new-packet-mark=Stal
add action=mark-connection chain=prerouting dst-address=[AN IPV6 ADDRESS] dst-port=44201 \
    new-connection-mark=Stall passthrough=yes protocol=udp
add action=mark-connection chain=prerouting dst-address-list=[A HOSTNAME] new-connection-mark=[A HOSTNAME] \
    passthrough=yes
add action=mark-packet chain=prerouting connection-mark=Stall new-packet-mark=Stall passthrough=no
add action=mark-packet chain=prerouting connection-mark=[A HOSTNAME] new-packet-mark=[A HOSTNAME] \
    passthrough=no
/ipv6 nd
set [ find default=yes ] managed-address-configuration=yes ra-delay=5s ra-lifetime=15m retransmit-interval=15s
/ipv6 nd prefix default
set preferred-lifetime=15m valid-lifetime=15m
/system clock
set time-zone-name=Europe/Berlin
/system identity
set name=Router_RB4011
/system package update
set channel=development
/tool mac-server
set allowed-interface-list=LAN
/tool mac-server mac-winbox
set allowed-interface-list=LAN
 
thadrumr
newbie
Posts: 32
Joined: Sat Dec 23, 2017 2:02 am

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 12:16 am

My CHR seems to be rebooting every 30-45 minutes with no reason in the logs. I think it may be related to the Queue. I tried to change to FQ_CODEL and it went into a reboot loop. I disabled my queue tree and just did a simple queue using CAKE and will see how it runs.

Edit it seems that the Cake Queue is causing the reboot as well. Not sure what is causing this. On one of the reboots I noticed the error System is deadlocked on memory on the VM console.
Last edited by thadrumr on Fri Dec 04, 2020 1:07 am, edited 3 times in total.
 
MoNsTeRRR
just joined
Posts: 5
Joined: Tue Oct 27, 2020 2:46 am
Location: France

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 12:17 am

*) other fixes and improvements;
Does IPv6 tunnels are fixed with the new release ? If someone can tell me before upgrading for nothing :) thanks
And the IPQ4019 devices with 16MB storage like HAP AC2 e CHATEAU LTE12??? It's possible to use external memory on usb2 port for the driver?
Unfortunately, it's not. The wifiwave2 package is a preview of the wireless driver and configuration interface being built for future products and an opportunity to provide feedback on it.
Existing products will continue to receive updates for the bundled wireless package.
It's really a joke it's sad to see that, fortunately I didn't buy chateau (never buy hardware where there is only beta firmware available on it).
 
storrgie
just joined
Posts: 7
Joined: Mon Aug 10, 2020 12:34 am

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 1:56 am

Reporting that on multiple CCR2004 with zero configuration that the system is barely responsive.

Assigning an IP to an interface while using MAC control via winbox then attempting to ssh works periodically, getting a lot of packet loss. Literally nothing running on these (tested on three that all came in the same batch).

Should it be expected that the CCR2004 is not usable with this build?
Last edited by storrgie on Fri Dec 04, 2020 2:56 am, edited 1 time in total.
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 2:42 am

OSPFv2 is somewhat unstable now, with either broadcast or PTP network type forming neighbor with ROS 6 - "received wrong LS Ack" in log, with ROS 6 router. Appears to result in crashing entire routing stack for a second, causing tunnels to drop and re-establish and also causing BGP peering to break and re-establish.

When the routing stack crashes, a default route received via DHCP disappears. I've had to create a static default route instead.
 
User avatar
Paternot
Forum Veteran
Forum Veteran
Posts: 953
Joined: Thu Jun 02, 2016 4:01 am
Location: Niterói / Brazil

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 4:09 am

Finally! That was one long wait...
 
lcohen999
just joined
Posts: 14
Joined: Fri Oct 18, 2019 3:34 am

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 4:44 am

I upgraded my Audience today.

Had to factory reset it but when it came up, I saw this error

error while running customized default configuration script: expected end of command (line 1310 column 53)

I was able to get the wireless interface manually but there is really no configuration on the device.

It works fine but no default settings were able to come up
 
santyx32
Member Candidate
Member Candidate
Posts: 215
Joined: Fri Oct 25, 2019 2:17 am

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 7:38 am

At least we have OpenWrt to provide Wave2 drivers + WPA3 on our hAP ac2s, btw kudos to Mikrotik for hearing user requests and implementing modern queue management algorithms on ROS.
 
User avatar
FToms
MikroTik Support
MikroTik Support
Posts: 87
Joined: Fri Jul 24, 2020 3:28 pm

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 7:41 am

Is 802.11ax included in wave2 drivers?
Or is it just an image?
As stated before, the wifiwave2 package is being developed for future products. Devices compatible with the package that are on sale currently are limited to 802.11ac by their hardware.
 
abiv
just joined
Posts: 24
Joined: Sat Nov 23, 2019 4:51 am

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 8:18 am

Oh well, guess I'll just get a Wifi 6 AP instead. Sad.
 
ivicask
Member
Member
Posts: 417
Joined: Tue Jul 07, 2015 2:40 pm
Location: Croatia, Zagreb

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 10:36 am

Is this a bug or some kinda of new feature, my bridge gets new MAC every time i reboot router (Hex), just installed beta3, so DHCP reservation is messed up as it gets new ip every reboot.
 
User avatar
osc86
Member Candidate
Member Candidate
Posts: 197
Joined: Wed Aug 09, 2017 1:15 pm

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 10:51 am

Is this a bug or some kinda of new feature, my bridge gets new MAC every time i reboot router (Hex), just installed beta3, so DHCP reservation is messed up as it gets new ip every reboot.
No, this has always been the case - really annoying. The bridge uses the mac-address of one of the slaved interfaces. Use Admin Mac on bridges.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10183
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 12:07 pm

Finally! That was one long wait...
Frankly, the feature list is a bit disappointing after such a long wait and after seeing some of the feature matrices on the help site.
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 26290
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 12:09 pm

Which features are missing in your opinion?
 
User avatar
osc86
Member Candidate
Member Candidate
Posts: 197
Joined: Wed Aug 09, 2017 1:15 pm

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 12:21 pm

Which features are missing in your opinion?
avahi / mdns-reflection; I have to do this on a raspberry pi now. It's a necessary feature, if you separate your iot stuff from production networks.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10183
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 12:41 pm

Which features are missing in your opinion?
To be clear: I mean the list of new/updated features in the "What's new in 7.1beta3".
I hoped for BGP GUI. What I got was BGP that no longer works (even in commandline, see report above).
I am hoping for new features in IPv6, including NPT. (I think policy routing is already getting better)
 
User avatar
SiB
Forum Guru
Forum Guru
Posts: 1888
Joined: Sun Jan 06, 2013 11:19 pm
Location: Poland

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 12:41 pm

LHGGR
Image

Image
 
CosmosNetwork
just joined
Posts: 3
Joined: Fri Mar 27, 2020 1:22 pm

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 12:44 pm

Which features are missing in your opinion?
DHCP leases as DNS entries without scripts.
 
babelmonk
just joined
Posts: 4
Joined: Sun Nov 22, 2020 7:02 pm

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 12:58 pm

Which features are missing in your opinion?
DHCP leases as DNS entries without scripts.
+1 Would be nice to have a checkbox on a lease / pool
 
haedertowfeq
just joined
Posts: 15
Joined: Thu Nov 19, 2020 5:58 pm

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 1:10 pm

LHGGR
Image

Image
My routes didn't upgrade too it's stuck on "calculate download size"

تم الإرسال من Redmi Note 8 Pro باستخدام Tapatalk

 
pe1chl
Forum Guru
Forum Guru
Posts: 10183
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 1:12 pm

LHGGR
You cannot update that way. You have to download it yourself, upload to the router, and reboot.
 
glueck05
newbie
Posts: 37
Joined: Fri Jan 26, 2018 12:49 pm

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 2:35 pm

Hello, i try to install on X86.
[admin@mikrotik] /system package> print
Flags: X - disabled
# NAME VERSION SCHEDULED
0 ipv6 6.42.12
1 security 6.42.12
2 dhcp 6.42.12
3 mpls 6.42.12
4 routing 6.42.12
5 advanced-tools 6.42.12
6 ppp 6.42.12
7 system 6.42.12

[admin@mikrotik] /system package> update download
channel: development
current-version: 6.42.12
latest-version: 7.1beta3
status: ERROR: missing ipv6-7.1beta3.npk
Is IPv6 not implemented yet?

thanks,
glueck
 
pe1chl
Forum Guru
Forum Guru
Posts: 10183
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 2:43 pm

AGAIN: you cannot update it that way.
Download the package from the website, upload it to your router, and reboot.
And at least make sure you have a backup of your system that you can restore outside of RouterOS (like a disk image), as it is probably going to fail.
Certainly when you try to update from such an ancient version!
Why don't you update that to 6.47 first???
 
glueck05
newbie
Posts: 37
Joined: Fri Jan 26, 2018 12:49 pm

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 2:53 pm

AGAIN: you cannot update it that way.
Download the package from the website, upload it to your router, and reboot.
And at least make sure you have a backup of your system that you can restore outside of RouterOS (like a disk image), as it is probably going to fail.
Certainly when you try to update from such an ancient version!
Why don't you update that to 6.47 first???
Yes, sorry. I do it that way and it worked!

thanks,
glueck
 
thadrumr
newbie
Posts: 32
Joined: Sat Dec 23, 2017 2:02 am

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 3:09 pm

I changed both my simple queue and my queue-tree back to sfq and my router has remained stable for 14 hours. I SOO wanted CAKE to be ready for primetime usage on my home router but as I stated above it was causing reboots every 30-45 mins or so. Heres hoping they get the kinks ironed out in the next release.
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 26290
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 3:31 pm

please remember that this is an unstable beta, and things can and will break. Please report your findings to support or here. The version is not ready for commercial use on important systems
 
vaka
just joined
Posts: 22
Joined: Fri Dec 04, 2020 4:08 pm
Location: Ukraine

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 4:14 pm

Reporting that on multiple CCR2004 with zero configuration that the system is barely responsive.
catched the same problem on my ccr2004 with 7beta3. 7beta2 worked more stable
 
User avatar
macgaiver
Forum Guru
Forum Guru
Posts: 1764
Joined: Wed May 18, 2005 5:57 pm
Location: Sol III, Sol system, Sector 001, Alpha Quadrant

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 5:26 pm

ok, NOW hap ac3 makes perfect sense, it was custom made for new wireless package. and works on my device like a charm, i need to double check it but the feel is that mobile devices have easier time to communicated to AP when i'm on the far side of the house. Normal home GW features work like a charm, will play with new queueing shortly.

Only issue so far is that one of the old laptops refuses to connect to new wireless driver, and nothing in the logs. will have to dig into what chipset is there, some kind of Intel that is all i can say so far.
 
jeetlal
just joined
Posts: 13
Joined: Mon Oct 08, 2018 8:14 pm

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 5:36 pm

Which features are missing in your opinion?
Macvlan feature missing
 
lcohen999
just joined
Posts: 14
Joined: Fri Oct 18, 2019 3:34 am

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 6:26 pm

Just a quick update/feedback on wifiwave2 on an Audience

As mentioned, the default scripts do not work, even with a factory reset. So I had to connect via MAC, setup a bridge, add wifi 1/2/3 and ethernet to it, assign dhcp client so I can give it an IP.

On my Surface Pro 5, I would get with the old drivers 150-230 on a fast.com speedtest (I have a 1GB download connection but the Surface is only 2x2). With wifiwave2, it seems to be 190-250 more consistently, as well I see an anecdotal boost in range as well, except in one dead spot in my house but nothing works there as it is over the garage.

I tried running the command to kick off weak signal'ed devices but it crashed the router when I tried and had to be factory reset.

Seems like a good first step...and since my Audience isn't my primary router ( I have a Hap AC for that) I don't care that the default script didn't work.
 
mafiosa
Member Candidate
Member Candidate
Posts: 266
Joined: Fri Dec 09, 2016 8:10 pm
Location: Kolkata, India
Contact:

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 6:37 pm

Which features are missing in your opinion?
Unicast VxLAN tunnels would be of great use.
A better explanation of route filters.
Zerotier
 
hci
Long time Member
Long time Member
Posts: 674
Joined: Fri May 28, 2004 5:10 pm

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 7:52 pm

It seems that IPv6 dhcp client over PPPoE no longer works. Worked in beta2. Keeps searching.
 
anuser
Long time Member
Long time Member
Posts: 601
Joined: Sat Nov 29, 2014 7:27 pm

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 8:35 pm

!) added new experimental wireless package "wifiwave2" for ARM devices with more than 256 MB of RAM (CLI only);
Please consider to make the new package compatible to current IPQ4018/IPQ4019 access points with 128MB RAM, e.g. cAP ac, hAP ac2, aswell.
 
lcohen999
just joined
Posts: 14
Joined: Fri Oct 18, 2019 3:34 am

Re: v7.1beta3 [development] is released!

Fri Dec 04, 2020 11:17 pm

Came home today to no wifi. Looks like the Audience was caught in a boot loop

I ended up having to reset

See if this is a one off or daily occurrence
 
mikegleasonjr
Frequent Visitor
Frequent Visitor
Posts: 55
Joined: Tue Aug 07, 2018 3:14 am

Re: v7.1beta3 [development] is released!

Sat Dec 05, 2020 12:25 am

I changed both my simple queue and my queue-tree back to sfq and my router has remained stable for 14 hours. I SOO wanted CAKE to be ready for primetime usage on my home router but as I stated above it was causing reboots every 30-45 mins or so. Heres hoping they get the kinks ironed out in the next release.
Me too on my RB4011 (non-wifi). I didn't try reverting to SFQ, I just downgraded to the long-term release.

Here is the last logs of reboots:
jan/02/1970 00:02:55 system,error,critical router was rebooted without proper shutdown
jan/01/2002 01:00:00 system,error,critical router was rebooted without proper shutdown
jan/02/1970 00:02:55 system,error,critical router was rebooted without proper shutdown
jan/01/2002 01:00:00 system,error,critical router was rebooted without proper shutdown
Maybe the constant times can tell something...
 
mhugo
Member Candidate
Member Candidate
Posts: 179
Joined: Mon Sep 19, 2005 11:48 am

Re: v7.1beta3 [development] is released!

Sat Dec 05, 2020 2:17 am

Hi,

This build is not working on 2004s. High packetloss. Same reported on last 6.48beta.

/Mikael
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v7.1beta3 [development] is released!

Sat Dec 05, 2020 3:54 am

Came home today to no wifi. Looks like the Audience was caught in a boot loop

I ended up having to reset

See if this is a one off or daily occurrence
I had to revert back to Beta 2 on my Audience. No boot loop, but the management interface was only accessible via MAC telnet and showed no interfaces and most other things were blank. Rebooting it fixed it for another hour or so, at which point the same thing would happen again.

The only device I've been able to keep Beta 3 on is my hAP ac, which is a MIPS-BE architecture device. It seems to work normally. Both my RB4011 and Audience were crashing.
 
storrgie
just joined
Posts: 7
Joined: Mon Aug 10, 2020 12:34 am

Re: v7.1beta3 [development] is released!

Sat Dec 05, 2020 4:32 am

Came home today to no wifi. Looks like the Audience was caught in a boot loop

I ended up having to reset

See if this is a one off or daily occurrence
I had to revert back to Beta 2 on my Audience. No boot loop, but the management interface was only accessible via MAC telnet and showed no interfaces and most other things were blank. Rebooting it fixed it for another hour or so, at which point the same thing would happen again.

The only device I've been able to keep Beta 3 on is my hAP ac, which is a MIPS-BE architecture device. It seems to work normally. Both my RB4011 and Audience were crashing.
This would substantiate the issues I'm seeing on all the CCR2004 I've tried. So the build of ROS7B3 is borked for Arm?
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v7.1beta3 [development] is released!

Sat Dec 05, 2020 4:57 am

This would substantiate the issues I'm seeing on all the CCR2004 I've tried. So the build of ROS7B3 is borked for Arm?
It is hard to say whether it is due to the architecture or instead something related to the drivers or the particular configuration I have. The RB4011 is my main router at home so I am using a lot of features on it, I am not entirely surprised that I am encountering instability as a result. However, my hAP ac and Audience are both acting as pretty normal CAP devices managed by the RB4011 CAPsMAN. The hAP ac is stable, the Audience is not, even though their configurations are rather simple and virtually identical.
 
User avatar
anav
Forum Guru
Forum Guru
Posts: 18958
Joined: Sun Feb 18, 2018 11:28 pm
Location: Nova Scotia, Canada
Contact:

Re: v7.1beta3 [development] is released!

Sat Dec 05, 2020 5:29 am

That's the point. They choose the words carefully so that you have to ask for more questions and with each reply you start to realize what is going on. At this point we are 100% right about not getting Wave2 support for 16MB with 128MB devices until proven otherwise.
One reason more not to buy any WiFi device from Mikrotik, until this is clear
I have two capacs, but since then, when wifi needs arose I purchased other products (eap245) and looking at their other offerings (AX10) one can get good value (mikrotiks excellent value proposition for routers) in wifi from other vendors. This diversion to others was not what I wanted to do and was not based on feature set but on the lack of stability dropouts and overall sense of not knowing what was wrong. In other words although the feature sets are great on the others it was the confidence that they would simply work that was most important. Hopefully I wish MT good luck, in establishing a more stable predictable experience with the new driver!! It would be great to be able to recommend not only the routers but also the wifi to others!(right now the 60hz stuff is the only product I would recommend).
 
nemoforum
Frequent Visitor
Frequent Visitor
Posts: 58
Joined: Thu Jan 05, 2017 11:08 pm

Re: v7.1beta3 [development] is released!

Sat Dec 05, 2020 12:39 pm

!) added new experimental wireless package "wifiwave2" for ARM devices with more than 256 MB of RAM (CLI only);
Does it mean that 802.11ax devices are coming soon?
Can we expect this new wi-fi driver to replace the old one in 7.x for hAP ac2 (mine has 16M of flash and 256 of RAM)?
 
pe1chl
Forum Guru
Forum Guru
Posts: 10183
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.1beta3 [development] is released!

Sat Dec 05, 2020 1:01 pm

!) added new experimental wireless package "wifiwave2" for ARM devices with more than 256 MB of RAM (CLI only);
Does it mean that 802.11ax devices are coming soon?
Can we expect this new wi-fi driver to replace the old one in 7.x for hAP ac2 (mine has 16M of flash and 256 of RAM)?
Did you bother to read some of the replies and remarks above?
 
HotBlock
just joined
Posts: 18
Joined: Sun Apr 16, 2017 12:30 pm

Re: v7.1beta3 [development] is released!

Sat Dec 05, 2020 5:09 pm

Can I connect Wireguard to hostnames instead ip adresses?
 
lcohen999
just joined
Posts: 14
Joined: Fri Oct 18, 2019 3:34 am

Re: v7.1beta3 [development] is released!

Sat Dec 05, 2020 5:41 pm

Came home today to no wifi. Looks like the Audience was caught in a boot loop

I ended up having to reset

See if this is a one off or daily occurrence
I had to revert back to Beta 2 on my Audience. No boot loop, but the management interface was only accessible via MAC telnet and showed no interfaces and most other things were blank. Rebooting it fixed it for another hour or so, at which point the same thing would happen again.

The only device I've been able to keep Beta 3 on is my hAP ac, which is a MIPS-BE architecture device. It seems to work normally. Both my RB4011 and Audience were crashing.
Same here. Worked for a few hours, just wifi enabled nothing else and it would crash and bootloop.

Restored from backup and back on 6 (for now)
 
vfreex
just joined
Posts: 10
Joined: Sat Dec 05, 2020 8:49 pm

Re: v7.1beta3 [development] is released!

Sat Dec 05, 2020 8:53 pm

L3 hardware offloading is not working on my CRS309-1G-8S+IN. Setting l3hw=yes or no has no difference and the routing performance is only about 200Mbps.
 
nemoforum
Frequent Visitor
Frequent Visitor
Posts: 58
Joined: Thu Jan 05, 2017 11:08 pm

Re: v7.1beta3 [development] is released!

Sat Dec 05, 2020 9:53 pm

!) added new experimental wireless package "wifiwave2" for ARM devices with more than 256 MB of RAM (CLI only);
Does it mean that 802.11ax devices are coming soon?
Can we expect this new wi-fi driver to replace the old one in 7.x for hAP ac2 (mine has 16M of flash and 256 of RAM)?
Did you bother to read some of the replies and remarks above?
I read all the thread.
This viewtopic.php?f=1&t=169992#p832274 reply doesn't cover the part of my question regarding wifi driver replacement.
Also, nothing about ax devices.
 
anuser
Long time Member
Long time Member
Posts: 601
Joined: Sat Nov 29, 2014 7:27 pm

Re: v7.1beta3 [development] is released!

Sat Dec 05, 2020 11:37 pm

!) added new experimental wireless package "wifiwave2" for ARM devices with more than 256 MB of RAM (CLI only);
If you unpack the new wireless package you´ll see that there are many components which do not all belong to IPQ40xx chipset, so 16MB of ROM should be sufficient some day when the new wireless driver is optimized and repackaged if MikroTik wants to do so.
Also looking at a https://forum.openwrt.org/t/support-for ... 2/23333/44 there´s something like a "ath10k-ct-smallbuffers" which helps reducing the amount of RAM being needed.Nobody is stopping MikroTik developers to use the same technique to improve needed RAM requirements.
Is 802.11ax included in wave2 drivers?
Well, 802.11ax is way more than MU-MIMO, i.e.
- UL MU-MIMO
- DL MU-MIMO
- OFDMA
- Target Wake Time (TWT)
- ...

There are other features beside 802.11ac / 802.11ax, e.g. "airtime fairness" which actually helps a lot and is used by a lot of vendors, not only the big ones
I like the article ""Ending the Anomaly: Achieving Low Latency and Airtime Fairness in WiFi" on https://www.bufferbloat.net/projects/ma ... fast/wiki/
 
User avatar
rooted
Member Candidate
Member Candidate
Posts: 129
Joined: Tue Feb 04, 2020 5:58 pm

Re: v7.1beta3 [development] is released!

Sun Dec 06, 2020 1:49 am


I purchased other products (eap245)
I purchased this as well and 5ghz above channel 100 was semi-broken (super slow), also it didn't have DFS. I went back to using a ea7500 as an AP for my hAP ac2.
 
User avatar
npeca75
Frequent Visitor
Frequent Visitor
Posts: 75
Joined: Thu Aug 03, 2017 3:12 pm

Re: v7.1beta3 [development] is released!

Sun Dec 06, 2020 6:01 am

IPv4-mapped IPv6 addresses

ROS v6
::169.254.101.1/96

OpenWRT
::169.254.101.103/96

ROS v7.1b3
::169.254.101.199/96

v6 could ping own adress and .103. Ping to v7 does not work
OpenWRT could ping .1 and own adress. Ping to v7 does not work

v7 could NOT ping own address
v7 could NOT ping .1 or .103
 
rplant
Member Candidate
Member Candidate
Posts: 282
Joined: Fri Sep 29, 2017 11:42 am

Re: v7.1beta3 [development] is released!

Sun Dec 06, 2020 7:00 am

Looking at Wireguard,

Happy to see the peer endpoints appear to be stay at what I set them,
Peer by DNS looks to mostly work.
Both maybe seem a little bit fragile, time will tell.

Thanks :)

However, I now notice that it is all a bit opaque, (for a Mikrotik)
There is not much monitoring currently available.

This is a low priority.

I would like to perhaps have an additional tab on the wireguard peer
which gives traffic information for that peer.

eg.
-Time of Last received packet for the peer.
-Actual IP address/port of remote peer
-How many packets have been dropped (perhaps indicating
the allowed address or remote config is wrong)
-Peer Traffic Counters and Graphs.

Perhaps if this were done well the changes required could be pushed back
to wireguard?

If have a persistent keepalive setting, could log a connected state.
(eg. If last peer packet received was less than 5 keepalive timeouts
ago, peer is up)
 
nevolex
Member Candidate
Member Candidate
Posts: 167
Joined: Mon Apr 20, 2020 1:09 pm

Re: v7.1beta3 [development] is released!

Sun Dec 06, 2020 11:13 am

wifiwave2 experimental support -- thanks a lot Mikrotik for start your work on this, can't wait to see the final version integrated into winbox sometime next year!
 
User avatar
npeca75
Frequent Visitor
Frequent Visitor
Posts: 75
Joined: Thu Aug 03, 2017 3:12 pm

Re: v7.1beta3 [development] is released!

Sun Dec 06, 2020 12:08 pm

Hi @Mikrotik

is there any chance to implement custom UDP port for sending SNMP traps in next Beta?

now it is impossible to set any port value in traps destination in any IPv4 or IPv6 form
tried from winbox and from CLI
 
User avatar
anav
Forum Guru
Forum Guru
Posts: 18958
Joined: Sun Feb 18, 2018 11:28 pm
Location: Nova Scotia, Canada
Contact:

Re: v7.1beta3 [development] is released!

Sun Dec 06, 2020 2:53 pm

I purchased other products (eap245)
I purchased this as well and 5ghz above channel 100 was semi-broken (super slow), also it didn't have DFS. I went back to using a ea7500 as an AP for my hAP ac2.
Thanks was not aware of the limitations, where I live DFS has never been an issue and I live in a single home on a large lot so significant freq interference is also a non-issue.
 
User avatar
mozerd
Forum Veteran
Forum Veteran
Posts: 871
Joined: Thu Oct 05, 2017 3:39 pm
Location: Canada
Contact:

Re: v7.1beta3 [development] is released!

Sun Dec 06, 2020 3:03 pm

Thanks was not aware of the limitations, where I live DFS has never been an issue and I live in a single home on a large lot so significant freq interference is also a non-issue.
@anav, FYI EAP245, V3 firmware 2.3.0 Build 20190731 Rel. 51932 provides support for DFS
 
User avatar
anav
Forum Guru
Forum Guru
Posts: 18958
Joined: Sun Feb 18, 2018 11:28 pm
Location: Nova Scotia, Canada
Contact:

Re: v7.1beta3 [development] is released!

Sun Dec 06, 2020 3:34 pm

Good to know Mozerd, never seen DFS in Nova Scotia though LOL. what about above channel 100 limitation?
Also have you had a chance to look at the tp-link AX10, just for its wifi?? (as an AP switch combo)
 
User avatar
StubArea51
Trainer
Trainer
Posts: 1739
Joined: Fri Aug 10, 2012 6:46 am
Location: stubarea51.net
Contact:

Re: v7.1beta3 [development] is released!

Sun Dec 06, 2020 3:41 pm

I am ***soo*** excited to finally see fq-codel and cake in RouterOS, this is going to be a game changer for shaping options in ISP networks.

Nice work MikroTik :)
 
anuser
Long time Member
Long time Member
Posts: 601
Joined: Sat Nov 29, 2014 7:27 pm

Re: v7.1beta3 [development] is released!

Sun Dec 06, 2020 4:20 pm

RouterOS version 7.1beta3 has been released in public "development" channel!
!) added new experimental wireless package "wifiwave2" for ARM devices with more than 256 MB of RAM (CLI only);
Can you please provide a kind of "wifiwave2-lite" package for cAP ac, hAP ac2,, ... only, i.e. just remove the folders "QCA9984", "QCA9888" "IPQ8074v2", "IPQ8074" and "IPQ6018", i.e.remove all non IPQ4019 stuff from the current big wifiwave2 package.Without those folders the package could actually be installed on the 16MB ROM of both access points. Please, let us users test that new wireless package on our current cAP ac and hAP ac2 access points even with 128MB only. Let´s see how it works and improve the driver step to step together.
 
User avatar
anav
Forum Guru
Forum Guru
Posts: 18958
Joined: Sun Feb 18, 2018 11:28 pm
Location: Nova Scotia, Canada
Contact:

Re: v7.1beta3 [development] is released!

Sun Dec 06, 2020 8:20 pm

I am ***soo*** excited to finally see fq-codel and cake in RouterOS, this is going to be a game changer for shaping options in ISP networks.

Nice work MikroTik :)
Hi IPANet, I am in awe of your network designs........... I don't know or think I will ever need fz-codel or cake functionality but I can guarantee you I will probably be eating cake when I read your posts demonstrating such features !! :-)
 
heidarren
Member Candidate
Member Candidate
Posts: 136
Joined: Mon Aug 05, 2019 9:56 am

Re: v7.1beta3 [development] is released!

Sun Dec 06, 2020 8:46 pm

Those who has installed wave2 wireless can please share with us about the experience? Any improvement? Does it support 802.11k/v/r?
 
heidarren
Member Candidate
Member Candidate
Posts: 136
Joined: Mon Aug 05, 2019 9:56 am

Re: v7.1beta3 [development] is released!

Sun Dec 06, 2020 8:48 pm

Those who has installed wave2 wireless can please share with us about the experience? Any improvement? Does it support 802.11k/v/r? It can be check by installing WinFi Lite from https://www.helge-keck.com/ in windows.
 
templeos
just joined
Posts: 19
Joined: Mon Aug 26, 2019 3:58 pm

Re: v7.1beta3 [development] is released!

Sun Dec 06, 2020 9:09 pm

Can you please provide a kind of "wifiwave2-lite" package for cAP ac, hAP ac2,, ... only, i.e. just remove the folders "QCA9984", "QCA9888" "IPQ8074v2", "IPQ8074" and "IPQ6018", i.e.remove all non IPQ4019 stuff from the current big wifiwave2 package.Without those folders the package could actually be installed on the 16MB ROM of both access points. Please, let us users test that new wireless package on our current cAP ac and hAP ac2 access points even with 128MB only. Let´s see how it works and improve the driver step to step together.
You are 100% right. I also unpacked the .npk file and unsquashfs and I did find new firmware for those new Qualcomm chips as well. IPQ6018, IPQ8074 and IPQ8074v2. No wonders it doesn't fit on devices with only 16MB storage.
wifiwave2.png
At least we now know that you are going to use these chips for future products. Totally agree with anuser about a wifiwave2-lite package.
You do not have the required permissions to view the files attached to this post.
 
Quasar
newbie
Posts: 33
Joined: Sun Oct 05, 2014 1:11 pm

Re: v7.1beta3 [development] is released!

Sun Dec 06, 2020 10:57 pm

At least we now know that you are going to use these chips for future products. Totally agree with anuser about a wifiwave2-lite package.
As always, there are some other interesting bits in there. Models containing '924' and '5009' for example.

5009 would be the 4011 successor with 802.11ax, IPQ8074? Interestingly only 9 wired ports..
 
User avatar
anav
Forum Guru
Forum Guru
Posts: 18958
Joined: Sun Feb 18, 2018 11:28 pm
Location: Nova Scotia, Canada
Contact:

Re: v7.1beta3 [development] is released!

Sun Dec 06, 2020 11:23 pm

Can you please provide a kind of "wifiwave2-lite" package for cAP ac, hAP ac2,, ... only, i.e. just remove the folders "QCA9984", "QCA9888" "IPQ8074v2", "IPQ8074" and "IPQ6018", i.e.remove all non IPQ4019 stuff from the current big wifiwave2 package.Without those folders the package could actually be installed on the 16MB ROM of both access points. Please, let us users test that new wireless package on our current cAP ac and hAP ac2 access points even with 128MB only. Let´s see how it works and improve the driver step to step together.
You are 100% right. I also unpacked the .npk file and unsquashfs and I did find new firmware for those new Qualcomm chips as well. IPQ6018, IPQ8074 and IPQ8074v2. No wonders it doesn't fit on devices with only 16MB storage.wifiwave2.png

At least we now know that you are going to use these chips for future products. Totally agree with anuser about a wifiwave2-lite package.
Okay how do I remove the chip from my capac and solder one of the above chips ................ and add memory etc................
 
User avatar
xvo
Forum Guru
Forum Guru
Posts: 1237
Joined: Sat Mar 03, 2018 1:12 am
Location: Moscow, Russia

Re: v7.1beta3 [development] is released!

Sun Dec 06, 2020 11:33 pm

Interestingly only 9 wired ports..
Probably 8-port switch + 10Gb combo-port.
Would be nice.
 
templeos
just joined
Posts: 19
Joined: Mon Aug 26, 2019 3:58 pm

Re: v7.1beta3 [development] is released!

Sun Dec 06, 2020 11:39 pm

Okay how do I remove the chip from my capac and solder one of the above chips ................ and add memory etc................
You don't. You either wait for new SOHO routers from MikroTik or ask them kindly to support already existing devices with limited resources. But if they plan to drop support and no Wave2 driver then you will have to buy the new stuff anyway. I really really hope there's no planned obsolescence. I don't think MikroTik wanted us to dig deeper but they should have been a little more clear about Wave2 support for hAP ac2, cAP ac and wAP ac.
 
User avatar
Paternot
Forum Veteran
Forum Veteran
Posts: 953
Joined: Thu Jun 02, 2016 4:01 am
Location: Niterói / Brazil

Re: v7.1beta3 [development] is released!

Mon Dec 07, 2020 4:08 am

I really really hope there's no planned obsolescence. I don't think MikroTik wanted us to dig deeper but they should have been a little more clear about Wave2 support for hAP ac2, cAP ac and wAP ac.
Up until now I haven't seen planned obsolescence from Mikrotik: even devices discontinued more than 3 years ago still run the latest production version of RoS. Also, I don't remember any mention of wave2 on these devices You listed. Yes, looks like the hardware can do it - but I don't recall they been sold as wave2 capable (were they?).

Yes, it sucks. It would be much better if they could get the new driver. Absolutely. Mikrotik knows very well that ANY piece of code that we (the community) gets our hands on WILL be picked apart. Time and again we see this on the forum - and even Mikrotik employees answered these posts. So, no. I don't think Mikrotik hoped for secrecy - they know us better than this.
 
sdegler
just joined
Posts: 8
Joined: Sun Oct 11, 2020 8:54 am

Re: v7.1beta3 [development] is released!

Mon Dec 07, 2020 4:47 am

Had to roll back to beta2. Ospf v2 and route/redistribution is broken?

On beta2 my setup with pcc and multi-wan works but is flaky. Sometimes the route injects, and sometimes it doesn't.
Triggering dhcp release/renewals is often enough to get the route installed.

On beta3 my setup immediately and always generates an "opaque area" TE lsa, but it doesn't contain the default route information.

Is there any way I can debug route filtering and ospf route redistribution further ?
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v7.1beta3 [development] is released!

Mon Dec 07, 2020 5:10 am

It is hard to say whether it is due to the architecture or instead something related to the drivers or the particular configuration I have. The RB4011 is my main router at home so I am using a lot of features on it, I am not entirely surprised that I am encountering instability as a result. However, my hAP ac and Audience are both acting as pretty normal CAP devices managed by the RB4011 CAPsMAN. The hAP ac is stable, the Audience is not, even though their configurations are rather simple and virtually identical.
I was wrong, actually. My Audience DOES work on 7 beta 3, but I had to upgrade it to the final release of beta 3 and not the "early" release given out. The early release was crashing every hour or so and the final release is stable. I've also upgraded my RB4011 to the final beta 3 release. I didn't realize they changed anything other than the TILE architecture fixes. However, after the issues I was having, it was obvious that they changed a lot more in the final beta 3 version rather than just fixing the TILE architecture version.

OSPFv3 is still quite broken though - everything says "wrong checksum". OSPFv2 and BGP both seem fine.
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v7.1beta3 [development] is released!

Mon Dec 07, 2020 8:37 am

Also, I had hoped for MPLS to be added in this new beta. Do you expect to have MPLS support added before RouterOS 7 is released? Although it seems there are a few glitches here and there to work out, for the most part things are working in ROS 7 now. MPLS seems to be the biggest thing missing.
 
User avatar
raimondsp
MikroTik Support
MikroTik Support
Posts: 267
Joined: Mon Apr 27, 2020 10:14 am

Re: v7.1beta3 [development] is released!

Mon Dec 07, 2020 9:19 am

L3 hardware offloading is not working on my CRS309-1G-8S+IN. Setting l3hw=yes or no has no difference and the routing performance is only about 200Mbps.

We have identified the issue and are working on the fix. Meanwhile, please downgrade back to 7.1beta2 to use l3hw.
 
User avatar
bpwl
Forum Guru
Forum Guru
Posts: 2978
Joined: Mon Apr 08, 2019 1:16 am

Re: v7.1beta3 [development] is released!

Mon Dec 07, 2020 3:09 pm

It can be check by installing WinFi Lite from https://www.helge-keck.com/ in windows.
Thanks for that link @heidarren. WinFi Lite = Nice tool ! (Now I can trash inSIDDer, Netspot, Netsurveyor .... )
 
gdanov
Member Candidate
Member Candidate
Posts: 150
Joined: Thu Jan 17, 2019 1:10 pm

Re: v7.1beta3 [development] is released!

Mon Dec 07, 2020 3:10 pm

upgraded to this beta my RBM33G with LTE6 and 5Ghz wifi card and I'm very satisfied. The LTE card went missing and weird PPP interface showed up but after couple of restarts & lte firmware upgrade everything was back to normal.

I upgraded mostly because of wireguard and I'm writing to share how happy I am with it, this is what I've been needing for a while. So, good job and can't wait for the final release :)

Some rough edges as expected in beta, the only one that's worth mentioning for me is how the ip/routes looks and works. Searched the changelog for mention of that but found nothing. Could you please shed some light what's going on there — is this because the web UI is behind or something else?
 
santyx32
Member Candidate
Member Candidate
Posts: 215
Joined: Fri Oct 25, 2019 2:17 am

Re: v7.1beta3 [development] is released!

Mon Dec 07, 2020 4:28 pm

!) added new experimental wireless package "wifiwave2" for ARM devices with more than 256 MB of RAM (CLI only);
If you unpack the new wireless package you´ll see that there are many components which do not all belong to IPQ40xx chipset, so 16MB of ROM should be sufficient some day when the new wireless driver is optimized and repackaged if MikroTik wants to do so.
Also looking at a https://forum.openwrt.org/t/support-for ... 2/23333/44 there´s something like a "ath10k-ct-smallbuffers" which helps reducing the amount of RAM being needed.Nobody is stopping MikroTik developers to use the same technique to improve needed RAM requirements.
Yep, OpenWrt built with ath10k-ct-smallbuffers driver works flawlessly on 16/128mb Wave2 devices.

On my ac2 under heavy WiFi load free RAM can go as low as 30mb but I think Mikrotik can further optimize that since they're the original manufacturer and free disk space is 8mb.
 
sdegler
just joined
Posts: 8
Joined: Sun Oct 11, 2020 8:54 am

Re: v7.1beta3 [development] is released!

Mon Dec 07, 2020 6:09 pm

Had to roll back to beta2. Ospf v2 and route/redistribution is broken?

On beta2 my setup with pcc and multi-wan works but is flaky. Sometimes the route injects, and sometimes it doesn't.
Triggering dhcp release/renewals is often enough to get the route installed.

On beta3 my setup immediately and always generates an "opaque area" TE lsa, but it doesn't contain the default route information.

Is there any way I can debug route filtering and ospf route redistribution further ?
It turns out the Opaque LSA's are actually for MPLS TE, which means there's at least some life in the MPLS stack.
So its just that my efforts to inject the route are failing.
In other ospf implementations, you could declare both interfaces and subnetworks as belonging to OSPF.
All I see here is the interface templates. If I specify an interface template with just a network and no interface, is that equivalent to a network statement?
also if I specify the import statement wrong it seems to hang the routing engine?
 
WeWiNet
Long time Member
Long time Member
Posts: 591
Joined: Thu Sep 27, 2018 4:11 pm

Re: v7.1beta3 [development] is released!

Mon Dec 07, 2020 7:01 pm

On RB4011, after boot following error in the log:
error while running customized default configuration script: expected end of command (line 1310 column 53)
Only thing I did is create 5Ghz Wifi radio as it is described in the Wiki:
/interface wifiwave2
add disabled=no mac-address=B6:64:D4:AB:29:13 name=wifi1 security.authentication-types=wpa2-psk,wpa3-psk \
.passphrase=password ssid=MikroTik
Also, can Mikrotik support please post a setup example for dual band AP config with the wave2 package?
On RB4011 I can create one radio interface with the 4x4 5Ghz radio, but are unable (or have not found yet) how
to create/enable the 2.4G radio card...?

PS: Would be good to create maybe new Forum section for Wave2 questions ...?
 
santyx32
Member Candidate
Member Candidate
Posts: 215
Joined: Fri Oct 25, 2019 2:17 am

Re: v7.1beta3 [development] is released!

Mon Dec 07, 2020 7:21 pm

On RB4011, after boot following error in the log:
error while running customized default configuration script: expected end of command (line 1310 column 53)
Only thing I did is create 5Ghz Wifi radio as it is described in the Wiki:
/interface wifiwave2
add disabled=no mac-address=B6:64:D4:AB:29:13 name=wifi1 security.authentication-types=wpa2-psk,wpa3-psk \
.passphrase=password ssid=MikroTik
Also, can Mikrotik support please post a setup example for dual band AP config with the wave2 package?
On RB4011 I can create one radio interface with the 4x4 5Ghz radio, but are unable (or have not found yet) how
to create/enable the 2.4G radio card...?

PS: Would be good to create maybe new Forum section for Wave2 questions ...?
2.4ghz it's not supported on RB4011 with the new driver
 
WeWiNet
Long time Member
Long time Member
Posts: 591
Joined: Thu Sep 27, 2018 4:11 pm

Re: v7.1beta3 [development] is released!

Mon Dec 07, 2020 7:54 pm

2.4ghz it's not supported on RB4011 with the new driver
What on the Audience? Will you have the two 5Ghz Radio available to play around?
 
User avatar
Znevna
Forum Guru
Forum Guru
Posts: 1347
Joined: Mon Sep 23, 2019 1:04 pm

Re: v7.1beta3 [development] is released!

Mon Dec 07, 2020 8:46 pm

[...]
Also, can Mikrotik support please post a setup example for dual band AP config with the wave2 package?
On RB4011 I can create one radio interface with the 4x4 5Ghz radio, but are unable (or have not found yet) how
to create/enable the 2.4G radio card...?
PS: Would be good to create maybe new Forum section for Wave2 questions ...?
Why another forum section if nobody bothers to read the help page for it?
https://help.mikrotik.com/docs/display/ROS/WifiWave2
**Note that the 2.4GHz wireless interface on the RB4011iGS+5HacQ2HnD is not compatible with the wifiwave2 package. It will not be usable with the package installed.
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v7.1beta3 [development] is released!

Mon Dec 07, 2020 9:32 pm

What on the Audience? Will you have the two 5Ghz Radio available to play around?
Yes, I tested it on my Audience and all three radios appear. However, there is no support for bridging as of yet, so using the second radio as an uplink as it was designed is not really possible. You would need to connect the AP with an ethernet cable.
 
jrpaz
Frequent Visitor
Frequent Visitor
Posts: 89
Joined: Wed Jun 05, 2013 5:54 am

Re: v7.1beta3 [development] is released!

Tue Dec 08, 2020 1:53 am

Can confirm Wave2 is twice as fast vs the regular drivers on the RB4011.

However, it's not stable enough to run tests at least with my iMac and Macbook pro.
 
User avatar
DanielJB
Frequent Visitor
Frequent Visitor
Posts: 82
Joined: Mon May 27, 2013 3:05 pm

Re: v7.1beta3 [development] is released!

Tue Dec 08, 2020 4:48 am

Fantastic work Mikrotik! CAKE and Wave2 are both a big deal; I am very excited.

Looking forward to Mikrotik adding testcases to your automated testing, so your users can detect only more complex cases. The resulting user feedback would then help Mikrotik progress their automated regression testing and tighten the loop.

Netinstalling 7.1beta3 on a hAP ac2 (128MB), default config enabled, I found:
1. no default configuration, error messages seen when Winboxing in and opening terminal (likely from default configuration script)
2. /export hangs (support reports they have reproduced this)
3. configuration is lost when rebooting

Many thanks guys; you fine work is appreciated!
- Daniel
 
anuser
Long time Member
Long time Member
Posts: 601
Joined: Sat Nov 29, 2014 7:27 pm

Re: v7.1beta3 [development] is released!

Tue Dec 08, 2020 8:34 pm

!) added new experimental wireless package "wifiwave2" for ARM devices with more than 256 MB of RAM (CLI only);
I do have a thesis about why MiikroTik doesn´t release those new driver for existing low cost IPQ40xx access points. It´s not about ROM or RAM size, it´s about license costs
The old wireless driver is available on every device. This driver is written by MikroTik itself. Have you looked at the unpacked wifiwave2 package (www.7-zip.org works, btw.)? Those drivers, those config files, those modules look like they were completely done by Qualcomm, i.e. the chipset vendor. No opensource driver from the linux kernel, the original one from the vendor itself which explains the way better benchmark results from some of you. I assume Qualcomm charges for each sold device. Therefore the driver will only be available on new MikroTik devices, those with higher pricing. And MikroTik as vendor doesn´t want to be charged by Qualcomm for all of those million devices MikroTik sold in the past.

@MikroTik If this is correct, please let us buy inexpensive licenses for our older devices. I don´t know what MikroTik pays to Qualcomm for each device: Is it 5$ or 10$?
 
User avatar
Larsa
Forum Guru
Forum Guru
Posts: 1025
Joined: Sat Aug 29, 2015 7:40 pm
Location: The North Pole, Santa's Workshop

Re: v7.1beta3 [development] is released!

Tue Dec 08, 2020 9:26 pm

Normally you don't pay license costs for the template device drivers but for the chip (and sometimes different features) which can be either flat fee but for the most part volume based. But you do need to buy and licence a number of development kits (boards) that includes tech and pre-productions support such as best practice för PCB and antenna constructions.
 
infabo
Long time Member
Long time Member
Posts: 586
Joined: Thu Nov 12, 2020 12:07 pm

Re: v7.1beta3 [development] is released!

Tue Dec 08, 2020 9:29 pm

On Chateau12 it looks like L2TP Server broken - at least I am unable to connect and can't see any logs even if I enable l2tp logging. Firewall filter rules seem OK - but only PPTP works. Can anyone confirm?
 
nellson
newbie
Posts: 27
Joined: Wed Nov 06, 2019 9:10 am

Re: v7.1beta3 [development] is released!

Tue Dec 08, 2020 9:38 pm

!) added new experimental wireless package "wifiwave2" for ARM devices with more than 256 MB of RAM (CLI only);
I do have a thesis about why MiikroTik doesn´t release those new driver for existing low cost IPQ40xx access points. It´s not about ROM or RAM size, it´s about license costs
The old wireless driver is available on every device. This driver is written by MikroTik itself. Have you looked at the unpacked wifiwave2 package (www.7-zip.org works, btw.)? Those drivers, those config files, those modules look like they were completely done by Qualcomm, i.e. the chipset vendor. No opensource driver from the linux kernel, the original one from the vendor itself which explains the way better benchmark results from some of you. I assume Qualcomm charges for each sold device. Therefore the driver will only be available on new MikroTik devices, those with higher pricing. And MikroTik as vendor doesn´t want to be charged by Qualcomm for all of those million devices MikroTik sold in the past.

@MikroTik If this is correct, please let us buy inexpensive licenses for our older devices. I don´t know what MikroTik pays to Qualcomm for each device: Is it 5$ or 10$?
I don't thinks that's the case, it's merely a space issue. I would happily pay for an upgrade license too, if it were the case.
 
anuser
Long time Member
Long time Member
Posts: 601
Joined: Sat Nov 29, 2014 7:27 pm

Re: v7.1beta3 [development] is released!

Tue Dec 08, 2020 9:58 pm

I don't thinks that's the case, it's merely a space issue. I would happily pay for an upgrade license too, if it were the case.
I don´t know about the modules folders, but most of those chipset folders could be abandoned I think:
Image
 
arm920t
Frequent Visitor
Frequent Visitor
Posts: 61
Joined: Sat Aug 03, 2019 8:02 am

Re: v7.1beta3 [development] is released!

Wed Dec 09, 2020 5:42 am

Is there any information about 802.11 K V R ????
 
chubbs596
Frequent Visitor
Frequent Visitor
Posts: 90
Joined: Fri Dec 06, 2013 6:07 pm

Re: v7.1beta3 [development] is released!

Wed Dec 09, 2020 10:46 am

Hi,

This build is not working on 2004s. High packetloss. Same reported on last 6.48beta.

/Mikael
I have seen the same issue
 
jakuro
just joined
Posts: 1
Joined: Wed Dec 09, 2020 10:41 am

Re: v7.1beta3 [development] is released!

Wed Dec 09, 2020 10:48 am

Hi,

I did upgrade from stable routeros to this beta for wireguard support. It has massive memory usage and i cannot find what's a reaon.
Stable has usage about 60Mb and this version is just raising up with no limits.

I have only wifi running and few static networks. Any idea? I love wireguard setup but sadly 256Mb of ram looks is not enough for this beta version.
mikrotik_memory.png
You do not have the required permissions to view the files attached to this post.
Last edited by jakuro on Wed Dec 09, 2020 4:25 pm, edited 1 time in total.
 
User avatar
StubArea51
Trainer
Trainer
Posts: 1739
Joined: Fri Aug 10, 2012 6:46 am
Location: stubarea51.net
Contact:

Re: v7.1beta3 [development] is released!

Wed Dec 09, 2020 3:54 pm

Hi IPANet, I am in awe of your network designs........... I don't know or think I will ever need fz-codel or cake functionality but I can guarantee you I will probably be eating cake when I read your posts demonstrating such features !! :-)

Thanks for the feedback, I appreciate it :-)

We'll definitely be doing some development and testing work on shaping with fq_codel and cake
 
User avatar
dgnevans
Member
Member
Posts: 469
Joined: Fri Mar 08, 2013 11:24 am
Location: Zimbabwe
Contact:

Re: v7.1beta3 [development] is released!

Wed Dec 09, 2020 4:26 pm

After upgrade, all my OSPF settings disappeared (except of Instance)

And I cannot change it or create a new instance via WinBox setting "version": it saus, incorrect version. If I add a new instance via Terminal, WinBox shows "unknown" under Version
Ospf not working same issue as Chupaka. downgrading to beta2 to resolve. Beta 2 was straight forward to get OSPF working either.
 
r00t
Long time Member
Long time Member
Posts: 672
Joined: Tue Nov 28, 2017 2:14 am

Re: v7.1beta3 [development] is released!

Wed Dec 09, 2020 7:40 pm

Stable has usage about 60Mb and this version is just raising up with no limits.
That looks like a memory leak. When it gets really high, make supout file and send it to the support. They should be able to find the culprit and fix it.
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v7.1beta3 [development] is released!

Thu Dec 10, 2020 12:27 am

Ospf not working same issue as Chupaka. downgrading to beta2 to resolve. Beta 2 was straight forward to get OSPF working either.
OSPFv2 does work, but it doesn't convert the beta 2 config to the new beta 3 style, so any lines of config that have had syntax changes will disappear completely when you upgrade. This is not really a bug - they simply did not bother to write the code to automate the syntax changes. Before upgrading from beta 2 to beta 3 you should delete all OSPF and BGP config and then reconfigure it manually in beta 3. If you do not do that, you can end up with some messed up OSPF/BGP config in beta 3 where some lines are partially there but not really.

OSPFv2 works perfectly in beta 3. OSPFv3 is not working.
Last edited by mducharme on Thu Dec 10, 2020 1:00 am, edited 1 time in total.
 
infabo
Long time Member
Long time Member
Posts: 586
Joined: Thu Nov 12, 2020 12:07 pm

Re: v7.1beta3 [development] is released!

Thu Dec 10, 2020 12:50 am

On Chateau12 it looks like L2TP Server broken - at least I am unable to connect and can't see any logs even if I enable l2tp logging. Firewall filter rules seem OK - but only PPTP works. Can anyone confirm?
okay - seems to be an android issue. works on another device.
 
lelmus
newbie
Posts: 28
Joined: Wed Oct 17, 2012 5:50 am

Re: v7.1beta3 [development] is released!

Thu Dec 10, 2020 1:59 am

Got a question regarding 2.4GHz wireless interface on the RB4011iGS+5HacQ2HnD and Wave2.

Correct me if I got this wrong, is the issue with 2.4GHz not working because it’s shared with the 4 antennas that’s used by the 5GHz and not separate? If so, I’m not sure if this will ever work unless you separate the antennas. The internal 2.4GHz PCIe card can be connected to separate antennas via the MMCX or U.FL pigtails. If I add new antennas to the 2.GHz PCIe card, can you enable the 2.4GHz?
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v7.1beta3 [development] is released!

Thu Dec 10, 2020 2:01 am

Correct me if I got this wrong, is the issue with 2.4GHz not working because it’s shared with the 4 antennas that’s used by the 5GHz and not separate?
No, it is because it uses an Atheros chip and the new WifiWave2 currently only includes drivers for Qualcomm (QCAxxxx and IPQxxxx) chips. The 5GHz in the 4011 is Qualcomm.
 
User avatar
DanielJB
Frequent Visitor
Frequent Visitor
Posts: 82
Joined: Mon May 27, 2013 3:05 pm

Re: v7.1beta3 [development] is released!

Thu Dec 10, 2020 4:51 am

I love the new features. Netinstalled routeros 7.1beta3 to an Audience LTE6 and I haven't had any downtime with it acting as a Wave2 WPA2/3 AP with CAKE traffic shaping :)

With Wave2, I find one processor core saturates at ~300Mb/s over WiFi:
/tool/profile 
Columns: NAME, USAGE
  NAME          USAGE
  ethernet      0.8% 
  console       0.1% 
  ssh           0%   
  networking    27%  
  management    0.2% 
  profiling     0%   
  bridging      1.6% 
  unclassified  6.6% 
  total         36.3%
-- [Q quit|D dump|C-z pause]

Using CAKE, I find there is likely an incorrect Mb to MB conversion, so eg 10Mbps actually limits at 80Mbps:
/queue/type set 2 kind=cake cake-bandwidth=10Mbps cake-flowmode=dual-dsthost

We also see 'autorate-ingress' can't be set (though it likely can be set with tc internally):
/queue/type set 2 kind=cake cake-bandwidth=autorate-ingress
value of cake-bandwidth contains invalid trailing characters

Though packets are queued during load, none are reported:
/queue/monitor
  queued-packets: 0
    queued-bytes: 0
-- [Q quit|D dump|C-z pause]

Finally, some of the issues reported (crashing/rebooting) may relate to allocation failure; Mikrotik can use the Linux kernel fault injection mechanism to detect and address such issues quicker:
https://www.kernel.org/doc/html/latest/ ... ction.html

UPDATE

After a couple of days of uptime, I find the AP rebooting ~20s after coming up - at this time the autosupout mechanism was likely running to capture state from the previous boot, possibly triggering a race condition with the wifiwave2 interfaces coming up and rebooting again, looping. I was able to quickly SSH in, disable the wifiwave2 interfaces, let the autosupout mech complete and sent the file to Mikrotik, though this will obviously miss the original kernel crash that triggered the cascade of events.

UPDATE 2

Disabling the wifiwave2 package, I see every ~1-2 days "system,error,critical router was rebooted without proper shutdown by watchdog timer" on an Audience running as only an AP with CAKE, all 3 WiFi interfaces enables, 11 clients.

- Daniel J Blueman
Last edited by DanielJB on Thu Dec 17, 2020 5:20 am, edited 2 times in total.
 
WeWiNet
Long time Member
Long time Member
Posts: 591
Joined: Thu Sep 27, 2018 4:11 pm

Re: v7.1beta3 [development] is released!

Thu Dec 10, 2020 10:02 am

V7.1beta3 on "wap R ac" with EP06.

Was running nice for ~3 days (just one kernel failure).
Now it entered into a boot loop.
This started to happen when trying to connect to its Wifi with a device that had previously DHCP issues on 7beta2.

Disabled the Wifi interface, and boot loop is stopped!!!
This is happening with the "normal" Wifi package (not wave2).

V71beta3 on Chateau:
Was rock solid with 7.0.1 (October compile date).
Now unstable, loosing connection to Chateau over ethernet cable every 30 minutes or so...
--> How can I down grade again to 7.0.1 to have it working again?
 
User avatar
dreamind
just joined
Posts: 10
Joined: Thu Apr 18, 2013 9:15 pm
Location: Germany
Contact:

Re: v7.1beta3 [development] is released!

Thu Dec 10, 2020 10:19 am

V7.1beta3 on RB3011

I tried already multiple times to update my RB3011UiAS to 7.1beta3.
Tried copying the file with scp to the routerboard and also using:
/system/package/update/install
Both ways the display just shows "rebooting" but the device is locked up. Once I power cycle it, it boots to the currently installed 7.1beta2.
 
Guntis
MikroTik Support
MikroTik Support
Posts: 153
Joined: Fri Jul 20, 2018 1:40 pm

Re: v7.1beta3 [development] is released!

Thu Dec 10, 2020 1:08 pm

WeWiNet Could you please contact support regarding the wAP R ac boot loop, while having wireless enabled?
 
edmondfm
just joined
Posts: 5
Joined: Sat Jan 30, 2016 2:01 am

Re: v7.1beta3 [development] is released!

Thu Dec 10, 2020 4:19 pm

I upgraded CCR2004 and reconfigure OSPF but i do not get a link, all i get is Exchange, ExStart and no Full link. Is there something i am missing?
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v7.1beta3 [development] is released!

Thu Dec 10, 2020 10:41 pm

I upgraded CCR2004 and reconfigure OSPF but i do not get a link, all i get is Exchange, ExStart and no Full link. Is there something i am missing?
Impossible to tell without seeing your setup, but I can confirm that OSPFv2 works fine for me in beta 3. OSPFv3 is not working.
 
chubbs596
Frequent Visitor
Frequent Visitor
Posts: 90
Joined: Fri Dec 06, 2013 6:07 pm

Re: v7.1beta3 [development] is released!

Fri Dec 11, 2020 10:43 am

Hi Guys,

Has anyone have experience or converted /routing filter from v6 to V7.1beta3 ?

With the upgrade from v6 most other BGP config is being converted , Looks like there is extensive changes in the routing filters,
 
pe1chl
Forum Guru
Forum Guru
Posts: 10183
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.1beta3 [development] is released!

Fri Dec 11, 2020 11:26 am

Have you read all previous replies, in particular #53 ??
 
chubbs596
Frequent Visitor
Frequent Visitor
Posts: 90
Joined: Fri Dec 06, 2013 6:07 pm

Re: v7.1beta3 [development] is released!

Fri Dec 11, 2020 12:36 pm

Have you read all previous replies, in particular #53 ??
Hi, I have seen this post thanks,
that is why Im asking if someone has maybe written some clever script or something to convert the route filters
 
heidarren
Member Candidate
Member Candidate
Posts: 136
Joined: Mon Aug 05, 2019 9:56 am

Re: v7.1beta3 [development] is released!

Fri Dec 11, 2020 8:47 pm

It can be check by installing WinFi Lite from https://www.helge-keck.com/ in windows.
Thanks for that link @heidarren. WinFi Lite = Nice tool ! (Now I can trash inSIDDer, Netspot, Netsurveyor .... )
You're welcome, can you please check if 802.11k/v/r is available on v7.1b3?
 
cklee234
newbie
Posts: 44
Joined: Tue Sep 29, 2020 6:49 am

Re: v7.1beta3 [development] is released!

Sat Dec 12, 2020 12:43 am

My x86 could be upgraded from beta 2 to beta 3. However, I could not able to login from the winbox via lan ip or Mac address. After I hook up the hdmi cable to check the console message, I am able to login via console. internally seems working. The wan side login but not lan ip login via winbox is ok.

Downgrade to 6.47.8 brought me to x86 but return to v7 beta 3 gave me x86_64

Strange,

Need more efforts to fix the bugs.
 
HamedPC2
just joined
Posts: 2
Joined: Sat Sep 21, 2019 2:00 pm

Re: v7.1beta3 [development] is released!

Sun Dec 13, 2020 10:48 pm

Approximately on what date will version 7 be finalized?
 
User avatar
mkx
Forum Guru
Forum Guru
Posts: 11381
Joined: Thu Mar 03, 2016 10:23 pm

Re: v7.1beta3 [development] is released!

Mon Dec 14, 2020 10:29 am

Approximately on what date will version 7 be finalized?

Your guess is as good as anyone's. I'm not sure MT devs have any firm deadline.
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: v7.1beta3 [development] is released!

Mon Dec 14, 2020 11:43 am

Approximately in 2020s
 
User avatar
SiB
Forum Guru
Forum Guru
Posts: 1888
Joined: Sun Jan 06, 2013 11:19 pm
Location: Poland

Re: v7.1beta3 [development] is released!

Mon Dec 14, 2020 12:18 pm

I think the 21st century :)
 
colin
Frequent Visitor
Frequent Visitor
Posts: 74
Joined: Mon May 11, 2015 11:11 am

Re: v7.1beta3 [development] is released!

Mon Dec 14, 2020 3:10 pm

Which features are missing in your opinion?
Macvlan feature missing
+1
 
cenizass
just joined
Posts: 6
Joined: Mon Dec 14, 2020 7:01 pm

Re: v7.1beta3 [development] is released!

Mon Dec 14, 2020 7:04 pm

Hello! It is not clear to me if wave2 will finally reach my mikrotik rb4011. They said they were experimental packages and that old devices would not be supported. I misunderstood?

greetings and thanks
Fernando
Last edited by cenizass on Mon Dec 14, 2020 8:49 pm, edited 1 time in total.
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v7.1beta3 [development] is released!

Tue Dec 15, 2020 5:58 am

Hello! It is not clear to me if wave2 will finally reach my mikrotik rb4011. They said they were experimental packages and that old devices would not be supported. I misunderstood?
Yes, I think this is mostly their beta testing for WiFi 6 (802.11ax). However, since the current wave2 beta test package supports the 4011 and the audience and the hap ac3, I would suspect the final version will continue to support those devices.
 
babelmonk
just joined
Posts: 4
Joined: Sun Nov 22, 2020 7:02 pm

Re: v7.1beta3 [development] is released!

Tue Dec 15, 2020 1:00 pm

Has anyone seen hangs on export? Something to do with /routing section I think.

Last lines in a .in_progress file:
/ipv6 nd
set [ find default=yes ] disabled=yes
add disabled=yes dns=XXX hop-limit=64 interface=home-admin \
    mtu=1500
add disabled=yes dns=XXX hop-limit=64 interface=home-lan \
    mtu=1500
add advertise-dns=no disabled=yes hop-limit=64 interface=home-guest mtu=1500
add advertise-dns=no disabled=yes hop-limit=64 interface=home-phones mtu=1500
#error exporting /routing/bfd/authentication
 
pe1chl
Forum Guru
Forum Guru
Posts: 10183
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.1beta3 [development] is released!

Tue Dec 15, 2020 4:03 pm

Please read earlier items in the topic before you ask...
 
aboiles
Frequent Visitor
Frequent Visitor
Posts: 56
Joined: Sat Nov 07, 2015 6:52 pm

Re: v7.1beta3 [development] is released!

Tue Dec 15, 2020 5:05 pm

On the subject of export-
On my RB4011 it does complete, it just takes an average of 21 minutes.
The only errors on the export are:
#error exporting /routing/bfd/authentication
#error exporting /routing/bfd/configuration
But export terse compact file=$fileName does finally complete.
 
ivantirado
just joined
Posts: 20
Joined: Sun May 12, 2019 4:58 am

Re: v7.1beta3 [development] is released!

Wed Dec 16, 2020 7:33 am

IPv6 stopped forwarding suddenly. Reboots didn't fix, neither did release/renew of the IPv6 DHCPv6 from the ISP. I checked that from the router I could ping outside IP's on IPv6, I could ping an internal host via IPv6, and viceversa, I could ping the router (even another router interface) from an internal host via IPv6... but nothing would make it work to ping or access anything on the IPv6 internet from an internal host. I couldn't even see the packets in torch.

Since I couldn't make it work, I went back to 6.x (latest stable).

I'll give it another shot later, having fq_codel was a great improvement :)
 
techlord
Frequent Visitor
Frequent Visitor
Posts: 58
Joined: Mon Nov 18, 2019 4:33 pm

Re: v7.1beta3 [development] is released!

Wed Dec 16, 2020 11:25 am

RouterOS version 7.1beta3 has been released in public "development" channel!

What's new in 7.1beta3 (2020-Dec-02 15:59):

!) added new experimental wireless package "wifiwave2" for ARM devices with more than 256 MB of RAM (CLI only);
- big thanks to Mikrotik for working on this
Now make the people worship you by developing an "wifiwave2_lite" for IPQ-4018 with 128MB memory.
 
User avatar
sszbv
Trainer
Trainer
Posts: 10
Joined: Sun Oct 07, 2012 11:47 am
Contact:

Re: v7.1beta3 [development] is released!

Wed Dec 16, 2020 12:09 pm

Testing wifiwave2 on hAP ac3:

Very interesting to see the new way of configuring wifi interfaces.

It worked for a few hours, speed was really good, better than regular wifi package.
Then it started rebooting, kernel errors during boot, reboot, reboot etc
Had to reset the config to get it up and running again.

edit: I'll add a bootscript that disables the wifi, hopefully that prevents a reboot loop

Will test some more!
Thanks for sharing this test version.
 
anuser
Long time Member
Long time Member
Posts: 601
Joined: Sat Nov 29, 2014 7:27 pm

Re: v7.1beta3 [development] is released!

Wed Dec 16, 2020 8:50 pm

You're welcome, can you please check if 802.11k/v/r is available on v7.1b3?
Just tested on RB4011. (I cannot find any option for enabling or disabling those parameters at all). 802.11v and 802.11w is enabled with WPA2 PSK. I haven´t tried WPA2 Enterprise, yet.
 
faragalla
just joined
Posts: 10
Joined: Wed Jan 28, 2015 9:11 pm

Re: v7.1beta3 [development] is released!

Thu Dec 17, 2020 5:39 pm

I am trying 7.1beta3 so I can use Winguard and for the most part things are working well. There is however one MAJOR problem I keep having with multiple routerboards. Sometimes when I make configuration changes and reboot the router or restore the router to a previously saved configuration, the router reboots, but loses all configuration and has an IP of 0.0.0.0. This includes even making the most minor of changes. This obviously makes remote configuration impossible as when this happens the router loses internet connectivity and I have no way of putting it online unless someone physically goes there, factory resets it and configures it. Has anyone else experienced this issue?
 
notToNew
Member Candidate
Member Candidate
Posts: 174
Joined: Fri Feb 19, 2016 3:15 pm

Re: v7.1beta3 [development] is released!

Fri Dec 18, 2020 4:49 am

same here as reported earlier. Updates LTE6 Router to this beta, ended in a bootloop.

read somewhere that simpleque causes this. disabled alls simpleque rules and voila, bootloop is gone.
 
User avatar
kiler129
Member
Member
Posts: 352
Joined: Tue Mar 31, 2015 4:32 pm
Location: IL, USA
Contact:

Re: v7.1beta3 [development] is released!

Fri Dec 18, 2020 7:16 am

In case someone is experiencing a problem where "beta3" seems to kill some WG tunnels with the following error on iOS/iPadOS/macOS:
2020-12-17 23.13.42.jpg
However, this is not a problem with ROS but actually a bug in WireGuard's client apps: https://www.mail-archive.com/wireguard@ ... 05806.html
When you test make sure you have a client version of at least 1.0.11 or use "DNS" in the client interface configuration.


----------------------------------------------------------------------------------------------------
Edit

Something strange is happening when 7.1beta3 is used as a client in WG and the remote peer uses a domain in "endpoint-address". The tunnel will appear dead (0bps, 0pps) after reboot. Disabling the interface and enabling it again does nothing. Attempting ping to that hostname from the router followed by deactivation & reactivation of the wg interface fixes the problem.
You do not have the required permissions to view the files attached to this post.
 
infabo
Long time Member
Long time Member
Posts: 586
Joined: Thu Nov 12, 2020 12:07 pm

Re: v7.1beta3 [development] is released!

Sat Dec 19, 2020 5:25 pm

One specific wifi-client is not able to connect to the Chateau LTE12 accesspoint. It's a TP-Link TL-MR3020. It can see the wifi SSID but it won't connect. It connects fine to any other AP (like Pixel hotspot or Linksys WRT3200 running OpenWRT). On the Mikrotik-side I can't see any wifi client registration - just nothing. Anyone else with similar issues?
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v7.1beta3 [development] is released!

Sun Dec 20, 2020 12:03 am

Something strange is happening when 7.1beta3 is used as a client in WG and the remote peer uses a domain in "endpoint-address". The tunnel will appear dead (0bps, 0pps) after reboot. Disabling the interface and enabling it again does nothing. Attempting ping to that hostname from the router followed by deactivation & reactivation of the wg interface fixes the problem.
As an idea for a temporary workaround for this issue, try creating an address list with the endpoint address DNS entry in it. You shouldn't have to use the address-list for anything - simply creating one and adding that might force the router to resolve that name on boot which might result in the wireguard interface coming up properly.
 
MarcSN
just joined
Posts: 15
Joined: Wed Jul 01, 2020 7:18 pm

Re: v7.1beta3 [development] is released!

Mon Dec 21, 2020 1:07 am

*) crs3xx - added initial Bridge Port Extender support (CLI only);
*) crs3xx - added initial Controlling Bridge support for CRS317, CRS309, CRS312, CRS326-24S+2Q+ and CRS354 devices (CLI only);
will this come to v7?
 
User avatar
nz_monkey
Forum Guru
Forum Guru
Posts: 2095
Joined: Mon Jan 14, 2008 1:53 pm
Location: Over the Rainbow
Contact:

Re: v7.1beta3 [development] is released!

Mon Dec 21, 2020 9:47 am

Is anyone else seeing port-flapping with 7.1b3 on RB3011's ?
 
msatter
Forum Guru
Forum Guru
Posts: 2897
Joined: Tue Feb 18, 2014 12:56 am
Location: Netherlands / Nīderlande

Re: v7.1beta3 [development] is released!

Mon Dec 21, 2020 11:51 am

On the subject of export-
On my RB4011 it does complete, it just takes an average of 21 minutes.
The only errors on the export are:
#error exporting /routing/bfd/authentication
#error exporting /routing/bfd/configuration
But export terse compact file=$fileName does finally complete.
See the answer MRZ gave: viewtopic.php?f=1&t=169992&sid=be4de264 ... 04#p832375
 
Borizo
newbie
Posts: 40
Joined: Thu Oct 28, 2010 4:38 pm

Re: v7.1beta3 [development] is released!

Mon Dec 21, 2020 8:15 pm

Hangup running code:
/metarouter add name=test1
Am I miss something?
 
ivanxx
just joined
Posts: 2
Joined: Sun May 11, 2014 12:22 am

Re: v7.1beta3 [development] is released!

Mon Dec 21, 2020 10:22 pm

I found Hairpin NAT stopped working after updating from 7.1beta2 to beta3. Any idea on how to get it back?
Looks like packets are not being masqueraded again after being dstnated...
 
bergonz
just joined
Posts: 12
Joined: Fri Oct 16, 2015 3:01 pm

Re: v7.1beta3 [development] is released!

Tue Dec 22, 2020 4:44 pm

While trying to troubleshoot an issue with a chateau, I updgraded it to 7.1beta3 and then cleaned it up with:
/system/reset-configuration no-defaults=yes keep-users=no
After the reboot, it cannot complete the "/export" command, getting stuck just after the "/ip vrf" section.

I retried with
/system/reset-configuration
to restore the factory default config, and after that the /export gets stuck a bit later, just after the "/ipv6 firewall filter" section.

It seems to me that the troublesome section is "/routing/bfd", because "/routing/bfd/export" always gets stuck. I am of course not using nor configuring bfd.

This is not present in 7.1beta2, where the "/export" succeeds.

Regards,
Bergonz
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7038
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v7.1beta3 [development] is released!

Tue Dec 22, 2020 5:00 pm

Look a few posts above
 
gtj0
just joined
Posts: 15
Joined: Wed Sep 23, 2020 8:08 pm

Re: v7.1beta3 [development] is released!

Tue Dec 22, 2020 6:25 pm

CCR-1009 (tile) went into boot loop after upgrade from 3.48beta58 to 7.1beta3. I'm not exactly sure what triggers the reset but I was just barely able to get a supout which is on its way to MT support. Unfortunately, I couldn't get it to stay up long enough to downgrade but also unfortunately, netinstall simply will not answer the etherboot requests. I guess that's my problem to figure out.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10183
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.1beta3 [development] is released!

Tue Dec 22, 2020 6:34 pm

You should have partitioned the router (2 partitions) before diving into beta version installation.
Then you can always go back to the working partition, or the router will even do that by itself when the newly updated partition fails to boot.
 
gtj0
just joined
Posts: 15
Joined: Wed Sep 23, 2020 8:08 pm

Re: v7.1beta3 [development] is released!

Tue Dec 22, 2020 7:19 pm

You should have partitioned the router (2 partitions) before diving into beta version installation.
Then you can always go back to the working partition, or the router will even do that by itself when the newly updated partition fails to boot.
Yeah probably should have but all of the other devices upgraded fine so I didn't think. I'll partition this one before I do anything else with it.
 
notToNew
Member Candidate
Member Candidate
Posts: 174
Joined: Fri Feb 19, 2016 3:15 pm

Re: v7.1beta3 [development] is released!

Tue Dec 22, 2020 7:34 pm

CCR-1009 (tile) went into boot loop after upgrade from 3.48beta58 to 7.1beta3. I'm not exactly sure what triggers the reset but I was just barely able to get a supout which is on its way to MT support. Unfortunately, I couldn't get it to stay up long enough to downgrade but also unfortunately, netinstall simply will not answer the etherboot requests. I guess that's my problem to figure out.
try disabling simple queues
 
gtj0
just joined
Posts: 15
Joined: Wed Sep 23, 2020 8:08 pm

Re: v7.1beta3 [development] is released!

Wed Dec 23, 2020 1:23 am

try disabling simple queues
I finally managed to get the device partitioned and get 6.48beta58 running partition 0 and 7.1beta3 installed on partition 1. With the exact same config, 7.1beta3 reboots as soon as traffic starts passing through. No simple queues enabled.
 
gtj0
just joined
Posts: 15
Joined: Wed Sep 23, 2020 8:08 pm

Re: v7.1beta3 [development] is released!

Wed Dec 23, 2020 3:43 pm

Got a response from support... IGMP snooping seems to be the culprit.

If you've got a device in a boot loop, disconnect everything except a management machine (or use the serial console) and turn IGMP snooping off on your bridges and see if that helps.
 
r00t
Long time Member
Long time Member
Posts: 672
Joined: Tue Nov 28, 2017 2:14 am

Re: v7.1beta3 [development] is released!

Wed Dec 23, 2020 6:57 pm

I really hope there will be new v7 beta released soon (say in ~1 month) that fixes all these small bugs... it would be rather bad having to wait another 6 months for next version.
Right now this beta is too broken to be even tested properly...
 
User avatar
Nevon
Frequent Visitor
Frequent Visitor
Posts: 72
Joined: Thu Sep 05, 2013 6:06 pm
Location: Sweden
Contact:

Re: v7.1beta3 [development] is released!

Thu Dec 24, 2020 12:22 am

Lost connectivity between my CCR1072 with 6.46.8 and CCR2004 7.1b3... SFP+ flapping.. and no neigb. no IP or IPv6... worked with 7.1b2...
Tip?
 
User avatar
Nevon
Frequent Visitor
Frequent Visitor
Posts: 72
Joined: Thu Sep 05, 2013 6:06 pm
Location: Sweden
Contact:

Re: v7.1beta3 [development] is released!

Thu Dec 24, 2020 12:23 am

Is anyone else seeing port-flapping with 7.1b3 on RB3011's ?
Flapping on my CCR2004
 
kidtienk
just joined
Posts: 5
Joined: Thu Dec 24, 2020 7:53 am

Re: v7.1beta3 [development] is released!

Thu Dec 24, 2020 7:55 am

ipip tunnel still not working wihout disable keepalive
 
User avatar
kiler129
Member
Member
Posts: 352
Joined: Tue Mar 31, 2015 4:32 pm
Location: IL, USA
Contact:

Re: v7.1beta3 [development] is released!

Thu Dec 24, 2020 8:52 am

Something strange is happening when 7.1beta3 is used as a client in WG and the remote peer uses a domain in "endpoint-address". The tunnel will appear dead (0bps, 0pps) after reboot. Disabling the interface and enabling it again does nothing. Attempting ping to that hostname from the router followed by deactivation & reactivation of the wg interface fixes the problem.
As an idea for a temporary workaround for this issue, try creating an address list with the endpoint address DNS entry in it. You shouldn't have to use the address-list for anything - simply creating one and adding that might force the router to resolve that name on boot which might result in the wireguard interface coming up properly.
Clever! ;) It actually works but it needed interface restart after ~5-10s after reboot. Good enough for lab purposes ;)
 
User avatar
SiB
Forum Guru
Forum Guru
Posts: 1888
Joined: Sun Jan 06, 2013 11:19 pm
Location: Poland

Re: v7.1beta3 [development] is released!

Mon Dec 28, 2020 3:26 am

SUP-37432 [SOLVED]

SXTR DHCP Server + AccessPoint + Galaxy-S20-Ultra-5G - phone show "Couldn't get IP address".
DHCP logs:
dec/27 19:11:02 dhcp,debug dhcp1 received discover id 3137409431 from 0.0.0.0 '1:8a:b9:ca:47:82:92'
dec/27 19:11:02 dhcp,debug,packet secs = 6
dec/27 19:11:02 dhcp,debug,packet ciaddr = 0.0.0.0
dec/27 19:11:02 dhcp,debug,packet chaddr = 8A:B9:CA:47:82:92
dec/27 19:11:02 dhcp,debug,packet Msg-Type = discover
dec/27 19:11:02 dhcp,debug,packet Client-Id = 01-8A-B9-CA-47-82-92
dec/27 19:11:02 dhcp,debug,packet Max-DHCP-Message-Size = 1500
dec/27 19:11:02 dhcp,debug,packet Class-Id = "android-dhcp-11"
dec/27 19:11:02 dhcp,debug,packet Host-Name = "Thomas-s-Galaxy-S20-Ultra-5G"
dec/27 19:11:02 dhcp,debug,packet Parameter-List = Subnet-Mask,Router,Domain-Server,Domain-Name,Interface-MTU,Broadcast-Address,Address-Time,Renewal-Time,Rebinding-Time,Vendor-Sp
ecific,Unknown(114)
dec/27 19:11:02 dhcp,debug delayed
EDIT:
This delay-threshold was generated from QuickSet at some ros version: 7.0beta5 or 7.1beta2 . I disable "delay-threshold" value and now it's work properly
Last edited by SiB on Tue Dec 29, 2020 12:53 pm, edited 2 times in total.
 
User avatar
erkexzcx
Member Candidate
Member Candidate
Posts: 263
Joined: Mon Oct 07, 2019 11:42 pm

Re: v7.1beta3 [development] is released!

Mon Dec 28, 2020 2:56 pm

ipip tunnel still not working wihout disable keepalive

When I wrote viewtopic.php?f=23&t=169538 I was using ROS7 as a VPN client to ROS6 VPN server. EoIP did work, but was silently flapping leading to random disconnects from online multiplayer games. Disabling keepalive in both sides fixed the issue.

Can this be related?
 
pe1chl
Forum Guru
Forum Guru
Posts: 10183
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.1beta3 [development] is released!

Mon Dec 28, 2020 3:20 pm

Yes, EoIP is layered on top of GRE, and GRE keepalives is a MikroTik patch in the Linux kernel (Linux does not support it by itself) which probably has to be re-done for RouterOS v7.
 
nannou9
Frequent Visitor
Frequent Visitor
Posts: 65
Joined: Tue Nov 10, 2020 9:56 pm

Re: v7.1beta3 [development] is released!

Tue Dec 29, 2020 12:48 pm

Mikrotik Audience, bridge mode, UK, updated to 7.1 Beta 3, reset to clean and then setup, purchased 3 days ago from Amazon.
I have spent last 3 days testing and ROS 6.X is no go for me as it deliver much worse WIFI than my 7 years old Apple Airports which I am looking to replace.
Therefore looking to stay on 7.1 with wave2.

Test method:
1. Audience with minimal configuration in bridge mode, just set up the bridge, DHCP client and wifi3: add band=5ghz-ac channel-width=20/40/80mhz disabled=no mac-address=XXXXXXXXXX mode=ap name=wifi3 security.authentication-types=wpa3-psk ssid="MikroTik"
2. Iperf3 MBP Pro 13" 2020 5GHz 80mhz 2x2 -wifi-> Audience -1gb-> CRS305 -10gb-> CRS305 -10gb-> Window10 PC with ConnectX 10GB fibre card
3. Iperf3 MBP Pro 15" 2018 5GHz 80mhz 3x3 -wifi-> Audience -1gb-> CRS305 -10gb-> CRS305 -10gb-> Window10 PC with ConnectX 10GB fibre card
4. ookla speed test for mobile devices

Observations:
1. Wifiwave2 link stability, performance and range is a game changer compared to ROS 6 implementation, I am getting consistently:
1.a. 520Mbit max stable iperf3 bandwidth regardless if in same or different room (Apple AirPort getting ~600MBit for 2x2 client when in same room so clearly there is more potential for wave2)
1.b. 340Mbit internet speed (not wifi link speed) on iPhones where previously link was very unstable (and rather unusable) and jumping between 10-150Mbit previously
2. Works well with QCA9984 card (not tested IPQ4019 since I am interested in 3x3+ mu mimo only)
3. CPU usage seems to be limiting factor now for bandwidth of real data as regardless of wifi link speed I cannot pass 540MBit in iperf3
3.a. Can't pass 50% cpu (not using all cores but just 2) seems to be limitation in current wave2 impl in Audience
3.b. CPU set to Auto, which is maxing out CPU to almost ~900MHz, setting CPU to lowest ~400MHz is cutting the iperf3 bandwidth to about 200MBit, so definitely CPU related

Problems in order of importance for me:
1. Once connected and disconnected devices are not able to reconnect for hour or so with error in logs: XX:XX:XX:XX:XX@wifi3 disconnected, key handshake timeout, signal strength -57, this affects all my devices
2. CPU limit at 50% needs fixing as otherwise no point of using 3x3+ devices as all of them will be limited 520MBit data speed.
3. DFS going crazy from time to time, disconnecting WiFi, this has not been observed for ROS 6.48
4. Setting all 3 radios resulted in crash loop
5. gcmp, ccmp-256 encryption crashes Audience

PS:
The 7.1 ROS with Wave2 is the only reason why I am not returning my Audience as otherwise it has slow, unstable and rather short link regardless of config
I have quite few wired MikroTik devices and I am really pleased with them, however I am really shocked how bad wifi impl is in ROS 6 regardless of config. It might have been good once in pre and early 2010 but not anymore.

EDIT 1:
Attaching profile output for Iperf3 test:
NAME C USAGE
ethernet 0 0%
networking 0 6.5%
winbox 0 0%
management 0 0.5%
profiling 0 0%
telnet 0 0%
bridging 0 0%
unclassified 0 0.5%
cpu0 7.5%
ethernet 1 0%
console 1 0.5%
networking 1 5%
winbox 1 0%
management 1 0%
profiling 1 0%
bridging 1 1%
unclassified 1 2.5%
cpu1 9%
ethernet 2 3%
networking 2 67.5%
management 2 0%
profiling 2 0%
bridging 2 3.5%
unclassified 2 19%
cpu2 93%
ethernet 3 1%
networking 3 54.5%
management 3 0%
bridging 3 3.5%
unclassified 3 23.5%
cpu3 82.5%
 
User avatar
dreamind
just joined
Posts: 10
Joined: Thu Apr 18, 2013 9:15 pm
Location: Germany
Contact:

Re: v7.1beta3 [development] is released!

Sat Jan 02, 2021 1:15 pm

Is anyone else seeing port-flapping with 7.1b3 on RB3011's ?
I'm also seeing flapping of ethernet interfaces on my RB3011 connected to my CRS328-24p running 6.48.
I tried connecting two cables using RTSP, but for some reason both links flapped at the same time, but I only used eth1 and eth2, so on the same switch chip.
I'll retry using the second switch chip (ether1 + ether6).
 
User avatar
dreamind
just joined
Posts: 10
Joined: Thu Apr 18, 2013 9:15 pm
Location: Germany
Contact:

Re: v7.1beta3 [development] is released!

Sat Jan 02, 2021 10:09 pm

Is anyone else seeing port-flapping with 7.1b3 on RB3011's ?
I'm also seeing flapping of ethernet interfaces on my RB3011 connected to my CRS328-24p running 6.48.
I tried connecting two cables using RTSP, but for some reason both links flapped at the same time, but I only used eth1 and eth2, so on the same switch chip.
I'll retry using the second switch chip (ether1 + ether6).
So I'm now using ether1 and ether6 and changed the RSTP priority on my switch to prefer the port connected to ether6. So far for the last few hours no more port flapping, so it might be related to the first switch of the RB3011.
 
igkhv
just joined
Posts: 3
Joined: Sat Jan 21, 2017 3:15 am

Re: v7.1beta3 [development] is released!

Sun Jan 03, 2021 12:32 am

There is no "foolproof". By mistake I updated ros7.1beta2 arm to ros7.1beta3 arm64 instead of arm. I got a "brick".
 
nannou9
Frequent Visitor
Frequent Visitor
Posts: 65
Joined: Tue Nov 10, 2020 9:56 pm

Re: v7.1beta3 [development] is released!

Sun Jan 03, 2021 11:33 am

There is no "foolproof". By mistake I updated ros7.1beta2 arm to ros7.1beta3 arm64 instead of arm. I got a "brick".
Just use netinstall https://wiki.mikrotik.com/wiki/Manual:Netinstall and you should be fine.
I managed to brick my device too once when it lost power during upgrade. Netinstall helped me to recover the device.
 
ntsecrets
just joined
Posts: 5
Joined: Mon Jan 04, 2021 11:15 pm

Re: v7.1beta3 [development] is released!

Mon Jan 04, 2021 11:19 pm

I had to revert back to beta2 for the following reasons:
  • L3 routing would crash, switching would continue
  • export config hangs (as reported by others)
  • the hardware offload on CRS309-1G-8S+ seems to not work, works ok in beta2
 
User avatar
Jotne
Forum Guru
Forum Guru
Posts: 3279
Joined: Sat Dec 24, 2016 11:17 am
Location: Magrathean

Re: v7.1beta3 [development] is released!

Tue Jan 05, 2021 6:49 pm

I had to revert back to beta2 for the following reasons:
It sounds like you are using it in a production environment? This is just beta. :)
 
Buster2
newbie
Posts: 46
Joined: Sun Jan 06, 2013 9:04 pm
Contact:

Re: v7.1beta3 [development] is released!

Tue Jan 05, 2021 8:04 pm

Running hap ac (RB962UiGS-5HacT2HnT) on 7.1beta3 I've seen the following:

issue #1:
Copying a file via SMB from HP Microserver at ether3 to PC at ether1 in same bridge (both negotiated 1Gbps) leads to slow performance and connection drops
  • only 40-70 MegaBytes/s instead of expected 100+
  • after about 1 Gigabyte of file transfer the connection gets lost
  • It seems it's not a problem of speed, but of volume: even a slow starting Thunderbird reading directories from offline imap folders gets stuck after about 1 Gigabyte
  • ping timeout on PC<->Microserver in both directions, after 5min downtime connection is restored-> arp suspected
I put a TP-Link router in between as a switch to copy from HP Microserver <-> hap ac <-> TP-Link router <-> PC
  • connection drops remains, but connection loss only last some seconds
  • ping goes up to 3000-5000ms with up to 10% packet loss, but I get about 100 MegaBytes/s transfer speed
  • winbox log shows both ether interfaces gone down and up after 2 secs two times
Is the bridge faulty? I put PC from ether1 to ether4:
  • 5min downtime till PC can ping hap ac as gateway (reproducible with every pull/insert plug)
  • winbox neighbour discovery shows at PC shows new mac, but no connection is possible
  • dhcp works, but no ping to router and no udp/tcp connections
  • after reboot of hap ac: when link comes back, PC shows 1-3 pings ok, then no pings until 5 min later (arp timeout?). During this time PC can ping to Microserver at ether3 without any problems. Same problem can be observed from HP Microserver.
  • after reboot of hap ac, I need to wait 320 secs (after second beep) till ping, winbox and mac-telnet work
  • I lowered arp aging time in bridge settings to 30secs, and rebooted hap ac. Then ping and winbox connection was possible after approximately 60sec (after second beep).

issue #2:
  • disabling bridge: no access to MikroTik hap ac at all, because it even didn't appear in neighbor list
  • i had to factory reset the device to gain access. I think mac-telnet to ether interface should still be possible?
 
ntsecrets
just joined
Posts: 5
Joined: Mon Jan 04, 2021 11:15 pm

Re: v7.1beta3 [development] is released!

Tue Jan 05, 2021 9:59 pm

I had to revert back to beta2 for the following reasons:
It sounds like you are using it in a production environment? This is just beta. :)
yeah I realize that, this is for my house. I like the hardware acceleration for the L3 routing, so thats why I'm using it. If they could put that in a stable 6x release I'd use that.
 
gnikola
just joined
Posts: 1
Joined: Thu Jan 07, 2021 9:47 pm

Re: v7.1beta3 [development] is released!

Thu Jan 07, 2021 9:54 pm

X86 not work.Attemped to reinstall by the iso image.System boot up and hunged with " file system corruption".Reinstall with Beta2 works well,but when upgrade to beta3 with npk file.System hung up again
-
My Alix 2D2 board will not boot v7.1beta3, after upgrade from 6.48 it just hangs up.
 
Solaris
Member Candidate
Member Candidate
Posts: 111
Joined: Thu Apr 29, 2010 5:05 pm

Re: v7.1beta3 [development] is released!

Sun Jan 10, 2021 9:36 pm

Boot loop on RB4011 when using fq-codel or codel in queue tree, will it be fixed for 7.1beta4?
 
r00t
Long time Member
Long time Member
Posts: 672
Joined: Tue Nov 28, 2017 2:14 am

Re: v7.1beta3 [development] is released!

Sun Jan 10, 2021 11:41 pm

I really hope will will see new beta with some fixes sooner than later... there's just so many bugs that make beta3 really hard to use, even for testing.
 
User avatar
buvarbeno
just joined
Posts: 9
Joined: Thu Mar 07, 2019 12:11 pm

Re: v7.1beta3 [development] is released!

Mon Jan 11, 2021 9:42 am

My hap mini is instable, when I touch to Wifi interface settings. Default the wifi is disabled after config reset. With my original config the router cant boot with 7.1b3.
The 32 MByte RAM (hap lite and mini) will be enough for stable ROS 7?
 
letsroute
just joined
Posts: 3
Joined: Tue Jan 12, 2021 1:58 am

Re: v7.1beta3 [development] is released!

Tue Jan 12, 2021 2:25 am

Hello Everyone,

Just wanted to post my results of v7.1beta3 with hEX S focusing on Wireguard:

Device: hEX S
Raw Internet Speed: 500/500 mbps
Wireguard (Mullvad): 130 / 80 Mbps (Ping 6ms)

I noticed some things when implementing wireguard:
* I had to disable fasttrack connection in filter rules because it makes the internet unusable.
* Free memory hovers around 200 MiB, but CPU usage hits 90%+ when doing a speedtest.
* I used these instructions to setup my wireguard connection to my vpn provider: viewtopic.php?f=1&t=165248&sid=51e92041 ... a9#p813884
* Using the standard wireguard client on my computer (with old router) allows me to max out my internet connection.

I'm new to the routerOS environment so any help on debugging or increasing the speed would be appreciated! After some additional testing it seems that the lack of fasttrack is what is slowing this down so much (without fasttrack raw internet speed drops to 450/400). I'm wondering if upgrading the hardware to something more powerful will fix my speed issues.

EDIT: Upgraded to 4011 and I can basically max out my connection over wireguard @ 480/500 with fasttrack off!
Last edited by letsroute on Wed Jan 20, 2021 2:55 am, edited 3 times in total.
 
yasano
just joined
Posts: 1
Joined: Tue Jan 12, 2021 8:49 am

Re: v7.1beta3 [development] is released!

Tue Jan 12, 2021 9:00 am

HI Dear

I read the post twice and found that 2 friends could not update beta3 on the X86 platform, but no one responded.
I also encountered the same problem, very strange

My platform:X86

Device 1 3867u with Intel1211-AT
Device 2 8265u with Intel1211-AT
Device 3 10900 with rog b460m with intel x520

These three devices cannot install beta3

It will prompt“error:your disk file system is corrupted! Please reinstall your router”

I tried various methods

Install via U disk, install via CD,Neither can.

Then try to install beta2, and it succeeded once

After that,I upgraded Beta3 with winbox.It has the same problem again.

I tried different upgrade methods.Drag npk or winbox check for updates ,Or downgrade to beta1 first, and then upgrade to beta3, it fails

I have no idea about this. After tossing for a few nights, I didn’t solve it

I came here hoping to ask for help. But I found that the x86 problem seems to be ignored. No one responded to them

Can anybody can help me?
 
dgnome
just joined
Posts: 8
Joined: Sat Nov 14, 2015 9:54 pm

Re: v7.1beta3 [development] is released!

Mon Jan 18, 2021 3:57 pm

Which features are missing in your opinion?
Fat DHCPv6 Relay Agent which can install routes for prefixes delegated by upstream DHCPv6-server. The current lightweight one does not install routes and does not enable dynamically advertising paths to delegated subnets. This would be very handy in cases where it's needed to keep legal entities separated from each other when one does not have all of the required L2-features available to do so, or when one prefers L3 over L2 (ethernet-frames, yuck) :)

The workaround is to add DHCPv6 server instances to every downstream interface, which is awkward, error-prone and tedious, when there are many VRRP-interfaces and they can only be added while the VRRP-interface is active.

Thanks @Mikrotik, good work, but give us this fat one for the skinny one is useless :D
 
letsroute
just joined
Posts: 3
Joined: Tue Jan 12, 2021 1:58 am

Re: v7.1beta3 [development] is released!

Wed Jan 20, 2021 2:28 am

Wireguard question - Has anyone figured out what needs to be added/adjusted in order to be able to access local PCs? I'm not able to communicate with other computers on my network at the moment when wireguard is active. I used these instructions: viewtopic.php?f=1&t=165248&sid=51e92041 ... a9#p813884
 
jmdomini
just joined
Posts: 2
Joined: Sat Apr 25, 2020 12:47 am

Re: v7.1beta3 [development] is released!

Thu Jan 21, 2021 2:51 am

It is impossible to add routing filters in beta 3 as you get an error that "add" is not a valid command. In addition if you try to use Winbox to do it, clicking on Filters in the routing menu does nothing. Just for kicks I tried downgrading to 6.48, adding the needed rule and then upgrading to 7.1B3 and yup...it wiped out my rule from the config. Running a RB4011 here.
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7038
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v7.1beta3 [development] is released!

Thu Jan 21, 2021 10:15 am

See here how to use routing filters:
https://help.mikrotik.com/docs/display/ ... ingFilters
 
mafiosa
Member Candidate
Member Candidate
Posts: 266
Joined: Fri Dec 09, 2016 8:10 pm
Location: Kolkata, India
Contact:

Re: v7.1beta3 [development] is released!

Thu Jan 21, 2021 11:55 am

See here how to use routing filters:
https://help.mikrotik.com/docs/display/ ... ingFilters
When can we expect the next release of v7.1?
 
jmdomini
just joined
Posts: 2
Joined: Sat Apr 25, 2020 12:47 am

Re: v7.1beta3 [development] is released!

Thu Jan 21, 2021 10:12 pm

That would most certainly explain it! Thank you!
See here how to use routing filters:
https://help.mikrotik.com/docs/display/ ... ingFilters
 
anuser
Long time Member
Long time Member
Posts: 601
Joined: Sat Nov 29, 2014 7:27 pm

Re: v7.1beta3 [development] is released!

Thu Jan 21, 2021 11:05 pm

]
When can we expect the next release of v7.1?
v7.1beta4,,,
 
User avatar
Steveocee
Forum Guru
Forum Guru
Posts: 1120
Joined: Tue Jul 21, 2015 10:09 pm
Location: UK
Contact:

Re: v7.1beta3 [development] is released!

Fri Jan 22, 2021 1:53 pm

@normis Can I just say Thank You for MT listening to customer base and bringing in FQ_CoDel.
I have been waiting for this for so long!
 
MoNsTeRRR
just joined
Posts: 5
Joined: Tue Oct 27, 2020 2:46 am
Location: France

Re: v7.1beta3 [development] is released!

Mon Jan 25, 2021 2:16 pm

Does v7 support RFC 3021 ? I can't find the information, if anyone can confirm thanks :)
 
bruins0437
newbie
Posts: 33
Joined: Thu Jul 13, 2017 4:30 am
Location: New Hampshire

Re: v7.1beta3 [development] is released!

Mon Jan 25, 2021 4:20 pm

Does v7 support RFC 3021 ? I can't find the information, if anyone can confirm thanks :)
We had issues using /31 subnets on 6.4x. Not sure if the problem still exists in 7.x betas. We had the ISP switch to /30 for the WAN block.
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7038
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v7.1beta3 [development] is released!

Mon Jan 25, 2021 4:50 pm

/31 is not supported and there are no plans to support it.
 
MoNsTeRRR
just joined
Posts: 5
Joined: Tue Oct 27, 2020 2:46 am
Location: France

Re: v7.1beta3 [development] is released!

Mon Jan 25, 2021 4:57 pm

Does v7 support RFC 3021 ? I can't find the information, if anyone can confirm thanks :)
We had issues using /31 subnets on 6.4x. Not sure if the problem still exists in 7.x betas. We had the ISP switch to /30 for the WAN block.
Yes I just tested today on 6.48 and it doesn't works
/31 is not supported and there are no plans to support it.
Thanks you for confirmation, I hope mikrotik will reconsider this position later.
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7038
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v7.1beta3 [development] is released!

Mon Jan 25, 2021 4:59 pm

As it is discussed in many topics in this forum you can use /32 instead of /31. Using /32 instead of /31 will not work only in specific setups.
 
User avatar
Paternot
Forum Veteran
Forum Veteran
Posts: 953
Joined: Thu Jun 02, 2016 4:01 am
Location: Niterói / Brazil

Re: v7.1beta3 [development] is released!

Mon Jan 25, 2021 8:22 pm

As it is discussed in many topics in this forum you can use /32 instead of /31. Using /32 instead of /31 will not work only in specific setups.
But why not allow /31? It's a common enough setup, and looks like the /32 doesn't cover every case. Is it some specific reason not to support /31?
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v7.1beta3 [development] is released!

Tue Jan 26, 2021 1:43 am

We would like to see /31 support as well. /32 works for quite a few things, but /31 support is a long established RfC and it is generally expected that most modern day routers will support it.
 
sundalez
just joined
Posts: 11
Joined: Tue Dec 27, 2016 6:42 pm

Re: v7.1beta3 [development] is released!

Tue Jan 26, 2021 2:50 pm

Is it just me or does it seem like a long time between 7.1 beta3 and the next beta.

Beta 3 came out dec. 2nd and we are almost in feb. now, so just short of 3 months.

let's say we need 3 more beta's and then a couple of release candidates, with this pace it could mount to more than 1.5 years from now ?

Anyone have some insight on the status of ros7 ?

Martin
 
huntermic
Member Candidate
Member Candidate
Posts: 111
Joined: Wed Oct 26, 2016 3:42 pm

Re: v7.1beta3 [development] is released!

Tue Jan 26, 2021 3:16 pm

Is it just me or does it seem like a long time between 7.1 beta3 and the next beta.

Beta 3 came out dec. 2nd and we are almost in feb. now, so just short of 3 months.

let's say we need 3 more beta's and then a couple of release candidates, with this pace it could mount to more than 1.5 years from now ?

Anyone have some insight on the status of ros7 ?

Martin
I don't think we can expect a somewhat stable fully functional v7 within 1.5 years
Also bear in mind: it is common knowledge that things are only stable in the 'long term' branch so it could be many years from now before it will be really stable.
This makes me very sad
 
sundalez
just joined
Posts: 11
Joined: Tue Dec 27, 2016 6:42 pm

Re: v7.1beta3 [development] is released!

Tue Jan 26, 2021 4:15 pm

Is it just me or does it seem like a long time between 7.1 beta3 and the next beta.

Beta 3 came out dec. 2nd and we are almost in feb. now, so just short of 3 months.

let's say we need 3 more beta's and then a couple of release candidates, with this pace it could mount to more than 1.5 years from now ?

Anyone have some insight on the status of ros7 ?

Martin
I don't think we can expect a somewhat stable fully functional v7 within 1.5 years
Also bear in mind: it is common knowledge that things are only stable in the 'long term' branch so it could be many years from now before it will be really stable.
This makes me very sad
Yes, sad indeed, especially since the new car 2004 are as unstable as they are on the 6 train..
 
markonen
just joined
Posts: 23
Joined: Tue Aug 11, 2020 4:28 pm

Re: v7.1beta3 [development] is released!

Tue Jan 26, 2021 4:25 pm

I don't think we can expect a somewhat stable fully functional v7 within 1.5 years
Also bear in mind: it is common knowledge that things are only stable in the 'long term' branch so it could be many years from now before it will be really stable.
It's worth noting that MikroTik already sells hardware that either requires ROS7 (the Chateau) or is clearly designed for it (the CCR2004). I wouldn't be surprised if the upcoming bigger CCR20xx routers also require ROS7 and the OS not being ready is thus blocking their release.

You are probably right in terms of it being years before ROS7 can replace the long term branch, but if no version of ROS7 ships this year at all, it's increasingly going to be a business problem for MT.
 
mikeybreks
just joined
Posts: 3
Joined: Tue Jul 07, 2020 11:37 pm

Re: v7.1beta3 [development] is released!

Wed Jan 27, 2021 4:17 am

As it is discussed in many topics in this forum you can use /32 instead of /31. Using /32 instead of /31 will not work only in specific setups.

Hi MRZ, while I always find your answers good and accurate, I will have to admit that I am running:
add address=aaa.bbb.ccc.253/31 interface=ether11 network=aaa.bbb.ccc.252
add address=aaa.bbb.ccc.255/31 interface=ether12 network=aaa.bbb.ccc.254
with 7.1b3 on a RB11AHx4, also had the same working on a CCR1009 (obviously not on ether11/12 though).

Ether 11 as a primary is running well with BGP and ether 12 as a backup with a simple static default gateway

I'm just hanging out for BFD on static routes to clear out a lot of (what will then be) unnecessary BGP config!

Cheers MRZ and MikroTik, and keep up the great work.
 
szhura
just joined
Posts: 18
Joined: Fri May 17, 2019 1:04 pm

Re: v7.1beta3 [development] is released!

Wed Jan 27, 2021 3:45 pm

One thing i instantly noticed is that /export never terminates. Tried to reset to an empty configuration, same thing. When i run /export verbose the last thing that gets displayed is /radius incoming set accept=no port=3799 and then it hangs forever.
Export problem is known, /routing menu export is the one that fails.
when this known problem will be dealt with?
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: v7.1beta3 [development] is released!

Wed Jan 27, 2021 6:20 pm

In beta4 :)
 
victorafp
just joined
Posts: 2
Joined: Wed Jan 27, 2021 6:08 pm

Re: v7.1beta3 [development] is released!

Wed Jan 27, 2021 6:37 pm

Hello

Is it possible to create navigation groups for users using active directory and a radius hotspot? I need to segregate the browsing by user groups, I already created a hotspot in the mikrotik and this validates with users of a domain by active directory. Now, I need the users to have different access to certain pages. Is it possible to do this segregation?

Regards
 
szhura
just joined
Posts: 18
Joined: Fri May 17, 2019 1:04 pm

Re: v7.1beta3 [development] is released!

Thu Jan 28, 2021 8:12 am

my question was "when" not "where"
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: v7.1beta3 [development] is released!

Thu Jan 28, 2021 12:06 pm

Okay, when beta4 is out.
 
User avatar
memelchenkov
Member Candidate
Member Candidate
Posts: 202
Joined: Sun Oct 11, 2020 12:00 pm
Contact:

Re: v7.1beta3 [development] is released!

Thu Jan 28, 2021 12:51 pm

my question was "when" not "where"
Ask support, they may send you pre-beta4 version, where this issue is already fixed.
 
nevolex
Member Candidate
Member Candidate
Posts: 167
Joined: Mon Apr 20, 2020 1:09 pm

Re: v7.1beta3 [development] is released!

Tue Feb 02, 2021 1:52 am

Do you guys know when the final version is out, shell we aim for the end on 2021?
 
User avatar
mkx
Forum Guru
Forum Guru
Posts: 11381
Joined: Thu Mar 03, 2016 10:23 pm

Re: v7.1beta3 [development] is released!

Tue Feb 02, 2021 1:45 pm

Do you guys know when the final version is out, shell we aim for the end on 2021?

We can aim at whatever we want, devs will surely move the target at their will (if they have a target at all).
 
infabo
Long time Member
Long time Member
Posts: 586
Joined: Thu Nov 12, 2020 12:07 pm

Re: v7.1beta3 [development] is released!

Tue Feb 02, 2021 9:51 pm

beta4 possibly in 2021 ;)
 
jmmikrotik
just joined
Posts: 24
Joined: Thu Aug 01, 2019 7:48 pm

Re: v7.1beta3 [development] is released!

Tue Feb 02, 2021 10:37 pm

testing to have wireguard functionality. i am just home user, no special usage, i do some home and remote videostreaming including 4k content, tvh server, plex server, hass os, couple of local wifi clients. wireguard tested by connecting two of my mikrotiks and few roadwarriors (iOS, android, windows10 and archwiki). all working w/o any hickups, except that i lost configuration with last night's power outage. i remember someone reporting lossing the config with reboot, so it seems reproducable.
 
User avatar
emils
Forum Veteran
Forum Veteran
Topic Author
Posts: 906
Joined: Thu Dec 11, 2014 8:53 am

Re: v7.1beta3 [development] is released!

Thu Feb 04, 2021 10:52 am

New version 7.1beta4 has been released in development RouterOS channel:

viewtopic.php?f=1&t=172274

Who is online

Users browsing this forum: No registered users and 30 guests