I have had a bit of a read into these functions: bgscan - Enable or disable background scanning. By default it is on so 1. Can be turned off by setting it to 0. bgscanidle - How often is background scanning done. Measured in milliseconds. By default it is set to 250. The minimum is 100. I think this measures how long the medium must be idle for before it begins a background scan. Does this include management frames. If it does then the medium may never be idle. bgscanintvl - How often a background scan is performed. Measured in seconds. By default it is set to 300s or 5 mins. The minimum is 15 seconds. scanvalid - Scan cache valid threshold. By default it is 60. Not really sure what this does. So, as far as my understanding goes, if you have bgscan set to 1, the device will perform background scanning. Once the bgscanintvl has been reached the device will wait until the device has been idle for bgscanidle. Is this correct? I have been playing around with these values but the "iwlist scan" and "wlanconfig ath0 list scan" outputs always remain the same. Has anyone else looked into this before? Thanks Dave Quoting Michael Taylor <mike.taylor@apprion.com>:------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
| KOSAKI Motohiro | [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" |
| Faik Uygur | Re: Linux 2.6.21-rc1 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Trent Piepho | [PATCH] [POWERPC] Improve (in|out)_beXX() asm code |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jens Axboe | Re: [BUG] New Kernel Bugs |
