Thanks for the info. I had not heard of mutiny before. I have played with Cacti though.
A couple years back I tried to nmap all the connected address space to get an idea of what is out there:
http://www.qsl.net/kb9mwr/wapr/tcpip/amrprnet-nmap-2014.txt
Looking back I feel a bit guilty about doing this as some of the radio links are slower ones. I wish under the gateways tab of the portal there was a check box to signify 1200 baud or hsmm. Of course I wish a lot of things.
I had a script grab an encap file and merged that with the 44 BGP list and had a script incrementally nmap each connected subnet.
Hi Steve,
OK. Mutiny gives less traffic, you can only ping (and time between ping is adjustable). If needed snmp can be fired so we can have extra informations about hardware.
-----Message d'origine----- De : 44Net [mailto:44net-bounces+magnier.jeanmarc=numericable.fr@hamradio.ucsd.edu] De la part de Steve L Envoyé : vendredi 26 février 2016 18:31 À : 44net@hamradio.ucsd.edu Objet : Re: [44net] Example of nodes monitoring
(Please trim inclusions from previous messages) _______________________________________________ Thanks for the info. I had not heard of mutiny before. I have played with Cacti though.
A couple years back I tried to nmap all the connected address space to get an idea of what is out there:
http://www.qsl.net/kb9mwr/wapr/tcpip/amrprnet-nmap-2014.txt
Looking back I feel a bit guilty about doing this as some of the radio links are slower ones. I wish under the gateways tab of the portal there was a check box to signify 1200 baud or hsmm. Of course I wish a lot of things.
I had a script grab an encap file and merged that with the 44 BGP list and had a script incrementally nmap each connected subnet. _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net