Hello Michael! > I think this is desired behavior. Yes. > We voluntarily associated with the > "test" AP on channel 4. Yes this is correct because IEEE80211_IBSS_AUTO_CHANNEL_SEL flag was set. > Who says that we want to assoc to the "test" ssid on channel 11? Because this setting is now outdated. The channel is set to 11 and the IEEE80211_IBSS_AUTO_CHANNEL_SEL flag is clear. If we now set the SSID to test again, we assoc to "test" on channel 11. Do not recover from the channel set automatically, is a broken behavior, I think. > This is a > policy decision and such policy > doesn't belong into the kernel. Userspace can initiate a reassociation > after the channel change, > if the AP switch is desired. > There are good reasons to leave roaming decisions in userspace, because > these decisions are simply very > complex and would put lots of policy into the kernel or require lots of > kernel API. I think the basic functionality should work without any userspace daemon. All the that can be implemented without real problems with a few lines of code. This would better for embedded systems, if we don't need the wpa_supplicant for an unencrypted network, or so. Regards Alina -- Computer Bild Tarifsieger! GMX FreeDSL - Telefonanschluss + DSL für nur 17,95 ¿/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
