WLAN signal detect to long

Claas · 06-02-2004

I notice that the WLAN signals kept too long. For example: I detect a new AP. Then I drive on and 500 m away I still detect the signal. Or: I am standing before a red traffic light. Still detecting a signal from an AP. Then, suddenly, the AP is not reachable.
I test this with my own AP. I switch it on and 5 sec later my notebook and NS detect the signal. Then I switch off the AP – and approx. 35 sec I detect the signal.
That's different when my notebook was logged in into my AP. Then, after I switch off the AP, the signal detection is lost after 5 sec.
And I think it's not a problem of NS – it's a problem of my WLAN card (Intel pro wireless 2100 3B mini pci adapter) or Windows XP.

Can I force it to "rescan" faster ?

beauvoir · 06-02-2004

I think there is a feature that allows netstumbler to probe more times per sec. If you click on View then Options, and then move the scan speed slider to fast. This should do the trick - i think

Claas · 06-02-2004

Quote:

Originally Posted by beauvoir

I think there is a feature that allows netstumbler to probe more times per sec.

I wrote that this problem also appears when NetStumbler is not running. But perhaps NetStumbler can force the re-scan by itself ...

Quote:

Originally Posted by beauvoir

If you click on View then Options, and then move the scan speed slider to fast. This should do the trick - i think

The slider already was set to "fast" ...

Thorn · 06-02-2004

You can also allow the GPS to control the scan rate. The slower velocity will result in slower scans; higher velocity give faster scans.

View|Options|General tab. Check the "Auto adjust using GPS" checkbox.

Dutch · 06-02-2004

Not knowing if the Intel card is based on the Atheros chipset, but the symptoms you describe, sounds like the ones Marius wrote about regarding the Atheros support in Netstumbler.

As why you have the same problem outside of Netstumbler beats me.

Some more info please.. OS, Driver version, If a reinstall/downgrade of the driver change the behaviour, etc etc

Just my 0.02€'s worth...

Dutch

JTX · 06-02-2004

I have the Intel Pro/Wireless 2100 3B aka "Centrino" card as well. NS 0.4 works with it, but i have the same problems. The card doesn't seem to refresh at realtime, so I while i drive, it still says it's getting signal from a block away.

I noticed that Windows XP's WZC also shows the same symptom while I was installing a new AP in the house. After I changed the SSID of the new AP from the default to something else, the WZC for the Intel card didn't update. I had to manually go into the WZC config page and click the Refresh button.

It seems to me it's a driver/hardware issue. It never bugged me since I use my Orinoco cards when i drive.

Claas · 06-03-2004

Quote:

Originally Posted by JTX

... The card doesn't seem to refresh at realtime, so I while i drive, it still says it's getting signal from a block away.
I noticed that Windows XP's WZC also shows the same symptom ...

I have tested a simple batch file:
€echo off
net stop WZCSVC
net start WZCSVC

This stops and restarts the WZC service within 15 sec. And this do also the job for a refresh. Perhaps I should program this batch job as an infinite loop with 5 sec delay after "net start WZCSVC" ...

06-02-2004	#1 (permalink)
Claas Registered Member Join Date: May 2004 Location: Germany Posts: 24	WLAN signal detect to long I notice that the WLAN signals kept too long. For example: I detect a new AP. Then I drive on and 500 m away I still detect the signal. Or: I am standing before a red traffic light. Still detecting a signal from an AP. Then, suddenly, the AP is not reachable. I test this with my own AP. I switch it on and 5 sec later my notebook and NS detect the signal. Then I switch off the AP – and approx. 35 sec I detect the signal. That's different when my notebook was logged in into my AP. Then, after I switch off the AP, the signal detection is lost after 5 sec. And I think it's not a problem of NS – it's a problem of my WLAN card (Intel pro wireless 2100 3B mini pci adapter) or Windows XP. Can I force it to "rescan" faster ?

06-02-2004	#2 (permalink)
beauvoir Registered Member Join Date: May 2004 Posts: 24	I think there is a feature that allows netstumbler to probe more times per sec. If you click on View then Options, and then move the scan speed slider to fast. This should do the trick - i think __________________ A World Without Wardriving is like the Sea Without Water!

06-02-2004	#4 (permalink)
Thorn Did you do the math? Join Date: Apr 2002 Location: Villa Straylight Posts: 10,351	You can also allow the GPS to control the scan rate. The slower velocity will result in slower scans; higher velocity give faster scans. View\|Options\|General tab. Check the "Auto adjust using GPS" checkbox. __________________ Thorn "Read Altas Shrugged. Compare it to today. Repeat as necessary"

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

06-02-2004	#5 (permalink)
Dutch Humourless EuroMod. Join Date: Mar 2004 Location: City of Mermaids, Denmark Posts: 6,819	Not knowing if the Intel card is based on the Atheros chipset, but the symptoms you describe, sounds like the ones Marius wrote about regarding the Atheros support in Netstumbler. As why you have the same problem outside of Netstumbler beats me. Some more info please.. OS, Driver version, If a reinstall/downgrade of the driver change the behaviour, etc etc Just my 0.02€'s worth... Dutch

06-02-2004	#6 (permalink)
JTX kawaii desu ne Join Date: Oct 2003 Location: Vancouver, BC Posts: 72	I have the Intel Pro/Wireless 2100 3B aka "Centrino" card as well. NS 0.4 works with it, but i have the same problems. The card doesn't seem to refresh at realtime, so I while i drive, it still says it's getting signal from a block away. I noticed that Windows XP's WZC also shows the same symptom while I was installing a new AP in the house. After I changed the SSID of the new AP from the default to something else, the WZC for the Intel card didn't update. I had to manually go into the WZC config page and click the Refresh button. It seems to me it's a driver/hardware issue. It never bugged me since I use my Orinoco cards when i drive.