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'm eternally new to Linux.
I'm running Fedora 8 in Dell XPS M1513 with a Broadcom BCM4312 wireless network controller. In order to have it running I have tried b43 drivers and also ndiswrapper. I haven't been successful enough so far despite trying for several days with lots of googling. I'm now struggling with ndiswrapper. The WIFi led in the computer is on. When I try to connect
Quote:
[root@localhost network-scripts]# ifup wlan0
Determining IP information for wlan0... failed; no link present. Check cable?
The output I got with the usually recommended commands is:
But the configuration of wlan0 seems not to be adequate, despite setting the ESSID to ODINGA using the Network Configuration tool in System>Administration:
Quote:
[root@localhost Omar]# iwconfig
lo no wireless extensions.
wlan0 IEEE 802.11g ESSID: off/any
Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:32 dBm
RTS thr:2347 B Fragment thr:2346 B
Encryption key: off
Power Management: 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
eth1 no wireless extensions.
virbr0 no wireless extensions.
By the way, the content of the file ifcfg-wlan0 in /etc/sysconfig/network-scripts/ is:
[root@localhost /]# dmesg | grep wlan0
wlan0: ethernet device 00:1f:3a:12:d4:d0 using NDIS driver: bcmwl5, version: 0x4281300, NDIS version: 0x501, vendor: 'NDIS Network Adapter', 14E4:4312.5.conf
wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
ADDRCONF(NETDEV_UP): wlan0: link is not ready
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: no IPv6 routers present
ADDRCONF(NETDEV_UP): wlan0: link is not ready
ADDRCONF(NETDEV_UP): wlan0: link is not ready
and:
Quote:
[root@localhost /]# dmesg | grep ndiswrapper
ndiswrapper version 1.52 loaded (smp=yes, preempt=no)
ndiswrapper (link_pe_images:576): fixing KI_USER_SHARED_DATA address in the driver
ndiswrapper: driver bcmwl5 (Broadcom,03/23/2006, 4.40.19.0) loaded
ndiswrapper: using IRQ 17
usbcore: registered new interface driver ndiswrapper
ndiswrapper (iw_set_bitrate:442): setting bit rate failed (C00000BB)
ndiswrapper (iw_set_bitrate:442): setting bit rate failed (C00000BB)
ndiswrapper (iw_set_bitrate:442): setting bit rate failed (C00000BB)
Maybe it helps to know that as I had tried b43 driver with f-cutter I have blacklisted:
Quote:
blacklist bcm43xx_mac80211
What could be the problem?
I look forward for help.
Thanks in advance.
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,697
Rep:
Blacklist the ssb, b43, b43legacy, mac80211, bcm43xx as well. List loaded modules to see if anything is strange. Also I would disable any security on the router and just make a plain non encrypted connection. Once you get that then turn on and get that working.
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,697
Rep:
I just want to eliminate the module setup as the issue not working versus just the encryption setup not working. I just perfer to keep the connection simply as possible to begin with. From the looks using Network_Manager so can't help there. Never liked it.
But now what does ' ndiswrapper -l ' say?
Then as root issue the following commands.
/sbin/ifdown eth0
/sbin/ifdown wlan0
/sbin/ifup wlan0
Determining IP information for wlan0... failed; no link present. Check cable?
I understand that by removing the encryption we make things easier, but the fact that a iwconfig shows (see first post) that not even the ESSID is the one that should be according to the settings suggest that there is at least one encryption-independent problem.
Not knowing if there is a wired nic but if so and is eth0 then edit ifcfg-eth0 and put a # infront of NM_CONTROLLED and set ONBOOT=no
Now run the following commands as root
/sbin/service NetworkManager stop
/sbin/chkconfig --level 2345 NetworkManager off
/sbin/service network restart
/sbin/ifup wlan0
Did it connect to your access point
If not post
/sbin/iwconfig
/sbin/ifconfig -a
/sbin/iwlist wlan0 scan
ndiswrapper -l
cat /etc/modprobe.conf
Also try rebooting if something else has gotten in there. On reboot it will not start networkManager service because of the chkconfig command and neither wired or wireless will start on boot. Once up as root issue as root.
/sbin/ifup wlan0
Brian! Thanks, I've wireless connection now but it is unencrypted. Let me tell you, for the record, what I did. First, I did everything you suggested me in your last reply except removing the encryption. I made no progress at all. Just when I remove the encryption, I got connection. I don't know if the changes plus removing the encryption made the trick or it was just a matter of removing the encryption.
Now, what can I do to have the encryption back and keep the wireless connectivity? Whenever I go encrypted I loss the connection.
What to do?
Thanks in advance.
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,697
Rep:
This is the way I do it for wpa. If wpa2 then just a line code of change.
Run this command to generate the encrypted passphrase. Be sure to make sure if anything is capital that you do it exactly the same for ESSID and passphrase. Both are case sensitive.
Now take that piece of generate code and place in /etc/wpa_supplicant/wpa_supplicant.conf file.
Here is and example of mine as wpa
Code:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
# update_config=1
network={
ssid="NETGEAR"
#psk="linuxisgreat"
psk=6890cc1ba4d9742b1cac7e6b8a100532c34035798defb93048f2b9121cba5b61
proto=WPA
}
# WPA for WPA
# RSN for WPA2
Change proto to RSN if using WPA2.
Change router back to encryption mode.
Issue this command to test. It should say connection establish after several lines of info going by.
Then /sbin/ifup wlan0. It may have to run before the above line. Been a while dealing with DHCP. Normally use defined static IPs.
To automate on start then do the following. Be sure the command is on a single line. May have to turn off line wrap for editor you are using.
Place this line at the end of /etc/sysconfig/network-scripts/ifup-wireless.
It took so long that I stopped at some point just to realize that after "ifup wlan0" I got no connection at all. The story is longer and goes through having killed a wpa_supplicant process ($ kill -KILL wpa_supplicant) in order to manually delete the file wlan0 at /var/run/wpa_supplicant, something that was suggested by the lines that followed a second try of the code above just to have nothing at the end.
Now, I'm trying the command above again, after bringing back wlan0 to /var/run/wpa_supplicant and rebooting. I see no wpa_supplicant process running ($ ps). As you may have realized I know nothing about what I'm doing. I'm just following your suggestions, and reading the lines that pop up after the command above, etc. I'm lost, as simple as that.
On the other hand, I don't follow you when you said: "Then /sbin/ifup wlan0. It may have to run before the above line. Been a while dealing with DHCP. Normally use defined static IPs." It is clear that I should ifup wlan0, just as I did but what do you mean by "It may have to run before the above line. Been a while dealing with DHCP. Normally use defined static IPs."?
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,697
Rep:
Get back to you later tonight or tomorrow.
I normally use static IP so the network nic is up before I start wpa_supplicant. Not sure how to handle this for dhcp but would think the way I done this would work. You may have to define a static IP for the moment till I can google for DHCP and WPA setup under Redhat or Fedora.
Brian, I have been also out. Having a wireless connection, even if non-encrypted, turned me into the main course. I don't know exactly how much am I risking by doing this. I'm now taking a look at http://www-users.york.ac.uk/~mdc1/fedora_wireless.html and I see some new lines to be included in wpa_supplicant.conf and /etc/sysconfig/wpa_supplicant but I don't know yet if this is going to solve the problem. Have you found a solution? In any case I really appreciate your help. It has allowed me to have this wireless fired up and ready to go.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.