*) 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?
So the hap ac² will never receive full wave2 support, not even the models with 256 MB RAM?
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
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
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…
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.
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.
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.
The export never completes and the last complete section is: /ip service
Missing CHR disk space was false alarm, the magic “turn it off and on again” fixed it. Now there’s 34.6MB free.
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.
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.
Export problem is known, /routing menu export is the one that fails.
“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.
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.
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.
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?
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.
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.