Moved from caps-man 1 to the newer version that supports WiFi6 and wAP AX units.
Have VLANs working on different SSIDs and still use and access control list to allow different passwords to land you in a different VLAN.
Most stuff is working and working decently.
However I have a few devices that just won’t connect at all.
If I swap back to other manufactures… same SSID and Password. They connect no problem.
So what log entries do i need to enable to show me why my Lenox thermostats won’t connect.
Wireless + Debug gives some info. Any difference in security settings?
Nope… I have 6 different WiFi vendors set up with the same settings. I swap between them all the time.
Mikrotik’s recommends turning off fast transition and wifi 6.
(I should have seen that coming.)
Probably gonna end up in the box for a few firmware updates.
You might want to give v7.18RC1 a try.
I would have to move the caps-controller off my router. Not that big a deal but I would need to rebuild on a router and make it a controller only.
Just use a wAP AX for this, CAPsMAN is not resource intensive.
I had a 960 I have configured as a switch.
Copy pasted my config off my router to 960 after putting the RC on it. (Annoying that is doesn't move passwords)
Enabled caps-man and both wAP AX connected.
Turned off wifi6 and ft.
Turned on wifi 6.
Turned on FT.
Sent support file to Mikrotik.
mkx
February 21, 2025, 12:39pm
9
The fact is that some clients barf on seeing some feature bits set … even if they don’t know about them. And will refuse to connect.
The other day I had to use wifi on an old laptop (has Intel Centrino WiFi supporting abgn). It wouldn’t connect to my WiFi APs until I created slave SSID with only WPA2 enabled and without any FT features. So the problem is essentially identical to what you see with thermostats.
I don’t blame MT for it though.
Mkx
With the stable release… Turning on WiFi 6 prevented the thermostats from connecting. Need to go back and check that later today.
I’ll have 50 quid on FT, as far as I am aware nothing has changed even into the later beta versions where devices refuse to connect with FT enabled.
Edit: Or to be pedantic, since FT arrived!
I’ll have 50 quid on FT, as far as I am aware nothing has changed even into the later beta versions where devices refuse to connect with FT enabled.
Edit: Or to be pedantic, since FT arrived!
Offending devices are usually only using 2GHz bands.
mkx
February 21, 2025, 6:44pm
13
Mine is dual-band device … I created that “backwards compatibke” virtual SSID on 5GHz radio and device was happy with that.