I am having the devil of a time getting my aironet 350 to work again. I have a linux thinkpad and and for some time all worked well at my job location. One day it didn't. I have found that if I use ACU, I cannot associate with an AP so no authentication can take place. However, if I use iwconfig to set all parameters, I can associate to an AP. Here is the wierd part:

If I have ACU running and am looking at the status when I run iwconfig with all the parameters, the association suddenly begins and I get a nice long green signal strength bar with a MAC of the AP to which I am associated. Great. But as soon as I use either leaplogin, leapset, leapscript or the menu selection for "Set leap information", BAM! no more association. It seems as if ACU is battling for control with wireless tools and it is changing the config of eth1. If I just use ACU to set the parameters, it never associates at all.

I have reinstalled the cisco linux tools and drivers. I have tried it with pcmcia and airo drivers from the kernel source as well as using pcmcia-cs tools separately. Both ways fail like I described above.

Is there some way to do a leap login without ACU? Does this make any sense? The killer is that it just suddenly stopped authenticating one day and tech support at my company swears everything should be fine for me to log in. I cannot think of anything I might have changed...hell, I even reinstalled my entire Linux distro (needed it anyway).


Kudos to anyone who can help!