Free linksys wireless network monitor problems software for linux

Skipole Network Monitor project is a simple network monitor with built in web server.

It allows the user to input host IP addresses, it then pings these hosts every five minutes and displays their status via a built-in web server, on port 8000.

So calling http://your_pc_address:8000 will display pages showing green, yellow or red host or group symbols.

Each host is pinged four times every five minutes, and symbols are displayed as:

green : if three or four pings are successfull
yellow : if only one or two are successfull
red : if all four fail

As well as hosts, group symbols are displayed, and can be opened to show hosts, or sub-groups nested within. The operator can create groups, and sub-groups via the gui.

KWirelessMonitor is a small KDE application that docks into the system tray and monitors the wireless network interface. It supports both Linux (tested on several major distributions) and FreeBSD (tested on 5.2.1).
I wrote this because I like the compactness of the Wavelan/Orinoco monitor in Windows. The KWirelessMonitor systray icon shows the signal quality and the bit rate using a "bar graph" and a "pie chart", respectively.
The tool tip also displays the network name (ESSID) and the power management mode. In the configuration dialog, you can change the bit rate and power management settings of the wireless interface.
It is also able to automatically enable power management when using battery power and/or automatically disable power management during data transfer. By default, it tries to automatically detect the wireless interface.
You can also manually set the interface name if necessary. Experimental: Starting with version 0.5.91, KWirelessMonitor can connect to a network specified by the user (currently only supports unencrypted networks).
Installation:
If you want to install from source, you can do the following in the top level directory (kwirelessmonitor-x.y.z):
./configure --prefix=
make
make install
A few notes:
1. < your_KDE_base > is the base directory in which KDE is installed (/usr for Red Hat/Fedora, /opt/kde3 for SUSE, or try the output of "kde-config --prefix"). This must be set correctly (otherwise the application will not be able to find the icons).
2. If the application builds successfully but it always says "No signal", it is quite possible that your glibc kernel headers and your running kernel are of different versions. You can check this by comparing /usr/include/linux/wireless.h and < your_kernel_source_dir >/include/linux/wireless.h.
3. On FreeBSD 5.2.1, it seems that the following is necessary:
./configure --prefix=/usr/local --with-extra-includes=/usr/local/include
--with-extra-libs=/usr/local/lib
Usage:
To start KWirelessMonitor, simply run the application, and it will dock into the system tray. By default, the application tries to automatically detect the wireless interface. If there are multiple wireless interfaces, the first one is selected. If necessary, you can manually set the wireless interface name by right click on the icon and select "Configure..." (see the screenshot above).
In the configuration dialog, the first time you switch to the "Settings" page, kdesu will ask for the root password, which is necessary for changing the bit rate and power management settings of the wireless interface. If you click "Ignore" or "Cancel", you will not be able to change the settings.
After the settings are enabled, the previously saved settings are immediately applied. Enabling settings and applying the previously saved settings can also be achieved by selecting "Enable Settings..." in the right-click menu. Mouse over the icon to see the tool tip, and left click on the icon to bring up the small status window (left click again to hide it).
Enhancements:
- Experimental: added support for connecting to a network specified by the user. User can enter the appropriate network name (ESSID) and click Ok/Apply to connect to the network. (Currently only supports unencrypted networks.)
Note: Tested on Fedora Core 2, Mandrake 10, and FreeBSD 5.2.1, which are supported by distribution-specific code. For other distributions, it falls back to generic code, which theoretically should work. However, given the quirks I have encountered in the above three distributions, there are likely problems with other distributions as well. Please test this feature and report problems if it does not work.

The Network Security Monitor Daemon is a lightweight network security monitor for TCP/IP LANs. It will capture certain network events and record them in a relational database. The recorded data is available for analysis through a CGI-based interface.
You can run test version with ./Monitord, just to see how it works. Production version should be run in background, v.g. with nohup ./monitord &. Both versions will accept a device name as a parameter (default: eth0). You can send them SIGHUP at any time to print some stats. If you send SIGTERM, SIGQUIT or SIGINT, all threads will end gracefully.
Enhancements:
- Linux Kernel with "packet sockets" and "socket filtering" support.
- GNU C Library 2 (glibc2) with LinuxThreads support. (integrated in most recent versions).
- Full MySQL, including headers and libmysqlclient_r.
- GNU C Compiler (gcc).
- GNU Make (make).
- Perl (perl).
- Wget (wget).
Enhancements:
- Added chmod 4755 ... in Makefile
- Root should run make now, but not the daemon ;-)
- The daemon will drop root privileges as soon as possible
- (after creating the raw socket with an attached linux socket
- filter and putting the interface in promiscuous mode)
- No threads run with root privileges so its much safer
- (specially the new server thread which reads remote user input)
- Added stats thread
- To calculate/mantain exponential averages
- Added server thread
- It accepts HTTP requests and serves stats in XML

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.

Ad-hoc Wireless Distribution Service (AWDS) is a Layer 2 routing protocol for wireless mesh networks. The project provides transparent Ethernet-like access to all participating nodes, thus easily allowing the employment of different higher level protocols like IP (with DHCP), IPv6, AppleTalk, ...

A Linux implementation of AWDS can be downloaded from our download section. Ports to other platforms are highly appreciated!

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.

GlassMonitor is a SuperKaramba monitor that has all the basic information in a small space, like:
Main features:
- Cpu usage
- Up time monitor
- Ram and Swap monitor
- Network traffic monitor
- Partitions monitor

Argus Monitoring System software is a system and network monitoring application.
It will monitor nearly anything you ask it to monitor (TCP + UDP applications, IP connectivity, SNMP OIDS, Programs, Databases, etc).
It presents a nice clean, easy to view web interface that will keep both the managers happy (Red Bad. Green Good.) and the techs happy ("Ah! thats what the problem is").
It can send alerts numerous ways (such as via pager) and can automatically escalate if someone falls asleep.
Main features:
- It is open-source available at no charge.
- It has a clean and intuitive web interface.
- The web pages can easily be understood by non-technical people.
- It can generate graphs of what is going on.
- It can monitor network connectivity (Ping test)
- It can monitor TCP/UDP ports
- It can monitor a wide variety of TCP/UDP applications (HTTP, SMTP, RADIUS, ...)
- It can monitor the output or exit code of a program (Program test)
- It can monitor the content of a web page (such as a shopping cart application)
- It can monitor the authoritativeness of a nameserver
- It can monitor SNMP OIDs (such as BGP status, UPS voltage, room temperature, ...)
- It can monitor the results of SQL queries
- It can monitor itself.
- It can be extended to monitor things that the author didnt think of
- It can notify someone (or many people) when something happens
- It can escalate, and notify someone else, if things dont get fixed.
- It can not alarm for known downtime (maintenance overrides)
- It will summarize and rate-limit multiple notifications to prevent paging-floods.
- It keeps historical statistics, for analysis or SLA verification.
- It scales well and can monitor many, many things.
- It can restrict users to viewing only certain items (user "views")
- It can restrict users access to certain features (access control)
- It can support IPv6.
- It can support SNMPv3.
- It can support l10n for your native language.
- It can support redundant multi-server configurations.
Enhancements:
- This release offers improved performance and scalability, adds support for additional tests, and adds support for failover and redundancy.