RAX43 fast roaming

Thx for the reply.    Issues are that the camera was working fine for many months.  Dropped out once in a while…maybe 2-3 times.   it now will not stay connected.  I have done a complete reset of the camera and a delete/reinstall of the Circleview camera in HomeKit and it drops out (says “no response”) after less than a day?   Apple suggested installing from another device, which I have done and still not staying connected to WiFi. 
The “they” I referenced in my post, was Logitech (the manufacturer of the camera).   I read in one of their forums to try turning off fast roaming, then test to see if it works. 
can’t find a where to turn off in RAX 43 settings?

---

michaelkenward wrote:

Can I turn off “fast roaming”? 

---

That's not something you'll find mentioned in most Netgear manuals. Perhaps it goes under another name.

---

Amazing what ideas certain communities are bringing up 8-) Think about what fast roaming is, and what it is good for. Fast Roaming is == Fast BSS transition (802.11r). "802.11r streamlines the authentication process using a feature called Fast BSS Transition (FT) when your device roams from one AP to another on the same network. FT allows the devices to associate with APs more quickly."

Before 802.11r could take an advantage (for the wireless client) must understand much more what is going up around it.

Are we talking about a simple Circle View Camera (pure 2.4 GHz if I'm not wrong), or a Circle View Doorbell Camera (dual-band 2.4 & 5 GHz) - both non-moving, static mounted devices? And a single RAX43 Wi-Fi router? Assuming we face a capable Wi-Fi Client, one that does support both bands, the radio measurement (802.11k) feature of the client might come into play.

"802.11k allows these devices to quickly identify nearby access points that are available for roaming. When the signal strength of the current AP weakens and your device needs to roam to a new one, the device already knows which access point offers the best connection. ... A roam scan is the process used by a device to check for access points that support the currently associated ESSID."

What could cause this situation? Probably some interference on the 5 GHz band lowering the connection quality massively, but hey the Circle View Camera is 2.4 GHz only.

Granted, there might be some Netgear WiFi Repeater, or for the sake also an Orbi system on air, also announcing their presence by the wireless network management (802.11v)

"802.11v provides additional information about nearby access points that could be optimal candidates to join. When a device must roam, the BSS transition data (supplied by the network) is reviewed so the device can quickly determine which access points are best for roaming."

Still in doubt and think something needs to be disabled on the RAX43?

Much more I suspect the 2.4 GHz band - in case of a client does not remain associated - should be evaluated, look for less used channel (don't forget there is not much of a choice, in the FCC regulatory channels 1-5/6-11, and keep in mind there are services in this band which are not easily visible in a Wi-Fi analyzer).

Correct Razor512: crappy IoT don't love 802.11r!

In the case of Netgear and most routers, functions like band steering and others are selectively applied based on the reported capabilities of the device. During the authentication, the client device will provide details about what is supported.

For example, here (pasted at the bottom of this reply) are the capabilities detected from my laptop connecting to the network.
The AP will then take that into account when deciding on things such as band steering, for example, the AP will not attempt to bandsteer the device to the 6GHz band, as as that would simply fail, but it will have no issue moving it between the 2.4GHz and 5GHz band. Overall the WiFi router will try to avoid using functions with a client that doesn't list it as a capability, though features that result in certain frames being sent to all clients regardless of capability, can lead to other issues.
The ones most likely to cause issues with clients are WPA 2+3 , as well as 802.11r, and some clients may only exhibit issues when both WPA 2+3 and 802.11r are both in use at the same time, for example, with some older Foscam branded cameras

flags 0x8d1e03a: WME N_CAP VHT_CAP HE_CAP AMPDU AMSDU GBL_RCLASS MBO_CAP
HT caps 0x9e7: LDPC 40MHz SGI20 SGI40 STBC-Tx STBC-Rx
VHT caps 0x5f: LDPC SGI80 SGI160 STBC-Tx STBC-Rx SU-BFE
HE caps 0x66a9: LDPC HE-HTC SU&MU-BFE
OMI 0x0259: 160Mhz rx=2ss tx=2ss ER_SU_DISABLE

MCS SET : [ 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 ]
VHT SET : 0x1 1x1 2x1 3x1 4x1 5x1 6x1 7x1 8x1 9x1
: 0x2 1x2 2x2 3x2 4x2 5x2 6x2 7x2 8x2 9x2
HE SET :
20/40/80 MHz:
NSS1 Tx: 0-11 Rx: 0-11
NSS2 Tx: 0-11 Rx: 0-11
160 MHz:
NSS1 Tx: 0-11 Rx: 0-11
NSS2 Tx: 0-11 Rx: 0-11
smoothed rssi: -54
tx nrate
he mcs 10 Nss 2 Tx Exp 0 bw160 ldpc 2xLTF GI 0.8us auto
rx nrate
he mcs 7 Nss 2 Tx Exp 0 bw160 ldpc 2xLTF GI 0.8us auto
wnm
0x101: BSS-Transition Notification
link bandwidth = 160 MHZ
RRM capability = 0x72 Neighbor_Report Beacon_Passive Beacon_Active Beacon_Table
Frequency Bands Supported: 2.4G 5G