v7.13.5 [stable] is released!

[holvoetn]

Remove qcom on rb5009. Not needed since wave 2 is default present in ROS package as of 7.13.

How is capsman upgrade strategy set on your device ?

Maybe best to start separate thread with config of your controller and one of your caps (assuming they are all the same)

[erlinden]

Well, the first step is already done by posting this problem

Are the hAP ax2’s also upgraded? Would it be possible to set it up from scratch? What version where you running?
The qcom package is only required for devices that have wireless interfaces, no need to install it on the RB5009.

Can you share your config:

/export file=anynameyoulike

Post here (or better, create a new topic), remove serial and any other private information and post it in between code tags by using </> button.

[aspen63]

Thank you all, I managed to resolve my issue but I’ll post a new thread to clarify MikroTik’s logic.

[Dario1982]

One week ago I upgraded to 7.13 the following
RB5009UPr+S+IN
cAP AC
hAP AC2

Today I moved both cAP AC and hAP AC2 to the new wifi-qcom-ac-7.13-arm package and setup them as CAP with the new CAPsMAN (the one under /wifi/interface) however I have an issue.
If access points get rebooted all works fine, after power cycle the CAPs come back, but in case the RB5009 is rebooted then CAPs are not showing up in remote CAP tab. The only way to bring them back is to disable and re-enable CAPsMAN.

To mitigate the issue I added a script to do an off/on of CAPSman at each startup but I wonder if this is a something wrong with my configuration or a bug.

I don’t have use cases with RouterOS < 7.13 because until now my AP couldn’t get wave2 drivers so until now I used only the old CAPsMAN so I cannot tell if this is something happenning also with previous version and I cannot downgrade to test otherwise I cannot use the new wave2 drivers.

Is someone facing the same issue?

Thanks

**** EDIT - PROBLEM SOLVED ****

I found that this behaviour happens if the CAPs are setup to reach the CAPsMAN using a fixed IP address put in “CAPsMAN address” parameter instead of using discovery interface. I put a fixed IP in my early test from wireless to wifi package and I left the configuration like that as I didn’t imagine to have a side effect. Now I moved back to discovery interface and after the reboot of the CAPsMAN the remote CAP are showing up without any problem.

[Dario1982]

Just a quick question before saying happy new year…
If i am gonna move to new wifi drivers for my hap ac2 and create all the configuration from scratch, does anyone know if vlans are working on the wifi interfaces with the new drivers?

It does, I just did it today.
It’s just different than before. You don’y have to use datapath but in short for each AP you need to (assuming you are connecting your AP via ether01 and using a management VLAN):

\

1. create all the WLAN you need (in my case I have 3 SSID on 3vlan so I created 2 virtual WLAN for each master WLAN internface)
2. create a bridge
3. Add to the bridge ether1 and all the WLAN interfaces.Assign the correct VLAN PVID to each WLAN interface
4. create all the VLAN entries under /bridge/vlan
5. Assign bridge and ether1 as tagged and link the appropiate WLAN interface as untagged to the respective VLAN basically you must treat the WLAN as access port)
6. create a VLAN interface under /interface/vlan and setup and ip or a dhcp client (depending on your setup)
7. enable vlan filtering on the bridge
8. setup master WLAN interface to use capsman as manager
9. create a datapath that uses the bridge above as brigde. Do not assign any vlan to the datapath.
10. now you can enable CAP and select “slave static = yes” and slave “datapath = datapath_created_above”

Of course on the other side you must setup the interface that is interconnected to you hap ac2 as tagged for all the VLAN you need to pass, including the management VLAN.

So it’s a bit more cumbersome than before with datapath taking care of forwarding but for sure it works.

[Dario1982]

Is there a guide on making both CAPSMANs work at the same time on the same MikroTik device?

I’ve tried but they don’t seem to be able to coexist. I suspect that may have to be listening on different interfaces, can’t check that right now but would appreciate any advise.

