Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm pretty newbish. I've searched all over these forums and i cannot find the answer to my problem (could be due to poor searching, i'm not totally sure). I also wasn't sure where to post this, thought this looked the best.
Basically i've finally gotten the driver for my wireless card (Linksys WPC54G) installed, using Ndiswrapper and the driver for another card with the TI chipset. When i do lspci it shows that the card is enabled (although upon first boot, everything is disabled until i modprobe ndiswrapper?!). The problem is that i can't see the card through the Network Device Control, nor can i see the card or driver listed under the Network Config GUI.
I run iwconfig/ifconfig and i see the card, i assign it an IP, nothing, i tell it to pick any ap, nothing, tell it a channel, nothing. I'm stumped, as are some friends of mine whose knowledge FAR surpasses mine. Thanks in advance for ANY help you can possibly offer.
Upon review of that thread, i'm pretty sure i've passed most of what they were talking about, i have the drivers configured (or so i think) and what not.
The only thing that did look somewhat promising was this piece:
Quote:
Originally posted by rgheck The WPC54G card works with the ndiswrapper module, available from ndiswrapper.sourceforge.net. I've got it working with the windows drivers on the Linksys website. I had to edit files in /etc/sysconfig/network-scripts by hand (horrors!) to get dhcp working and the file /etc/pcmcia/config to get the module to load automatically when the card does. But it's now working like a charm.
Richard
If anyone could maybe go into detail about the part i've outlined in red, it won't DHCP, so maybe what he's talking about would do the trick.
I'm having the same problem with my WPC54G and Fedora 3. I get ndiswrapper to load the driver, and create a wlan0 interface. I can user iwspy to list the available ap's, and I can set values such as essid and enkey through iwconfig. I've created /etc/sysconfig/network-scripts/ifcfg-wlan0 and /etc/sysconfig/network-scripts/keys-wlan0
I get no dhcp reply from my dhcp server, and I get no connectivity if I manualy set an IP. I'm using 128bit encryption - however - I get the same results without encryption.
I currently have this card working under Ubuntu (Debian woody) and Gentoo. It works perfectly under both of those distros - using 128bit encryption.
Hi, sorry I can't help but I too am having the same problem. But, I found the kwifimanager does come up and shows my wireless AP. It just will not grab an IP from it. I think it has to do with setting the open/restricted value but I don't know the correct token in the ifcfg-wlan0 file to set that with. Anyone out there go this working? My laptop dual boots WinXP and it works fine under that with the same settings...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.