Ubuntu
linux package

  1. Bug #331103
  2. Comment #21

Comment 21 for bug 331103

Revision history for this message
pacaj2am (paci-paci) wrote : Re: Wireless network disconnects randomly, won't reconnect

I dont think it affcet wireless drivers for particular network card. I saw a lot posts on iternet and this porblem is affecting all range of wireles cards (eg. http://ubuntuforums.org/showthread.php?t=1146367&page=11). I also dont thionk Network-manager or something else is the reason. I palied a little and found, that when the connection drops, the rate of wireless card is set just to 1Mbit and than conecction drops (ping fails...).

root@paci-laptop:~# iwconfig wlan0
wlan0 IEEE 802.11abgn ESSID:"pacihome"
          Mode:Managed Frequency:2.422 GHz Access Point: 00:1F:1F:1C:C0:D0
          Bit Rate=1 Mb/s Tx-Power=15 dBm
          Retry min limit:7 RTS thr:off Fragment thr:off
          Encryption key:1575-9C1D-20BA-10B9-1C9C-E276-CD02-BDCD [2] Security mode:open
          Power Management:off
          Link Quality=38/70 Signal level=-72 dBm Noise level=-93 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

root@paci-laptop:~# iwconfig wlan0 rate 54M
root@paci-laptop:~# iwconfig wlan0
wlan0 IEEE 802.11abgn ESSID:"pacihome"
          Mode:Managed Frequency:2.422 GHz Access Point: 00:1F:1F:1C:C0:D0
          Bit Rate=54 Mb/s Tx-Power=15 dBm
          Retry min limit:7 RTS thr:off Fragment thr:off
          Encryption key:1575-9C1D-20BA-10B9-1C9C-E276-CD02-BDCD [2] Security mode:open
          Power Management:off
          Link Quality=34/70 Signal level=-76 dBm Noise level=-95 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

it also seems that outgoing packets are sent and he accespoint accepts them, because when i reconnect quickly i can see very long returning icmp packets:

64 bytes from 192.168.2.1: icmp_seq=47 ttl=64 time=2.45 ms
64 bytes from 192.168.2.1: icmp_seq=48 ttl=64 time=2.40 ms
-----here occures the disconnection---
64 bytes from 192.168.2.1: icmp_seq=49 ttl=64 time=31079 ms
64 bytes from 192.168.2.1: icmp_seq=50 ttl=64 time=30071 ms
64 bytes from 192.168.2.1: icmp_seq=51 ttl=64 time=29063 ms
64 bytes from 192.168.2.1: icmp_seq=52 ttl=64 time=28055 ms
64 bytes from 192.168.2.1: icmp_seq=53 ttl=64 time=27047 ms
64 bytes from 192.168.2.1: icmp_seq=54 ttl=64 time=26039 ms
64 bytes from 192.168.2.1: icmp_seq=55 ttl=64 time=25031 ms
64 bytes from 192.168.2.1: icmp_seq=56 ttl=64 time=24023 ms
64 bytes from 192.168.2.1: icmp_seq=57 ttl=64 time=23015 ms
64 bytes from 192.168.2.1: icmp_seq=58 ttl=64 time=22001 ms
64 bytes from 192.168.2.1: icmp_seq=59 ttl=64 time=21001 ms
64 bytes from 192.168.2.1: icmp_seq=60 ttl=64 time=20001 ms
64 bytes from 192.168.2.1: icmp_seq=61 ttl=64 time=19001 ms
64 bytes from 192.168.2.1: icmp_seq=62 ttl=64 time=18001 ms
64 bytes from 192.168.2.1: icmp_seq=63 ttl=64 time=17001 ms
64 bytes from 192.168.2.1: icmp_seq=80 ttl=64 time=9.81 ms
64 bytes from 192.168.2.1: icmp_seq=81 ttl=64 time=2.43 ms
64 bytes from 192.168.2.1: icmp_seq=82 ttl=64 time=2.39 ms

It is really just question of Jaunty. 8.10 worked well.

Jan