Stuart Prescott wrote:
 <rant>Long story... when I was setting this system up that was the recommended way to do it. It worked really well for me. Then the wpa_supplicant maintainers changed their minds...I was similarly pissed about the change. I didn't notice the change until I had upgraded all of my boxes and, by that time, the /etc/init.d script for wpasupplicant had vanished without a trace and I started cleaning my guns and looking up the names of the wpa-supplicant maintainers. :) Fortunately (for them *and* me), I was able to find an earlier wpa-supplicant in /var/cache/apt/archives, installed it, made safe copies of my beloved /etc/init.d/wpa* and /etc/wpa* scripts and confs, then re-upgraded, and *then* fixed the scripts all back to how they're supposed to work.
I forget why they changed it. I think it was to make it more compatible with kwifimanager or something like that. Likewise, I don't remember exactly why I concluded that the new method was unsuitable for my needs at the time. (I *think* it was because I wanted my laptop to automatically associate with any open AP if it didn't see any of the ones I told it about). I do remember that several other people were asking "WTF?" because they were in the same boat as me.
Perhaps someone here on the list can fill us in on if the "new way" of wpasupplicant has finally become accessible to those of us who had problems with it right after the change....
Description: S/MIME Cryptographic Signature