Re: Backwards thinking - forced re-connect
- From: Jeff Liebermann <jeffl@xxxxxxxxxx>
- Date: Mon, 22 Dec 2008 13:38:06 -0800
On Mon, 22 Dec 2008 13:58:00 -0600, "Lloyd E. Sponenburgh"
Jeff Liebermann <jeffl@xxxxxxxxxx> fired this volley in
Otherwise, use a connection tool that manages connections by MAC
address instead of just SSID. For example:
<http://www.wifihopper.com> ($18 students, $35 other)
This way, you can manually select the strongest AP to connect.
Yeah... I've got the Intel Pro-Set wireless tool, and it has that
I suspect a competent programmer could put together a background task
that "watched" signal levels, and did the same steps automatically as
if by hand.
But I did not say, and should have, that each of these zones can have
a different SSID. In fact, that would be appropriate in order to
identify their association with a specific building.
Would that change the nature of the task?
Welcome to the search for the holy grail. In this case, it's called
Methinks you're asking for the impossible (or the rediculous). All
the fast roaming specs are based on one assumption, that you want to
connect to a specific network as identified by a specific SSID. If
you want to connect to *ANY* random network, regardless of SSID, the
algorithm must be very different. For example, you will need a list
of included acceptable SSID's. You'll also need an exclusion list to
avoid black holes, slow networks with strong signals, and other
undesireables. Fortunately, there is software that does some of this.
It has a list of known open access points and automatically connects
you when in range. However, under the surface, it's just another
wireless connection manager. I've played with it on my XV6700 Windoze
Mobile phone. No conclusions yet.
If this is unacceptable, someone (not me) can scribble a VBS script
that takes the output of the Windoze network status commands, filters
the mess for SSID, signal strength, SNR, or whatever your fancy, and
determines whether to change connections. It's easy enough in Vista,
where the incantation:
netsh wlan show networks mode=bssid
delivers the desired info. However, to do the same with XP or W2K
would require a program the excavates the numbers from the NDIS
driver. Once you have the data and decision mechanism, it's
impossible to swap AP's without losing the IP address. Well, not
exactly. If your network of AP's has Cisco or 3com proprietary
roaming features, you can do seamless roaming. But with a random mix
of commodity routers, forget it. The best you can do is issue a
disconnect command to the driver, and then reconnect to the new AP.
If I find anything useful, I'll send it your way, but offhand, I
suspect this is a major project.
Jeff Liebermann jeffl@xxxxxxxxxx
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558
- Prev by Date: Re: Inexpensive point-to-point solution needed
- Next by Date: Re: Backwards thinking - forced re-connect
- Previous by thread: Re: Backwards thinking - forced re-connect
- Next by thread: Re: Backwards thinking - forced re-connect