WiFi Wave2 / CAPsMAN v2 clients don't get IP

RouterOS Wireless Networking
1

Hello,

I’m learning the new ROS 7 / WiFi Wave2 and CAPsMAN on 3011 (MAN) and hAP ax2 (CAP).
I set up everything and I have running radio, but clients on CAP can’t get IP.
I additionally setup Datapath, and I read on forum to try add cap-wifi1 to bridge but these doesn’t do the trick.

What I missed?
Thank You

/interface bridge
add name=DEFAULT-BRIDGE
/interface wifiwave2
add configuration.mode=ap name=cap-wifi1
/interface pppoe-client
add add-default-route=yes dial-on-demand=yes disabled=no interface=ether1 \
    name=ISP use-peer-dns=yes user=username
/interface wifiwave2 channel
add disabled=no frequency=2300-7000 name=5GHZ width=20/40/80mhz
/interface wifiwave2 datapath
add bridge=DEFAULT-BRIDGE disabled=no interface-list=all name=datapath1
/interface wifiwave2 security
add authentication-types=wpa3-psk disabled=no name=WPA3 wps=disable
/interface wifiwave2 configuration
add channel=5GHZ country=Hungary datapath=datapath1 disabled=no name=\
    "MAIN CFG" security=WPA3 ssid=WIFINAME
/ip pool
add name=dhcp_pool0 ranges=192.168.1.2-192.168.1.254
/ip dhcp-server
add address-pool=dhcp_pool0 interface=DEFAULT-BRIDGE name=dhcp1
/port
set 0 name=serial0
/interface bridge port
add bridge=DEFAULT-BRIDGE interface=sfp1
add bridge=DEFAULT-BRIDGE interface=ether2
add bridge=DEFAULT-BRIDGE interface=ether3
add bridge=DEFAULT-BRIDGE interface=ether4
add bridge=DEFAULT-BRIDGE interface=ether5
add bridge=DEFAULT-BRIDGE interface=ether6
add bridge=DEFAULT-BRIDGE interface=ether7
add bridge=DEFAULT-BRIDGE interface=ether8
add bridge=DEFAULT-BRIDGE interface=ether9
add bridge=DEFAULT-BRIDGE interface=ether10
add bridge=DEFAULT-BRIDGE interface=cap-wifi1
add bridge=DEFAULT-BRIDGE interface=cap-wifi2
/interface wifiwave2 capsman
set ca-certificate=auto enabled=yes package-path="" require-peer-certificate=\
    no upgrade-policy=none
/interface wifiwave2 provisioning
add action=create-dynamic-enabled disabled=no master-configuration="MAIN CFG" \
    supported-bands=5ghz-ax
/ip address
add address=192.168.1.1/24 interface=sfp1 network=192.168.1.0
/ip cloud
set ddns-enabled=yes
/ip dhcp-server network
add address=192.168.1.0/24 dns-server=192.168.1.1 gateway=192.168.1.1
/ip dns
set allow-remote-requests=yes
/ip firewall nat
add action=masquerade chain=srcnat out-interface=ISP
/system clock
set time-zone-name=Europe/Budapest
2

/interface wifiwave2 datapath
add bridge=DEFAULT-BRIDGE disabled=no interface-list=all name=datapath1

Bridge property in datapath refers to name of bridge on CAP device when this datapath is used in capsman configuration[*]. So then question follows: does CAP device have bridge named “DEFAULT-BRIDGE”? As far as I can see, default configuration in ROS v7.8 creates bridge named “bridgeLocal” when device is in CAP mode while it’s named “bridge” if device is in “normal” mode.

[*] … and local forwarding is used. Which is (so far) the only forwarding mode available in capsman v2 AFAIK.

3

Ok I tried and it’s do the trick BUT the datapath setting applied on manager before, why now is work “reversed”? If I need “guest” datapath for example (we use this method on ROS6*) it won’t work anymore?
If I stay with this solution I have to setup “DEFAULT-BRIDGE” on every CAP, if I remove datapath then how can I get IP on clients?
Ok I think I found the problem, I need basic configuration which is defected at me.


Now I noticed my hAP ax2 not have any configuration when starts in CAP mode, furthermore I have to enable CAP manually.

Thank You

4

Latest 7.9rc has default config for device acting as AP.


