agbagb wrote: > That's interesting - I'm not sure of correct terminology, but are you > saying that getting the router to use a static IP (instead of an > DHCP-allocated and changing one....) has enabled a steady Radio > connection even on WiFi6 kit?
No, not exactly. While I am a proponent of assigning a static IP to the LMS server machine, what I was referring to was binding a wireless client to a particular AP in extender, media bridge, roaming or mesh environments. What we initially experienced, not just with the SB Radio, but with other legacy 2.4 Ghz clients as well, is that the connection would drop, either on the initial optimization phase, when the system assigns each client to its optimal AP, and during the handoff phase, when a system transfers a client from one AP or node to another. Either the AP and/or the client chipsets cant handle that handshake routine, either initially or on renegotiation, and the connection would drop. What I found solved the problem (for us) in these multi AP environments was binding those clients to the main wireless router. That is done on the AP side, at the router or DHCP server, and it forces a continuing static connection to that AP, and that AP alone, with no roaming, handoff, or renegotiation events, and the backhaul and repeater links are also completely removed from the equation. Ideally, the client should be bound to the router AP if the router is equipped with one. It is a much simpler connection in more complicated wireless environments (with increasingly diverse traffic). Not all roaming, extender-equipped, and mesh equipment supports wireless client binding. And if you are already running a single AP wireless network, it is inapplicable. And we were unable to pull this off for one fringe range Touch where binding to the router AP was impractical, and even a bound connection to the nearest node would inevitably drop. In that extreme situation, the solution was an EX2700 extender operating as a media bridge, where the Touch enjoys an ethernet connection, and the wireless network sees only an N protocol client (which presents no problem). ------------------------------------------------------------------------ sgmlaw's Profile: http://forums.slimdevices.com/member.php?userid=13995 View this thread: http://forums.slimdevices.com/showthread.php?t=109953
_______________________________________________ Radio mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/radio
