Page 1 of 1

Official NetStumbler Version 0.3 FAQ

PostPosted: Tue Jul 23, 2002 9:19 am
by blackwave
· Where is the Official NetStumbler Version 0.3 FAQ?
http://www.netstumbler.com/modules.php?op=modload&name=FAQ&file=index&myfaq=yes&id_cat=1&categories=Official+NetStumbler+Version+0.3+FAQ

excerpt from ONSFAQ:
· Who should use this program?
Security folks wanting to check that their corporate LAN isn't wide open
Systems admins wanting to check coverage of their Wireless LAN
Gatherers of demographic information about 802.11 popularity
Drive-by snoopers
Overly curious bystanders.

· What OS does this work on?
Windows 2000, Windows 9x, Windows XP.

· What cards does it work on?
Version 0.3 works on:
Lucent Technologies WaveLAN/IEEE (Agere ORiNOCO) Dell TrueMobile 1150 Series (PCMCIA and mini-PCI) Avaya Wireless PC Card Toshiba Wireless LAN Card (PCMCIA and built-in) Compaq WL110 Cabletron/Enterasys Roamabout Elsa Airlancer MC-11 ARtem ComCard 11Mbps IBM High Rate Wireless LAN PC Card 1stWave 1ST-PC-DSS11IS, DSS11IG, DSS11ES, DSS11EG

· Will this work on 802.11a cards?
Yes, in Windows XP.

· I only see my own network / I don't see any networks. How do I fix this?
Possible solutions:
Try using the client manager to create and use a profile that uses AP mode, with an empty network name.
Orinoco networks that are configured to be "closed" will not appear, because they do not respond to the probe requests that Network Stumbler sends.

· Is there an equivalent utility for Linux / *BSD?
See dstumbler and kismet.

· Will this be ported to Windows CE?
If you send me a suitable system, I'll be happy to port it at my leisure (and return the unit to you!).

· What does the Flag field mean?
The flag field contains the 802.11 capability information in hexadecimal. It's documented in section 7.3.1.4 of the 802.11b spec. To save you having to go and look, the bits are: 0001 ESS ("Infrastructure")
0002 IBSS ("Ad-Hoc")
0004 CF-Pollable
0008 CF-Poll Request
0010 Privacy ("WEP")
0020 Short Preamble
0040 PBCC
0080 Channel Agility
FF00 Reserved

updated: 11-22-02

PostPosted: Sat Aug 31, 2002 10:49 am
by Eyecannon
bw, think it's time to update the FAQ!! XP works, and I think there's a few other things that have been fixed/changed... also might want to mention kismet as a linux alternative. Feel free to delete this post :)

PostPosted: Wed Sep 04, 2002 8:46 am
by unclex

PostPosted: Wed Sep 04, 2002 8:56 am
by blackwave
Originally posted by Eyecannon
bw, think it's time to update the FAQ!! XP works, and I think there's a few other things that have been fixed/changed... also might want to mention kismet as a linux alternative. Feel free to delete this post :)


Thanks Eyecannon, little by little we are changing things, logging things, we plan to come out with a large FAQ/user guide type of thing... if you have spare time feel free to post which post id's and thread id's should be updated, usually I try to include the NetStumbler version when talking about compatibilities so this would not be changed since it specifies that NSv0.3.23 does not support prism, and never will... but NSv.0.3.30 always has supported prism/xp... :)

PostPosted: Thu Sep 19, 2002 5:48 pm
by subterphuge
With marius' reply in my ZoneAlarm thread, perhaps you might want to add the following to the FAQ:

Q. Does Netstumbler need TCP/IP enabled on your wireless card at all? (Or: why does ZoneAlarm occasionally show Netstumbler wanting to access 255.255.255.255 port 192?)

A. Netstumbler doesn't need the TCP/IP protocol bound to the wireless adapter to get SSIDs. However, if you want to be able to determine the wired-side MAC address on certain Orinoco APs, you need to have TCP/IP enabled so that Netstumbler can send a query to IP 255.255.255.255 port 192 to fetch that info.

(Or something to that effect.)

PostPosted: Thu Sep 19, 2002 5:51 pm
by blackwave
Originally posted by subterphuge
With marius' reply in my ZoneAlarm thread, perhaps you might want to add the following to the FAQ:


Thanks subterphuge, you just did. :)

NDIS 5.1

PostPosted: Sun Nov 23, 2003 10:16 pm
by miguelrvs
I suggest adding to the current an future faq's in the part of <b>supported cards </b> any card that has a ndis driver under XP, I have tested 6 of "unsuported" and they work even if the chipset is unsuported by NS, as long the ndis driver is up and running, in fact, NS displays 2 cards with the same name, one with the chipset (if the chipset is unsupported it's greyed out) and one more with the "ndis 5.x" chipset.

Re: NDIS 5.1

PostPosted: Mon Nov 24, 2003 2:43 am
by G8tK33per
Originally posted by miguelrvs
I suggest adding to the current an future faq's in the part of <b>supported cards </b> any card that has a ndis driver under XP, I have tested 6 of "unsuported" and they work even if the chipset is unsuported by NS, as long the ndis driver is up and running, in fact, NS displays 2 cards with the same name, one with the chipset (if the chipset is unsupported it's greyed out) and one more with the "ndis 5.x" chipset.

The NDIS drivers are inherent to the operating system, not the card.

Re: NDIS 5.1

PostPosted: Mon Nov 24, 2003 5:13 am
by Thorn
Originally posted by miguelrvs
I suggest adding to the current an future faq's in the part of <b>supported cards </b> any card that has a ndis driver under XP, I have tested 6 of "unsuported" and they work even if the chipset is unsuported by NS, as long the ndis driver is up and running, in fact, NS displays 2 cards with the same name, one with the chipset (if the chipset is unsupported it's greyed out) and one more with the "ndis 5.x" chipset.

The problem is that unsupported cards may work on your system fine, but will not work on an "identical" system. Unsupported cards may also have sudden failures or unexplained hangs. This is all part of the behavior of the NDIS drivers.

The "acid test" for NS 0.3.30 is Win9x. If it runs there, it will run on any system. Only the supported cards pass this test.

All of this is is well known, and detailed in numerous places here. Please keep reading.