Joined: 19 Jul 2008
|Posted: Sun Jan 06, 2019 19:22 Post subject: Querying wireless clients via SNMP
I'm using build 3.0-r37305 on two TP-Link TL-WDR4300v1.7 and other access points in my network. It's a quite complex setup (consisting of four common SSIDs on 2.4 as well as 5GHz, WPA2/Enterprise + freeRADIUS, wireless accounting, etc.). To narrow down client problems I'd find it relly handy to use SNMP, so i came accross this
and I enabled SNMP on all of my APs. Using
|snmpwalk -v 1 -c public <AP-IP> .126.96.36.199.4.1.2021.255 |
I can retrieve a detailed list of clients, i.e. their MACs, user names for authentication, AP interface they're connected to, their uptime, SNR etc. (just like on the wireless status page)
|iso.188.8.131.52.1.2021.255.3.54.184.108.40.206.1.1 = INTEGER: 1
iso.220.127.116.11.1.2021.255.3.54.18.104.22.168.1.2 = INTEGER: 2
iso.22.214.171.124.1.2021.255.3.54.126.96.36.199.1.3 = INTEGER: 3
iso.188.8.131.52.1.2021.255.3.54.184.108.40.206.4.1 = STRING: "E8 B1 FC XX XX XX"
iso.220.127.116.11.1.2021.255.3.54.18.104.22.168.4.2 = STRING: "6C C7 EC XX XX XX"
iso.22.214.171.124.1.2021.255.3.54.126.96.36.199.4.3 = STRING: "24 18 1D XX XX XX"
iso.188.8.131.52.1.2021.255.3.54.184.108.40.206.13.1 = INTEGER: -97
iso.220.127.116.11.1.2021.255.3.54.18.104.22.168.13.2 = INTEGER: -97
iso.22.214.171.124.1.2021.255.3.54.126.96.36.199.13.3 = INTEGER: -94
iso.188.8.131.52.1.2021.255.3.54.184.108.40.206.26.1 = INTEGER: 28
iso.220.127.116.11.1.2021.255.3.54.18.104.22.168.26.2 = INTEGER: 21
iso.22.214.171.124.1.2021.255.3.54.126.96.36.199.26.3 = INTEGER: 9
iso.188.8.131.52.1.2021.255.3.54.184.108.40.206.27.1 = INTEGER: 123
iso.220.127.116.11.1.2021.255.3.54.18.104.22.168.27.2 = INTEGER: 14683
iso.22.214.171.124.1.2021.255.3.54.126.96.36.199.27.3 = INTEGER: 17733
iso.188.8.131.52.1.2021.255.3.54.184.108.40.206.28.1 = STRING: "ath0"
iso.220.127.116.11.1.2021.255.3.54.18.104.22.168.28.2 = STRING: "ath0"
iso.22.214.171.124.1.2021.255.3.54.126.96.36.199.28.3 = STRING: "ath1"
iso.188.8.131.52.1.2021.255.3.54.184.108.40.206.29.1 = STRING: "someuser"
iso.220.127.116.11.1.2021.255.3.54.18.104.22.168.29.2 = STRING: "someother"
iso.22.214.171.124.1.2021.255.3.54.126.96.36.199.29.3 = STRING: "anotherone"
iso.188.8.131.52.1.2021.255.3.54.184.108.40.206.30.1 = INTEGER: 54
iso.220.127.116.11.1.2021.255.3.54.18.104.22.168.30.2 = INTEGER: 24
iso.22.214.171.124.1.2021.255.3.54.126.96.36.199.30.3 = INTEGER: 12
iso.188.8.131.52.1.2021.255.3.54.184.108.40.206.31.1 = INTEGER: 43
iso.220.127.116.11.1.2021.255.3.54.18.104.22.168.31.2 = INTEGER: 78
iso.22.214.171.124.1.2021.255.3.54.126.96.36.199.31.3 = INTEGER: 13
iso.188.8.131.52.1.2021.255.3.54.184.108.40.206.32.1 = STRING: "0:02:03"
iso.220.127.116.11.1.2021.255.3.54.18.104.22.168.32.2 = STRING: "4:04:43"
iso.22.214.171.124.1.2021.255.3.54.126.96.36.199.32.3 = STRING: "4:55:33"
Yet, there is a problem – it seems to only work for a couple of queries/certain time. After that the output seems to freeze, i.e. I alway get the same values and shows client's as connected, which have disconnected hours ago and are many kilometers away.
The wireless status page seems to work correctly though.
Rebooting the AP seems to help for a while.
Can you give me some hints as to what happens inside the box the moment it's going pear shaped? Can I potentially fix this problem or will I have to wait for a new release of DD-WRT?
Thanks in advance!