Free network interface card software for linux

NetworkControl is a utility to control and monitor network interfaces, including wireless ones (for which you see a signal strength meter, as shown).

NetworkControl addresses a conspicuous lack in most Linux distributions — most tend to be short on easy-to-use network utilities, even something as trivial as a robust, informative way to log on and off a dialup connection. NetworkControl also provides the connection IP, configuration and statistics (gleaned from "ifconfig" and updated each second), and provides graphic signal levels for wireless interfaces, handy for evaluating a system of wireless devices.

NetworkControl allows you to see network activity at a glance and lets you control your network interfaces in a fast, convenient way. It is designed to be easy to use and informative.

If you have downloaded the binary, just put it in /usr/local/bin, give it executable permissions and run it like this:
networkcontrol

You can make a desktop shortcut with this as its executable target.

If you have downloaded the source package:
Put it in any convenient location.
tar -xjf networkcontrol.tar.bz2
cd networkcontrol.dist
./auto_install.sh

If you dont want the automatic installation or you want to fine-tune the process, instead of running "auto_install.sh", after the unpacking step above, do this:

make -f Makefile.cvs dist
./configure
make
sudo make install

Obviously you may want to modify some of these steps to suit your platform.

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.

X Interface Monitor (abbriviated xifmon) monitors any network interface (most suitable, the ppp# interface) for traffic, load average, and various other statistics using purly ioctl() directly to the Linux kernel.

It also has options to run `connect and `disconnect scripts, for dialup modem users who want easy connecting and disconnecting.

gnetload network load meter project is a network and ISDN load meter that is similar to xisdnload, but works in a distributed environment.
It includes an agent (devstata) that runs on machines with interfaces to be monitored and periodically sends status information over the network. A display program (gnetload) collects and displays the data.
Both can be run on the same machine, or be used to report on the state of a dedicated router on another machine. Using multicast or broadcast addresses, data can be fed to more than one instance of gnetload. A menu for taking network interfaces up and down is also provided.
Usage: ./gnetload [-I] [-t tickscale] [-g geometry] [-d] [ip]:port
Enhancements:
- The config script was updated to build with GTK2 and GCONF2 where available.
- There are no other code changes.

Jimsim Network Simulator project can emulate several routers connected via virutal networks. You can connect to the routers with your own favorite telnet program.
Connecting to the Virtual Routers
Use your favorite telnet program to connect to each of the virtual routers. For example:
For router 1 type:
C:>telnet localhost 10000
For router 2 type:
C:>telnet localhost 10001
For router 3 type:
C:>telnet localhost 10002
Network Layout
Currently the network is configured like this:
access-list [1-99] [permit/deny] [ ip wildcard-mask | host a.b.c.d | any ]
ip acccess-list [standard] [name]
ip access-group
show access-list
show ip interface
show ip interface brief
debug interface
encapsulation [hdlc,ppp] (serial interfaces only)
bandwidth
clock rate (serial interfaces)
interface loopback0
User commands:
?
enable
exit
ping ip
show cdp
show cdp neigh
show cdp neigh detail
show interface
show interface e0,eth0,etc
show ip route
show version
Enable commands:
clear counters
clear counters interface
config terminal
copy running startup
copy startup running
debug all
debug ip routing
debug ip eigrp
debug cdp
disable
exit
reload
show run
show startup
show ip eigrp neighbors
show ip eigrp topology
traceroute ip
undebug all
undebug ip routing
undebug ip eigrp
undebug cdp
Config commands:
cdp run
enable password password
end
hostname
banner motd delimiter
banner exec delimiter
banner login delimiter
ip route network netmask dest
interface e0,eth0,etc
bandwidth value
ip address addr netmask
description
cdp enable
shutdown
line con0, console0, console 0
login
login local
password passwd
router eigrp number
network a.b.c.d
service password-encryption
user username password password
Version restrictions:
- The EIGRP support is very basic. Just the network command for now. (Neighbors dont expire.) You can disable EIGRP with "no router eigrp process_id"
- The routing table isnt 100% correct. It doesnt summarize subnets. Nor does it understand multiple routes to the same destination. This will be fixed in the next version.
- Traceroute seems to count extra hops. Its counting each remote interface on a router as a hop. So, when you traceroute from router1 to router3, it counts router2 twice (once for 192.168.1.2 and 10.1.1.1)

Network Configurator is a network configuration tool.
Network Configurator is user-level tool that aims to make network configuration more easy. It have command line and GTK+ interface.
Supported network types:
- Ethernet
- PPPoE
- PPTP
- Wi-Fi (no WEP and WPA for now)
- dialup

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.

Los Alamos Message Passing Interface is an implementation of the Message Passing Interface (MPI) motivated by a growing need for fault tolerance at the software level in large high-performance computing (HPC) systems.
This need is caused by the vast number of components present in modern HPC systems, particularly clusters. The individual components -- processors, memory modules, network interface cards (NICs), etc. -- are typically manufactured to tolerances adequate for small or desktop systems.
When aggregated into a large HPC system, however, system-wide error rates may be too great to successfully complete a long application run. For example, a network device may have an error rate which is perfectly acceptable for a desktop system, but not in a cluster of thousands of nodes, which must run error free for many hours or even days to complete a scientific calculation.
LA-MPI has two primary goals: network fault tolerance and high performance.
Network fault tolerance is acheived by implementing a highly efficient checksum/retransmission protocol. The integrity of delivered data is (optionally) verified at the user-level using a checksum or CRC. Data that is corrupt (or never delivered) is retransmitted.
As for high performance, LA-MPIs lightweight checksum/retransmission protocol allows us to achieve low latency messaging. Furthermore, the flexible approach taken to the use of redundant data paths in a network-device-rich system leads to high network bandwidth since different messages and/or message-fragments can be sent in parallel along different paths. Also, since LA-MPI is developed for use on the the large systems at Los Alamos National Laboratory we have verified that LA-MPI is scalable to over 3,500 processes.
An alternative solution to the network fault tolerance problem is to use the TCP/IP protocol. We believe, however, that this protocol -- developed to handle unreliable, inhomogeneous and oversubscribed networks -- performs poorly and is overly complex for HPC system messaging, and that LA-MPIs lightweight checksum/retransmission protocol is a more appropriate choice.
Main features:
- Standard compliant (MPI version 1.2 integrated with ROMIO for MPI-IO)
- Highly portable
- Open source (LGPL)
- Thread safe
- Optimized for SMP systems, including NUMA architectures
- Network fault tolerant (data integrity checked at user level)
- Message-fragment striping across multiple network devices
Enhancements:
- Namespace conflicts have been fixed.
- Error detection and handling of fragments has been improved.
- Bugs in memory barriers and spinlocks for x86 and x86_64 architectures have been fixed.
- Profiling and backtracing support have been added.
- Asynchronous I/O has been disabled by default as a workaround for problems with some filesystems.
- Minor timeout bugs have been fixed.