Now I switched to WEP auth, for trying:<br><br><br>wlan0 IEEE 802.11bg ESSID:"XXXX" <br> Mode:Managed Frequency:2.437 GHz Access Point: 00:18:4D:2E:85:4A <br> Bit Rate=5.5 Mb/s Tx-Power=20 dBm <br>
Retry long limit:7 RTS thr:off Fragment thr:off<br> Encryption key:XXXX-XXXX-XXXX-XXXX-XXXX-XXXX<br> Power Management:off<br> Link Quality=70/70 Signal level=-23 dBm <br> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0<br>
Tx excessive retries:0 Invalid misc:0 Missed beacon:0<br><br>The wlan0 interface is up & running:<br><br>ifconfig wlan0 |grep inet<br> inet addr:192.168.0.100 Bcast:192.168.0.255 Mask:255.255.255.0<br>
inet6 addr: fe80::21d:60ff:fee7:53b8/64 Scope:Link<br><br>but nothing to do: it does not ping the ap (192.168.0.2)<br><br>PING 192.168.0.2 (192.168.0.2) 56(84) bytes of data.<br><br>--- 192.168.0.2 ping statistics ---<br>
3 packets transmitted, 0 received, 100% packet loss, time 2016ms<br><br>Here's a dmesg output:<br><br>[ 160.482533] b43-phy1: Broadcom 4318 WLAN found (core revision 9)<br>[ 160.524036] b43-phy1 debug: Found PHY: Analog 3, Type 2, Revision 7<br>
[ 160.524058] b43-phy1 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 8<br>[ 160.548601] phy1: Selected rate control algorithm 'minstrel'<br>[ 160.549717] Registered led device: b43-phy1::tx<br>[ 160.549746] Registered led device: b43-phy1::rx<br>
[ 160.549778] Registered led device: b43-phy1::assoc<br>[ 160.549799] Registered led device: b43-phy1::radio<br>[ 160.549911] Broadcom 43xx driver loaded [ Features: PL, Firmware-ID: FW13 ]<br>[ 181.508303] b43 ssb0:0: firmware: requesting b43/ucode5.fw<br>
[ 181.510885] b43 ssb0:0: firmware: requesting b43/pcm5.fw<br>[ 181.513857] b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw<br>[ 181.516679] b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw<br>[ 181.632028] b43-phy1: Loading firmware version 410.2160 (2007-05-26 15:32:10)<br>
[ 181.652056] b43-phy1 debug: Chip initialized<br>[ 181.652203] b43-phy1 debug: 32-bit DMA initialized<br>[ 181.652211] b43-phy1 debug: QoS disabled<br>[ 181.672368] b43-phy1 debug: Wireless interface started<br>[ 181.704094] b43-phy1 debug: Adding Interface type 2<br>
[ 181.734463] ADDRCONF(NETDEV_UP): wlan0: link is not ready<br>[ 181.916349] wlan0: authenticate with 00:18:4d:2e:85:4a (try 1)<br>[ 181.917759] wlan0: 00:18:4d:2e:85:4a denied authentication (status 13)<br>[ 181.918140] wlan0: authenticate with 00:18:4d:2e:85:4a (try 1)<br>
[ 181.923714] wlan0: authenticated<br>[ 181.924100] wlan0: associate with 00:18:4d:2e:85:4a (try 1)<br>[ 181.925832] wlan0: RX AssocResp from 00:18:4d:2e:85:4a (capab=0x411 status=0 aid=1)<br>[ 181.925834] wlan0: associated<br>
[ 181.926327] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready<br>[ 191.932006] wlan0: no IPv6 routers present<br><br>I'm using a netgear <span class="postbody">WG602 v3 as access point with 1.2.5 firmware.<br><br>
</span>Now I'm trying to upgrade AP firmware with WRT<br><br><br><div class="gmail_quote">2010/6/22 Larry Finger <span dir="ltr"><<a href="mailto:Larry.Finger@lwfinger.net">Larry.Finger@lwfinger.net</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">On 06/22/2010 01:54 PM, Fabrizio Regalli wrote:<br>
> Gábor, Larry<br>
><br>
> first of all, excuse me for my mistake: I forget to add in Cc: the ml.<br>
><br>
> The actual situation is:<br>
><br>
> ## /etc/modprobe.d/b43.conf ##<br>
><br>
> options b43 pio=0 qos=0 nohwcrypt=1<br>
><br>
> I remove network-manager and gnome-network-manager<br>
<br>
</div>That step was not necessary. I run under the KDE NetworkManager all the time.<br>
<div class="im"><br>
> It seems to recognize correctly the access point:<br>
><br>
> ## iwconfig ##<br>
><br>
> wlan0 IEEE 802.11bg ESSID:"XXXXX"<br>
> Mode:Managed Frequency:2.472 GHz Access Point:<br>
> 00:18:4D:2E:85:4A<br>
> Bit Rate=1 Mb/s Tx-Power=20 dBm<br>
> Retry long limit:7 RTS thr:off Fragment thr:off<br>
> Encryption key:off<br>
> Power Management:off<br>
> Link Quality=70/70 Signal level=-21 dBm<br>
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0<br>
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0<br>
<br>
</div>Yes, you are associated.<br>
<div class="im"><br>
><br>
> ## ifconfig ##<br>
><br>
> wlan0 Link encap:Ethernet HWaddr 00:1d:60:e7:53:b8<br>
> inet addr:192.168.0.100 Bcast:192.168.0.255 Mask:255.255.255.0<br>
> inet6 addr: fe80::21d:60ff:fee7:53b8/64 Scope:Link<br>
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br>
> RX packets:49 errors:0 dropped:0 overruns:0 frame:0<br>
> TX packets:91 errors:0 dropped:0 overruns:0 carrier:0<br>
> collisions:0 txqueuelen:1000<br>
> RX bytes:4471 (4.3 KiB) TX bytes:12226 (11.9 KiB)<br>
<br>
</div>You also have an IP number. Some systems have trouble with IPv6. If you do<br>
not need it, you might disable it.<br>
<div class="im"><br>
> but the ping is very horrible and the connection is unstable:<br>
><br>
><br>
> ING 192.168.0.2 (192.168.0.2) 56(84) bytes of data.<br>
</div>> 64 bytes from 192.168.0.2 <<a href="http://192.168.0.2" target="_blank">http://192.168.0.2</a>>: icmp_req=1 ttl=64<br>
> time=2180 ms<br>
> 64 bytes from 192.168.0.2 <<a href="http://192.168.0.2" target="_blank">http://192.168.0.2</a>>: icmp_req=3 ttl=64<br>
> time=888 ms<br>
><br>
<div class="im">> 24 packets transmitted, 13 received, 45% packet loss, time 23128ms<br>
> rtt min/avg/max/mdev = 215.307/2399.514/5875.790/1923.942 ms, pipe 6<br>
<br>
</div>Yes - awful performance.<br>
<div class="im"><br>
><br>
> ..<br>
><br>
> I'm using wpa_supplicant with wpa2 authentication Could be this the<br>
> problem?<br>
<br>
</div>No. I use WPA2 authentication all the time.<br>
<br>
I have no idea what is causing the changes in performance. I do not see<br>
them. My system will go off-line once in a while, but I never see the<br>
dropouts or the very long ping times.<br>
<font color="#888888"><br>
Larry<br>
</font></blockquote></div><br>