Free network device software for linux

Network Device Change Control (NDCC) is a system that monitors and records changes to the configurations of network equipment.

Network Device Change Control can store configuration snapshots for any text-based configs. It has been used to store configurations from Unix and Linux systems, Cisco routers, switches, load balancers, and firewalls, Foundry, NetScreen, Juniper, NetScaler, and others.

It only took a while to realize that router changes should be tracked. I rewrote the system to give a current and once-back system of configurations. Since I was using diff, I decided to leave the diff information in the system. Those diffs were emailed to a group so everyone knew when something was changed, along with what was changed.

Some time later, a bank needed to track configuration files, and the system was upgraded for use within a database. The first implementation was using perl as a CGI script against a PostgreSQL database. The company wanted many changes made for their auditing needs and most of those changes enhanced NDCC. Upgrades to their environment moved things to PHP and MySQL, and the system was rewritten for that environment and the old perl code has since been lost.

This program will help you to view network activity on your network device such as eth0, ppp0 and so on.

It put animated, graduated, icons near the KDE tray.

Understanding computer networks without performing practical experiments is really difficult, not to say it is almost impossible. Unfortunately, setting up a networking lab can be very expensive.

Netkit has been conceived as an environment for setting up and performing networking experiments at low cost and with little effort. It allows to "create" several virtual network devices (full-fledged routers, switches, computers, etc.) that can be easily interconnected in order to form a network on a single PC. Networking equipments are virtual but feature many of the characteristics of the real ones, including the configuration interface.

Netkit exploits open source software (mostly licensed under GPL) and is heavily based on the User Mode Linux (UML) variant of the linux kernel. The purpose of this project is to solve many of the difficulties and technicalities that a user could have in using UML for networking. We offer the users an easy-to-use-and-install package, which at the same time implements effective network emulation. Further, we provide a corpus of teaching material that can be used for courses at different levels.

KNetworkLED is a KDE system tray app that basically mimics the behaviour of the windows network activity system tray icon.
Main features:
- Docks into KDE system tray.
- Has a configuration dialog from which you can select what network device to monitor (out of the ones you have available)and how often you want to poll that device for activity (100ms to 1000ms).
- Tooltip popup when mouseovering the systemtray icon that displays what device is being monitored and how many TX/RX packets have been transmitted/recieved.
Enhancements:
- Poll Timer was not updating on the fly when user changed it.

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.

Java Network Stack provides a Java library for research oriented network programming.

Java Network Stack is a library used by the DIMES project to create new internet measurements. It provides a clean API for packet manipulation, send, receive, filter, and analysis. It is a unification of raw socket capabilities, MAC level networkingm, and IPv6 capabilities.

802.11b Network Discovery Tools is a gtk tool to scan for 802.11b networks using wavelan/aironet hardware and Linux wireless extensions. It includes the ability to log coordinates of found networks from a GPS device that is NMEA-compatible, and can be linked to a serial port.

It currently logs the WAP MAC to a database, along with the frequency the AP uses and link quality info. aside from that, you can also connect a Garmin GPS receiver and snarf that data. Im just using GPS::Garmin, which currently doesnt support NMEA, and i didnt feel like writing another NMEA library, so maybe ill do that later. for now, youll have to
have your GPS receiver sending data in GRMN/GRMN.

To install the program, you should just have to run "make install" as root.

Just run perlskan, or /usr/local/bin/perlskan *** AS ROOT ***

ive included a small perl program called "catdb" thatll just print the contents of the database in very hard-to-read format.

To examine the db further, you can either write a program to use the PSkan::DB module to examine the database (very simple, its just a Tie::Hash module). to iterate through the database, all you have to do is:

tie(%foo, PSkan::DB);
while(($key, $data) = each %foo) {
...
}
untie(%foo);

it doesnt get much easier.

KNetworkManager is the KDE front end for NetworkManager. KNetworkManager project provides a sophisticated and intuitive user interface which enables users easily to switch their network environment.

The range of functions encompasses the features implemented by NetworkManager daemon. Up until now NetworkManager supports:

Wired Ethernet Devices (IEEE 802.3)
Wireless Ethernet Devices (IEEE 802.11): Unencrypted, WEP, WPA Personal, WPA Enterprise
Virtual Private Network (VPN): OpenVPN, VPNC
Dial-Up (PPP)

How does it work?

For both, Wireless LAN and Wired LAN, NetworkManager supports devices known to HAL. Unless working in offline mode, NetworkManager tries to keep the system connected at any time. For this, NetworkManager follows the following policy.

Once started, NetworkManager asks HAL about available network interfaces. If a wired network interface with a carrier is found, NetworkManager connects to this. Either by DHCP (default) or by setting up previously defined static configuration. Later on, when KNetworkManager starts up, NetworkManager will expose its information about network devices and wireless networks found by scanning to the applet.

At this point, if a user decides to unplug the wired connection, NetworkManager will not connect to an arbitrary wireless network. By default all available networks are untrusted. Only if a user decides to connect to a network manually once, this specific network n henceforth being marked as trusted.

n = { ESSID, Hardware address or addresses of the access point}

The trusted networks are stored individually for each user. KNetworkManager stores them and informs NetworkManager about the known, trusted networks. If a wired connection drops due to unplugging the cable NetworkManager will automatically connect to a trusted network. As this step was done without user interaction, NetworkManager will reconnect to the wired connection once it has a carrier.

If a user joins a wireless network by manual intervention (e.g. user clicks on a network listed in the context menu of KNetworkManager or connects to a hidden wireless network), NetworkManager will take down any previous connection. If one unplugs the wired connection after such a step, NetworkManager will not connect to the wired connection once it has a carrier.