Historical ath9k-devel archives
 help / color / mirror / Atom feed
From: Mark Gannon <mark@truenorth.nu>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Packet Injection in Monitor Mode Sending Packets Twice
Date: Wed, 25 Mar 2015 10:26:04 -0400	[thread overview]
Message-ID: <8622163.Jly0hxWGXe@scooby> (raw)
In-Reply-To: <CALU5yQDOTDE+fBiqeyjuG7WkSH1czp9-m1_cvf9UqUWtuwcKYw@mail.gmail.com>

On Wednesday, March 25, 2015 10:49:43 AM Thomas V wrote:
> There is a possibility that the 1st frame is retried. Can you check for the
> "retry bit"  in the sniffer capture.

The retry flag in the IEEE 802.11 section is set to zero for both the first and 
second packet.  Here is a text version of Wireshark's exported packet 
dissection for the second packet:

 IEEE 802.11 Data, Flags: .......T
    Type/Subtype: Data (0x0020)
    Frame Control Field: 0x0801
        .... ..00 = Version: 0
        .... 10.. = Type: Data frame (2)
        0000 .... = Subtype: 0
        Flags: 0x01
            .... ..01 = DS status: Frame from STA to DS via an AP (To DS: 1 
From DS: 0) (0x01)
            .... .0.. = More Fragments: This is the last fragment
            .... 0... = Retry: Frame is not being retransmitted
            ...0 .... = PWR MGT: STA will stay up
            ..0. .... = More Data: No data buffered
            .0.. .... = Protected flag: Data is not protected
            0... .... = Order flag: Not strictly ordered
    .000 0000 0000 0000 = Duration: 0 microseconds
    Receiver address: Broadcast (ff:ff:ff:ff:ff:ff)
    BSS Id: Broadcast (ff:ff:ff:ff:ff:ff)
    Transmitter address: 13:22:33:44:55:66 (13:22:33:44:55:66)
    Source address: 13:22:33:44:55:66 (13:22:33:44:55:66)
    Destination address: 13:22:33:44:55:66 (13:22:33:44:55:66)
    Fragment number: 0
    Sequence number: 2145

Thanks for your help!

Regards,

Mark Gannon

-- 
You have to accept whatever comes, and the only important thing is that you 
meet it with the best you have to give. 

	? Eleanor Roosevelt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part.
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20150325/3cd0faba/attachment.pgp 

  reply	other threads:[~2015-03-25 14:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24 19:35 [ath9k-devel] Packet Injection in Monitor Mode Sending Packets Twice Mark Gannon
2015-03-25  5:19 ` Thomas V
2015-03-25 14:26   ` Mark Gannon [this message]
2015-03-25 14:42     ` Federico Tramarin
2015-03-25 15:45       ` Michael Stahn
2015-03-25 17:04         ` Mark Gannon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8622163.Jly0hxWGXe@scooby \
    --to=mark@truenorth.nu \
    --cc=ath9k-devel@lists.ath9k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox