Hi all,
I've 2 devices, an L009UiGS-2HaxD with CAPsMAN enabled with 2 cfg for 2ghz and 5Ghz 802.11ax radios and a C53UiG+5HPaxD2HPaxD with CAP client enabled.
The client connects to the capsman but no radio are listed in the proper section. The other strange thing is that on remote CAP i see the device connected but with no IP.
(on IP -> Neighbors i see that device with the IP, BTW these devices are on the same subnet)
Any idea on what's happening?
It's the 1st wifi-qcom and capsman configuration.
With past wireless and capsman i never seen this kind of problem.
CAPsMAN not working on 7.13.4
You do not have the required permissions to view the files attached to this post.
Re: CAPsMAN not working on 7.13.4
Have you tried clearing out all certificates ?
Re: CAPsMAN not working on 7.13.4
yes, I've tried also to leave default (blank) on Cert and CA fields with the same result.Have you tried clearing out all certificates ?
Question: the CAP client hasn't a cert and doesn't generate a new one. I've to create it manually and set on Wifi -> CAP settings?
Re: CAPsMAN not working on 7.13.4
Personally I don't use certificates.
I don't see the benefit from using it in my own LAN environment.
I don't see the benefit from using it in my own LAN environment.
Re: CAPsMAN not working on 7.13.4
me too but leaving blank the related fields or setting to "auto" makes no differences, the cert will be autogenerate (and i suppose used)Personally I don't use certificates.
I don't see the benefit from using it in my own LAN environment.
Re: CAPsMAN not working on 7.13.4
Last edited by fabio on Mon Feb 19, 2024 3:28 pm, edited 1 time in total.
Re: CAPsMAN not working on 7.13.4
There is no video attached (yet).please see the attached video.
Could you please share both configs of CAPS and of CAPsMAN?
Code: Select all
/export file=anynameyoulikeRe: CAPsMAN not working on 7.13.4
Main (L009UiGS-2HaxD):
AP1 (C53UiG+5HPaxD2HPaxD):
Code: Select all
# 2024-02-19 13:39:28 by RouterOS 7.13.4
#
# model = L009UiGS-2HaxD
/disk
set usb1 type=hardware
/interface bridge
add name=bridge-local
/interface ethernet
set [ find default-name=ether1 ] name=ether1
set [ find default-name=ether2 ] name=ether2
set [ find default-name=ether3 ] name=ether3
set [ find default-name=ether4 ] name=ether4
set [ find default-name=ether5 ] name=ether5
set [ find default-name=ether6 ] name=ether6
set [ find default-name=ether7 ] name=ether7
set [ find default-name=ether8 ] name=ether8
set [ find default-name=sfp1 ] name=sfp1-AP
/interface list
add exclude=dynamic name=discover
add name=mactel
add name=mac-winbox
add name=WANs
add name=LANs
/interface wifi channel
add band=2ghz-ax disabled=no name=channel1
/interface wifi datapath
add bridge=bridge-local disabled=no name=datapath1
/interface wifi security
add authentication-types=wpa3-psk disabled=no encryption=ccmp \
group-encryption=ccmp name=sec1
/interface wifi configuration
add channel=channel1 country=Switzerland datapath=datapath1 disabled=no mode=\
ap name=cfg1 security=sec1 ssid=Test1234
/port
set 0 name=serial0
/zerotier
set zt1 comment="ZeroTier Central controller - https://my.zerotier.com/" \
disabled=yes disabled=yes name=zt1 port=9993
/interface wifi
set [ find default-name=wifi1 ] configuration=*1 configuration.mode=ap
/interface bridge port
add bridge=bridge-local ingress-filtering=no interface=ether2
add bridge=bridge-local ingress-filtering=no interface=ether6
add bridge=bridge-local ingress-filtering=no interface=ether4
add bridge=bridge-local ingress-filtering=no interface=ether3
add bridge=bridge-local ingress-filtering=no interface=ether5
add bridge=bridge-local ingress-filtering=no interface=ether7
add bridge=bridge-local interface=ether8
add bridge=bridge-local interface=sfp1-AP
/interface detect-internet
set detect-interface-list=WANs internet-interface-list=WANs \
lan-interface-list=LANs wan-interface-list=WANs
/interface wifi cap
set certificate=request discovery-interfaces=bridge-local enabled=yes
/interface wifi capsman
set ca-certificate=auto certificate=auto enabled=yes interfaces=bridge-local \
package-path="" require-peer-certificate=no upgrade-policy=none
/ip address
add address=192.168.88.1/24 comment="default configuration" interface=\
bridge-local network=192.168.88.0
/system identity
set name=Main
/system logging
add topics=caps,debug
/system note
set show-at-login=no
/system routerboard settings
set enter-setup-on=delete-key
Code: Select all
# 2024-02-19 13:38:58 by RouterOS 7.13.4
#
# model = C53UiG+5HPaxD2HPaxD
/interface bridge
add name=bridge1
/zerotier
set zt1 comment="ZeroTier Central controller - https://my.zerotier.com/" \
disabled=yes disabled=yes name=zt1 port=9993
/interface bridge port
add bridge=bridge1 interface=ether5
add bridge=bridge1 interface=ether4
add bridge=bridge1 interface=ether3
add bridge=bridge1 interface=ether2
add bridge=bridge1 interface=ether1
/interface wifi cap
set certificate=request discovery-interfaces=bridge1 enabled=yes \
lock-to-caps-man=no
/interface wifi capsman
set package-path="" require-peer-certificate=no upgrade-policy=none
/ip dhcp-client
add interface=bridge1
/system identity
set name=AP1
/system logging
add topics=caps,debug
/system note
set show-at-login=no
Re: CAPsMAN not working on 7.13.4
L009:
/interface wifi
set [ find default-name=wifi1 ] configuration=*1 configuration.mode=ap
Where is the missing configuration ?
/interface wifi cap
set certificate=request discovery-interfaces=bridge-local enabled=yes
You can not enable caps mode on local interfaces for wave2 device. You need to configure them locally (using 90% the same settings as you would for capsman).
/interface wifi
set [ find default-name=wifi1 ] configuration=*1 configuration.mode=ap
Where is the missing configuration ?
/interface wifi cap
set certificate=request discovery-interfaces=bridge-local enabled=yes
You can not enable caps mode on local interfaces for wave2 device. You need to configure them locally (using 90% the same settings as you would for capsman).
Re: CAPsMAN not working on 7.13.4
I don't know, i've exported and cut only routes, dhcp-server, dns, etcL009:
/interface wifi
set [ find default-name=wifi1 ] configuration=*1 configuration.mode=ap
Where is the missing configuration ?
All steps done are shown in this video: https://youtu.be/LHnmF4_-Da0
Yes I agree, i've done it for seeing if there're differences between a remote cap client./interface wifi cap
set certificate=request discovery-interfaces=bridge-local enabled=yes
You can not enable caps mode on local interfaces for wave2 device. You need to configure them locally (using 90% the same settings as you would for capsman).
Re: CAPsMAN not working on 7.13.4
Tried also with 7.13.5 with no success
Re: CAPsMAN not working on 7.13.4
My suggestions:
1) disable CAP mode on main
2) apply cfg1 to interface wifi1 on main
3) disable detect internet on main
4) disable capsman on AP1
5) remove "certificate=request" on cap configuration of AP1
Probably, resetting AP1 to CAP mode is the best option (instead of points 4-5).
And please remember that L009UiGS does not have 5GHz radio, AFAIK.
1) disable CAP mode on main
2) apply cfg1 to interface wifi1 on main
3) disable detect internet on main
4) disable capsman on AP1
5) remove "certificate=request" on cap configuration of AP1
Probably, resetting AP1 to CAP mode is the best option (instead of points 4-5).
And please remember that L009UiGS does not have 5GHz radio, AFAIK.
Re: CAPsMAN not working on 7.13.4
Side note: the L009 is much less powerful than the hAP ax3. Have you considered to switch the two device roles?
Re: CAPsMAN not working on 7.13.4
to be honest i've already tried to switch role of 2 RBs with same result.Side note: the L009 is much less powerful than the hAP ax3. Have you considered to switch the two device roles?
I've done video and config dump when in the 2nd scenario but doesn't matter at the moment.
The main problem is that new wifi CAPsMAN is not working following official wiki.
Re: CAPsMAN not working on 7.13.4
Have you tried my suggestions 1-5? Can you post the full configs after you applied them?
Re: CAPsMAN not working on 7.13.4
done with no changesMy suggestions:
1) disable CAP mode on main
skipped because i'm not interested on L009 wifi2) apply cfg1 to interface wifi1 on main
why? internet detection is enabled on other interfaces different to local bridge3) disable detect internet on main
done, with no changes on capsman, no dynamic remote radio created.....4) disable capsman on AP1
5) remove "certificate=request" on cap configuration of AP1
Probably, resetting AP1 to CAP mode is the best option (instead of points 4-5).
Yes, it's only a 2.4 GHZ 802.11ax interface, but at the moment i'm not interested on using it. My goal is to make wifi-qcom CAPsMAN working for adding more HAP ax3 with one as CAPsMAN Main and other 2 pcs as CAP clients.And please remember that L009UiGS does not have 5GHz radio, AFAIK.
You do not have the required permissions to view the files attached to this post.
Re: CAPsMAN not working on 7.13.4
Main:Have you tried my suggestions 1-5? Can you post the full configs after you applied them?
Code: Select all
# 2024-02-20 09:58:59 by RouterOS 7.13.5
#
# model = L009UiGS-2HaxD
/interface wifi channel
add band=2ghz-ax disabled=no name=channel1
/interface wifi security
add authentication-types=wpa3-psk disabled=no encryption=ccmp \
group-encryption=ccmp name=sec1
/interface wifi
set [ find default-name=wifi1 ] configuration=*1 configuration.mode=ap
/interface wifi capsman
set ca-certificate=auto certificate=auto enabled=yes interfaces=bridge-local \
package-path="" require-peer-certificate=no upgrade-policy=none
/interface wifi configuration
add channel=channel1 country=Switzerland datapath=datapath1 disabled=no mode=\
ap name=cfg1 security=sec1 ssid=Test1234
/interface wifi datapath
add bridge=bridge-local disabled=no name=datapath1
Code: Select all
# 2024-02-20 09:57:37 by RouterOS 7.13.5
#
# model = C53UiG+5HPaxD2HPaxD
/interface bridge
add name=bridge1
/zerotier
set zt1 comment="ZeroTier Central controller - https://my.zerotier.com/" \
disabled=yes disabled=yes name=zt1 port=9993
/interface bridge port
add bridge=bridge1 interface=ether5
add bridge=bridge1 interface=ether4
add bridge=bridge1 interface=ether3
add bridge=bridge1 interface=ether2
add bridge=bridge1 interface=ether1
/interface wifi cap
set discovery-interfaces=bridge1 enabled=yes lock-to-caps-man=no
/interface wifi capsman
set package-path="" require-peer-certificate=no upgrade-policy=none
/ip dhcp-client
add interface=bridge1
/system clock
set time-zone-name=Europe/Rome
/system identity
set name=AP1
/system logging
add topics=caps,debug
/system note
set show-at-login=no
Re: CAPsMAN not working on 7.13.4
To properly troubleshoot problems it is often useful to reduce potential factors that interferes.
We are trying to help and I never got you were not interested in configuring wifi on L009.
My impression is that your config lacks of provisioning rules.
https://help.mikrotik.com/docs/display/ ... iFiCAPsMAN
We are trying to help and I never got you were not interested in configuring wifi on L009.
My impression is that your config lacks of provisioning rules.
https://help.mikrotik.com/docs/display/ ... iFiCAPsMAN
Re: CAPsMAN not working on 7.13.4
... which also raises the question:
why use capsman with only ONE Access point ??
why use capsman with only ONE Access point ??
Re: CAPsMAN not working on 7.13.4
I never told that this is the final scenario.... which also raises the question:
why use capsman with only ONE Access point ??
My final config has 3 x HAP ax3 and 1 x L009
Re: CAPsMAN not working on 7.13.4
Secondly, you probably missed the following part on the CAP:
Code: Select all
/interface/wifi/set wifi1,wifi2 configuration.manager=capsman-or-local
Re: CAPsMAN not working on 7.13.4
In that case you definitely need those provisioning rules and ideally even per radio mac address to steer correct frequency setting for each of those APs (other options also possible. I find MAC address to be the easiest way to be sure what goes where).I never told that this is the final scenario.
My final config has 3 x HAP ax3 and 1 x L009
PS official help pages do show all this.
Are you sure you are looking at the correct page ?
https://help.mikrotik.com/docs/display/ ... iFiCAPsMAN
Re: CAPsMAN not working on 7.13.4 [SOLVED]
Thanks, this was the missing element!Secondly, you probably missed the following part on the CAP:Code: Select all/interface/wifi/set wifi1,wifi2 configuration.manager=capsman-or-local
Since I've done all config in WinBox I've not found the proper section to assign wifi interfaces to capsman.
You do not have the required permissions to view the files attached to this post.
Re: CAPsMAN not working on 7.13.4
The 2nd tab when you open that interface.Since I've done all config in WinBox I've not found the proper section to assign wifi interfaces to capsman.
Configuration and then the field labeled Manager.
Re: CAPsMAN not working on 7.13.4
I've followed this page: https://help.mikrotik.com/docs/pages/vi ... Id=1409149In that case you definitely need those provisioning rules and ideally even per radio mac address to steer correct frequency setting for each of those APs (other options also possible. I find MAC address to be the easiest way to be sure what goes where).I never told that this is the final scenario.
My final config has 3 x HAP ax3 and 1 x L009
PS official help pages do show all this.
Are you sure you are looking at the correct page ?
https://help.mikrotik.com/docs/display/ ... iFiCAPsMAN
But I've done all steps with WinBox and missed to configure interface mode....
Thanks
Re: CAPsMAN not working on 7.13.4
The structure of the command gives you the hint about where the option is located. However, see https://www.youtube.com/watch?v=37aff6d14Xk minute 4.00 onwards.
Let me point out that you were following the wrong page (old CAPsMAN). The right help page is the one I linked before.
I warmly suggest you to reset to CAPS mode (same youtube video, at minute ~3.00) your future APs.
PS: You probably want to mark the topic as resolved.
Let me point out that you were following the wrong page (old CAPsMAN). The right help page is the one I linked before.
I warmly suggest you to reset to CAPS mode (same youtube video, at minute ~3.00) your future APs.
PS: You probably want to mark the topic as resolved.
Re: CAPsMAN not working on 7.13.4
You're right, I relied too much on the old capsman setup.The structure of the command gives you the hint about where the option is located. However, see https://www.youtube.com/watch?v=37aff6d14Xk minute 4.00 onwards.
Let me point out that you were following the wrong page (old CAPsMAN). The right help page is the one I linked before.
I warmly suggest you to reset to CAPS mode (same youtube video, at minute ~3.00) your future APs.
PS: You probably want to mark the topic as resolved.
Topic solved, and thanks again.
Re: CAPsMAN not working on 7.13.4
I just set up my first new Capsman (wifi-qcom) and found that when I set the configuration manager to capsman, when the radios provision, each caps controlled entry makes a second copy of the local radio entry, and the wifi radios never transmit. I even verified the /interface wifi print detail and the config is correct. The only way I was able to get it to work was to set the configuration explicitly to "local" and then reprovision the radios. At that point the ghost entries disappear and the radios work again.Secondly, you probably missed the following part on the CAP:Code: Select all/interface/wifi/set wifi1,wifi2 configuration.manager=capsman-or-local
Anyone have the same problem with duplicate radio entries and wifi not transmitting?
[Update]: I currently only have one CAP for evaluation, so I am running Capsman on the CAP.
Re: CAPsMAN not working on 7.13.4
Provisioning local radios via local capsman works differently. You use "/interface/wifi/radio/print" to lookup local radios, these are marked with "L". Usually 0 and 1. Then issue "/interface/wifi/radio/provision 0,1" and now your local radios are under local capsman control. This is AFAIK the correct way.
Re: CAPsMAN not working on 7.13.4
RadioProvisioning
CAPsMAN cannot manage it's own wifi interfaces using configuration.manager=capsman, it is enough to just set the same configuration profile on local interfaces manually as you would with provisioning rules, and the end result will be the same as if they were CAPs. That being said, it is also possible to provision local interfaces via /interface/wifi/radio menu, it should be noted that to regain control of local interfaces after provisioning, you will need to disable the matching provisioning rules and press "provision" again, which will return local interfaces to an unconfigured state.
Re: CAPsMAN not working on 7.13.4
THANK YOU!RadioProvisioningCAPsMAN cannot manage it's own wifi interfaces using configuration.manager=capsman, it is enough to just set the same configuration profile on local interfaces manually as you would with provisioning rules, and the end result will be the same as if they were CAPs. That being said, it is also possible to provision local interfaces via /interface/wifi/radio menu, it should be noted that to regain control of local interfaces after provisioning, you will need to disable the matching provisioning rules and press "provision" again, which will return local interfaces to an unconfigured state.
Well, that's why I missed it. Foolish me read the CAPSMAN documentation. I should have been reading the WiFi documentation.
What is important is that I have Capsman/Caps set up so the router shows up under the wifi->steering->neighbor groups for roaming. And I found that it indeed does even if the radios are not directly controlled by Capsman.
Who is online
Users browsing this forum: No registered users and 7 guests