I have configuration for wifi on capsman set to 2GHz b/g/n. On the CAP the wifi is set to b/g. I cannot set it manually to b/g/n because it is managed by capsman. On the capsman you can also see that the wifi for this cap is set b/g/n. So the wifi settings are not synced with what is set on capsman to what is actually running on the cap.
What could be the reason? Cap is RB951G-2HnD which supports n band.
Post config for cap please.
It is possible to set things locally which will overwrite capsman settings.
# 2025-01-16 21:07:13 by RouterOS 7.17
# software id = MN9K-ZKYA
#
# model = RB951G-2HnD
# serial number = ****
/interface bridge
add admin-mac=4C:5E:0C:E9:6B:E2 auto-mac=no comment=defconf name=bridgeLocal \
port-cost-mode=short
/interface wireless
# managed by CAPsMAN
# channel: 2412/20-Ce/gn(20dBm), SSID: xxxxx, local forwarding
set [ find default-name=wlan1 ] antenna-gain=0 country=no_country_set \
disabled=no frequency-mode=manual-txpower ssid=MikroTik station-roaming=\
enabled
/interface ethernet
set [ find default-name=ether1 ] advertise="10M-baseT-half,10M-baseT-full,100M\
-baseT-half,100M-baseT-full,1G-baseT-half,1G-baseT-full,2.5G-baseT,5G-base\
T,10G-baseT"
/interface list
add name=WAN
add name=LAN
/interface lte apn
set [ find default=yes ] ip-type=ipv4 use-network-apn=no
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/interface bridge port
add bridge=bridgeLocal comment=defconf ingress-filtering=no interface=ether1 \
internal-path-cost=10 path-cost=10
add bridge=bridgeLocal comment=defconf ingress-filtering=no interface=ether2 \
internal-path-cost=10 path-cost=10
add bridge=bridgeLocal comment=defconf ingress-filtering=no interface=ether3 \
internal-path-cost=10 path-cost=10
add bridge=bridgeLocal comment=defconf ingress-filtering=no interface=ether4 \
internal-path-cost=10 path-cost=10
add bridge=bridgeLocal comment=defconf ingress-filtering=no interface=ether5 \
internal-path-cost=10 path-cost=10
/ip firewall connection tracking
set udp-timeout=10s
/ip neighbor discovery-settings
set discover-interface-list=!dynamic
/ip settings
set max-neighbor-entries=8192
/ipv6 settings
set disable-ipv6=yes max-neighbor-entries=8192
/interface list member
add interface=ether1 list=WAN
add interface=ether2 list=LAN
add interface=ether3 list=LAN
add interface=ether4 list=LAN
add interface=ether5 list=LAN
add interface=wlan1 list=LAN
/interface ovpn-server server
add auth=sha1,md5 mac-address=FE:87:62:A9:5D:D2 name=ovpn-server1
/interface wireless cap
#
set bridge=bridgeLocal discovery-interfaces=bridgeLocal enabled=yes \
interfaces=wlan1
/ip address
add address=10.0.0.4/24 interface=ether2 network=10.0.0.0
/ip dns
set allow-remote-requests=yes servers=10.0.0.1
/ip ipsec profile
set [ find default=yes ] dpd-interval=2m dpd-maximum-failures=5
/ip route
add disabled=no dst-address=0.0.0.0/0 gateway=10.0.0.1
/ip service
set telnet disabled=yes
set ftp disabled=yes
set ssh disabled=yes
set api disabled=yes
set api-ssl disabled=yes
/routing bfd configuration
add disabled=no
/snmp
set contact=xxxxx enabled=yes location=NM trap-generators=\
start-trap,interfaces trap-interfaces=all trap-version=2
/system clock
set time-zone-name=Europe/Ljubljana
/system identity
set name=Klet
/system note
set show-at-login=no
/system ntp client
set enabled=yes
/system ntp client servers
add address=193.2.1.117
add address=193.2.1.92
Why do you have these set on cap ?
Since they show, it means it deviates from default settings.
antenna-gain=0
country=no_country_set
frequency-mode=manual-txpower
ssid=MikroTik
station-roaming=enabled
Especially that country setting is something I would look into.
That is the thing. On capsman the configuration for this cap has for example country set to my country. But when you go to the cap it’s like this. country=no_country_set
Can you open that setting on cap, make it blank and then fold the setting closed ?
It might be needed to disable caps mode first (I don’t have any legacy capsman installation anymore, so I can not check)
That should really make it “not set”. And then capsman config should be applied.
The thing is, normally when you see something in export, it means it deviates from default setting.
So that would mean it’s something which has been changed.
Since I see that country setting in your export, I assume it has been changed (probably unintentional but changed nonetheless).
Tnx. That helped. I thought the capsman would overwrite all the settings on the cap but I guess this is not the case.
No, it doesn’t and that is the beauty and problem with ROS.
There are situations where it might be needed to set something individually on a caps device in capsman mode, deviating from capsman settings.
And it is possible do so with ROS. A blessing but also a huge pitfall …
If you set your device via reset in caps mode, then this problem definitely does not occur. Everything is cleared and capsman settings will be applied.
For cases mentioned above, I use dedicated configs and provisioning rules so I know in 1 place where something is applied and why.
Thanks for the feedback. Others having the same problem might find it back this way.
The problem with using capsman is that checking config locally doesn’t actually have to reflect running values. One thing that CAPsMAN definitely doesn’t do is overwrite configuration stored on CAP devices. So running export doesn’t show any of CAPsMAN-provisioned settings. Running “monitor” command (in sections where it exists) might show actual state of “monitored” interface … but it might not show anything for CAPsMAN-controlled wireless interfaces. In wifi CAPsMAN environment, running monitor against cap interface shows running values:
# on CAP device
/interface/wifi/monitor [ find where name=wifi1 ] once
;;; managed by CAPsMAN BA:69:F4:20:A5:49%vlan-99, traffic
;;; processing on CAP
;;; mode: AP, SSID: mkxTestwAP, channel: 2412/ax
state: managed-by-capsman
# on CAPsMAN device:
/interface/wifi/monitor [ find where name=cap-wifi1 ] once
state: running
channel: 2412/ax
registered-peers: 0
authorized-peers: 0
tx-power: 23
channel-priorities: 0:2412/ax,0:2432/ax