From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] figuring out who's actually on an ap
Date: Sat, 26 Jan 2013 10:22:17 -0800 [thread overview]
Message-ID: <CAA93jw4VaE5Y=imPKCbPrxEFr7cuv+c8+h+N5P0uW7w-PfgM+A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1272 bytes --]
Once upon a time it was possible to write quick and dirty tools in shell.
You used to just be able to open a port, write a tiny little daemon, and
go. And we used to have handy tools like rwho and finger to figure out who
was online, ruptime to check uptime, etc, etc.
That's too insecure nowadays...
so we have 3 different levels of snmp which you can use (if you can secure
it), and
run a shell command from that, remotely, then parse... or use ssh, and
parse.
And then we have dhcp, which hands out leases, but is not tied to how wifi
goes up
and down.
This morning I had a need to figure who was actually on a couple cerowrt
APs,
and a few statistics as to their connected rate...
I haven't got so as figuring out how to do all that via snmpd yet, but as
this uses
an obscure feature of the mac802.11 stack, I thought I'd document this much.
If there is a better way, a mib, something, let me know....
#!/bin/sh
# rup: quickly see whos really on the wifi
A=`ls /sys/kernel/debug/ieee80211/phy*/netdev:*/stations | \
cut -f8 -d/ | tr '\n' '|'`
# cut off last |
egrep ${A%?} /tmp/dhcp.leases | awk '{print $3 " " $4 }'
--
Dave Täht
Fixing bufferbloat with cerowrt:
http://www.teklibre.com/cerowrt/subscribe.html
[-- Attachment #2: Type: text/html, Size: 1472 bytes --]
next reply other threads:[~2013-01-26 18:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-26 18:22 Dave Taht [this message]
2013-01-26 19:00 ` Dave Taht
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw4VaE5Y=imPKCbPrxEFr7cuv+c8+h+N5P0uW7w-PfgM+A@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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