WINDOWS DISCOVERY TOOLS

Most platforms have one or two popular scanning tools along with a handful of other less feature-filled applications available. Windows is no exception. The ubiquitous NetStumbler is by far the most popular scanning tool, and for the Windows user who wants monitor mode, AiroPeek is the usual solution.

NetStumbler

NetStumbler is by far the most popular scanning tool on Windows. While NetStumbler has a lot of unique features, it also has some drawbacks. It has GPS support, so it can record the location of an access point (AP), but it is not tightly integrated into mapping/ navigation software. Also, because it's an active scanner, it might not be able to find "hidden" APs, and it definitely will not be able to find the name of a hidden AP. Access points that are closed or hidden (your vendor may use different language) don't respond to broadcast probe requests. They also don't transmit their real name in beacons (they are set to null). A examination of how NetStumbler works is detailed here. The best way to see what NetStumbler can do is to install it. One of the biggest advantages of NetStumbler is the intuitive interface. A screenshot of the main window is shown.

umbler's main window

When running NetStumbler on Windows, it may not be clear exactly who is "running" your wireless card. Knowing what your hardware is up to on any platform is important; however, when using an active scanner on Windows, it becomes much more so.
Assuming you are using a recent copy of Windows, you probably have run across the Wireless Zero Configuration service (WZC). If you have ever installed a driver for a wireless card from a CD, you have probably also seen some sort of proprietary wireless configuration client. Almost every vendor has their own. They vary from barely usable, intrusive programs with glitzy interfaces and unnecessary sound effects (Linksys, I'm thinking of you) to feature-rich, useful programs that give you finer control of your wireless card.
The reason that Microsoft developed WZC was to provide users with a uniform experience across wireless cards. Either the wireless configuration client that shipped with the card, or WZC, can be used to configure a modern wireless card on Windows. However, only one of these clients can control the card at any time. If you have another program controlling your wireless card, you will see the Windows Cannot Configure This Device message inside the WZC window.
When using NetStumbler on Windows, either WZC or the card's configuration client can interfere with your scanning. Essentially what is happening is NetStumbler is trying to get your card to send out probe requests periodically and to let it know if any responses come back; at the same time, your wireless configuration utility is telling the card to do its own thing. For example, even though NetStumbler asks your card to send out probe requests, your card may ignore any responses that don't come from the network it is currently connected or connecting to. And maybe it won't send requests out at all.
One of the least desirable things that might happen is that Windows will actually associate and connect to a network when you are just passing by with NetStumbler. Unfortunately, NetStumbler doesn't exactly discourage this, as some of the information it displays can only be gathered by connecting to the network. The act of associating and (possibly) obtaining an IP address from DHCP very likely crosses a legal line. In any case, it can hardly be considered stealthy. In general, you don't want your computer connecting to networks unless you explicitly order it to. Hopefully, this background will provide some insight into the precautions to take when using NetStumbler.


Postingan populer dari blog ini

The 802.11 MAC

Membangun Jaringan Wireless Dengan Mikrotik

Wi-Fi vs. 802.11