What’s new in 7.9rc4 (2023-Apr-24 16:34):

*) defconf - added CAPs mode script for wifiwave2 devices;

5

I received my brand new and shiny cAP ax yesterday. After installing wifiwave2 on my RB5009 the CAPsMAN setup was pretty straightforward, except that I wasn’t able to make use of the Datapath profile on the CAPsMAN manager (RB5009) - at least it doesn’t do anything on the cAP (which makes sense). Since currently there is only local forwarding available for wifiwave2-based CAPsMAN, the only option seems to be adding the cAP interface(s) statically to the local bridge - which works for me. Is there any other way of using the CAPsMAN Datapath profile for doing this dynamically? Adding the profile on the cAP doesn’t seem sensible either. TIA!

6

Disable VLAN filtering on Cap AX bridge.
Then it should work with Capsman added interfaces.

Temp workaround until properly fixed in a next version.

7

For me disabled by default but still not working.

Do you have info what will be fixed, the datapath or the local forwarding (added manager forwarding)?

8

I tried this because I’m suffering from the exact same problem, but mine still not belongs to the dedicated bridge (I have two bridges with different DHCPs, and on both bridges only the first DHCP working), can you share your settings?
Thank You

9

That’s actually pretty simple:

/interface bridge
add comment=defconf name=bridge
/interface bridge port
add bridge=bridge comment=defconf ingress-filtering=no interface=wifi2
add bridge=bridge comment=defconf ingress-filtering=no interface=wifi5
add bridge=bridge comment=defconf ingress-filtering=no interface=ether1

And then of course do the other part of the CAPsMAN config.

10

The same problem here. I can only get IP address if I add wi-fi interfaces to local bridge on CAP. Still this address belongs to my LAN network whether I have three actually: LAN intranet wi-fi and guest wi-fi. Have no idea how to set up three separate networks with wave2 and CAPsMAN. Not possible at the moment, right?
And how to provision CAP properly? When I press Provision button on CAPsMAN nothing happens on CAP despite it being configured to listen to CAPsMAN on local bridge. Only CLI command on CAP works. Is it supposed to work this way?

11

“It is funny when it’s happening to someone else…”
Howard Walowitz

12

That’s funny how many new users comes due Wifiwave2 and other ROS7 problems (ok I’m cheating, I had as old registration which is already lost) so I asked only few times in the past 10 years (thanks to the stable ros and good documentation) and now I’m standing here as the user who sees mikrotik at first time, so that’s “funny”…

13

Ohh sorry I misunderstood, I thought only dynamic datapath not working but you could separate networks somehow.

14

For network separation use vlans (yes, they are working), and you need to add wifi interface to bridge on AP side, not controller side.

15

Please advise me what bridge I actually need to set in Datapath on capsman. Setting local bridge on Capsman doesn’t do anything. Is it still the case with 7.9?

16

You can leave it blank, for basic settings check Mikrotik help page, but they don’t mention this “add wifi interface to bridge” stuff there. I wonder why?

17

I’ve just tested today with 7.9rc5 CAPSMAN (RB1100AHx4) and 7.9 CAP (hAPac3), and AFAIK:

  • setting vlan in capsman datapath won’t work (it seems only 802.3 ax radios work with datapath vlans)
  • setting bridge in CAPSMAN datapath also doesn’t works, even if we setup the same bridge name on CAPSMAN and CAPs (i.e: bridgeLocal)
  • setting bridge in CAPs datapath does works, for example:
/interface bridge
add comment=defconf name=bridgeLocal
add name=hotspot
/interface wifiwave2
# managed by CAPsMAN
# mode: AP, SSID: caps_2ghz, channel: 2437/n/Ce
set [ find default-name=wifi1 ] configuration.manager=capsman .mode=ap \
    disabled=no
# managed by CAPsMAN
# mode: AP, SSID: caps_5ghz, channel: 5200/ac/eCee
set [ find default-name=wifi2 ] configuration.manager=capsman .mode=ap \
    datapath.bridge=hotspot disabled=no[b][/b]
