Robo Blaster [EMAIL PROTECTED] writes:
I'm using madwifi-0.9.1 and wpa_supplicant 0.5.4, so maybe this
doesn't work for everybody, but I recompiled NM with ap_scan=2 and
it works great. Now I quickly connect to APs I couldn't see before
and even the ones I used before are faster. It's
On Wed, 2006-07-12 at 13:35 -0400, Derek Atkins wrote:
I'm sitting here in the IETF, and from where I sit I can hear at least
15 Access Points, some A, some B/G. I get this number by manually
running iwlist ath0 scan and looking at the results. I see
three ESSIDS:
[EMAIL PROTECTED] ~]$
It would be nice if opening the scan list triggered a rescan. In crowded AP
areas, I often have problems getting connected. A contributing problem is that
AP_SCAN always equals 1 if the ssid is in the scan list. A new scan is taken,
my AP isn't there (usually), and it waits, scans again, and
Quoting Dan Williams [EMAIL PROTECTED]:
Hmm. I blame madwifi :) Ok, just kidding.
hahahaha..
However, I was just at a Hyatt in San Diego last weekend, and there were
a _ton_ of access points there. 30. And ipw2200 displayed them all,
and I could even connect to some. The differences
On Wed, 2006-07-12 at 13:51 -0500, Robo Blaster wrote:
It would be nice if opening the scan list triggered a rescan. In crowded AP
areas, I often have problems getting connected. A contributing problem is
that AP_SCAN always equals 1 if the ssid is in the scan list. A new scan is
taken, my
Quoting Dan Williams [EMAIL PROTECTED]:
Actually, it does. When you drop the menu down, NM schedules a scan in
a very short period of time, and reduces the inter-scan interval to 20s.
When you haven't touched the menu for a while, it pushes the scan
interval out to 20 minutes or something
Thanks for the info on scan behaviour. I was worried, because my list wasn't
changing. It may be that the madwifi driver's scan routine usually finds the
same ones.
Wireless scans are never complete or reliable on _any_ platform.
I meant to stress the comparison of using the AP_SCAN parameter
On Wed, 2006-07-12 at 15:12 -0400, Derek Atkins wrote:
Quoting Dan Williams [EMAIL PROTECTED]:
Actually, it does. When you drop the menu down, NM schedules a scan in
a very short period of time, and reduces the inter-scan interval to 20s.
When you haven't touched the menu for a while, it
On Wed, 2006-07-12 at 14:38 -0500, Robo Blaster wrote:
Thanks for the info on scan behaviour. I was worried, because my list wasn't
changing. It may be that the madwifi driver's scan routine usually finds the
same ones.
Wireless scans are never complete or reliable on _any_ platform.
I
Quoting Dan Williams [EMAIL PROTECTED]:
It pulls them down and enlarges the buffer a few times before failing
out if the buffer required is too large. But I don't think you're
hitting this for a number of reasons:
1) if ((errno == E2BIG) (buflen 10)) that means NM will
stop
- Original Message -
From: Dan Williams [EMAIL PROTECTED]
To: Robo Blaster [EMAIL PROTECTED]
Subject: Re: Limit on number of APs? Some way to force-rescan?
Date: Wed, 12 Jul 2006 16:13:50 -0400
On Wed, 2006-07-12 at 14:38 -0500, Robo Blaster wrote:
Thanks for the info on scan
11 matches
Mail list logo
