Properties of the CAP interface seem to differ from the actual interface.
E.g. for my 2.4 Ghz network I have a configuration that customizes band to 2ghz-onlyn. When I print this interface on the actual device it says that it is managed by CAPsMAN, but the band is 2ghz-b/g/n.
Why is that?
I’m on 6.49.2
CAPsMAN doesn’t actually write configuration on CAPs. While CAP is being controlled by CAPsMAN, the only relevant configuration, aside from antenna-gain, is “/interface wireless cap”, everything else should be checked under CAPsMAN.
I meant configuration of wireless interfaces, not configuration in general. All wireless interface configuration is done on CAPsMAN, not on individual CAPs
On my CAPsMAN I configured channel (/caps-man channel) to be 2ghz-onlyn. I then added a CAP interface (/caps-man interface) for a different AP. While this results in CAP interface being propagated onto that AP, the channel options are not applied which I verified via /interface wireless print on that AP:
CAPsMAN:
/caps-man interface print detail
name=“…” mac-address=… arp-timeout=auto
radio-mac=… master-interface=none
radio-name=“…” configuration=Matryoshka 2.4Ghz
security=Matryoshka datapath=Matryoshka mtu=1500 l2mtu=1600 arp=enabled
channel=Matryoshka 2.4Ghz channel.tx-power=20
current-state=“running-ap” current-channel=“2427/20-Ce/gn(20dBm)”
current-rate-set=“CCK:1-11 OFDM:6-54 BW:1x-2x SGI:1x-2x HT:0-15”
current-basic-rate-set=“OFDM:6 BW:1x HT:0-7”
current-registered-clients=4 current-authorized-clients=4/caps-man configuration print detail
name=“Matryoshka 2.4Ghz” mode=ap ssid=“Matryoshka” country=united states3
installation=any disconnect-timeout=10s security=Matryoshka
datapath=Matryoshka channel=Matryoshka 2.4Ghz/caps-man channel print detail
name=“Matryoshka 2.4Ghz” control-channel-width=20mhz band=2ghz-onlyn
extension-channel=XX reselect-interval=1h skip-dfs-channels=no
CAP:
/interface wireless print
;;; managed by CAPsMAN
;;; channel: 2427/20-Ce/gn(20dBm), SSID: Matryoshka, local forwarding
name=“wlan1” mtu=1500 l2mtu=1600 mac-address=…
arp=enabled interface-type=Atheros AR9300 mode=ap-bridge
ssid=“MikroTik-3790B5” frequency=auto band=2ghz-b/g/n
channel-width=20/40mhz-Ce secondary-frequency=“” scan-list=default
wireless-protocol=802.11 vlan-mode=no-tag vlan-id=1 wds-mode=disabled
wds-default-bridge=none wds-ignore-ssid=no bridge-mode=enabled
default-authentication=yes default-forwarding=yes default-ap-tx-limit=0
default-client-tx-limit=0 hide-ssid=no security-profile=default
compression=no
Do I understand correctly that most of the data printed on CAP is noise and is not actually used?
Yes, the only relevant information from printout made on cAP is the comment section, the rest is all noise in this context.
Is there a different place to look for applied config on cap?
What’s the problem ?
You don’t trust what capsman does ?
I want to be sure how the configuration is actually applied.
Answer is in 2nd post.
Some settings are not visible on CAPsMAN, e.g. ampdu-priorities. I assume that there can be values that are not be applicable as-is on the actual chip and some close-enough values get actually picked instead. There may be a situation when there is no access to CAPsMAN as well.
I believe there is value in seeing what’s actually being applied on the device from within the device.
There are indeed some (low-level advanced) settings which can not be set via CAPsMAN and those will be taken from device in question. But you have to hand-pick those from print outs made on device … whatever can be set via CAPsMAN will be set by CAPsMAN and if not set explicitly in CAPsMAN config it’ll use own defaults (which may or may not be same as device’s defaults).
If CAP looses connection to CAPsMAN, then it quickly disables managed wireless interface(s).
But then if you really have to dwell into those advanced low-level settings and monitoring, perhaps using CAPsMAN is not warranted any more?
Immutable entries (e.g. dynamic) do exist on RouterOS, so I don’t quite understand why not go the extra mile and show the complete list of applied configuration on a CAP.
But then if you really have to dwell into those advanced low-level settings and monitoring, perhaps using CAPsMAN is not warranted any more?
CAPsMAN is not “high level” in terms of configuration, it’s actually harder than configuring “plain” wireless interfaces. But it’s convenient: config management, forwarding, upgrades, access lists etc.