From: James Prestwood <prestwoj@gmail.com>
To: iwd@lists.linux.dev
Cc: James Prestwood <prestwoj@gmail.com>
Subject: [RFC 0/5] Using l_notice for low level IWD state information
Date: Wed, 14 Feb 2024 11:37:38 -0800 [thread overview]
Message-ID: <20240214193743.963349-1-prestwoj@gmail.com> (raw)
Lots is explained in the commit description but being able to run
tooling over IWD logs would be very useful to gather statistics on
how IWD is behaving with respect to connections, roaming, or whatever
else is desired. With these patches I've written a tool that monitors
only the NOTICE log level in the journal and spits out much more
concise information about IWD, for example running it against one of
the FT autotests:
connecting to TestFT (12:00:00:00:00:01) signal: -80 load: 127/255
connected
No scan issued to connect
Connected SSID: TestFT
Connected BSS: 12:00:00:00:00:01
Connecting time: 0ms
initiating roam to 12:00:00:00:00:02 signal: -30 load: 127/255
failed to ft-roam to BSS 12:00:00:00:00:02 reason: association-timeout
disconnected
Time connected: 5739ms
connecting to TestFT (12:00:00:00:00:01) signal: -80 load: 127/255
connected
Scan time: 5320ms
Connected SSID: TestFT
Connected BSS: 12:00:00:00:00:01
Connecting time: 0ms
Time disconnected: 5320ms
initiating roam to 12:00:00:00:00:02 signal: -30 load: 127/255
failed to ft-roam to 12:00:00:00:00:02 reason: authentication timeout
initiating roam to 12:00:00:00:00:03 signal: -70 load: 127/255
FT roamed
Scan time: 12752ms
Connected SSID: TestFT
Connected BSS: 12:00:00:00:00:03
Connecting time: 230ms
disconnected
Time connected: 1ms
connecting to TestFT (12:00:00:00:00:01) signal: -80 load: 127/255
connected
Scan time: 5318ms
Connected SSID: TestFT
Connected BSS: 12:00:00:00:00:01
Connecting time: 0ms
initiating roam to 12:00:00:00:00:03 signal: -60 load: 127/255
failed to ft-roam to 12:00:00:00:00:03 status: 53
initiating roam to 12:00:00:00:00:03 signal: -60 load: 127/255
roamed
Scan time: 12758ms
Connected SSID: TestFT
Connected BSS: 12:00:00:00:00:03
Connecting time: 210ms
initiating roam to 12:00:00:00:00:02 signal: -75 load: 127/255
FT roamed
Scan time: 12759ms
Connected SSID: TestFT
Connected BSS: 12:00:00:00:00:02
Connecting time: 10ms
disconnected
Time connected: 1ms
connecting to TestFT (12:00:00:00:00:01) signal: -80 load: 127/255
connected
Scan time: 5318ms
Connected SSID: TestFT
Connected BSS: 12:00:00:00:00:01
Connecting time: 0ms
initiating roam to 12:00:00:00:00:03 signal: -71 load: 127/255
failed to ft-roam to 12:00:00:00:00:03 status: 53
initiating roam to 12:00:00:00:00:02 signal: -73 load: 127/255
FT roamed
Scan time: 12752ms
Connected SSID: TestFT
Connected BSS: 12:00:00:00:00:02
Connecting time: 220ms
disconnected
Time connected: 1ms
James Prestwood (5):
main: add runtime flag for setting the logger
station: use l_notice for station_debug_event, allow arguments
station: add additional station_debug_event's
netdev: add notice events for connection timeouts
doc: document use of l_log APIs
doc/coding-style.txt | 24 ++++++++++++++++++++
src/main.c | 14 ++++++++++--
src/netdev.c | 6 ++---
src/station.c | 52 ++++++++++++++++++++++++++++++++------------
4 files changed, 77 insertions(+), 19 deletions(-)
--
2.34.1
next reply other threads:[~2024-02-14 19:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 19:37 James Prestwood [this message]
2024-02-14 19:37 ` [RFC 1/5] main: add runtime flag for setting the logger James Prestwood
2024-02-14 19:37 ` [RFC 2/5] station: use l_notice for station_debug_event, allow arguments James Prestwood
2024-02-14 19:46 ` Marcel Holtmann
2024-02-14 20:02 ` James Prestwood
2024-02-14 20:11 ` Marcel Holtmann
2024-02-14 19:37 ` [RFC 3/5] station: add additional station_debug_event's James Prestwood
2024-02-14 19:37 ` [RFC 4/5] netdev: add notice events for connection timeouts James Prestwood
2024-02-14 19:37 ` [RFC 5/5] doc: document use of l_log APIs James Prestwood
2024-02-14 19:49 ` Marcel Holtmann
2024-02-14 19:55 ` James Prestwood
2024-02-14 20:12 ` Marcel Holtmann
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=20240214193743.963349-1-prestwoj@gmail.com \
--to=prestwoj@gmail.com \
--cc=iwd@lists.linux.dev \
/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).