BCM4318 wont connect

Axeia · #1 (**permalink**) 01-Jun-2009, 06:36

I got an ancient laptop with a BCM4318 chipset and installed the drivers using:
/usr/sbin/install_bcm43xx_firmware
After that the networks do show up in the list when confuring ifup, however it does not seem to connect properly.

ipv6 is disabled and ifconfig gives

Code:

wlan0     Link encap:Ethernet  HWaddr 00:17:31:3E:1D:23
          inet addr:192.168.1.67  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:393 errors:0 dropped:0 overruns:0 frame:0
          TX packets:445 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:44409 (43.3 Kb)  TX bytes:73687 (71.9 Kb)

which is strange as it seems to have obtained an IP from somewhere? Got no internet connection however

/sbin/lspci
00:09.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)

/sbin/lspci -n
00:09.0 0280: 14e4:4318 (rev 02)

iwlist scan

Code:

          Cell 10 - Address: 00:24:01:2A:37:CA                                           
                    Channel:3                                                            
                    Frequency:2.422 GHz (Channel 3)                                      
                    Quality=70/70  Signal level=-40 dBm                                  
                    Encryption key:on                                                    
                    ESSID:"Bakhuis"                                                      
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s                          
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s                  
                              36 Mb/s; 48 Mb/s; 54 Mb/s                                  
                    Mode:Master                                                          
                    Extra:tsf=000003c3e05fd180                                           
                    Extra: Last beacon: 584ms ago                                        
                    IE: Unknown: 000742616B68756973                                      
                    IE: Unknown: 010482848B96                                            
                    IE: Unknown: 030103                                                  
                    IE: Unknown: 2A0100                                                  
                    IE: Unknown: 32080C1218243048606C                                    
                    IE: IEEE 802.11i/WPA2 Version 1                                      
                        Group Cipher : TKIP                                              
                        Pairwise Ciphers (2) : TKIP CCMP                                 
                        Authentication Suites (1) : PSK                                  
                    IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00    
                    IE: Unknown: 2D1A4C101BFFFF000000000000000000000000000000000000000000
                    IE: Unknown: 3D1603001B0000000F000000000000000000000000000000        
                    IE: Unknown: DD1E00904C336C101BFFFF000000000000000000000000000000000000000000
                    IE: Unknown: DD1A00904C340300030000000F000000000000000000000000000000        
                    IE: Unknown: DD7F0050F204104A0001101044000102103B00010310470010A61E0B9B6B8A394381CA50B40105E7841021000E442D4C696E6B2053797374656D73102300074449522D363535102400024134104200046E6F6E651054000800060050F204000110110017587472656D65204E204749474142495420526F7574657210080002008C

Axeia · #2 (**permalink**) 01-Jun-2009, 06:50

Well it's getting the IP from my router..
spamming f5 on my routers wireless status page I see the .67 ip most of the time, but not all of the time.
So I guess it's stuck in some sort of loop?

syampillai · #3 (**permalink**) 01-Jun-2009, 06:59

What is the output of:

Code:

iwconfig

Also, see if you can ping the router.
What about DNS?

Code:

cat /etc/resolv.conf

Axeia · #4 (**permalink**) 01-Jun-2009, 07:30

iwconfig

Code:

lo        no wireless extensions.

eth0      no wireless extensions.

wmaster0  no wireless extensions.

wlan0     IEEE 802.11bg  ESSID:"Bakhuis"
          Mode:Managed  Frequency:2.422 GHz  Access Point: Not-Associated
          Tx-Power=20 dBm
          Retry min limit:7   RTS thr:off   Fragment thr:off
          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

cat /etc/resolv.conf

Code:

### /etc/resolv.conf file autogenerated by netconfig!
#                                                    
# Before you change this file manually, consider to define the
# static DNS configuration using the following variables in the
# /etc/sysconfig/network/config file:
#     NETCONFIG_DNS_STATIC_SEARCHLIST
#     NETCONFIG_DNS_STATIC_SERVERS
#     NETCONFIG_DNS_FORWARDER
# or disable DNS configuration updates via netconfig by setting:
#     NETCONFIG_DNS_POLICY=''
#
# See also the netconfig(8) manual page and other documentation.
#
# Note: Manual change of this file disables netconfig too, but
# may get lost when this file contains comments or empty lines
# only, the netconfig settings are same with settings in this
# file and in case of a "netconfig update -f" call.
#
### Please remove (at least) this line when you modify the file!
search arnhem.chello.nl
nameserver 192.168.1.254

