Free network performance software for linux

Network FIFO project is a network object that provides data transfering tunnel across network in first in/first out manner.

Simply put,

fifo server file is: monotech_fifo.pl
This script require Net::Server::NonBlocking at least 4.1(you can grab from CPAN)

% perl monotech_fifo.pl < address > < port >

and itll show up like this:

[root@WongWai monotech_fifo]# perl monotech_fifo.pl 192.168.3.52 12000
Listen on 192.168.3.52:20005
Listen on 192.168.3.52:12000

12000 is the port in which the fifo resides.
20005 is the port in which backoffice management resides.

--------------------------------------------------

port 20005 in which the management control resides can be accessed by "admin.pl"

% perl admin.pl < address >

for example

perl admin.pl 192.168.3.52

itll show something like this:

message>

where you can type some commands and press enter

the commands are:

message>readers
message>flush

(flush is the command that read all socket buffer of the admin client socket)

to show all reader in the fifo, it is very useful when some reader is connection disconnected by his ISP or readers machine hangs, the fifo will hold his connection forever (It is because the monotech_fifo.pl doesnt set SO_KEEPALIVE and TCP_KEEPALIVE which will be fixed in the future)

and

message>kill_reader[tab]< fifo name >

to kill any connection of < fifo name >

This package is heavily used by my company, so it is likely reliable.

Netmap is a program to create network weathermaps based on existing images created by other software. It uses SNMP for collecting data from other devices and it does not depend on MRTG or any other statistics program.
Enhancements:
- configure.in, db/create_tables.sql, doc/netmap.tex, interface/admin/netmap_a.css, interface/admin/common/config.inc, interface/admin/netmap/nm_config.cgi.in, interface/admin/points/points_edit.cgi.in, interface/ui/index.cgi.in, src/conf.cc, src/conf.h, src/db.cc, src/db.h, src/main.cc, src/snmp.cc: Minor compilation and othe fixes. Added check_same_ifdescr(). Added option to store acct data for used interfaces only.

Network Traffic Analyser provides a script-driven network traffic monitor.

Network Traffic Analyser (formerly known as sniffer) is designed to be an extremely powerful, configurable, and versatile tool for monitoring network traffic.

It can be used as a plain sniffer, as a tool for accounting, dynamic firewall updates, and many more things.

It features scripting support and an event-driven architecture.

The idea behind this project is to create a powerful tool for playing around with network traffic. The basic concepts are simplicity and flexibility. Instead of building tool that does something specific (and does a good job at it), were trying to build a tool that will be able to do whatever you want it to do (and still be good at it :).

To put it very simply, you write a script that will be invoked for every packet that passes through your network. You write your scripts in a Tcl, fully blown, interpreted programming language. That fact guaranties that you wont be constrained in your creativity.

Manage your network with a free Network Monitoring Software application.
Network Management Tool is an organized way to manage your network. 100% web-based network management.
Manage your network devices with ease. 100% Free Network Managment Software! Manage all your network devices, routers, switches, firewalls, hubs, and more.
Enhancements:
- A display bug that occurred when viewing the comments on a device was fixed.

Netperf is a benchmark that can be used to measure the performance of many different types of networking.
It provides tests for both unidirecitonal throughput, and end-to-end latency. The environments currently measureable by netperf include:
- TCP and UDP via BSD Sockets
- DLPI
- Unix Domain Sockets
- Fore ATM API
- HP HiPPI Link Level Access

Performance Co-Pilot (PCP) is a framework and services to support system-level performance monitoring and performance management.
The services offered by PCP are especially attractive for those tackling harder system-level performance problems. For example this may involve a transient performance degradation, or correlating end-user quality of service with platform activity, or diagnosing some complex interaction between resource demands on a single system, or management of performance on large systems with lots of "moving parts".
The distributed PCP architecture makes it especially useful for those seeking centralized monitoring of distributed processing (e.g. in a cluster or webserver farm environment), especially where a large number hosts are involved.
Main features:
- A single API for accessing the performance data that hides details of where the data comes from and how it was captured and imported into the PCP framework.
- A client-server architecture allows multiple clients to monitor the same host, and a single client to monitor multiple hosts (e.g. in a Beowulf cluster). This enables centralized monitoring of distributed processing.
- Integrated archive logging and replay so a client application can use the same API to process real-time data from a host or historical data from an archive.
- The framework supports APIs and configuration file formats that enable the scope of performance monitoring to be extended at all levels.
- An "plugin" framework (libraries, APIs, agents and daemon) to collect performance data from multiple sources on a single host, e.g. from the hardware, the kernel, the service layers, the application libraries, and the applications themselves.
- Libraries and sample implementations encourage the development of new "plugins" (or agents) to capture and export the performance data that matters in your application environment, along side the other generic performance data.
- An endian-safe transport layer for moving performance metrics between the collector and the monitoring applications over TCP/IP. This means an IRIX desktop with PCP can monitor one or more Linux systems with the Open Source release of PCP installed.
- A Linux agent that exports a broad range of performance data from most kernels circa 2.0.36 (RedHat 5.2) or later. This includes coverage of activity in the areas of: CPU, disk, memory, swapping, network, NFS, RPC, filesystems and all the per-process statistics.
- Other agents export performance data from:
- Web server activity logs
- arbitrary application-level tracing (via a PCP trace library)
- Cisco routers
- sendmail
- the mail queue
- the PCP infrastructure itself
- Assorted simple monitoring tools that use the PCP APIs to retrieve and display either arbitrary performance metrics, or specific groups of metrics (as in pmstat a cluster-aware vmstat lookalike).
- The PCP inference engine supports automated monitoring through a rule-based language and interpreter that performs user-defined actions when rule predicates are found to be true.

Network Simulator (Ns) is a discrete event simulator targeted at networking research. Ns provides substantial support for simulation of TCP, routing, and multicast protocols over wired and wireless (local and satellite) networks.
Ns began as a variant of the REAL network simulator in 1989 and has evolved substantially over the past few years. In 1995 ns development was supported by DARPA through the VINT project at LBL, Xerox PARC, UCB, and USC/ISI.
Currently ns development is support through DARPA with SAMAN and through NSF with CONSER, both in collaboration with other researchers including ACIRI. Ns has always included substantal contributions from other researchers, including wireless code from the UCB Daedelus and CMU Monarch projects and Sun Microsystems.
Enhancements:
- Major updates were made to the PackMime-HTTP HTTP/1.1 and WPAN modules.
- Solaris/Sun C compilation bugs were fixed.