Free networking 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.

Network Ustadi is a Web interface for managing network services. It provides firewall management, routing table management, NAT configuration, DHCP server configuration, interface configuration, etc.
To ease the task of network administration, decrease the likelihood of erronous command execution and to maintain all network services from a central point, EnderUNIX SDT anounces the availability of its 9th open-source tool, netUstad.
The tool, designed and coded by one of our developers Ozkan KIRIK, has the capability to generate FreeBSD IPFW and Linux Iptables rulesets. It has been written in C language and includes its own HTTP server.
The newly anounced version provides a web interface for system administrators to add/delete/update IPFW and Iptables rulesets, manage routing table and network interfaces. You can manage your firewall via a TCP/IP connected remote PC, easily.
Enhancements:
- Problems that causes the process to terminate, solved.
- Virtual Server configuration problem fixed.
- Some fixes in nat management module.

My Network Catalog is an indexing engine that allows Windows shares (or Samba shares) to be bound together over a local network.

My Network Catalog allows an easy centralized search of all the files available over the network.

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.

Network Pipemeter is a tool for measuring available bandwidth between hosts. nepim is also useful to generate network traffic for testing purposes.
nepim operates in client/server mode, is able to handle multiple parallel traffic streams, reports periodic partial statistics along the testing, and supports IPv6.
nepim has been tested under Linux, Solaris and FreeBSD, though it should work under other platforms as well. If you manage to build nepim for different systems, please send the patch.
- nepim is useful to assess the throughput at the transport layer (TCP or UDP) as seen by applications.
- nepim runs single-threaded and should impose very light burden on your CPU. Unless, of course, your testing hosts have relatively high network bandwidth compared to low CPU power.
- One single server can service multiple clients simultaneously.
- As of nepim 0.11, one single client can interact simultaneously with multiple servers. For instance, suppose you want to test, from a single client, two remote servers, one located at 10.0.0.1,2000 and another at 192.168.0.1,3000:
- nepim -c 10.0.0.1,2000/192.168.0.1,3000
- The server listens to both TCP and UDP sockets. The client by default uses TCP sockets. Use the "-u" client option to switch the client operation to UDP.
- By default, only the server sends traffic towards the client. Use the "-s" client option to reverse the behavior, then only the client will send traffic. Use the "-d" client option to make both client and server to send traffic.
- Use the "-r" client option to establish an upper bit rate limit. Without a rate limiting option, nepim sends as fast as possible. See also "-R" below. Please notice the rate is specified in bps (bits per seconds); for instance, the following example states a rate limit of 100,000 bps (100 Kbps):
- nepim -c 10.0.0.1 -r 100000
- Use the "-R" client option to establish an upper "packet" rate limit (outbound rate limit for transport layer segments). Without a rate limiting option, nepim sends as fast as possible. If both "-r" and "-R" are given, nepim limits the sending rate at the lower of those bounds.
- Use the "-n" client option to run multiple parallel traffic streams.
- Use the "-b" server option to make the server to listen on specific local addresses.
- Use the "-6" option to disable IPv6 support.
Enhancements:
- Support for randomizing the UDP destination address/port has been added in order to put stress on routers with on-demand (dynamic) forwarding table caches.

poker-network project includes a poker server, a client library, an abstract user interface library, and a client based on it.

The server deals the cards and checks the user actions using a poker game engine (poker-engine). It listens on a TCP/IP port and understands its own specific protocol. The persistent information is stored in a MySQL database.

The client library implements the poker-network protocol for the client. The abstract user interface library provides a framework based on the client library and suited to implement a user friendly client.