From: Andreas Hartmann <andihartmann@freenet.de>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: AP: mon.wlan0 vs wlan0
Date: Sat, 25 Jun 2011 14:35:23 +0200 [thread overview]
Message-ID: <4E05D60B.5020007@dualc.maya.org> (raw)
Hello,
I traced mon.wlan0 and wlan0 on an accesspoint, because I wanted to see,
which data is sent through which device (WPA2 TLS).
That's what I saw:
mon.wlan0 wlan0
---------------------------------------------------------------------------------
initial authentication
probe request x
probe response x (2 times)
authentication requ x
authentication resp x (2 times)
association request x
association response x (2 times)
request identity x (2 times)
response identity x
request eaptls x (2 times)
Server Hello x
Client Hello x
IEEE 802.11 x
request eap-tls x (2 times)
response eap-tls x (2 times)
Change Cipher Spec x (2 times)
Certificate Client x
EAP Success x (2 times)
Response eap-tls x
EAPOL Key msg 1/4 x (2 times)
EAPOL Key msg 2/4 x
EAPOL Key msg 3/4 x (2 times)
EAPOL Key msg 4/4 x
IEEE 802.11 action success x
GTK - rekeying
QoS Data 2 times (WEP and CCMP)
EAPOL Key msg 2/2 x
Reauthentication
QoS (request identity?) x
response identity x
QoS (server hello?) x
client hello x
QoS (Change Cipher Spec?) x
QoS (EAPOL Key msg 1/4?) x
EAPOL Key msg 2/4 x
QoS (EAPOL Key msg 3/4?) x
EAPOL Key msg 4/4 x
QoS (IEEE 802.11 success) x
I'm surprised, that not all of the management packages went through the
mon-device.
At the beginning (initial connection), all data went through the
mon-device. After the association, all management data from the client
(supplicant) goes through the normal wlan0 device - I would have
expected, that all management and authorization data went through the
mon device.
Could anybody please shed some light on this?
Thank you,
Andreas
reply other threads:[~2011-06-25 12:34 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=4E05D60B.5020007@dualc.maya.org \
--to=andihartmann@freenet.de \
--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;
as well as URLs for NNTP newsgroup(s).