/interface vlan
add interface=bridgeLocal name=vlan100_hotspot vlan-id=100
/interface bridge port
add bridge=bridgeLocal comment=defconf interface=ether1
add bridge=hotspot interface=vlan100_hotspot
add bridge=hotspot interface=ether2
add bridge=hotspot interface=ether3
add bridge=hotspot interface=ether4
add bridge=hotspot interface=ether5
/interface wifiwave2 cap
set discovery-interfaces=bridgeLocal enabled=yes

There the steps I need to provision my hAPac3 as wifiwave2 CAPs, maybe I’m wrong but I couldn’t figure out another way:
on CAPSMAN router:

  • enable capsman on CAPSMAN router, upload wifiwave2 package and upgrade to wifiwave2/capsman compatible ROS (like 7.9)
    on CAPs:
  • boot it on CAPS mode (hold reset while powering up for ~15s until LED stop bllinking and turns solid)
  • it should startup with a dhcp-client, so check its ip address and connect with winbox, ssh (I do it with some shell scripts)…
  • upload wifiwave2 package according to the ROS version shipped with the board (mine were 7.5)
  • reboot
  • upgrade ROS to wifiwave2/capsman compatible ROS (like 7.9)
  • reboot
  • enable wifiwave2 caps mode
  • add bridgeLocal (or any interface used to reach capsman router) to capsman discover interface list. It won’t show up in CAPSMAN othewise.
  • create vlan interface
  • create a bridge and add the vlan interface to it
  • setup each wifiwave2 interface datapath with desired bridge

Hope it’ll help someone, I lost a lot of time figuring this out…

18
  • add bridgeLocal (or any interface used to reach capsman router) to capsman discover interface list. It won’t show up in CAPSMAN othewise.
  • create vlan interface
  • create a bridge and add the vlan interface to it
  • setup each wifiwave2 interface datapath with desired bridge

What do you mean here by “add bridgeLocal (or any interface used to reach capsman router) to capsman discover interface list. It won’t show up in CAPSMAN othewise”. It won’t show up in CAPsMAN anyway for me.
And also “create a bridge and add the vlan interface to it”. What bridge? bridgeLocal already exists.
“setup each wifiwave2 interface datapath with desired bridge” - where? No bridge on cAP shows up in datapath settings on CAPsMAN.

19

I’ve missed some explaination: this config is used to deploy a guest/hotspot network on VLAN 100 to the 2.4Ghz+5ghz wireless radios and ethernet ports 2-5 of the hAPac3. Based on other forum posts it seems that we cannot acheive this by setting the “datapath.vlan” parameter on the CAPSMAN router side (which worked well with CAPSMAN without WIFIWAVE2), unless we have 802.3ax interfaces, which is not the case on hAPac3.

So in my case, ether1 of hAPac3 is a trunk for untagged vlan 1 (management) and tagged vlan100 (hotspot), and wlan1-2 + ether2-5 are untagged vlan100 interfaces.

To acheive this with Wifiwave2 + capsman + hAPac3 CAPs, I had to (on all CAPs):

  • keep the bridgeLocal with only ether1 (I could also remove the bridgeLocal and use directly ether1)
  • create a vlan100 interface under bridgeLocal
  • create a bridge “hotspot” with vlan100 interface, ether2-5, and wlan1-2 (these ports are created dynamically when you set the CAP “datapath.bridge” value to the local “hotspot” bridge)

I didn’t try yet with several SSIDs (like “management” on vlan1, “hotspot” on vlan100, etc), but I think it would not work because with this config I place wifiwave2 interfaces wlan1 and wlan2 directly on the bridge “hotspot” which is on vlan100.

Regarding the discovery interface, I found that with the default config on the wifiwave2 enabled CAPs, these one never appears on CAPSMAN until we enable CAP mode AND add the interface pointing to CAPSMAN (in my case ether1 or bridgeLocal) to the discovery-interface-list setting.
To enable wifiwave2 + capsman you have to be sure to have:

  • wifiwave2 compatible hardware on both side (ex in my setup: RB1100AHx4 for CAPSMAN, and hAPac3 for CAPs)
  • wifiwave2 package installed on both side
  • latest 7.X ROS version on both side (wifiwave2 CLI commands apparead recently like >7.:sunglasses:
  • enable CAPSMAN mode on router (wifiwave2 → capsman → enable)
  • enable CAP mode on CAPs devices (wifiwave2 → cap → enable)
  • add interface used to reach CAPSMAN to the wfiwave2-> discovery-interfaces list