Hi, > What did the 3.0.y kernel do instead? Kernel 3.0.0 does not garble the essid upon ifdown. > It looks to me like the ESSID gets reset to "intranet" once it is time to > associate. Could you further explain the symptoms and how they differ > from the expected behavior? Nagh, it's not clear to me what happens. I did six sessions: Both with kernels 3.0.0 and 3.1.5, both with wep and wpa, and the wpa sessions both with "low level" tools and with ifup/ifdown. I found the iw commands were not supported -- maybe a driver specificum or something that goes beyond the limits of my experience. In summary: kernel 3.0.0, WEP, iwconfig: works kernel 3.0.0, WPA, iwconfig: works kernel 3.0.0, WPA, ifupdown: works kernel 3.1.5, WEP, iwconfig: works kernel 3.1.5, WPA, iwconfig: works! kernel 3.1.5, WPA, ifupdown: garbeld essid problem So in the end it looks like if the manner of ifdown to bring the interface down somehow conflicts with the 3.1.5 version of the ipw2200 driver. Find attached the six sessions, corresponding sylogs with iw event enabled, dmesgs of both kernels and corresponding kernel configs. Regards, Manuel -- Hintergasse 2, 37345 Silkerode Fon: +49 36072 88982 Mobil: +49 151 58822651 IM: myops@jabber.org
Attachment:
wep-session-3.0.0
Description: Binary data
Attachment:
syslog-wep-session-3.0.0
Description: Binary data
Attachment:
wpa-session-3.0.0
Description: Binary data
Attachment:
syslog-wpa-session-3.0.0
Description: Binary data
Attachment:
syslog-wpa-session-ifupdown-3.0.0
Description: Binary data
Attachment:
syslog-wpa-session-ifupdown-3.0.0
Description: Binary data