On Tue, 19 Mar 2013, Jack Bates wrote:

On 18/03/13 12:04 AM, David Lang wrote:
Thanks for posting this, I'm in a similar situation of trying to monitor
APs.

One problem I have had is finding a copy of the specs that say what
information should be available. If you can point me at a copy of that,
I can then easily say what OIDs in there are ones thatI care about.

I also struggled to determine what information should be available. The patch currently only supports wireless signal level and noise floor, e.g.

 $ snmpwalk -c public -On -v 1 192.168.1.1 1.3.6.1.4.1.762
 .1.3.6.1.4.1.762.2.5.2.1.1.1 = INTEGER: 1
 .1.3.6.1.4.1.762.2.5.2.1.3.1 = STRING: "wlan0"
 .1.3.6.1.4.1.762.2.5.2.1.7.1 = INTEGER: -256
 .1.3.6.1.4.1.762.2.5.2.1.8.1 = INTEGER: -59
 $

How do you want to monitor your APs? What tools do you want to use and how do you want to use them?

There are a huge number of SNMP based tools available (including the classic MRTG)

Besides the basic networking and load numbers that you want for any router/switch, wifi has additional things that just don't exist with wired interfaces.

For example:

# of clients connected to the SSID (associations)

information on each connection
  signal strength
  MAC

Radio airtime info
  how much time was spend recieving (unable to transmit)
  how much recieved traffic was corrupted by interference
  how much good recieved traffic was there
  how much time was spent transmitting
  how much idle airtime was there (time that transmissions could have occured)

going beyond the simple metrics that I want to graph into overall network management issues

some method (ideal something better than trying to sniff packets and correlate them in userspace) to try and figure out how much airtime a given station is eating up (especially something that can do this even if the station gets trompted on and so the transmitted packet cannot be fully received)

some method of being able to figure out what other SSIDs are broadcasting on the frequency that I'm currently tuned to and how much airtime each SSID is eating up (including ones that don't send beacons)

David Lang
_______________________________________________
openwrt-users mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-users

Reply via email to