Configuring wnda3100 with wireshark on windows : no adapter

The network is the forum.

Moderators: Steel, notfred

Configuring wnda3100 with wireshark on windows : no adapter

Postposted on Sat Jul 16, 2011 7:05 am

hi,

My aim is to test and verify my wlan is well secured and safe.
so i'd like to use wireshark with my wnda3100 adapter (usb netgear).

but once, wireshark is installed, it doesn't show my usb wireless adapter.

Do you know why ?

My Os windows xp is original sp3 updated, and my drivers are Ok : 3.0.0.141

thanks for your little help.

Mike

best regards
Michael REMY
Gerbil
 
Posts: 12
Joined: Mon Jun 06, 2011 9:18 am

Re: Configuring wnda3100 with wireshark on windows : no adap

Postposted on Sat Jul 16, 2011 11:23 am

I know under Linux you need to have root permissions to capture from an interface with wireshark, I suspect something similar under Windows - are you trying it as Administrator or just as a normal user?
notfred
Grand Gerbil Poohbah
 
Posts: 3775
Joined: Tue Aug 10, 2004 10:10 am
Location: Ottawa, Canada

Re: Configuring wnda3100 with wireshark on windows : no adap

Postposted on Sat Jul 16, 2011 12:05 pm

notfred wrote:I know under Linux you need to have root permissions to capture from an interface with wireshark, I suspect something similar under Windows - are you trying it as Administrator or just as a normal user?

Definitely need admin privs to run Wireshark in Windows.
Life is hard; but it's harder if you're stupid. Big Al.
Captain Ned
Global Moderator
Gold subscriber
 
 
Posts: 20640
Joined: Wed Jan 16, 2002 7:00 pm
Location: Vermont, USA

Re: Configuring wnda3100 with wireshark on windows : no adap

Postposted on Sat Jul 16, 2011 1:57 pm

You need support for Promiscuous Mode. The wiki should give you a good start on how/if you can enable it on any specific adaptor.

http://en.wikipedia.org/wiki/Promiscuous_mode

EDIT: I didn't fully read your orignial post. Getting a wireless adapter with promiscuous mode will still solve your problem, but windows sees wireless packets different than wired packets. Wireshark uses WinPcap to capture packets. It only works with a few wireless adapters. In order to get it fully functional with wireless you need to get the wireless version of WinPcap called AirPcap
Last edited by LaChupacabra on Sat Jul 16, 2011 5:30 pm, edited 1 time in total.
LaChupacabra
Gerbil First Class
Gold subscriber
 
 
Posts: 138
Joined: Tue Dec 30, 2008 10:59 pm

Re: Configuring wnda3100 with wireshark on windows : no adap

Postposted on Sat Jul 16, 2011 3:44 pm

yes my user accound is administrator priviledge. and i also see ethernet connexion adapter (which is not wireless at all!)

ok, i will see into this docu.

thanks.
Michael REMY
Gerbil
 
Posts: 12
Joined: Mon Jun 06, 2011 9:18 am

Re: Configuring wnda3100 with wireshark on windows : no adap

Postposted on Sat Jul 16, 2011 5:36 pm

i solved my problem.
in fact my usb adapter is named as Atheros OTUS wireless network adapter instead of Netgear WNDA3100. so i didn't understand it was it !
and now it runs ! (cause i disabled promiscuous mode)
Michael REMY
Gerbil
 
Posts: 12
Joined: Mon Jun 06, 2011 9:18 am

Re: Configuring wnda3100 with wireshark on windows : no adap

Postposted on Sun Jul 17, 2011 2:21 pm

A lot of the cheaper network stuff (both wired and wireless) is actually repackaged and rebranded. Wireshark and drivers will usually be for the original chip rather than for the name on the box. It's easy enough to see the chip on a PCI / PCIe card, but obviously you don't want to go opening up USB stuff. If you can find a utility that lists off the device identifiers (e.g. in Linux "lsusb") that can help in working out what driver you need or what it will be called in wireshark etc.
notfred
Grand Gerbil Poohbah
 
Posts: 3775
Joined: Tue Aug 10, 2004 10:10 am
Location: Ottawa, Canada

Re: Configuring wnda3100 with wireshark on windows : no adap

Postposted on Sun Jul 17, 2011 3:35 pm

notfred wrote:A lot of the cheaper network stuff (both wired and wireless) is actually repackaged and rebranded. Wireshark and drivers will usually be for the original chip rather than for the name on the box. It's easy enough to see the chip on a PCI / PCIe card, but obviously you don't want to go opening up USB stuff. If you can find a utility that lists off the device identifiers (e.g. in Linux "lsusb") that can help in working out what driver you need or what it will be called in wireshark etc.


Plugging in the FCC ID into the EAS search is also handy for determining the chipset.
#182 TT: 13/DNVT, Precedence: Flash Override. Switch: Node Center. MSE forever.
Contingency
Gerbil Jedi
 
Posts: 1533
Joined: Sat Jun 19, 2004 4:03 pm
Location: al.us


Return to Networking

Who is online

Users browsing this forum: Google [Bot] and 6 guests