Ruggiero wrote:
> i just installed fedora 8 and with b43-fwcutter i installed firmware 
> v4...now if i use NetworkManager and i connect to the ap,i insert wep key 
> but after a while it ask me again for the password and i don't get 
> connected...
> while if i use iwconfig i got connected but i can't ping anything or 
> visiting websites,also on the access point it tells me that another device 
> is connected..here there is some informations:
> 
> [EMAIL PROTECTED] ~]# iwconfig
> lo        no wireless extensions.
> 
> eth0      no wireless extensions.
> 
> wmaster0  no wireless extensions.
> 
> wlan0     IEEE 802.11g  ESSID:"che12345"
>           Mode:Managed  Frequency:2.462 GHz  Access Point: 00:0C:41:19:2D:C1
>           Bit Rate=1 Mb/s   Tx-Power=27 dBm
>           Retry min limit:7   RTS thr:off   Fragment thr=2346 B
>           Encryption key:6FFB-F8F9-D105-87F6-335C-8985-D8
>           Link Quality=96/100  Signal level=-38 dBm  Noise level=-38 dBm
>           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
> 
> [EMAIL PROTECTED] ~]# dmesg|grep b43
> b43-phy0: Broadcom 4311 WLAN found
> b43-phy0 debug: Found PHY: Analog 4, Type 2, Revision 8
> b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2
> b43-phy0 debug: Adding Interface type 2
> b43-phy0 debug: Loading firmware version 351.126 (2006-07-29 05:54:02)
> b43-phy0 debug: Chip initialized
> b43-phy0 debug: 32-bit DMA initialized
> b43-phy0 debug: Wireless interface started
> b43-phy0 debug: Using hardware based encryption for keyidx: 0, mac: 
> ff:ff:ff:ff:ff:ff
> b43-phy0 debug: Disabling hardware based encryption for keyidx: 0, mac: 
> ff:ff:ff:ff:ff:ff
> b43-phy0 debug: Using hardware based encryption for keyidx: 0, mac: 
> ff:ff:ff:ff:ff:ff
> b43-phy0 debug: Disabling hardware based encryption for keyidx: 0, mac: 
> ff:ff:ff:ff:ff:ff
> b43-phy0 debug: Using hardware based encryption for keyidx: 0, mac: 
> ff:ff:ff:ff:ff:ff
> b43-phy0 debug: Disabling hardware based encryption for keyidx: 0, mac: 
> ff:ff:ff:ff:ff:ff
> b43-phy0 debug: Removing Interface type 2
> b43-phy0 debug: Wireless interface stopped
> b43-phy0 debug: DMA-32 0x0200 (RX) max used slots: 1/64
> b43-phy0 debug: DMA-32 0x02A0 (TX) max used slots: 0/128
> b43-phy0 debug: DMA-32 0x0280 (TX) max used slots: 0/128
> b43-phy0 debug: DMA-32 0x0260 (TX) max used slots: 0/128
> b43-phy0 debug: DMA-32 0x0240 (TX) max used slots: 0/128
> b43-phy0 debug: DMA-32 0x0220 (TX) max used slots: 8/128
> b43-phy0 debug: DMA-32 0x0200 (TX) max used slots: 0/128
> b43-phy0 debug: Adding Interface type 2
> b43-phy0 debug: Loading firmware version 351.126 (2006-07-29 05:54:02)
> b43-phy0 debug: Chip initialized
> b43-phy0 debug: 32-bit DMA initialized
> b43-phy0 debug: Wireless interface started
> b43-phy0 debug: Using hardware based encryption for keyidx: 0, mac: 
> ff:ff:ff:ff:ff:ff
> 
> 
> i think i'm missing something...but i don't know what...hope anyone can help 
> me

In your dmesg output, you should see something like

b43-phy0 debug: Using hardware based encryption for keyidx: 0, mac: 
ff:ff:ff:ff:ff:ff
eth1: Initial auth_alg=0
eth1: authenticate with AP 00:14:bf:85:49:fa
eth1: RX authentication from 00:14:bf:85:49:fa (alg=0 transaction=2 status=0)
eth1: authenticated
eth1: associate with AP 00:14:bf:85:49:fa
eth1: RX AssocResp from 00:14:bf:85:49:fa (capab=0x431 status=0 aid=1)
eth1: associated

In your case, it will say wlan0 rather than eth1.

If you are not getting authentication, the problem is likely in your WEP key. 
How are you setting
that? If you are trying to use a passphrase, your AP and NetworkManager may not 
be converting to a
hex key using the same algorithm. When I use WEP, I enter a passphrase into my 
AP, but write down
the hex key and use that on all the computers.

Incidentally, are you aware that you published your encryption key for the 
entire world to see?

Larry
_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Reply via email to