From bea2dd5a061bf4e23b170c12c52f0e02f56c2aa6 Mon Sep 17 00:00:00 2001 From: sam Date: Fri, 2 Nov 2007 05:11:45 +0000 Subject: don't try to re-associate after a parameter change, too many ap's don't do this right; instead go to the scan cache so we pass through auth state (if the cache is warm we can do this w/o an actual scan) MFC after: 1 week --- sys/net80211/ieee80211_proto.c | 12 +----------- 1 file changed, 1 insertion(+), 11 deletions(-) (limited to 'sys/net80211') diff --git a/sys/net80211/ieee80211_proto.c b/sys/net80211/ieee80211_proto.c index 8c9f7c2..8e4df65 100644 --- a/sys/net80211/ieee80211_proto.c +++ b/sys/net80211/ieee80211_proto.c @@ -905,17 +905,7 @@ ieee80211_init(struct ieee80211com *ic, int forcescan) */ if (ic->ic_roaming != IEEE80211_ROAMING_MANUAL) { if (ic->ic_opmode == IEEE80211_M_STA) { - /* - * Try to be intelligent about clocking the state - * machine. If we're currently in RUN state then - * we should be able to apply any new state/parameters - * simply by re-associating. Otherwise we need to - * re-scan to select an appropriate ap. - */ - if (ic->ic_state != IEEE80211_S_RUN || forcescan) - ieee80211_new_state(ic, IEEE80211_S_SCAN, 0); - else - ieee80211_new_state(ic, IEEE80211_S_ASSOC, 1); + ieee80211_new_state(ic, IEEE80211_S_SCAN, 0); } else { /* * For monitor+wds modes there's nothing to do but -- cgit v1.1