From: "Arend van Spriel" <arend@broadcom.com>
To: "Mathieu Devos" <mathieu.devos@ugent.be>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Skb and ieee80211 headers
Date: Wed, 31 Jul 2013 12:08:40 +0200 [thread overview]
Message-ID: <51F8E228.9080600@broadcom.com> (raw)
In-Reply-To: <CAE_+Soy5=MfUUahaP3Ka2onp+jP9aupbhGu_QHco=CP7Y9sqhQ@mail.gmail.com>
On 07/31/2013 11:39 AM, Mathieu Devos wrote:
> Hi,
>
> I hope this is the right place to ask for a little bit of help as I'm
> currently beyond stuck on a challenge I'm trying to accomplish. I'm
> trying to write a "simple" LKM that properly uses a ieee80211 header
> to print information about the mac addresses (addr1->addr4) and later
> down the road try to send my own data.
>
> I only need to get L2 working, no need for TCP/IP, just a proper
> ieee80211 based on input from skb would be huge for me.
>
> So my issue: when placing the ieee80211 on my mac_header after I hook
> my skb from my wireless device (wlan0 on android - I9100)
Not sure what you goal is, but what wireless device is that? You may
just get 802.3 packets from the device.
Gr. AvS
> I get a huge
> amount of zero's and random(?) numbers when trying to print the
> addresses. This leads me to the first conclusion that mac_header is
> placed wrong when using 80211. After that I saw a lot of people just
> using the skb->data pointer. Now this gives even weirder issues for me
> and actually totally crashes my kernel.
next prev parent reply other threads:[~2013-07-31 10:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 9:39 Skb and ieee80211 headers Mathieu Devos
2013-07-31 10:08 ` Arend van Spriel [this message]
2013-07-31 10:28 ` Mathieu Devos
2013-07-31 11:05 ` Arend van Spriel
2013-07-31 12:39 ` Mathieu Devos
2013-07-31 12:55 ` Arend van Spriel
2013-07-31 13:45 ` Mathieu Devos
2013-07-31 15:04 ` Arend van Spriel
2013-07-31 15:11 ` Mathieu Devos
2013-08-02 7:49 ` Mathieu Devos
2013-08-07 10:27 ` Arend van Spriel
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=51F8E228.9080600@broadcom.com \
--to=arend@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mathieu.devos@ugent.be \
/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;
as well as URLs for NNTP newsgroup(s).