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.
I have installed ndiswrapper and successfully installed the drivers.
I have configured network-manager and this now shows a list of near by networks.
I'm having real trouble with mine though.
On trying to connect to my network (which uses WPA TKIP encryption) the adapter takes a while then shows me that it requires a secret key to connect I click connect and wait a while, sometimes I will get another box stating the same thing or I will get a disconnected message by the network-manager applet.
Please can somebody help I have no idea why this isn't working.
I did the exact same thing in ubuntu and it worked perfectly so I have no idea why it's not working in slackware
On trying to connect to my network (which uses WPA TKIP encryption) the adapter takes a while then shows me that it requires a secret key to connect I click connect and wait a while, sometimes I will get another box stating the same thing or I will get a disconnected message by the network-manager applet.
Since Slackware doesn't have a network manager applet, could you fill us in on what it is your using? Slackware DOES use wpa_supplicant, so if you haven't configured that, it could be part of the problem.
Hello, I'm running gnome (using a Gnome Slack Build [GSB]) I have installed.
The network-manager tool and I believe it is configured correctly, I have attempted using HOWTO's for wpa_supplicant, I followed several guides to the letter with no success.
I now take the assumption (which may be incorrect) that if wpa_supplicant is the problem I should still be able to connect to WEP and plain text wireless networks, therefore I will attempt to do this to see if I can connect.
Okay, I shutdown my machine came left to do shopping for an hour.
I came back and the adapter connected to my network straight away; I have no idea why it has suddenly started working, as I tried rebooting, hmm oh well I will make sure to keep hold onto the config files
The network-manager tool and I believe it is configured correctly, I have attempted using HOWTO's for wpa_supplicant, I followed several guides to the letter with no success.
Hm. I dont' use Gnome, so I'm afraid I'll be very little help with that tool.
Quote:
I now take the assumption (which may be incorrect) that if wpa_supplicant is the problem I should still be able to connect to WEP and plain text wireless networks, therefore I will attempt to do this to see if I can connect.
Yes, that is correct. Just the plain old vanilla iwconfig should let you use WEP and open networks.
Quote:
I came back and the adapter connected to my network straight away; I have no idea why it has suddenly started working, as I tried rebooting, hmm oh well I will make sure to keep hold onto the config files
I'm glad it works, but this is why I hate GUI tools. Stuff happens (both good and bad) and you have no idea why. Lets just hope that an hour of shopping isn't required for your WPA connection to work!
Having the same problem with a HP 530 running Ubuntu Hardy I've made the same notifications. As up to now, I've tested several different vendors and models and as far I as can see this chipset has no issues connecting to wireless APs running Broadcoms own chipset, like Motorolas units and SA/Cisco EPC2434. I have not been able to connect to Netgear or D-link at the moment. Any one out there knows what wireless chipset they're running? I don't have any good ideas ho to come around the problem (accept turning off the encryption).
You might not be aware, but Ubuntu Hardy has a bug in NetworkManager that primarily affects WPA encrypted networks. You might try using wicd to configure your card and see if that does the trick.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.