Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I'm trying to get my Cisco Aironet 350 PCMIA wirless card to work with WPA, but with no success. I'm using Ubuntu, and without WEP or WPA the card works out of the box great!
But I can't get it to work with WPA, I tried so many different ways and howto, still no luck. WPA_Supplicant does not support it as it seams, and I'm unable to use NDISwrapper with it. I even tried to get WEP to work with no luck.
I'm wondering if anybody had success with this card and either WEP or WPA, I'm really looking for a WPA, but if all I can get is WEP, I'll live with it.
You might try wpa_supplicant with the Generic driver " -D wext ", but if that doesn't work (likely), then you probably can't use WPA. You might still be able to get WEP working though using iwconfig, or even an older version of waproamd.
Thanks for your help. I tried "-D wext" but it did not work. I even tried WEP and it did not work either. unsecured access workes just fine!! is there anybody here using Aironet 350 with WPA? how about WEP?
Lets start at the beginning. Does the manual that came with the
card say it can support WEP or WPA.
Which card are you using? Which router are you using?
Which driver are you using for the wi-fi card?
Which version of linux are you using?
I got this card with a used laptop I picked off eBay, so no manuals . But what I found on the Cisco website tells me that the card originally supports WEP only, but with the new firmware updates and drivers it should support WPA on windows, nothing mentioned on Linux. I have flashed the latest WinXP firmware on the card using a windows laptop.
The card is “Cisco Aironet 350 PCMICA – PCM-352” and I’m using it with a Belkin 54G wireless router (model: F5D7230-4). For the driver I’m using the kernel internal driver airo.ko and airo_cs.ko. I tried to get this to work with secured connections on SUSE 10.0 and Ubuntu 5.10 and both did not work out. Unsecured connection works flawlessly on both distros. I have a newer Centrino laptop that has SUSE and Ubuntu working with the WPA setting on the same router.
Bump. Sounds like we have similar problems, I have an Airo wireless card and unsecure access works great, but I can't seem to get the encryption to work. I'm trying with Suse 10.0, and using a D-Link i-540 router. I don't know much about encryption though, what I did was basically choose a random number for the key, and set the same number on both the router and laptop, then I made sure both encryption formats were the same and that they were both set to encrypt, but when I do that I don't get anything. Any ideas?
Another question (I don't want to start another thread, and I can't seem to find the answer in any other forums). How do I set a certain piece of hardware to eth0 or eth1? Sometimes when I boot the computer, kinternet recognizes eth0 and I can connect and all is well (Aside from the encryption problem), but sometimes there appears to be no such thing as eth0. I do ifup eth0 and it says nothing is configured for eth0. Any ideas?
Back in my earliest forays into Linux I had a 350 - worked fine with RH9 (2.4.20-ish I think).
Cisco had a Linux package on their website that contained firmware and an ACU - Airo Client Utility maybe. You ran the latter in batch, and configured the card - also did firmware updates. As I have always used WEP, I guess it must have worked. I also used the same card on a Win2000 dual boot - caused problems, because if you installed a new Win client update, it also silently updated the firmware. I quickly learned not to do that as it broke the Linux ACU. I used to keep an old firmware level around just to allow me to downgrade when needed so I could use the 350 under RH.
Been a couple of years since I last used it, but it certainly used to work.