[SOLVED] CAPsMAN, DHCP forwarding

RouterOS Wireless Networking
1

Good day,

I am trying to achieve the following setup - hAP ac running as CAPsMAN, two wAP ac’s as CAPs. Currently I have managed to set up and running CAPsMAN, but the wAP ac router has its own DHCP server. I would like to disable the dhcp on the current and future wAP ac’s, so that the hAP ac is managing all DHCP leases to my clients. How can I achieve this ? Should I disable the DHCP server on the wAP ac (CAP), but how can I forward all DHCP/DNS requests? Please see my config below:

/caps-man channel
add band=2ghz-b/g/n extension-channel=disabled frequency=2412 name=channel1 \
    tx-power=15 width=20
add band=2ghz-b/g/n extension-channel=disabled frequency=2412 name=channel2 \
    tx-power=15 width=40
/caps-man datapath
add bridge=bridge client-to-client-forwarding=yes local-forwarding=yes name=\
    datapath1
/caps-man security
add authentication-types=wpa2-psk encryption=aes-ccm group-encryption=aes-ccm \
    name="SSID" passphrase=Test1234.
/caps-man configuration
add channel=channel1 datapath=datapath1 mode=ap name="SSID" \
    rx-chains=0,1,2 security="SSID" ssid="SSID" tx-chains=\
    0,1,2
/caps-man aaa
set interim-update=disabled mac-caching=disabled mac-format=XX:XX:XX:XX:XX:XX \
    mac-mode=as-username
/caps-man access-list
add action=accept disabled=no interface=all signal-range=-80..120 \
    ssid-regexp=""
add action=reject disabled=no interface=all signal-range=-120..-81 \
    ssid-regexp=""
/caps-man manager
set ca-certificate=none certificate=none enabled=yes package-path="" \
    require-peer-certificate=no upgrade-policy=none
/caps-man provisioning
add action=create-dynamic-enabled common-name-regexp="" disabled=no \
    hw-supported-modes="" identity-regexp="" ip-address-ranges="" \
    master-configuration="SSID" name-format=cap name-prefix="" \
    radio-mac=00:00:00:00:00:00 slave-configurations=""
2

I understand that you have a DHCP server on hap ac and each ac wap. If so, disable the DHCP server on the wap ac and since then the address will only issue your hap ac.

3

I have solved this issue with the help on IRC. On the wAP ac device I disabled the dhcp server

/ip dhcp-server disabled=yes

And changed the dhcp-client to listen on the bridge interface:

/ip dhcp-client interface=bridge

After that, I added the device to CAPsMAN.

4

Hi, I have the same problem, and yes I have two bridges (not using VLAN separations). The thing is, when reouter is rebooted, on whichever cap conf. connection is made first it will work and continue to work, and other will not. Connection will be established, but connected client will wait indefinetly for DHCP, and will never be assigned IP address to it…