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.
Wireless card is Linksys wmp54g with broadcom bcm4306 chipset
System is Suse 10.1 (the free version) with a recent 64-bit kernel
-I couldn't get it to work with Yast directly, or with the version of ndiswrapper that came with the distro, so i downloaded/made/installed the latest ndiswrapper.
-Drivers that came with my card (bcmwl5.sys and .inf) are 32-bit. Cue endless screens of warnings at boot saying "bad magic". I downloaded bcmwl564.sys, but it says it's an invalid driver. what drivers should i be using, and where can i get them? Are there native linux drivers available? (the official broadcom site is less than helpful here)
Ok, it's half working. Did you mean the bcm43xx.cat file that comes with some driver packages, or the bcm43xx project website?
The bmc43xx driver has been in the kernel since 2.6.17, so if you have a recent kernel, you could give it a try. The only bit I'm not sure about is the firmware. That has to be cut from a Windows driver file, and I don't know if you cut it from a 32 bit driver if it will work on a 64 bit system. The rumor is that it can work, but I don't know of any successful examples.
Originally Posted by -Olly-
I tried the site from your link (thanks), but couldn't access the "basic instructions for kernel versions 2.6.15 and 2.6.16". That might be broken link, not sure.
Um, I'm not sure what linke you're referring to.
Originally Posted by -Olly-
In the end i tried a file called netbc564.inf that was with one of the broadcom bundles, and i can ping my access point. i can't access the internet yet, but i'll browse the forum and see what i find.
Thanks for your help
If you can ping your access point, then you probably just need to configure the card and either request or assign an IP address.
I could ping my AP, but after i rebooted, iwconfig said:
wlan0 IEEE 802.11g ESSID:off/any
Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
Bit Rate=54 Mb/s Tx-Power:25 dBm
RTS thr:off Fragment thr:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
i ran >ifup wlan0 essid network
Is that the correct syntax? (my network essid is "network"). It said:
wlan0 Startmode is 'auto'
but the iwconfig output remained the same.
I checked the file /etc/sysconfig/network/ifcfg-wlan0 as suggested in: http://www.linuxquestions.org/questi...d.php?t=465714, and i checked the setup in Yast, and the ESSID is set to that of my network. Is there some way to get the interface to scan for available networks?
To be honest, I simply don't trust Yast and its brethern to handle wireless configuration. They screw up a lot and hide important error messages.
Try configuring the card in a console using iwconfig, not ifup. If it works that way, you can always write a script that you can run whenever you need the card configures. So the basic procedure would be:
iwconfig wlan0 essid network
The ifup script brings up the card and requests an IP address from a DHCP server, but it doesn't configure the card.
As far as scanning goes, there is the iwlist command:
iwlist wlan0 scan
And that should return a list of the access points it sees.
Thanks for the quick response, Hangdog. I see your name on most posts on this forum, and i really appreciate you taking the time to help newbies like me. The network comes up on the scan, so i'm probably just missing something very obvious.
If I then ping 192.168.1.1, I just get a stream of "destination host unreachable" messages. At what point should I enter the password to access the network, since it hasn't prompted me or warned me that I need to? Are these logs 'normal', or has my tooling about in Yast messed up some config file somewhere?
Once again, my profuse thanks for your patience - you're owed a lot of good karma, i think.
edit: if the problem is the passcode/security stuff, should i be using the wpa_supplicant stuff, as described on your site?
It's a little hard to tell from what you've posted if your configuration took. After you set the SSID, check the output of iwconfig. If you see a MAC address in the Access Point section, then you have associated with the access point (by the way, are you running WEP or WPA security? If so, then you have to have the key entered before the association can take place. I do like using wpa_supplicant for this and the stuff I've posted on my site works well, at least for me).
Once you've associated with an access point, running ifup should get an IP address if there is a DHCP server running on the router. After running check the output of ifconfig to make sure you do have an IP address. Also check the output of route -n to make sure that DHCP set up your gateway properly (it should have your router's IP address).
If you're still having trouble, post the outputs of iwconfig, ifconfig and route -n, and hopefully that will tell us where things have gone haywire.
not sure if that means it is WPA after all, or not. (btw, my PSK isn't actually password :P )
I can't ping the AP any more, but it still shows up on iwlist wlan0 scan. I'm pretty sure this is an issue with the interface config, but i don't know what. Perhaps i shouldn't have screwed about with that ifcfg file, or perhaps i shouldn't have used Yast...
iwconfig returns more or less the same output as i posted in #5 of this thread - not associating with the access point.
You need to focus on this first since nothing else can work until you get an association with an access point.
I thought my encryption was WPA, but now i'm not sure. is "iwconfig key" the right option to use for entering the key? because that gives me:
You REALLY need to figure out if you are using WPA or WEP. With WEP you can set the key with iwconfig. With WPA, you need to install wpa_supplicant.
# iwconfig key password
You've got a syntax error there. The correct command is iwconfig wlan0 key password.
Interestingly, wlan0 doesn't appear on the basic ifconfig list, but if i do:
The lack of wlan0 in the vanilla ifconfig just means that the interface hasn't been brought up. The fact that it appears in ifconfig wlan0 is good since it means the system does recognize it as a valid interface.
At this point I'm not sure that you are getting your card configured properly, so it is probably not the same problem as the thread you're referring to.
I hate to say it, but I'm a bit stumped. What you've done so far should have worked. What I would do at this point is:
- Spend some quality time with your log files (/var/log/syslog, /var/log/messages, and the dmesg command output) and see what wpa_supplicant and/or ndiswrapper are up to.
-Check the output of lsmod and make sure that bcm43xx isn't loaded. It will cause serious conflicts with ndiswrapper and some distros are starting to include it with their stock kernels.
- Try some different Windows drivers and see if any behave better. The kind of symptoms you are describing can be caused by a Windows driver that isn't real happy functioning under ndiswrapper.
- Try linuxant driveloader. It functions similar to ndiswrapper (allows Windows drivers to run in Linux) but sometimes it works when ndiswrapper doesn't. The downside is that it isn't free, but they do provide a decent test period so you can try before you buy.
Well, I'm writing this via my wireless connection. I think there was a conflict between configuration files here, if that's even possible. I went into Yast and deleted the wireless profile which had appeared there automatically, after i edited ifcfg-wlan0, meaning to start over, and then i was able to connect. I don't know if this state of affairs will persist after I reboot, but we'll find out.
Thankyou for your help and patience, HangDog. I hope this thread helps other new linux users to solve their problems.