Go Back   Wireless and Wifi Forums > News > Newsgroups > alt.internet.wireless
Register FAQ Forum Rules Members List Calendar Search Today's Posts Advertise Mark Forums Read

 
Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 05-12-2011, 09:23 PM
Aaron Leonard
Guest
 
Posts: n/a
Default Wireless Sniffing in Windows 7 with Netmon 3.4

Just posted this article:

Wireless Sniffing in Windows 7 with Netmon 3.4
https://supportforums.cisco.com/docs/DOC-16398

Let me know if there are any suggestions or corrections. Also I would be
interested in hearing whether anyone has an adapter / driver that appears
to successfully sniff 802.11n frames using Netmon (unfortunately, the Intel
11n adapters do not.)

Cheers,

Aaron

Reply With Quote
  #2 (permalink)  
Old 05-14-2011, 05:21 PM
Axel Hammerschmidt
Guest
 
Posts: n/a
Default Re: Wireless Sniffing in Windows 7 with Netmon 3.4

Aaron Leonard:

<snip>

> Also I would be interested in hearing whether anyone has an
> adapter / driver that appears to successfully sniff 802.11n frames
> using Netmon (unfortunately, the Intel 11n adapters do not.)


How do I tell from looking at the sniffed packets, that they really
are 802.11n?

I'm using Netmon 3.4 (Monitor Mode) with an Apple Macbook, Early 2009
running Windows Vista. Chipset is Broadcom 43xx, the driver is
probably an Apple Boot Camp driver - I'll check.

The AP is a Netgear WNHDE111 - well, actually a WNHDEB111, but I'm
only using one of them as an AP - 5 GHz, 802.11 Mode is set to
"802.11n only".

And security is disabled.

The Network Interface Configuration in NM 3.4 will not let me choose
802.11a channels, only 802.11n - and 802.11b/g. This setup is done
before capture is started.

So the packets probably are 802.11n. However I'm not sure that they
are 40 MHz packets. How to tell?

BTW, why are you using Wireshark when NM3.4 has easy to write
filters?


--
Banned from Version2.dk for writing a Firesheep script.

Reply With Quote
  #3 (permalink)  
Old 05-15-2011, 05:50 AM
Jeff Liebermann
Guest
 
Posts: n/a
Default Re: Wireless Sniffing in Windows 7 with Netmon 3.4

On 14 May 2011 17:21:57 GMT, Axel Hammerschmidt <hlexa@hotmail.com>
wrote:

>Aaron Leonard:
>
><snip>
>
>> Also I would be interested in hearing whether anyone has an
>> adapter / driver that appears to successfully sniff 802.11n frames
>> using Netmon (unfortunately, the Intel 11n adapters do not.)

>
>How do I tell from looking at the sniffed packets, that they really
>are 802.11n?


Good questions. If you sniff and get nothing, it's 802.11n. That's
because the data from a spatial diversity "N" radio goes via two or
more paths. Each path contains part of the data, each of which is
slightly time shifted, which is then reassembled by the receiver. In
order to sniff such multiple paths, the sniffer would need to hear all
the various paths, (which can be at different rates), hope that there
are no collisions or inter-symbol interference, and do quite a bit of
guesswork in order to get usable data. I don't think this is going to
happen.

>BTW, why are you using Wireshark when NM3.4 has easy to write
>filters?


