I have the following config working as expected, except that after power outage CAPSMAN is really slow to establish the connection to the CAPs after the power comes back up.
At the moment CAPSMAN connects and disconnects to the CAPs many times before it successfully establishes connection and provision the configuration.
Does it matter that hap AX3 is version 7.16 and the 2 wap ax are 7.15?
Are you referring to caps radios becoming visible in capsman or the radios themselves becoming visible to clients ?
The former should be rather quick. On my installations it is a matter of seconds after reboot.
The latter can take up to 15 minutes if you use DFS frequencies (radar checks needs to be completed first before the AP is allowed to transmit).
Only on 5GHz radios or also 2GHz radios ?
Which device is acting as controller ?
Is the problem with all APs or only some ?
Are you referring to caps radios becoming visible in capsman or the radios themselves becoming visible to clients ?
The radios pop up in CAPSMAN for few seconds and then disappear, the can’t become visible to the clients at all.
Only on 5GHz radios or also 2GHz radios ?
Both 5 and 2GHz radios.
Which device is acting as controller ?
Is the problem with all APs or only some ?
hap AX3 is the main controller, the problem is only with the 2 wap ax APs, the hap ax2 is being managed by CAPsMAN but also gets the management super slow.
From the time I posed this topic till now only ax2 has managed to get settings from AX3, the other two are still trying
I tried Skip DFS Channels all and disabled, no change
Then it may be time to put your config on the table.
Controller and 1 wap AX please.
Make sure to remove all private/public info.
And please post both configs between code quotes.
Here is my config, please let me know if you see anything wrong with it, but as I previously stated it was working few days ago when I installed the wap ax access points. Nothing has changed except the fact that I had power outage and then it was not working
# 2024-12-06 09:44:59 by RouterOS 7.15.1
# software id = 2881-0S7F
#
# model = wAPG-5HaxD2HaxD
# serial number = ******
/interface bridge
add name=bridge1
/interface wifi
# no connection to CAPsMAN, managed locally
# SSID not set
set [ find default-name=wifi1 ] configuration.manager=capsman-or-local .mode=ap disabled=no
# no connection to CAPsMAN, managed locally
# SSID not set
set [ find default-name=wifi2 ] configuration.manager=capsman-or-local .mode=ap disabled=no
/interface bridge port
add bridge=bridge1 interface=ether1
add bridge=bridge1 interface=ether2
add bridge=bridge1 interface=wifi1
add bridge=bridge1 interface=wifi2
/interface wifi cap
set discovery-interfaces=bridge1 enabled=yes
/ip dhcp-client
add interface=bridge1
/system clock
set time-zone-name=Europe/Sofia
/system identity
set name=vRS_backyard
/system note
set show-at-login=no
I’ve noticed that after 3 days of trying everything was working again as expected, but again today we had power outage for 5 minutes and now again it is struggling to get the radios back up.
I think this might be a clue why its not working, the cap-wifi1 and cap-wifi2 are getting provisioning fast and are identical to the management CAP. These 2 are on hap ax 2.
The cap-wifi3 and cap-wifi4 in red are on wap ax and from what i see in Radios tab for 5GHz band it is trying to get few more bands assigned. Do I need to set some additional parameters in Configuration or similar to get the same result as on hap ax2?
if by external you mean the radios of the wap ax devices that are managed by the hap ax3 CAPsMAN, yes I can’t get IP when I am trying to connect trough an external radio
I can connect to wifi and get IP when I connect to the radio on my main router hap ax3. But not trough the radios of the CAP devices.
add address=0.0.0.0/24 gateway=0.0.0.0 netmask=24
Its an artefact left from config, removed it - not solved the issue
I was able to resolve the issue by setting the Bridge - Admin MAC address and after that adding the cap WiFi interfaces to their bridges.
It seems the problem was that after reboot some times the CAP bridges get different MAC addresses assigned.