© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
I have the same problem as listed in the description, and it's generally pretty quick (1 < n < 5 minutes).
I thought it may be due to bad noise rejection by the wireless card, but running 'cat /proc/net/wireless' in a looping script that logs to /var/log/wireless shows the connection drops with an over-all quality value of 64/70, -46 signal strength, -72 noise, average values of 55 / -55 / -73.
I scanned for other wireless networks ( iwlist wlan0 scan ) and made sure I was using a channel others weren't (1, 4, 11 were used, so I chose 7), average values of 57. -53. -72. and still lost the connection.
The solution (which was not necessary with Windows 2000 on the same hardware) was to set the Wireless Access Point 'Control Tx Rates' to 18Mbps. This changes the way the AP sends information and "boosts the distance," although my test distance was 4 feet from the AP, no walls, direct line-of-sight, so distance wasn't an issue. Higher Tx rates use different encoding (such as 36, 48, and 54Mbps as compared to 18Mbps), and do not work as well.
I can now hold a connection at 20' through plaster walls without a problem, although a longer observation time is needed (currently on 2 days).