Edit: Tried running them on different VLAN ifaces with no luck - as soon as I enable the new CAPsMAN the old one seem to stop working and I lose all wi-fi connections, CAP interfaces, etc.

Strange.
I’m quite sure I was having both CAPsMAN running during my migration. I decided to move my CAPs one by one and all the old one were working until I didn’t reconfigure them.
Of course each CAP can point only to one CAPsMAN instance at time.
I have an old MIPSBE CAP parked somewhere, tomorrow I will bring it back and retest (I still have my old CAPsMAN config as rollback plan since I switched to wave2 only today).

[IgorOV]

Loaded 7.13 on a few AX2 units. Fetch from scripts is currently the only one item that stands out with errors compared to 7.12.1.

We have a script that triggers on boot and fetches a few files from our provisioning servers (Basic auth and HTTPS).
On 7.12.1 works every time.

Using 7.13 the first file is saved without issues, but we observe different errors for subsequent files:

script error: failure: Idle timeout - waiting data
script error: failure: connection timeout
script error: failure: remote disconnected while in HTTP exchange

The entire job is a single script.

Edit the delay does not fix the issue

Hi mate!
have you tried to run the script in terminal?
i have a script that runs a http post to whatsapp api which sends me alerts and after 7.13 netwatch does not run the fetch command however if I copy/paste the same script in terminal, it runs perfectly.

as below:

/tool fetch http-method=post http-header-field=“MY_TOKEN_STRING, Content-Type: application/json” http-data=“{"number":"my_phone-number","message":"the_message_I_wanna_send"}” url=“https://api-whatsapp-I-use.com/bla/bla/bla”

[Maggiore81]

I upgraded a CRS328 from 7.11 to 7.12 and then to 7.13
SFP flapped permanently, excessive broadcast, duplex mismatch etc…
downgraded to 7.12.1 and problem disappeared.

[sinisa]

…

1. create all the WLAN you need (in my case I have 3 SSID on 3vlan so I created 2 virtual WLAN for each master WLAN internface)
2. create a bridge
3. Add to the bridge ether1 and all the WLAN interfaces.Assign the correct VLAN PVID to each WLAN interface
4. create all the VLAN entries under /bridge/vlan
5. Assign bridge and ether1 as tagged and link the appropiate WLAN interface as untagged to the respective VLAN basically you must treat the WLAN as access port)
6. create a VLAN interface under /interface/vlan and setup and ip or a dhcp client (depending on your setup)
7. enable vlan filtering on the bridge
8. setup master WLAN interface to use capsman as manager
9. create a datapath that uses the bridge above as brigde. Do not assign any vlan to the datapath.
10. now you can enable CAP and select “slave static = yes” and slave “datapath = datapath_created_above”
    …
    So it’s a bit more cumbersome than before with datapath taking care of forwarding but for sure it works.

I have come to something similar to this. Not “a bit more cumbersome” but “very complicated”. Not good at all for deployment of more than a few APs. No automatic configuration. I would not call this “managed AP”. CAPsMAN is here only for faster roaming (OK, good thing, and I’m glad it’s fnaly here), but not something you could configure once and leave to the customer to add APs at will, as it was possible with old CAPsMAN.
Definitely needs more development.

[Dario1982]

I have come to something similar to this. Not “a bit more cumbersome” but “very complicated”. Not good at all for deployment of more than a few APs. No automatic configuration. I would not call this “managed AP”. CAPsMAN is here only for faster roaming (OK, good thing, and I’m glad it’s fnaly here), but not something you could configure once and leave to the customer to add APs at will, as it was possible with old CAPsMAN.
Definitely needs more development.

Agree and disagree at the same time.
I do agree because it was very handy to set a CAP in CAP mode and provision, and will be great to have it back on AC deviced (I understood that AX can be managed via datapath and vlan tagging)

But I disagree because there is stil a lot that you can manage remotly and deploy at scale

