Linux wireless drivers development
 help / color / mirror / Atom feed
From: pangyunong <029012@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: Some confusing segment of Beacon
Date: Fri, 26 Aug 2011 00:26:19 +0800	[thread overview]
Message-ID: <1314289579.3210.27.camel@Yunong> (raw)

Hi, 

I'm output the sk_buff at ieee80211_beacon_get_tim() in mac80211/tx.c

but I'm confused about some segments.

According to the book, 802.11 wireless networks: the definitive guide,  

-----------------------------------------------------------------------
Frame Control segment:
The two bytes in my condition should be 0000 0000 1000 0000 to indicate
that it is a management Beacon frame. 

However, the two bytes I obtain is      1000 0000 0000 0000 
------------------------------------------------------------------------

------------------------------------------------------------------------
Beacon Duration:
Two bytes in book should be 0000 0000 0010 0110 to indicate 100 ms
between two beacon from the 32th bytes but I calculate that segment
starts from 31th bytes. 
-------------------------------------------------------------------------



------------------ What I add into ieee80211_beacon_get_tim()---------

    printk("\n===============get_tim====================\n");  
    printk("     len = %u\n", skb->len);
    printk(" datalen = %u\n", skb->data_len);
    printk("mac len = %u\n", (unsigned int)skb->mac_len);
    printk("hdr len = %u\n", (unsigned int)skb->hdr_len);
    printk("     head= %u\n", (unsigned int)skb->head);
    printk("network head= %u\n", (unsigned int)skb->network_header); 
    printk("mac  head= %u\n", (unsigned int)skb->mac_header); 
    printk("data head= %u\n", (unsigned int)skb->data); 
    printk("tail head= %u\n", (unsigned int)skb->tail); 
    printk("end  head= %u\n", (unsigned int)skb->end); 

-----------------------------------------------------------------------

Hence, I’m wondering whether there are errors in my approach of
interpreting the data bytes. 



Yunong Pang
Regards,




                 reply	other threads:[~2011-08-25 16:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1314289579.3210.27.camel@Yunong \
    --to=029012@gmail.com \
    --cc=linux-wireless@vger.kernel.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