aircrack-ng is a set of tools for auditing wireless networks. It's an enhanced/reborn version of aircrack. It consists of airodump (an 802.11 packet capture program), aireplay (an 802.11 packet injection program), aircrack (static WEP and WPA-PSK cracking), airdecap (decrypts WEP/WPA capture files), and some tools to handle capture files (merge, convert, etc.).
MIB Smithy SDK is a dynamic extension to Tcl/Tk (8.4+) that allows development of custom scripts for controlling SNMP agents, manipulating SMI definitions, doing conversions, and more. It is based on the core of Muonics' MIB Smithy, and the SDK supports SMIv1 and SMIv2, as well as SNMPv1/v2c/v3 with HMAC-SHA-96 and HMAC-MD5-96 authentication and DES/CBC and AES128/CFB privacy. It also provides complete read-write access to all elements of SMI/MIB Module definitions, unlike similar extensions that provide only read access to a limited subset. The SDK allows multiple discrete SMI databases and SNMP sessions, and provides all of the built-in validation and error recovery capabilites of the full product, without the visual MIB development environment.
NetXMS is a network monitoring and management system with a modular architecture. It can be used for monitoring an entire IT infrastructure, starting with SNMP-capable hardware (like switches and routers) and ending with applications on servers. The system has a three-tier architecture; the information is collected by monitoring agents (either its own agents or SNMP agents) and delivered to the monitoring server for processing and storing, where it can be accessed by using the management console. It features centralized configuration and centralized agent upgrades.
Nagstamon is a Nagios status monitor with a UI that resides in the systray or as a floating statusbar on your desktop. It informs you in realtime about the status of your Nagios, Icinga, Opsview, Ninja, Check_MK/Multisite, Centreon, or Thruk-monitored network. It alerts you with sound and visual notification. Failed hosts and services are easy to connect with by SSH, RDP, and VNC. Custom actions can be run on certain events. It works best with GNOME, but also with KDE, Mac OS X, and Windows.
NOC Project is an Operation Support System (OSS) for telecom companies, service providers, and enterprise Network Operation Centers (NOC). Areas covered by NOC include fault management, performance management, service activation/provisioning, knowledge base, multi-VRF address space management (IPAM), multi-vendor configuration management, DNS provisioning, peering management, RPSL and BGP filter generation, and reporting.
collectd is a small and modular daemon which collects system information periodically and provides means to store the values. Included in the distribution are numerous plug-ins for collecting CPU, disk, and memory usage, network interface and DNS traffic, network latency, database statistics, and much more. Custom statistics can easily be added in a number of ways, including execution of arbitrary programs and plug-ins written in Perl. Advanced features include a powerful network code to collect statistics for entire setups and SNMP integration to query network equipment.
Lilith is a logging and access event viewer for the Logback logging framework. It has features comparable to Chainsaw, a logging event viewer for log4j. This means that it can receive logging events from remote applications using Logback as their logging backend. It uses files to buffer the received events locally, so it is possible to keep vast amounts of logging events at your fingertip while still being able to check only the ones you are really interested in by using filtering conditions.
Trojan scan is a simple shell script that allows for simple but relatively effective checking for trojans, rootkits and other malware that may be using your server and network for unwanted (and possibly illegal) purposes. It works by listing all processes that use the Internet with the lsof command (using -Pni flags). This list is then transformed into signatures in the form of process_name:port_number:user. These signatures then are matched against the allowed process defined in the configuration. If any signatures of running processes are found that do not match the allowed signatures, an email report is sent including ps, ls, and optional lsof output.