Perhaps because Wireshark can decode wireless packets directly, while
Netmon 3.4 relys on an external protocol decoder, err... parser?
<http://nmparsers.codeplex.com/>
(Note: I haven't tried this decoder/parser/whatever yet).


--
# Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
# 831-336-2558
# http://802.11junk.com jeffl@cruzio.com
# http://www.LearnByDestroying.com AE6KS

Reply With Quote
  #4 (permalink)  
Old 05-15-2011, 03:58 PM
Axel Hammerschmidt
Guest
 
Posts: n/a
Default Re: Wireless Sniffing in Windows 7 with Netmon 3.4

Jeff Liebermann <jeffl@cruzio.com> wrote:

> On 14 May 2011 17:21:57 GMT, Axel Hammerschmidt <hlexa@hotmail.com>
> wrote:
>
> >Aaron Leonard:
> >
> ><snip>
> >
> >> Also I would be interested in hearing whether anyone has an
> >> adapter / driver that appears to successfully sniff 802.11n frames
> >> using Netmon (unfortunately, the Intel 11n adapters do not.)

> >
> >How do I tell from looking at the sniffed packets, that they really
> >are 802.11n?

>
> Good questions. If you sniff and get nothing, it's 802.11n. That's
> because the data from a spatial diversity "N" radio goes via two or
> more paths. Each path contains part of the data, each of which is
> slightly time shifted, which is then reassembled by the receiver. In
> order to sniff such multiple paths, the sniffer would need to hear all
> the various paths, (which can be at different rates), hope that there
> are no collisions or inter-symbol interference, and do quite a bit of
> guesswork in order to get usable data. I don't think this is going to
> happen.


Does 802.11n use beam forming?

Anyway, I have the computer connected to the AP right next to the
computer doing the capture.

> >BTW, why are you using Wireshark when NM3.4 has easy to write
> >filters?

>
> Perhaps because Wireshark can decode wireless packets directly, while
> Netmon 3.4 relys on an external protocol decoder, err... parser?
> <http://nmparsers.codeplex.com/>
> (Note: I haven't tried this decoder/parser/whatever yet).


Here are two captures

http://users.cybercity.dk/~ds487543/Datatid.cap

http://users.cybercity.dk/~ds487543/Datatid20110514.cap

The first is a capture from an 802.11b AP done November 23rd last year.
I seem to remember using a Thinkpad, connected to the AP.

The second was captured yesterday, a Macbook Pro connected to the
Netgear WHDE111, setup running 802.11n only.

Both captures were done on the same Macbook Early 2009 running NM3.4 in
Monitor Mode under Vista.

The first thing one notices is that the second .cap file is much bigger
- almost 4x bigger - than the first, although both sessions connect to
www.datatid.dk and perform two login attempts and then close the
connection.

You'll also notice, that all frames are 802.11n, but i think that's
because the wireless card in the sniffing computer is 802.11n.

There are malformed packets in both .cap files.

The login attempts can be found by using a filter - that looks for
"POST".

But only the attempts in the first .cap can be found using NM3.4. I'm
not sure why?

Using Wireshark 1.4.1 (Mac OS X 10.5.8 - X Window System) the login
attempt can be found in both .cap files.

So I think Wireshark is capable of doing som reassembling that NM3.4
cannot do.

The username is: pladder, and the password is: balle. This is for
demonstration only. I don't have an account at the site - that belongs
to a Danish computer magasine.


Reply With Quote
  #5 (permalink)  
Old 05-15-2011, 06:28 PM
Axel Hammerschmidt
Guest
 
Posts: n/a
Default Re: Wireless Sniffing in Windows 7 with Netmon 3.4

Axel Hammerschmidt <hlexa@hotmail.com> wrote:

<snip>

> The first thing one notices is that the second .cap file is much bigger
> - almost 4x bigger - than the first, although both sessions connect to
> www.datatid.dk and perform two login attempts and then close the
> connection.


A reason for this could be that the Thinkpad - Windows XP - uses a HOSTS
file from www.mvps.org while the Mac Book Pro does not - it's running
Mac OS X. Therefor the TP doesn't have to download from as many
ad-servers as the MBP. Although this can't be confirmed by looking at
captured packets.


Reply With Quote
  #6 (permalink)  
Old 05-16-2011, 01:56 AM
Jeff Liebermann
Guest
 
Posts: n/a
Default Re: Wireless Sniffing in Windows 7 with Netmon 3.4

On Sun, 15 May 2011 17:58:25 +0200, hlexa@hotmail.com (Axel
Hammerschmidt) wrote:

>Does 802.11n use beam forming?


Optional. The committee threw in the kitchen sink with both beam
forming and spatial diversity. Vendors can impliment either, or both.

<http://en.wikipedia.org/wiki/MIMO#Forms_of_MIMO>
Note the comments on SISO etc, which might be what you're receiving.

I'll look at the capture files when I have time. I'm rather
over-subscribed for another week.

<http://www.sniffwifi.com/2010/03/dwa-160-good-80211n-bad-or-at-least.html>
The problem with 802.11n is that with most setups the Data frames
going in one direction will be missed. I don't know exactly why
this is and I don't know all of the technical reasons behind it,
but trust me, it happens. If you set your 802.11n capture to a
standard channel (in my case today, a 20 MHz wide, 2.4 GHz
channel 1) you'll almost always capture data going in one
direction but not the other. You will usually get non-data frames
going in both directions (identified by frequent acknowledgments
without data preceding), but not all of the data.

--
Jeff Liebermann jeffl@cruzio.com
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558

Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
Don't fall victim to the 'Free Wi-Fi' scam Ablang alt.internet.wireless 6 05-19-2011 02:38 PM
Best windows proection The Doctor comp.security.misc 3 11-18-2010 10:00 PM
wireless network / ethernet bridge question Pete alt.comp.hardware 13 03-19-2007 06:19 PM


All times are GMT. The time now is 05:00 AM.



Powered by vBulletin® Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.6.0 PL2

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45