From: lrhorer on

I have a network with 3 Linksys wireless devices, a WET-54G, a WRT-54G,
and a WAP-54G that I would like to monitor for signal strength, S/N
ratio, packets / octets handled, etc. 'Very basic and very limited in
scope, so I don't need anything like Enterprise Class software.I just
want a simple health and status check of the devices. I'm running
Debian "Lenny" on the server I would like to use for this, and I don't
care if access is via simple CLI, an X client, or via Web interface.
Does anyone have any good suggestions?
From: klaus zerwes on
lrhorer wrote:
> I have a network with 3 Linksys wireless devices, a WET-54G, a WRT-54G,
> and a WAP-54G that I would like to monitor for signal strength, S/N
> ratio, packets / octets handled, etc. 'Very basic and very limited in
> scope, so I don't need anything like Enterprise Class software.I just
> want a simple health and status check of the devices. I'm running
> Debian "Lenny" on the server I would like to use for this, and I don't
> care if access is via simple CLI, an X client, or via Web interface.
> Does anyone have any good suggestions?

nagios or cacti

Or write your own small perl script using libnet-snmp-perl

Klaus

--
Klaus Zerwes
http://www.zero-sys.net
From: lrhorer on
klaus zerwes wrote:

> lrhorer wrote:
>> I have a network with 3 Linksys wireless devices, a WET-54G,
>> a WRT-54G,
>> and a WAP-54G that I would like to monitor for signal strength, S/N
>> ratio, packets / octets handled, etc. 'Very basic and very limited in
>> scope, so I don't need anything like Enterprise Class software.I just
>> want a simple health and status check of the devices. I'm running
>> Debian "Lenny" on the server I would like to use for this, and I
>> don't care if access is via simple CLI, an X client, or via Web
>> interface. Does anyone have any good suggestions?
>
> nagios or cacti

Thanks, I'll look into those.

> Or write your own small perl script using libnet-snmp-perl

The issue is the standard MIB-2 does not cover wireless devices, and I
can't find a MIB for the devices in question. Snmpwalk can discover
all the snmp targets, but since they are not verbosely identified, I
have no way of knowing which target is which. Do you know if either of
the above have ready-made MIBs for the devices I mention?
From: klaus zerwes on
lrhorer wrote:
> klaus zerwes wrote:
[...]
>> nagios or cacti
> Thanks, I'll look into those.
>
>> Or write your own small perl script using libnet-snmp-perl
>
> The issue is the standard MIB-2 does not cover wireless devices, and I
> can't find a MIB for the devices in question. Snmpwalk can discover
> all the snmp targets, but since they are not verbosely identified, I
> have no way of knowing which target is which. Do you know if either of
> the above have ready-made MIBs for the devices I mention?

on a linux box the wireless devices are handled usually the same way as
ordinary ethernet devices:

IF-MIB::ifNumber.0 = INTEGER: 5
IF-MIB::ifIndex.1 = INTEGER: 1
IF-MIB::ifIndex.2 = INTEGER: 2
IF-MIB::ifIndex.3 = INTEGER: 3
IF-MIB::ifIndex.4 = INTEGER: 4
IF-MIB::ifIndex.5 = INTEGER: 5
IF-MIB::ifDescr.1 = STRING: lo
IF-MIB::ifDescr.2 = STRING: eth0
IF-MIB::ifDescr.3 = STRING: eth1
IF-MIB::ifDescr.4 = STRING: wlan0
IF-MIB::ifDescr.5 = STRING: tun0
IF-MIB::ifType.1 = INTEGER: softwareLoopback(24)
IF-MIB::ifType.2 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.3 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.4 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.5 = INTEGER: other(1)

With this, nagios or cacti should have no problems.

No idea what soup cisco / linksys is cooking ...

Klaus

--
Klaus Zerwes
http://www.zero-sys.net