From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Alexander Aring <alex.aring@gmail.com>,
Stefan Schmidt <stefan@datenfreihafen.org>,
linux-wpan@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org
Cc: David Girault <david.girault@qorvo.com>,
Romuald Despres <romuald.despres@qorvo.com>,
Frederic Blain <frederic.blain@qorvo.com>,
Nicolas Schodet <nico@ni.fr.eu.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-wireless@vger.kernel.org,
Miquel Raynal <miquel.raynal@bootlin.com>
Subject: [wpan-tools v2 0/7] IEEE 802.15.4 scan support
Date: Wed, 12 Jan 2022 18:35:22 +0100 [thread overview]
Message-ID: <20220112173529.765170-1-miquel.raynal@bootlin.com> (raw)
Hello,
This series follows the work done in the Linux kernel stack: now that
the core knows about the different netlink commands and attributes in
order to support passive scan requests from end-to-end, here are the
userspace changes to be able to use it.
Here is a list of the new available features.
* Sending (or stopping) beacons. Intervals ranging from 0 to 14 are
valid for passively sending beacons at regular intervals. An interval
of 15 would request the core to answer to received BEACON_REQ.
# iwpan dev wpan0 beacons send interval 2 # send BEACON at a fixed rate
# iwpan dev wpan0 beacons send interval 15 # answer BEACON_REQ only
# iwpan dev wpan0 beacons stop # apply to both cases
* Scanning all the channels or only a subset:
# iwpan dev wpan1 scan type passive duration 3 # will not trigger BEACON_REQ
# iwpan dev wpan1 scan type active duration 3 # will trigger BEACON_REQ
* If a beacon is received during this operation the internal PAN list is
updated and can be dumped or flushed with:
# iwpan dev wpan1 pans dump
PAN 0xffff (on wpan1)
coordinator 0x2efefdd4cdbf9330
page 0
channel 13
superframe spec. 0xcf22
LQI 0
seen 7156ms ago
# iwpan dev wpan1 pans flush
# iwpan dev wpan1 set max_pan_entries 100
# iwpan dev wpan1 set pans_expiration 3600
* It is also possible to monitor the events with:
# iwpan event
* As well as triggering a non blocking scan:
# iwpan dev wpan1 scan trigger type passive duration 3
# iwpan dev wpan1 scan done
# iwpan dev wpan1 scan abort
Cheers,
Miquèl
Changes in v2:
* Dropped the binaries added by accident.
* New sync of the headers with Linux.
* Added two new commands to configure the stack regarding the number of
PANs listed and their delay before expiration.
David Girault (4):
iwpan: Export iwpan_debug
iwpan: Remove duplicated SECTION
iwpan: Add full scan support
iwpan: Add events support
Miquel Raynal (2):
iwpan: Fix a comment
iwpan: Synchronize nl802154 header with the Linux kernel
Romuald Despres (1):
iwpan: Fix the channels printing
src/Makefile.am | 2 +
src/event.c | 221 +++++++++++++++++++++++
src/info.c | 4 +-
src/iwpan.c | 2 +-
src/iwpan.h | 13 +-
src/mac.c | 56 ++++++
src/nl802154.h | 99 ++++++++++
src/scan.c | 471 ++++++++++++++++++++++++++++++++++++++++++++++++
8 files changed, 859 insertions(+), 9 deletions(-)
create mode 100644 src/event.c
create mode 100644 src/scan.c
--
2.27.0
next reply other threads:[~2022-01-12 17:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 17:35 Miquel Raynal [this message]
2022-01-12 17:35 ` [wpan-tools v2 1/7] iwpan: Fix the channels printing Miquel Raynal
2022-01-12 17:35 ` [wpan-tools v2 2/7] iwpan: Export iwpan_debug Miquel Raynal
2022-01-12 17:35 ` [wpan-tools v2 3/7] iwpan: Fix a comment Miquel Raynal
2022-01-12 17:35 ` [wpan-tools v2 4/7] iwpan: Remove duplicated SECTION Miquel Raynal
2022-01-12 17:35 ` [wpan-tools v2 5/7] iwpan: Synchronize nl802154 header with the Linux kernel Miquel Raynal
2022-01-12 17:35 ` [wpan-tools v2 6/7] iwpan: Add full scan support Miquel Raynal
2022-01-12 17:35 ` [wpan-tools v2 7/7] iwpan: Add events support Miquel Raynal
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=20220112173529.765170-1-miquel.raynal@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=alex.aring@gmail.com \
--cc=davem@davemloft.net \
--cc=david.girault@qorvo.com \
--cc=frederic.blain@qorvo.com \
--cc=kuba@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nico@ni.fr.eu.org \
--cc=romuald.despres@qorvo.com \
--cc=stefan@datenfreihafen.org \
--cc=thomas.petazzoni@bootlin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).