Community discussions

MikroTik App
 
User avatar
noorhamed
just joined
Topic Author
Posts: 13
Joined: Sat Mar 27, 2021 2:45 pm

Please Respond - About new CapsMan (wifi)

Thu Nov 07, 2024 1:01 am

Hi everyone, :(

I’m trying to set up a wireless network with CAPsMAN, and I need the clients to receive IP addresses from a DHCP server on VLAN 202. Here’s my current setup:

I created VLAN 202 on the CAPsMAN router.
I added a bridge named Bridge-CAPsMAN-202 with vlan-filtering=yes.
DHCP server is configured to serve addresses.
I have set the WiFi configuration in CAPsMAN to use Bridge-CAPsMAN-202 but left the VLAN ID blank in the Datapath to avoid tagged VLAN traffic to clients.
However, clients are still not receiving an IP address from the DHCP server. I’ve also tried:

Testing the DHCP server directly on VLAN 202 with other devices (wired).

Here’s CapsMan configuration:
/interface bridge
add name=Bridge-CAPsMAN-202 pvid=202 vlan-filtering=yes
/interface vlan
add interface=ether2-SW name=VoIP-WLAN vlan-id=202
/interface wifi datapath
add bridge=Bridge-CAPsMAN-202 disabled=no name=DP-VoIP-WLAN
/interface wifi security
add authentication-types=wpa-psk,wpa2-psk disabled=no name=Akey-VoIP wps=\
    disable
/interface wifi configuration
add datapath=DP-VoIP-WLAN disabled=no name=5G-VWLAN security=Akey-VoIP ssid=\
    Heqom
add datapath=DP-VoIP-WLAN disabled=no name=2G-VWLAN security=Akey-VoIP ssid=\
    Heqom
/ip pool
add name=dhcp_pool3 ranges=172.30.202.12-172.30.202.30
/ip dhcp-server
add address-pool=dhcp_pool3 interface=VoIP-WLAN lease-time=5h name=VoIP-WLAN
/interface wifi capsman
set ca-certificate=auto enabled=yes interfaces=ether2-SW package-path="" \
    require-peer-certificate=no upgrade-policy=none
/interface wifi provisioning
    name-format=%I radio-mac=X:X:X:X:X slave-configurations=5G-VWLAN
    name-format=%I radio-mac=X:X:X:X:X slave-configurations=2G-VWLAN
/ip address
add address=172.30.202.1/24 interface=VoIP-WLAN network=172.30.202.0
/ip dhcp-server network
add address=172.30.202.0/24 dns-server=172.30.202.1 gateway=172.30.202.1
/ip dns
set servers=8.8.8.8,4.2.2.4
Here’s cAP AX configuration:
/interface vlan
add interface=E02-SW name=V-WLAN vlan-id=202
/interface wifi
# managed by CAPsMAN
# mode: AP, SSID: Heqom, channel: 2412/ax/Ce
set [ find default-name=wifi2 ] channel.band=2ghz-ax .frequency=2437 .width=\
    20mhz configuration.manager=capsman-or-local .mode=ap .ssid=Heqom \
    disabled=no name=WLAN-2.4GHz security=Akey
# managed by CAPsMAN
# mode: AP, SSID: Heqom, channel: 5500/ax/Ceee
set [ find default-name=wifi1 ] channel.skip-dfs-channels=all \
    configuration.manager=capsman-or-local .mode=ap .ssid=Heqom disabled=\
    no name=WLAN-5GHz security=Akey
/interface wifi cap
set discovery-interfaces=E02-SW enabled=yes
/ip address
add address=172.30.202.252/24 interface=V-WLAN network=172.30.202.0
I've been really struggling and I genuinely need help. :( :(
 
User avatar
mkx
Forum Guru
Forum Guru
Posts: 12916
Joined: Thu Mar 03, 2016 10:23 pm

Re: Please Respond - About new CapsMan (wifi)

Thu Nov 07, 2024 8:34 am

Not going into details, but ...

wifi CAPsMAN doesn't offer "capsman forwarding" ... which means that anything, defined in datapath, is applied on each CAP device.
In particular: your setting
/interface wifi datapath
add bridge=Bridge-CAPsMAN-202 disabled=no name=DP-VoIP-WLAN
means that CAP devices need a bridge named "Bridge-CAPsMAN-202".

Additionally: CAPsMAN only provisions radios on CAP devices. Meaning that bridge, mentioned in datapath, has to be created manually. So if you want to perform as little local configuration of CAP devices as possible, use features created by default config. And that is VLAN-oblivious bridge, named "bridge".
If CAP device runs wifi-qcom driver (not the -ac variant), then you can use property "vlan-id=XXX" of datapath ... in this case, wifi-qcom driver will tag/untag frames, passed via bridge ... and bridge can, thus, be VLAN oblivious ... and will simply pass frames (including VLAN tags) between bridge ports. Apart from VLAN bleeding (which is prevented by properly configuring bridge into fully-VLAN aware entity) it then works as intended, VLAN-tagged frames arrive at main router (or any other intended destination).
 
holvoetn
Forum Guru
Forum Guru
Posts: 6656
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: Please Respond - About new CapsMan (wifi)

Thu Nov 07, 2024 9:19 am

Default cap config it's called bridgeLocal.

So it depends if you start from default cap config or normal config and enable capsman manually (then it's indeed "bridge").
 
User avatar
mkx
Forum Guru
Forum Guru
Posts: 12916
Joined: Thu Mar 03, 2016 10:23 pm

Re: Please Respond - About new CapsMan (wifi)

Thu Nov 07, 2024 7:43 pm

Default cap config it's called bridgeLocal.

Interesting, I didn't know that.
 
erlinden
Forum Guru
Forum Guru
Posts: 2586
Joined: Wed Jun 12, 2013 1:59 pm
Location: Netherlands

Re: Please Respond - About new CapsMan (wifi)

Thu Nov 07, 2024 7:55 pm

Why do you use a (single) VLAN?

To understand (more?) about VLAN, please have a look at this great topic:
viewtopic.php?t=143620

Next, configure CAPsMAN as mentioned here:
https://help.mikrotik.com/docs/spaces/R ... ionexample:

And when you are ready for VLAN's, have a look at this example:
https://help.mikrotik.com/docs/spaces/R ... ionexample:

If you want trunk ports (instead of hybrid ports) to the cAP AX, be aware that you have to change default CAP with VLAN filtering enabled on the CAP's bridge.

Who is online

Users browsing this forum: vaughn and 16 guests