[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220112173529.765170-1-miquel.raynal@bootlin.com>
Date: Wed, 12 Jan 2022 18:35:22 +0100
From: Miquel Raynal <miquel.raynal@...tlin.com>
To: Alexander Aring <alex.aring@...il.com>,
Stefan Schmidt <stefan@...enfreihafen.org>,
linux-wpan@...r.kernel.org,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org
Cc: David Girault <david.girault@...vo.com>,
Romuald Despres <romuald.despres@...vo.com>,
Frederic Blain <frederic.blain@...vo.com>,
Nicolas Schodet <nico@...fr.eu.org>,
Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
linux-wireless@...r.kernel.org,
Miquel Raynal <miquel.raynal@...tlin.com>
Subject: [wpan-tools v2 0/7] IEEE 802.15.4 scan support
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
Powered by blists - more mailing lists