Resend. Message attached.
Regards,
David Ellingsworth
_________________________________________________________________
Enjoy 5 GB of free, password-protected online storage.
http://www.windowslive.com/skydrive/overview.html?ocid=TXT_TAGLM_WL_Refresh_skydrive_062008
For a while now, I've been experiencing connection stability issues which from
what I can tell seem to stem from the use of dhclient.
After upgrading to the latest wireless-testing kernel, I noticed the output from
wpa_supplicant and iwconfig regarding association status differed as well as an
inability to use dhclient to receive an ip address. In an attempt to resolve the
issue, I first eliminated the use of dhclient by issuing a static ip address for
the interface after it was associated with the AP. Doing so resulted in a very
stable and reliable connection. This led me to believe the issues were a result
of using dhclient. To verify, I tried dhcpcd in place of dhclient, which once
again resulted in a stable and reliable connection. Thus confirming my
suspicion.
While examining the behavior of dhclient and dhcpcd, I maintained a copy of the
resulting dmesg output that was produced for comparison. The results of which,
as
shown below, seem to indicate dhclient is causing the interface to be removed
and
then re-added. While I can only speculate at why this happens, I think it may be
related to the fact that dhclient tries to broadcast on all interfaces related
to
the one that was specified. Thus the command: "dhclient wlan0", causes dhclient
to
broadcast on wmaster0, moni0(when configured), and wlan0.
Despite the information in demsg, when dhclient is used wpa_supplicant seems to
maintain information that it is associated with the AP while iwconfig indicates
otherwise. In any case, the interface enters a state that seems to confuse
wpa_supplicant. Thus wpa_supplicant needs to be restarted or the AP needs to be
explicitly specified using iwconfig wlan0 ap <mac addr>.
While dhclient may clearly be at fault here, I have observed similar behavior on
2.6.25-wl as well as prior kernels. With 2.6.25-wl the output from both
"wpa_cli status" and "iwconfig wlan0" indicate there is an association with the
AP, when it is apparent there is not as a result of the removal and addition of
the interface by dhclient. In which case, issuing a static ip address to the
interface after attempting to use dhclient results in transmission timeouts
while
trying to ping another node on the network. Thus indicating that the interface
is
indeed not associated as otherwise indicated.
Regards,
David Ellingsworth
Output from "uname -r": 2.6.26-rc4-wl
Output from "lspci -vvn":
==================================================================================
00:09.0 0280: 14e4:4320 (rev 02)
Subsystem: 0e11:00e7
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping-
SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 64
Interrupt: pin A routed to IRQ 10
Region 0: Memory at d0000000 (32-bit, non-prefetchable) [size=8K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=2 PME+
Kernel driver in use: b43-pci-bridge
Kernel modules: ssb
Output from "dmesg | grep b43legacy" while using dhcpcd:
==================================================================================
b43legacy-phy0: Broadcom 4306 WLAN found
b43legacy-phy0 debug: Found PHY: Analog 1, Type 2, Revision 1
b43legacy-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2
b43legacy-phy0 debug: Radio initialized
firmware: requesting b43legacy/ucode4.fw
firmware: requesting b43legacy/pcm4.fw
firmware: requesting b43legacy/b0g0initvals2.fw
b43legacy-phy0: Loading firmware version 0x127, patch level 14 (2005-04-18
02:36:27)
b43legacy-phy0 debug: Chip initialized
b43legacy-phy0 debug: 30-bit DMA initialized
b43legacy-phy0 debug: Wireless interface started
b43legacy-phy0 debug: Adding Interface type 2
Output from "wpa_cli status" while using dhcpcd:
==================================================================================
bssid=00:11:22:33:44:55
ssid=myssid
id=2
pairwise_cipher=WEP-104
group_cipher=WEP-104
key_mgmt=NONE
wpa_state=COMPLETED
ip_address=192.168.1.102
Output from "iwconfig wlan0" while using dhcpcd:
==================================================================================
wlan0 IEEE 802.11 ESSID:"myssid"
Mode:Managed Frequency:2.437 GHz Access Point: 00:11:22:33:44:55
Bit Rate=1 Mb/s Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:1111-2222-3333-4444-5555-6666-77
Link Quality=70/100 Signal level:-55 dBm Noise level=-71 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Output from "dmesg | grep b43legacy" while using dhclient:
==================================================================================
b43legacy-phy0: Broadcom 4306 WLAN found
b43legacy-phy0 debug: Found PHY: Analog 1, Type 2, Revision 1
b43legacy-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2
b43legacy-phy0 debug: Radio initialized
firmware: requesting b43legacy/ucode4.fw
firmware: requesting b43legacy/pcm4.fw
firmware: requesting b43legacy/b0g0initvals2.fw
b43legacy-phy0: Loading firmware version 0x127, patch level 14 (2005-04-18
02:36:27)
b43legacy-phy0 debug: Chip initialized
b43legacy-phy0 debug: 30-bit DMA initialized
b43legacy-phy0 debug: Wireless interface started
b43legacy-phy0 debug: Adding Interface type 2
b43legacy-phy0 debug: Removing Interface type 2
b43legacy-phy0 debug: Wireless interface stopped
b43legacy-phy0 debug: DMA-30 0x0260 (RX) max used slots: 1/64
b43legacy-phy0 debug: DMA-30 0x0200 (RX) max used slots: 4/64
b43legacy-phy0 debug: DMA-30 0x02A0 (TX) max used slots: 0/128
b43legacy-phy0 debug: DMA-30 0x0280 (TX) max used slots: 0/128
b43legacy-phy0 debug: DMA-30 0x0260 (TX) max used slots: 0/128
b43legacy-phy0 debug: DMA-30 0x0240 (TX) max used slots: 0/128
b43legacy-phy0 debug: DMA-30 0x0220 (TX) max used slots: 2/128
b43legacy-phy0 debug: DMA-30 0x0200 (TX) max used slots: 0/128
b43legacy-phy0 debug: Radio initialized
b43legacy-phy0 debug: Radio initialized
b43legacy-phy0: Loading firmware version 0x127, patch level 14 (2005-04-18
02:36:27)
b43legacy-phy0 debug: Chip initialized
b43legacy-phy0 debug: 30-bit DMA initialized
b43legacy-phy0 debug: Wireless interface started
b43legacy-phy0 debug: Adding Interface type 2
Output from "wpa_cli status" while using dhclient:
==================================================================================
bssid=00:11:22:33:44:55
ssid=myssid
id=2
pairwise_cipher=WEP-104
group_cipher=WEP-104
key_mgmt=NONE
wpa_state=COMPLETED
Output from "iwconfig wlan0" while using dhclient:
==================================================================================
wlan0 IEEE 802.11 ESSID:"myssid"
Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:1111-2222-3333-4444-5555-6666-77
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
_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