• change SSID configuration
• change security configuration
• change channel configuration
• change access list

So it’s not perfect but VLANs are by far things that are less frequently changed. And once you create a standard for your CAP (e.g. always use ether1 to uplink, naming convention for your WLANs, number of WLANs you need) you can prepare a rsc file to be used to configure the device with everything you need without having to spend to much time.

[erlinden]

Definitely needs more development.

This is only necessary for AC devices, if new devices are AX it won’t be a problem.
But I agree AND have trust this will be available in the future.

[Dario1982]

Is there a guide on making both CAPSMANs work at the same time on the same MikroTik device?

I’ve tried but they don’t seem to be able to coexist. I suspect that may have to be listening on different interfaces, can’t check that right now but would appreciate any advise.

Edit: Tried running them on different VLAN ifaces with no luck - as soon as I enable the new CAPsMAN the old one seem to stop working and I lose all wi-fi connections, CAP interfaces, etc.

Hi Mazay,
as promised I’m back
I confirm that i succesfully deployed two CAP AC (7.13 on qcom drivers) and one RB951G-2HnD (on 7.13 with old drivers) on the same RB5009 CAPsMAN and obtained an hybrid setup (old and new CAPsMAN).
Both CAPsMAN are using the same management VLAN to connect between CAPs and CAPsMAN

[infabo]

another qcom-ac feedback: I have a Busch-Jaeger 8240-84 wifi radio. With legacy driver the device could connect once after restart/turn-on but lost connectivity after some time (disconnect in ROS log) and won’t reconnect anymore. the device thought it was still connected. Busch support never responded to my inquiries so it was a pita until 7.13.

Now with qcom-ac driver the device is finally working like a charm. Thanks again MT for bringing these (wave2) drivers to us.

[sinisa]

Definitely needs more development.

This is only necessary for AC devices, if new devices are AX it won't be a problem.
But I agree AND have trust this will be available in the future.

Sure, this was only about existing (and new) AC equipment.

I did not mean to be disrespectful for what Mikrotik is doing, actually I LOVE it. It's just that I would like it to be even better.
Old CAPsMAN v2 (anybody remember CAPsMAN v1?) was so easy to configure that I could delegate that to cable installers - even teach them to keep Reset button long enough, but not too long. Now I'll have to visit each AP before it is operational... and I'll do it gladly because of the added features.

[Chupaka]

This night I had another

system,error,critical router was rebooted without proper shutdown, probably kernel failure
system,error,critical kernel failure in previous boot
system,error,critical out of memory condition was detected

And Graphing looks innocent:

Hey MikroTik, is it worth sending autosupout to support?..

[erlinden]

Hey MikroTik, is it worth sending autosupout to support?..

Always a good idea!

What device are you using and how is it configured?
And for how long was it up?

[un9edsda]

There seems to be a typo/discrepancy in the new Wifi documentation’s Channel properties section: according to the docs the one of the possible values of the band property is 5ghz-an however on an actual router said property value pair is

band=5ghz-n

.

[mirolm]

Are you sure you are not seing just the bands your radio supports? On my hAP ax2 i see 5ghz-a, 5ghz-n, 5ghz-an for example. There is no “ax” because the router do not support that.

[Chupaka]

What device are you using and how is it configured?
And for how long was it up?

cAP ac, about 2 weeks uptime (first one rebooted with ~9 days uptime?..)

Will try to send a mail to support, thanks

[t0mm13b]

Hi,

Issue spotted with D53G-5HacD2HnD (Chateau LTE 12)

Two things happened with v7.13
Noticed new LTE firmware, downloaded it, and installed firmware, blue led light turned pink, periodically ended up intermittently flashing pink on and off.

Waited for few minutes then rebooted device, it came back up with blue led light on at a constant.

Navigated into Interfaces > LTE, clicked on lte interface and check firmware

Posted supout.rif - SUP-139367

Thanks,