From the screenshots above, your capsman has selected invalid channels. Devices will not generally find these non standard channels. We have had this happen sometimes and the result is that only macbook pros are able to connect up to the wireless on the non standard channel and no phones or other laptops or tablets seem to work.I'm still struggling here.
Thanks for taking the time to answer, but I think you got it wrong.Devices will not generally find these non standard channels.
I know the CAPsMAN interface doesn't have the R beside it, but it won't show as running with nobody connected. I haven't actually tested with an RF meter, but with no clients connected it might be in a low power mode where all it does is beacon from time to time and listen for client connections. It could also be that the wrong channel selection is causing it to not transmit at all.It's not a matter of transmitting in the wrong channel/wrong standard. The HackRF + PortaPack photo shows it's not even transmitting AT ALL. It's completely blue (pure noise), whereas any signal should be green. And there's no signal at all except for my neighbours' 5G routers in the lower part of the spectrum. :(
I suspect those are probably beacons. MikroTik has never added support for choosing the beacon interval and that makes me suspect it could potentially be random.The spectrum analyzer though, detects some short blips on the primary frequency (it chose 5550/20 and 5660/80 this time) every few seconds. Very faint, very short, kinda semi-randomly spaced in time.
# apr/09/2021 01:02:06 by RouterOS 6.48.1 # software id = H4EN-32RB # # model = RB4011iGS+5HacQ2HnD # serial number = 96890A123C45 /caps-man channel add band=5ghz-n/ac control-channel-width=20mhz extension-channel=Ceee \ frequency=5170,5190,5230,5270,5310,5510,5550,5590,5630,5660,5755,5795 \ name=5GHz-n-ac secondary-frequency=\ 5170,5190,5230,5270,5310,5510,5550,5590,5630,5660,5755,5795 /caps-man security add authentication-types=wpa2-psk encryption=aes-ccm group-encryption=aes-ccm \ name=security /caps-man configuration add channel.band=2ghz-b/g/n channel.control-channel-width=20mhz \ channel.extension-channel=XX country=brazil-anatel \ datapath.client-to-client-forwarding=yes datapath.local-forwarding=yes \ name=cfg-2ghz security=security ssid=Bifrost add channel=5GHz-n-ac country=brazil-anatel \ datapath.client-to-client-forwarding=yes datapath.local-forwarding=yes \ name=cfg-5ghz-ac security=security ssid=Bifrost add channel=5GHz-n-ac country=brazil-anatel \ datapath.client-to-client-forwarding=yes datapath.local-forwarding=yes \ name=cfg-5ghz-an security=security ssid=Bifrost /caps-man manager set enabled=yes /caps-man manager interface set [ find default=yes ] forbid=yes add disabled=no interface=bridge /caps-man provisioning add action=create-dynamic-enabled hw-supported-modes=gn master-configuration=\ cfg-2ghz name-format=prefix-identity name-prefix=2ghz add action=create-dynamic-enabled hw-supported-modes=ac master-configuration=\ cfg-5ghz-ac name-format=prefix-identity name-prefix=5ghz-ac add action=create-dynamic-enabled hw-supported-modes=an master-configuration=\ cfg-5ghz-an name-format=prefix-identity name-prefix=5ghz-an
Clear the entire secondary-frequency and frequency list, so that when you export, you only get this for caps-man channel:
/caps-man channel add band=5ghz-n/ac control-channel-width=20mhz extension-channel=Ceee \ frequency=5170,5190,5230,5270,5310,5510,5550,5590,5630,5660,5755,5795 \ name=5GHz-n-ac secondary-frequency=\ 5170,5190,5230,5270,5310,5510,5550,5590,5630,5660,5755,5795
/caps-man channel add band=5ghz-n/ac control-channel-width=20mhz extension-channel=Ceee name=5GHz-n-ac
No, it isn't exactly the same as how it was in the beginning:That is how it was in the beginning (config.rsc is attached in the first post).
Try upgrading RouterOS and also make sure that your routerboard firmware is upgraded via system->routerboard. Then, check to make sure the Upgrade Firmware is the same as the Current Firmware. If they are not, then click the button to upgrade the firmware and reboot.Wait, maybe I have some beacons, but they are extremely weak and curiously not really centered around the same frequency (maybe 5MHz for this or that side randomly), but this could be just noise.
If you reset it and it is working now without CAPsMAN you can try reapplying the most recent capsman config (the one after the edits we were making should work fine) and enabling that and see what happens. Make sure to set extension channel to Ceee or Ce or none (depending on what channel size you want).Forgot to tell you that they're up to date since day one, Rboard fw included!
I also changed the forbid thing. It was in Mikrotik's "example tutorial". I think it doesn't change much is your don't have another CAPsMAN on the network. But it's allowed now.
What cap device are you using and what frequency has it selected on 5GHz?The problem is that the router (the CAPs Manager) is now working with this new CAPsMAN config we came to, but the CAP itself isn't (again, only the 5Ghz network).
Is the routerboot firmware upgraded in the CAP as well? That is sometimes important depending on what frequency it chooses. Ideally disable the secondary frequency - most people don't really need 160MHz and it can cause issues, 80MHz is fine.I'm running two RB4011iGS+5HacQ2HnD-IN, one as CAPsMAN and the other as CAP.
It was way cheaper then buying a switch and a wireless-capable device, and saved me a lot of space and cables/wires.
CAPsMAN is running 5500/20-Ceee/ac/DP(15dBm)+5770/80(15dBm). Seems to be working.
CAP is running 5740/20-Ceee/ac(15dBm)+5610/80/DP(15dBm). No clients connected, and I'm sitting right next to it and can't find it in my Android Wi-Fi Analyser.
Both of those are outdoor frequencies, at least in many countries - in the CAPsMAN->Configurations tab, double click on your config, and make sure the country is properly set, and installation is set to "indoor".It's been at least 5 minutes they both finished the radar scanning and are "running ap".
# apr/10/2021 23:23:26 by RouterOS 6.48.1 # software id = 0FDY-HJ9L # # model = RB4011iGS+5HacQ2HnD # serial number = 96890A3CEFEB /interface bridge add admin-mac=74:4D:28:4A:FE:6A auto-mac=no comment=defconf name=bridgeLocal /interface wireless # managed by CAPsMAN set [ find default-name=wlan1 ] ssid=MikroTik # managed by CAPsMAN # channel: 2412/20-Ce/gn/P(17dBm), SSID: Bifrost, local forwarding set [ find default-name=wlan2 ] disabled=no ssid=MikroTik /interface ethernet switch port set 0 default-vlan-id=0 set 1 default-vlan-id=0 set 2 default-vlan-id=0 set 3 default-vlan-id=0 set 4 default-vlan-id=0 set 5 default-vlan-id=0 set 6 default-vlan-id=0 set 7 default-vlan-id=0 set 8 default-vlan-id=0 set 9 default-vlan-id=0 set 10 default-vlan-id=0 set 11 default-vlan-id=0 /interface wireless security-profiles set [ find default=yes ] supplicant-identity=MikroTik /interface bridge port add bridge=bridgeLocal comment=defconf interface=ether1 add bridge=bridgeLocal comment=defconf interface=ether2 add bridge=bridgeLocal comment=defconf interface=ether3 add bridge=bridgeLocal comment=defconf interface=ether4 add bridge=bridgeLocal comment=defconf interface=ether5 add bridge=bridgeLocal comment=defconf interface=ether6 add bridge=bridgeLocal comment=defconf interface=ether7 add bridge=bridgeLocal comment=defconf interface=ether8 add bridge=bridgeLocal comment=defconf interface=ether9 add bridge=bridgeLocal comment=defconf interface=ether10 add bridge=bridgeLocal comment=defconf interface=sfp-sfpplus1 /interface wireless cap # set bridge=bridgeLocal discovery-interfaces=bridgeLocal enabled=yes \ interfaces=wlan1,wlan2 /ip dhcp-client add comment=defconf disabled=no interface=bridgeLocal /system clock set time-zone-name=America/Bahia /system identity set name=Himinbjorg /system leds add interface=wlan2 leds="wlan2_signal1-led,wlan2_signal2-led,wlan2_signal3-le\ d,wlan2_signal4-led,wlan2_signal5-led" type=wireless-signal-strength add interface=wlan2 leds=wlan2_tx-led type=interface-transmit add interface=wlan2 leds=wlan2_rx-led type=interface-receive
You are still using secondary channels and probably don't need to be.I'll keep an eye on this, and if they ever stop working again, I'll check out their frequencies and post here again.
But I'd really like to understand what was going on...
But the weirdest part is that without CAPsMAN, I never seemed to have problems with the 5GHz band.[admin@Main_GW] > in wire info country-info brazil-anatel
[admin@Main_GW] > in wire info country-info brazil-922
[admin@Main_GW] > in wire info country-info "brazil direct"
It is not too surprising to me unfortunately. It seems that CAPsMAN is not quite as smart as the regular wireless setup when it comes to only selecting channels that will be supported by the devices. For instance, I have never had a single problem with the extension channel XXXX setting when not using CAPsMAN, but when using CAPsMAN on auto if I have extension channel set to XXXX it will sometimes choose frequencies that are offset from the proper ones so that devices will never find them (ex. 80MHz channel offset by 20 or 40MHz from where it is supposed to be). For whatever reason that doesn't seem to happen when I set Ceee with CAPsMAN instead. When I am not using CAPsMAN, I use XXXX instead of Ceee, but I only use Ceee with CAPsMAN due to these issues.But the weirdest part is that without CAPsMAN, I never seemed to have problems with the 5GHz band.
[admin@Michael-RB4011] > in wireless info country-info brazil ranges: 5170-5250/a,an20,an40,ac20,ac40,ac80,ac160,ac80+80(20dBm)/passive,indoor 5250-5330/a,an20,an40,ac20,ac40,ac80,ac160,ac80+80(20dBm)/dfs,passive 5490-5710/a,an20,an40,ac20,ac40,ac80,ac160,ac80+80(30dBm)/dfs,passive 5190-5230/a-turbo(20dBm)/dfs,indoor 5740-5820/a-turbo(30dBm)/outdoor 5180-5220/a-turbo(20dBm)/dfs,indoor 5745-5825/a-turbo(30dBm)/dfs,outdoor 2402-2482/b,g,gn20,gn40(30dBm)/passive 2417-2457/g-turbo(30dBm) 5730-5845/a,an20,an40,ac20,ac40,ac80,ac160,ac80+80(30dBm)/outdoor 907-932/b,g,g-turbo,gn20,gn40(30dBm) [admin@Michael-RB4011] > in wireless info country-info brazil-anatel ranges: 2402-2482/b,g,gn20,gn40(20dBm)/passive 5490-5710/a,an20,an40,ac20,ac40,ac80,ac160,ac80+80(15dBm)/dfs,passive 5730-5845/a,an20,an40,ac20,ac40,ac80,ac160,ac80+80(15dBm)/outdoor 900-910/b,g,g-turbo,gn20,gn40(30dBm) 913-928/b,g,g-turbo,gn20,gn40(30dBm) 915-928/b,g,g-turbo,gn20,gn40(30dBm)