Bugzilla – Bug 344
no wireless stats when not associated
Last modified: 2005-10-03 13:59:45
You need to log in before you can comment on or make changes to this bug.
I installed the FC2 RPM for waproamd from the DAG repository and tested. With T42 booted, the driver loaded but not configured, syslog produced the following messages. Oct 24 01:01:06 localhost waproamd(eth1)[3609]: 1. Found AP 00:01:24:f0:40:5a, ESSID 'cuairnet', script: yes Oct 24 01:01:06 localhost waproamd(eth1)[3609]: Scan completed with 1 suitable networks. (total: 1) Oct 24 01:01:06 localhost waproamd(eth1)[3609]: Failed to get interface quality I believe waproamd queries the network interface for wireless stats; v0.12 of the ipw2100 driver doesn't return any wireless stats if it is not currently associated. This is also causing problems for scripts that rely on /proc/net/wireless as that won't list an entry if it doesn't return stats, even if not associated.
fixed in 0.14
Can see some data in /proc/net/wireless with ipw2200 v0.14. Bill, Does this version fix your waproamd failure? If yes, please verify the bug.
2.6.9-1.681_FC3 wireless-tools-27-0.pre25.4 (development, FC3 released with .3) ipw2200-0.14 with IW_QUAL_QUAL_INVALID patch waproamd-0.6-1.1.fc3.rf syslog from boot waproamd(eth1)[2206]: Scan results: waproamd(eth1)[2206]: 1. Found AP 00:01:24:f0:40:5a, ESSID 'cuairnet', script: yes waproamd(eth1)[2206]: Scan completed with 1 suitable networks. (total: 1) waproamd(eth1)[2206]: Selected new AP 00:01:24:f0:40:5a with ESSID 'cuairnet' waproamd(eth1)[2206]: Running script '/etc/waproamd/scripts/essid:cuairnet start' rc: Starting waproamd: succeeded waproamd(eth1)[2206]: client: Setting policy 'open' waproamd(eth1)[2206]: client: Determining IP information for eth1... done. waproamd did not work with ipw2200-0.13. Fix of bug #344 has corrected this problem.
Mark the bug as Verified: Fixed.