I’ve seen ton of post about Mikrotik wifi equipment, yet I’ve decided to give it a shot.
I’ve got a ton of Samsung “smartthing” equipment that worked ok with previous TP Link Omada (EAP 670)
I’m extremely disappointed with this “cap ax”
CCR2004 as main router with wifi-qcom package (replaced wireless package)
CRS as POE switch, it just… switches (no qcom package here)
caps (they come with new packages preinstalled)
So assume my config is exactly the same as linked one
Result:
android samsung phones, laptops - connect
no other samsung “smart device” connects (fridge etc.)
yes yes: I have a separate profile without WPA3, they reside on 2.4Ghz N band only (like the “guest” from linked example)
all the CCR logs say is repeated every second:
dhcp_iot deassigned 192.168.60.209 for 40:CA:63:72:7C:B9 Samsung-Oven
dhcp_iot assigned 192.168.60.209 for 40:CA:63:72:7C:B9 Samsung-Oven
40:CA:63:72:7C:B9@cap-wifi2-virtual4 disconnected, connection lost, signal strength -49
I’ve pinned this to be concerned with ‘security’ only issue as exposing open network results in some devices (tested on one cause I have too many of them to f&*^% go one by one) connecting ok.
How to make these devices connect? I cannot imagine that they won’t work
Where do I even look for meaningful logs (debug tag doesn’t add ANY value - seriously wtf Mikrotik?!)
I haven`t had the pleasure to work with Samsung IOT-Devices yet…
But I had my fair share of IOT connectivity issues…
I don`t have a lot of Information on your System…
If I had to diagnose the Issue, I would configure a cAPax as a basic AP.
Same SSID and Password, but nothing else (Virtual-Interfaces / Slave-Interface, VLAN, AccessList, etc)
Furthermore If possible, also provide a unrestricted Internet-Access to the Network.
If you are comfortable with RouterOS / Mikrotik, it is a quick and easy way to Isolate the Issue.
I don’t know if that will help, what i found with the newest Samsung Smart TV is the settings for fast Roaming FT,
as long i have switch off that, all working good
Well, on my armbian boards I get “wpa_supplicant[647]: FT: Invalid key management type (2)” and fails to use ft (tested built in Chinese wifi chip and My Mediatek usb sticks). Also Im pretty sure my Samsung Galaxy tab S9 FE+ does support ft (haven’t verified), but fails to use it (the same as armbian), meanwhile S22 is fine. Still testing, but it seems that ft does have issues and is causing at least some part of disconnects and connectivity problems in general on 5ghz radios. I do use my wap ax to test connection to my home network, 2.4ghz bands connection is fine overall, can use ft or whatever I want and connection holds. 5ghz band is a different story - it drops at least once daily whit reason code 3 if ft is on. Whit out ft I tested connection over 3 days and it was fine.
Same here with rb5009 and two cAPax … enabling ft for 5GHz ends in disconnections of Devices like Samsung TV for example.
But on the Samsung TV I have observed the following when ft=on. I have one SSID for 2.4GHz and 5GHz on two cAPs … with ft=on I suddenly see my SSID twice on the TV (1x with the note 5GHz) and he wants again the (allready known) wifi password … with ft=off I see, as normal, my SSID only once ?
Maybe you could connect devices that support roaming to a virtual AP where ft=on and the master interface is ft=off for all devices that do not support it ?
You can create virtual SSIDs whit different security settings and you most likely see two SSIDs because security settings have changed. Important thing to remember - security change on SSID may require you to reconnect device (forget network and enter password again).
Btw wap ax whit out ft still got reason code 3 today, so removing ft is not a complete fix. It does help thru.
There is a difference in the two screenshots. No visible equals unset, while ft=no it is explicitly set. As “no” is default, the result will be the same.
Not really, that is a view on a part of the configuration that you believe is related, there could be other settings elsewhere, seemingly unrelated, that could cause the connection problem.
It is also worth checking what frequency the 5G is running on. I have experienced similar issues of not being able to see SSID, because router os decided to use higher frequency (5800+) due to surrounding noise.
In that instance i could see the ssid from phone but not from laptop.
When i manually set to lower frequency, equivalent to 36-40 band (cant remember exact numbers), i was able to see the ssid when scanning.
Not all devices are able to use full 5g frequency range.