One challenge, if graphing the wirelessClientsTable, would be the fact that as the clients came and went their corresponding entries in the tables would come and go. There would therefore be gaps in the recording of packets associated with these nodes. That's a fairly simple concept, but how would you manage roaming whereby a client hops between base stations? Would you try to tie these together so that a trace of traffic associated with such a client, irrespective of base station would be available? I think that decision might shape any framework; ie would it be base station or client centric? Of course more than one view may be desirable.

Steve

On 23 Feb 2014, at 20:30, Adam Armstrong <adama@memetic.org> wrote:


"...What's all needed..."

Did you relocate from Belgium to Alabama? :P

adam.

On 2014-02-23 12:12, Tom Laermans wrote:
Steve,
Why didn't stupid apple include the wireless interfaces into ifTable
instead of using their own MIB? Good luck on that one, at least..
For the other part of your e-mail, we're kind of pondering right now
about doing a wireless devices framework, supporting controller-based
and standalone access points, recording client count, mac addresses,
ssids, radios, frequencies, etc etc. But we're not sure what's all
needed to do this - airport with whatever stats the AIRPORT-EXTREME
MIB supplies would be one of the devices that could be supported in
there.
Tom
On 23/02/2014 18:22, Steve Evans wrote:
Firstly, I have to say how impressed I am with the clean, purposeful implementation of Observium.
One of the main reasons I was looking for such an SNMP network manager was to monitor my four apple airport base stations.
Whilst Observium recognises such devices, and graphs the wirelessNumber from the AIRPORT-BASESTATION-3-MIB if does not graph the corresponding physicalInterfacesTable traffic. Whilst the ifTable is graphed this doesn't actually include the wireless connections. This information would be very useful to determine how many packets are being passed on the wireless interface and at what speed. I've yet to dig into the structure of the code much, but presumably the physicalInterfacesTable could be logged/graphed using code very similar to that used for the ifTable.
Something that would also be very useful, would be to list the currently attached clients which could be reported in a similar manner to the ARP/NDP Table using information sourced from the wirelessClientsTable to display MAC address and speed/signal strength/noise. This information could be instantaneous rather than logged as the airport base stations appear not to actually return the number of packets passed despite the MIB supporting this. This looks like the simpler task.
Finally, some might be interested in the DHCP allocations, but as I run all my base stations in bridged mode that wouldn't be of interest to be.
So, before I start looking at the code, I thought I should ask if anybody is already looking into this?
Thanks,
Steve
_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [1]
Links:
------
[1] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium