From: Dan Williams <dcbw@redhat.com>
To: Thomas Thielemann <thomas@th-thielemann.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: How to use netlink to determine wifi protection WEP
Date: Thu, 06 Apr 2017 10:41:46 -0500 [thread overview]
Message-ID: <1491493306.9316.1.camel@redhat.com> (raw)
In-Reply-To: <C7BDEED9-DCEC-4BED-AC69-800EEFE4FF49@th-thielemann.de>
On Thu, 2017-04-06 at 16:27 +0200, Thomas Thielemann wrote:
> Thanks!
>
> If the sequence is the following:
>
> 1. Prepare and execute NL80211_CMD_TRIGGER_SCAN
> 2. Prepare and execute NL80211_CMD_GET_SCAN
> Together with NL80211_CMD_GET_SCAN a callback is registered.
> In the callback the raw data are parsed as BSS. The IE's are parsed
> to.
>
> When do I have to fetch the beacon to get the right beacon but
> without lost of the scan result?
> After I fetched all scan results or immediately after the receive of
> every scan result?
The scan results are essentially the beacons, so you just need to read
the GET_SCAN. Then when parsing the "bss info" you get from the scan
results handler that you registered, you look for:
NL80211_BSS_CAPABILITY: the Privacy bit is in here
NL80211_BSS_INFORMATION_ELEMENTS: the IEs are obviously in here
Dan
> Regards,
> Thomas
>
>
> > Am 05.04.2017 um 19:24 schrieb Dan Williams <dcbw@redhat.com>:
> >
> > On Wed, 2017-04-05 at 09:27 +0200, Thomas Thielemann wrote:
> > > Hello!
> > >
> > > I need a solution to determine whether a WiFi is using WEP. I
> > > know
> > > there is a protection flag within MAC frame but do not know how
> > > to
> > > access.
> > >
> > > To detect whether a WiFi i protected by WPA2 I found the
> > > following
> > > solution:
> > >
> > > Scan with
> > >
> > > nl_sock* socket = nl_socket_alloc();
> > > genl_connect(socket);
> > > struct nl_msg* msg = nlmsg_alloc();
> > > int driverId = genl_ctrl_resolve(socket, "nl80211");
> > > genlmsg_put(msg, 0, 0, driverId, 0, 0, NL80211_CMD_TRIGGER_SCAN,
> > > 0);
> > >
> > > and fetch with
> > >
> > > genlmsg_put(msg, 0, 0, driverId, 0, NLM_F_DUMP,
> > > NL80211_CMD_GET_SCAN,
> > > 0);
> > >
> > > Read the received structure using nl80211_bss::
> > > NL80211_BSS_INFORMATION_ELEMENTS from nl80211.h and
> > >
> > > examine the field RSN(id=48) (see IEEE802.11-2012.pdf, chapter
> > > 8.4.2
> > > Information elements)
> > >
> > > Which netlink command gives me the related data? Is it
> > > NL80211_CMD_GET_BEACON?
> >
> > You want both the beacon (for the Privacy bit) and the information
> > elements.
> >
> > If the privacy bit is set in beacon and there are no WPA/WPA2/RSN-
> > related information elements, then the AP is using
> > WEP. Unfortunately
> > you don't know whether it's WEP-40 or WEP-104, but that's another
> > topic.
> >
> > If the privacy bit is set, and there are WPA/WPA2/RSN information
> > elements, then the AP *might* be using WEP in compatibility
> > mode. This
> > isn't very common though, so you can probably just ignore this
> > case.
> >
> > Dan
> >
>
>
prev parent reply other threads:[~2017-04-06 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 7:27 How to use netlink to determine wifi protection WEP Thomas Thielemann
2017-04-05 17:24 ` Dan Williams
2017-04-06 14:27 ` Thomas Thielemann
2017-04-06 15:41 ` Dan Williams [this message]
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=1491493306.9316.1.camel@redhat.com \
--to=dcbw@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=thomas@th-thielemann.de \
/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).