Hap-ac2, wifi-qcom-ac, and station-bridge config

RouterOS
1

A quick question (and this may be all on me).

I have a new hap-ac2 that I just got, dropped wireless, upgraded to 7.23.3, and loaded wifi-qcom-ac without incident.

That works, and I can manually config everything fine.

The desired config is for the 2GHz radio to have it's Master config be a "station-bridge" to connect to another AP. The slave config will be as an AP, and offer the units 2GHz wireless once the bridge is up.

The 5GHz will just have an AP presented for admin, which will be there all the time.

(The rest is irrelevant at this point, and is not yet on this test unit - first time with wifi-qcom-ac, but the goal is to offer an ipsec tunnel drilled out behind a 3rd party NAT network. That config works fine . . . ).

I have 3 configs: One for the station-bridge, and one each for the other two AP's. If I config via the Wifi tab, all works fine. If I define the config via "Provisioning", despite the master config on 2GHz being the station-bridge, it applies it as an AP config instead.

This config is lean at this time - nothing in datapath, nothing in Channel, EAP, FT, AAA, Interworking or Steering, so I doubt that this setting is coming from another section. And, I can simply go into the wifi config as set by provisioning, toggle it, and all works.

Does anyone know any reason that provisioning won't correctly add the "station-bridge" config? I CAN do this directly, but doing it via provisioning is more consistent with the "rest of my world"

This is the entire WiFi config at this point (note that the change to station-bridge was done manually . . . all else as provisioned. I have omitted the security section since at this point, all it contains is the password, which would be dropped anyhow):

/interface wifi configuration
add channel.band=2ghz-n comment="The Victorian" country="United States" \
    disabled=no mode=station-bridge name=TheVictorian security=TheVictorian \
    ssid=TheVictorian
add comment=5301Infra disabled=no name=5301Infra security=5301Infra ssid=\
    5301Infra
add comment=5301Admin disabled=no mode=ap name=5301Admin security=5301Infra \
    ssid=5301Admin
/interface wifi
set [ find default-name=wifi1 ] comment="2GHz " configuration=TheVictorian \
    configuration.mode=station-bridge disabled=no name=2GHz
add configuration=5301Infra configuration.mode=ap disabled=no mac-address=\
    <gibberish1> master-interface=2GHz name="2GHz virt"
set [ find default-name=wifi2 ] comment=5GHz configuration=5301Admin \
    configuration.mode=ap disabled=no name=5GHz
/interface wifi provisioning
add action=create-enabled comment=2GHz disabled=no master-configuration=\
    TheVictorian radio-mac=<gibberish1> slave-configurations=5301Infra \
    supported-bands=2ghz-n
add action=create-enabled comment=5GHz disabled=no master-configuration=\
    5301Admin radio-mac=<gibberish2> supported-bands=5ghz-ac

Not the end of the world (or inoperable) but seems wrong . . . Anyone else tried this?

2

My answer is off-topic because I don't use MikroTik WiFi and cannot help you with the station-bridge config. But for the forum, if you need to post RouterOS scripts/commands, paste them between:

```routeros
<paste stuffs here>
```
7

Ahhh . . . fun with browser fonts! NOT! Got it! Thanks!

8

I can not find back anything in documentation which backs this up but my guess is because capsman can only control devices/radios which are in AP mode.

PS and for code block: either the 3 backticks or use this one

image
image575×105 7.83 KB

/interface wifi configuration
add channel.band=2ghz-n comment="The Victorian" country="United States" \
    disabled=no mode=station-bridge name=TheVictorian security=TheVictorian \
    ssid=TheVictorian
9

NOTE Errant! Leaving for continuity.

That may well be the case, but it would seem nonsensical, since I CAN set the config using CapsMan, just not with it's provisioning tool. You would think that since that tool simply associates a config with hardware devices, that it would take the whole thing over, and not just omit one field . . .

And, oddly, I don't get that item when I am in the editor, but thanks for the pointer.

10

??
AFAIK you can not set mode of a radio with capsman from the controller ?
CAP mode has to be enabled on the radio and then only AP mode should be used.

How do you do that then ?

And this more or less confirms it.

11

NOTE Errant! Leaving for continuity.

With the AP in CAP mode and the interfaces/radios set to CapsMan control via the "manager" parameter, create a config and set mode to station-bridge. Then go info the WiFi tab and associate it to the radio manually in "Configuration", and I recall that setting the mode correctly. You can also go into the WiFi section for the remote radio via CapsMan and directly set any mode.

(What I ended up doing here in the provisioning case was to provision with the same config file, have the mode misset, and then simply change mode under WiFi. When I got sick of fighting that, I didn't use provisioning, but rather the direct setting of the config in WiFi. Both work. I'd post the config, but that AP is down at the moment, and it's very AM here.)

12

NOTE Errant! Leaving for continuity.

That would be the WiFi tab in CapsMan (IE remote), not local on the AP . . . It's all CapsMan remote control . . . provisioning simply sets the config in WiFi based on rules . . . and is not required to use CapsMan.

13

Oh, and one more thing I note. I also did try a fully local config without any use of CapsMan, and the mode was botched by "provision" there as well. Not a big deal, since I only have a few of these wireless to wireless bridge units, but I tend to like to be consistent in config methodology, and since the config file is unchanged, things are at least still consistent there.

14

I know you can provision without capsman but again, AFAIK, only to radios in AP mode.
It's the trick to use when capsman controller has a local radio since capsman can not control own local radios.
But provisioning does work so you can keep the same provisioning profiles as for other radios.

15

Can you post that config for review (after getting some ZZZZs) ?

16

Let me apologize for leading folks modestly astray. I was working two issues yesterday, and this one dis NOT ever get to CapsMam . . . . Not setup in any way on this unit.

The issue is in the wifi-qcom-ac used locally on a new hap-ac2.

The config (station-bridge) applies correctly when applied to the 2GHz interface via the WiFi tab "by hand".

The same config fails when applied via provision.

(I never got to CapsMam . . . ) (Sorry for the misdirection! Seriously sleep deprived when I posted and had bad brain fade.)

The complete wifi config is already in post one. I have not setup anything other than wireless at this point. (Well, other than a dhcp client on the bridge, which contains all ports. No firewall rules either - it's a pure, simple AP) The only thing redacted (also as noted above) was security, since all it contailed was the passphrase, and I wasn't testing login anyhow.

17

Submitted the question/possible bug to support as SUP-221193 . . .

18

And I am pretty sure the answer will come back provisioning only works correcrly for AP mode :grinning_face:

19

Utterly brain damaged, but still not unlikely :slight_smile:

At least throw and error, an not silently botch the config!