CentOS+WLAN=No luck (BCM4311 / BCM 2050) Help needed

Issues related to hardware problems
Kelmas
Posts: 19
Joined: 2008/08/18 20:36:17
Location: Kaunas, Lithuania
Contact:

CentOS+WLAN=No luck (BCM4311 / BCM 2050) Help needed

Post by Kelmas » 2009/09/08 05:44:32

Hello CentOS people,

this is my first post here :-)

After reading and trying tons of tutorials and several OS reinstalls, I'm stuck trying to load wireless on my [b]Dell Vostro 1400[/b] laptop. Before you say [b]search forums![/b] I hurry to tell I did. No solution seems to work.

WLAN chipset - Broadcom's BCM4311 / BCM 2050.

[b]1st scenario - native CentOS 5.3 drivers[/b]

Although CentOS recognize WLAN card and displays it's name correctly, neither [b]network[/b] or [b]NetworkManager[/b] sees any of wireless networks.

[b]2nd scenario - Broadcom's drivers[/b]

Most know Broadcom has released [url=http://www.broadcom.com/support/802.11/linux_sta.php]Linux drivers[/url]. I had some more luck with them than in 1st scenario although problems occur. After successfully compiling Kernel module, wireless networks are discovered and can be successfully connected but [b]no pages load[/b]. It seems like DNS is not resolving at all and page loading timeouts instantly. Tested on TKIP-encrypted network.

Any help or step-by-step guide? My googling about making CentOS work on Dell Vostro laptop gave no working solution.

pschaff
Retired Moderator
Posts: 18276
Joined: 2006/12/13 20:15:34
Location: Tidewater, Virginia, North America
Contact:

Re: CentOS+WLAN=No luck (BCM4311 / BCM 2050) Help needed

Post by pschaff » 2009/09/09 20:24:23

Welcome to the CentOS fora.

Are you sure DNS is working properly? Can you ping the router/access point? Other local addresses? The DNS server? Do other devices work on the same AP? Perhaps the card is working but the AP is the problem.

Have you looked at the [url=http://wiki.centos.org/HowTos/Laptops]laptop[/url] page in the Wiki or found [url=http://elrepo.org/tiki/FAQ]FAQ #4[/url] at [url=//elrepo]ELRepo[/url]?
If no joy is found then please post the results of

[code]
[b]for BUSID in $(/sbin/lspci | awk '{ IGNORECASE=1 } /net/ { print $1 }'); do /sbin/lspci -s $BUSID -m; /sbin/lspci -s $BUSID -n; done[/b]
[/code]

NedSlider
Forum Moderator
Posts: 2896
Joined: 2005/10/28 13:11:50
Location: UK

CentOS+WLAN=No luck (BCM4311 / BCM 2050) Help needed

Post by NedSlider » 2009/09/09 23:14:45

[quote]
Kelmas wrote:

[b]2nd scenario - Broadcom's drivers[/b]

Most know Broadcom has released [url=http://www.broadcom.com/support/802.11/linux_sta.php]Linux drivers[/url]. I had some more luck with them than in 1st scenario although problems occur. After successfully compiling Kernel module, wireless networks are discovered and can be successfully connected but [b]no pages load[/b]. It seems like DNS is not resolving at all and page loading timeouts instantly. Tested on TKIP-encrypted network.

Any help or step-by-step guide? My googling about making CentOS work on Dell Vostro laptop gave no working solution.[/quote]

From what I've seen, most people seem to have success with this method. Here's an example:

http://lists.centos.org/pipermail/centos/2009-July/079638.html

and follow the link therein. But I don't have the hardware to test.

We looked at packaging that driver for inclusion in ELRepo, but then read the license terms which are [b]very unfriendly[/b] towards redistribution. If someone wants to ask Broadcom to reconsider their licensing terms then we may be prepared to revisit it, but as of now neither I nor ELRepo.org will be redistributing those Broadcom drivers under the current licensing terms. Shame :-(

Kelmas
Posts: 19
Joined: 2008/08/18 20:36:17
Location: Kaunas, Lithuania
Contact:

Re: CentOS+WLAN=No luck (BCM4311 / BCM 2050) Help needed

Post by Kelmas » 2009/09/11 05:59:11

Here are results of
[b]for BUSID in $(/sbin/lspci | awk '{ IGNORECASE=1 } /net/ { print $1 }'); do /sbin/lspci -s $BUSID -m; /sbin/lspci -s $BUSID -n; done[/b]

[code]09:00.0 "Ethernet controller" "Broadcom Corporation" "NetLink BCM5906M Fast Ethernet PCI Express" -r02 "Dell" "Unknown device 0227"
09:00.0 0200: 14e4:1713 (rev 02)
0c:00.0 "Network controller" "Broadcom Corporation" "BCM4311 802.11b/g WLAN" -r01 "Dell" "Wireless 1390 WLAN Mini-Card"
0c:00.0 0280: 14e4:4311 (rev 01)[/code]

When I follow guide, my WLAN card led flashes on when I blacklist b43xx module. Although it's blacklisted, eth1 still appears (which by default is wlan card detected by CentOS) even though I configure [b]wl[/b] on [b]wlan0[/b]. Here is what network config shows:

[img]http://www.nfstuning.com/files/images/broadcom/network-config-hardware.png[/img]

[img]http://www.nfstuning.com/files/images/broadcom/network%20config-devices.png[/img]

This is connection information from NetworkManager:

[img]http://www.nfstuning.com/files/images/broadcom/connection-information-2.jpg[/img]

I wonder why it shows eth1 instead of wlan0 :-(

Card seems to connet to the network (as shown in the picture) but all PINGs returns "network unreacheable" error.

Access point is not a problem because I use it successfully with Windows Vista/XP using the same hardware.

pschaff
Retired Moderator
Posts: 18276
Joined: 2006/12/13 20:15:34
Location: Tidewater, Virginia, North America
Contact:

Re: CentOS+WLAN=No luck (BCM4311 / BCM 2050) Help needed

Post by pschaff » 2009/09/11 13:29:56

[quote]
Kelmas wrote:
...
I wonder why it shows eth1 instead of wlan0 :-(
[/quote]

Depends on the driver - eth1 is a valid wireless device. I don't have a clear answer for you but something to check. Are you running both the "network" and "NetworkManager" services? They may be fighting each other. Generally need one or the other.
[code]
# chkconfig --list | grep -i network
NetworkManager 0:off 1:off 2:off 3:off 4:off 5:off 6:off
network 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[/code]
If you want to use [url=http://wiki.centos.org/HowTos/Laptops/NetworkManager]NetworkManager[/url] then it should be opposite the above.

You may confuse things by trying to force use of wlan0 when the correct device is eth1.

Kelmas
Posts: 19
Joined: 2008/08/18 20:36:17
Location: Kaunas, Lithuania
Contact:

Re: CentOS+WLAN=No luck (BCM4311 / BCM 2050) Help needed

Post by Kelmas » 2009/09/11 16:19:39

I have used [b]chkconfig network off[/b] to disable [i]network[/i] and am using [i]NetworkManager[/i]. But I haven't disabled wpa_supplicant (did not run [b]chkconfig wpa_supplicant off[/b]) - if I do, then I can't connect to WLAN.

Maybe I should have associated [b]wl[/b] with [b]eth1[/b] instead of [b]wlan0[/b] in [i]modprobe[/i] configuration...? Now it has [b]alias wlan0 wl[/b] line.

pschaff
Retired Moderator
Posts: 18276
Joined: 2006/12/13 20:15:34
Location: Tidewater, Virginia, North America
Contact:

Re: CentOS+WLAN=No luck (BCM4311 / BCM 2050) Help needed

Post by pschaff » 2009/09/11 17:34:02

Seems worth a try. After a lot of trial/error things get to be a mess. Hard to guess what to advise except to try to back out all changes and configure following a procedure that has worked for someone else.

r_hartman
Posts: 711
Joined: 2009/03/23 15:08:11
Location: Netherlands
Contact:

Re: CentOS+WLAN=No luck (BCM4311 / BCM 2050) Help needed

Post by r_hartman » 2009/09/14 19:21:05

Looking at your screen prints it would appear that your problem (wlan config) is already solved, but your network config has an issue.
You gateway is 193.219.72.250, which would indicate you are in the 193.219.72.0/24 network.
However, your IP is listed as 10..0.69.220, belonging to network 10.0.0.0/8.

This is what I would expect to explain your "network unreacheable" errors.

For your PC to use the listed gateway (default route) it would need to be in the same network.

If you don't have the network details, I suggest you look at these settings from your working Vista setup an replicate them.

Kelmas
Posts: 19
Joined: 2008/08/18 20:36:17
Location: Kaunas, Lithuania
Contact:

Re: CentOS+WLAN=No luck (BCM4311 / BCM 2050) Help needed

Post by Kelmas » 2009/09/15 07:28:20

[quote]
r_hartman wrote:
Looking at your screen prints it would appear that your problem (wlan config) is already solved, but your network config has an issue.
You gateway is 193.219.72.250, which would indicate you are in the 193.219.72.0/24 network.
However, your IP is listed as 10..0.69.220, belonging to network 10.0.0.0/8.

This is what I would expect to explain your "network unreacheable" errors.

For your PC to use the listed gateway (default route) it would need to be in the same network.

If you don't have the network details, I suggest you look at these settings from your working Vista setup an replicate them.[/quote]

Yes, [b]WLAN now works[/b] :-) Thanks! I'll post a guide to Wiki for everybody on Dell Vostros.

But now the problem is network configuration. I gess Windows has nothing against gateway IP being outside local IP network (where gateway is 193.219.72.250 and IP is 10.0.69.220). Here is network config read from successfully connected Windows Vista:

[code]
Windows IP Configuration

Host Name . . . . . . . . . . . . : gytis-vostro
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : vukhf.lt

[ REMOVED WIRED NETWORK DETAILS ]

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : vukhf.lt
Description . . . . . . . . . . . : Dell Wireless 1390 WLAN Mini-Card
Physical Address. . . . . . . . . : [ REMOVED ]
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.0.69.63(Preferred)
Subnet Mask . . . . . . . . . . . : 255.0.0.0
Lease Obtained. . . . . . . . . . : 2009 m. rugsėjo 15 d. 10:16:43
Lease Expires . . . . . . . . . . : 2009 m. rugsėjo 16 d. 10:16:43
Default Gateway . . . . . . . . . : 193.219.72.250
DHCP Server . . . . . . . . . . . : 193.219.72.250
DNS Servers . . . . . . . . . . . : 193.219.72.253
193.219.61.11
193.219.61.111
Primary WINS Server . . . . . . . : 193.219.72.253
NetBIOS over Tcpip. . . . . . . . : Enabled
[/code]

IP addess (10.0.69.63 here) changes dynamically after each connect.

Is it possible to support 10.0.69.63 IP addess on the same time having gateway at 193.219.72.250 on CentOS? Because it seems it's legal in Windows.

Another important thing is that outside networks sees everybody from this WLAN as 193.219.72.250.

pschaff
Retired Moderator
Posts: 18276
Joined: 2006/12/13 20:15:34
Location: Tidewater, Virginia, North America
Contact:

Re: CentOS+WLAN=No luck (BCM4311 / BCM 2050) Help needed

Post by pschaff » 2009/09/15 13:32:09

[quote]
Kelmas wrote:
...

Another important thing is that outside networks sees everybody from this WLAN as 193.219.72.250.[/quote]

That's typical for [url=http://en.wikipedia.org/wiki/Network_address_translation]NAT[/url] however, your setup seems anything but typical. From the Wikipedia link:

[quote]In a typical configuration, a local network uses one of the designated "private" IP address subnets (the RFC 1918). Private Network Addresses are 192.168.x.x, 172.16.x.x through 172.31.x.x, and 10.x.x.x (or using CIDR notation, 192.168/16, 172.16/12, and 10/8), and a router on that network has a private address (such as 192.168.0.1) in that address space. The router is also connected to the Internet with a single "public" address (known as "overloaded" NAT) or multiple "public" addresses assigned by an ISP. As traffic passes from the local network to the Internet, the source address in each packet is translated on the fly from the private addresses to the public address(es).[/quote]

Your DHCP server is apparently using NAT but not with the usual 192.168.x.x [url=http://en.wikipedia.org/wiki/Classful_network]Class[/url] C private addresses. It is apparently giving you a Class A private address with the gateway on a Class C public address. Like [b]r_hartman[/b] (good catch there) I don't see how that can work, but then I've been surprised before.

Post Reply

Return to “CentOS 5 - Hardware Support”