Can't ping it.

lwfinger · #5 (**permalink**) 01-Jun-2009, 09:48

Axeia wrote:
> *iwconfig*
> Code:
> --------------------
>
> lo no wireless extensions.
>
> eth0 no wireless extensions.
>
> wmaster0 no wireless extensions.
>
> wlan0 IEEE 802.11bg ESSID:"Bakhuis"
> Mode:Managed Frequency:2.422 GHz Access Point: Not-Associated
> Tx-Power=20 dBm
> Retry min limit:7 RTS thr

ff Fragment thr

ff
> Encryption key

ff
> Power Management

ff
> 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
> --------------------
>
>
> *cat /etc/resolv.conf *
> Code:
> --------------------
> ### /etc/resolv.conf file autogenerated by netconfig!
> #
> # Before you change this file manually, consider to define the
> # static DNS configuration using the following variables in the
> # /etc/sysconfig/network/config file:
> # NETCONFIG_DNS_STATIC_SEARCHLIST
> # NETCONFIG_DNS_STATIC_SERVERS
> # NETCONFIG_DNS_FORWARDER
> # or disable DNS configuration updates via netconfig by setting:
> # NETCONFIG_DNS_POLICY=''
> #
> # See also the netconfig(8) manual page and other documentation.
> #
> # Note: Manual change of this file disables netconfig too, but
> # may get lost when this file contains comments or empty lines
> # only, the netconfig settings are same with settings in this
> # file and in case of a "netconfig update -f" call.
> #
> ### Please remove (at least) this line when you modify the file!
> search arnhem.chello.nl
> nameserver 192.168.1.254
> --------------------
>
>
>
> Can't ping it.

According to this output, it has not associated. How you got an IP is
a mystery.

Look at the output of dmesg for additional clues. Do _NOT_ post the
entire output, only sections that concern wlan0, b43 or ssb.

<NITPICK>
The script /usr/sbin/install_bcm43xx_firmware does not install the
driver - it installs firmware. Q. What is the difference? A. The CPU
on which it runs. The driver runs on the CPU of your computer. The
firmware runs on the CPU of the BCM4318.
</NITPICK>

You didn't mention if you are using NetworkManager or the traditional
ifup method. If the former, you should also look at
/var/log/NetworkManager for clues.

syampillai · #6 (**permalink**) 01-Jun-2009, 09:55

Looks like 192.168.1.254 is your router and you should be able to ping it unless you have firewall set up on the router that disallows pinging:

Code:

ping 192.168.1.254

You also got DNS. That means, you should be able to do name resolution:

Code:

nslookup www.google.com

Axeia · #7 (**permalink**) 01-Jun-2009, 10:27

Unable to ping the router, can ping it from another PC in the same network perfectly fine though.

dmesg | grep wlan0
pastebin - collaborative debugging tool (too long to post here and probably the problem at hand)

grepping ssb and 443 came up blank.

Using ifup btw.

lwfinger · #8 (**permalink**) 01-Jun-2009, 10:55

Axeia wrote:
> Unable to ping the router, can ping it from another PC in the same
> network perfectly fine though.
>
> *dmesg | grep wlan0*
> 'pastebin - collaborative debugging tool'
> (http://pastebin.com/f28913d4e) (too long to post here and probably the
> problem at hand)
>
> grepping ssb and 443 came up blank.
>
> Using ifup btw.

The problem is here:

"[12922.628955] wlan0: deauthenticated (Reason: 9)"

Your system is not authenticating. The table at
http://forums.wi-fiplanet.com/showthread.php?t=6536 gives the
following interpretation:

9...staReqAssociationWithoutAuth...Client not authorized yet, still
attempting to associate with an access point.

In plain language, you are not specifying the correct encryption key.
If you are using WEP, you cannot use a passphrase, but must specify
the hexadecimal key.