v7.1beta3 [development] is released!

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

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.

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.

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?

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

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.

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.

http://forum.mikrotik.com/t/802-11ac-wave2-support/127501/1

wait a second - gotta grab some popcorn :wink:

Please report this to support@mikrotik.com and attach either a supout file from your device or just a configuration export.

Added a simple queue using cake. boot loop RB951

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.

Where exactly did they promise wawe2 support on existing devices? They mentioned that driver is WIP … didn’t mention which devices they’re targeting.

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.

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.

256MB of memory:

https://mikrotik.com/products?filter&s=c&f=[%22integrated_wireless%22,%22indoors%22]&a=[%22arm%22]&r={%22ram%22:{%22s%22:%22253%22,%22e%22:%22317%22}}#!

More than 256MB of memory:

https://mikrotik.com/products?filter&s=c&f=[%22integrated_wireless%22,%22indoors%22]&a=[%22arm%22]&r={%22ram%22:{%22s%22:%22319%22,%22e%22:%2216384%22}}#!

Less than 256MB of memory:

https://mikrotik.com/products?filter&s=c&f=[%22integrated_wireless%22,%22indoors%22]&a=[%22arm%22]&r={%22ram%22:{%22s%22:%220%22,%22e%22:%22200%22}}#!

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…

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

netinstall crashes on passing ip

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?

simple queues still don’t work. the router goes into an endless reboot.
router RB4011iGS+5HacQ2HnD-IN