Please note: This project is no longer active. The website is kept online for historic purposes only.
If you´re looking for a Linux driver for your Atheros WLAN device, you should continue here .

Ticket #2287 (new defect)

Opened 13 years ago

connection is lost for 5-10 seconds about every minute

Reported by: muszi@gungok.dyndns.org Assigned to:
Priority: minor Milestone:
Component: madwifi: other Version:
Keywords: Cc:
Patch is attached: 0 Pending: 0

Description

Connection to AP is lost for 5-10 seconds about every minute if there is almost no traffic (kernel: 2.6.29.1, madwifi-trunk-r4002-20090416). Using kernel 2.6.25.20 and madwifi 0.9.4 on the same hardware does not have this problem.

Tried different APs: an Edimax EW-7206APg (with latest firmware), and a madwifi 0.9.4-based Linux box, does not matter.

Disabling background scanning on the client solves the problem.

This is how pinging the AP looks like from my laptop:

# ping ap
PING ap (192.168.0.131) 56(84) bytes of data.
64 bytes from ap (192.168.0.131): icmp_seq=1 ttl=255 time=10.2 ms
64 bytes from ap (192.168.0.131): icmp_seq=2 ttl=255 time=1.20 ms
64 bytes from ap (192.168.0.131): icmp_seq=3 ttl=255 time=1.19 ms
[snip]
64 bytes from ap (192.168.0.131): icmp_seq=57 ttl=255 time=1.10 ms
64 bytes from ap (192.168.0.131): icmp_seq=58 ttl=255 time=1.11 ms
64 bytes from ap (192.168.0.131): icmp_seq=59 ttl=255 time=1.17 ms
64 bytes from ap (192.168.0.131): icmp_seq=60 ttl=255 time=63.2 ms
[*** packet loss ***]
64 bytes from ap (192.168.0.131): icmp_seq=67 ttl=255 time=16.5 ms
64 bytes from ap (192.168.0.131): icmp_seq=72 ttl=255 time=1.10 ms
64 bytes from ap (192.168.0.131): icmp_seq=73 ttl=255 time=1.14 ms
64 bytes from ap (192.168.0.131): icmp_seq=74 ttl=255 time=1.10 ms
[snip]
64 bytes from ap (192.168.0.131): icmp_seq=162 ttl=255 time=1.54 ms
64 bytes from ap (192.168.0.131): icmp_seq=163 ttl=255 time=1.13 ms
64 bytes from ap (192.168.0.131): icmp_seq=165 ttl=255 time=7.34 ms
[*** packet loss ***]
64 bytes from ap (192.168.0.131): icmp_seq=175 ttl=255 time=1.22 ms
64 bytes from ap (192.168.0.131): icmp_seq=176 ttl=255 time=1.18 ms
64 bytes from ap (192.168.0.131): icmp_seq=177 ttl=255 time=1.15 ms
[snip]
64 bytes from ap (192.168.0.131): icmp_seq=232 ttl=255 time=1.20 ms
64 bytes from ap (192.168.0.131): icmp_seq=233 ttl=255 time=1.63 ms
64 bytes from ap (192.168.0.131): icmp_seq=234 ttl=255 time=1.13 ms
[*** packet loss ***]
64 bytes from ap (192.168.0.131): icmp_seq=240 ttl=255 time=46.7 ms
64 bytes from ap (192.168.0.131): icmp_seq=245 ttl=255 time=1.19 ms
64 bytes from ap (192.168.0.131): icmp_seq=246 ttl=255 time=1.23 ms
64 bytes from ap (192.168.0.131): icmp_seq=247 ttl=255 time=1.19 ms

Signal strength should not be a problem:

# wlanconfig wlan0 list sta
ADDR               AID CHAN RATE RSSI  DBM  IDLE  TXSEQ  TXFRAG  RXSEQ  RXFRAG CAPS ACAPS ERP    STATE     MODE
00:0e:2e:af:61:7b    1   13  24M   48  -47     0    301       7   3059       0 EPSs         4        1   Normal