Free alchemy network monitor pro v7.78 software for linux

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.

GTKNetTraf is a GTK2 client for the NetTraf remote network monitor.

GTKNetTraf is designed to have a more user friendly and attractive interface than the existing Tk client.

It also provides a few additional features such as measurement unit selection, easily comparable graphs and a builtin configuration dialog.

Sysmon is a network monitoring tool designed to provide high performance and accurate network monitoring.
Currently supported tests include monitoring of SMTP, IMAP, HTTP, TCP, UDP, Radius, NNTP, and POP3 servers. It also includes the ability to ping hosts and routers, as well as the ability to perform SNMP queries and generate alerts based on those results.
Sysmon has the ability to understand real network topologies, including the ability to monitor multiple paths and only report the actual device that is down instead of a router that is down, and all the hosts behind it.
Enhancements:
- fix for crash/coredump with DNS check
- Darwin/OSX 10.4.x build cleanups
- reduce calls to time()
- new queuer for objects (may not work on all systems)
- numerous cleanups
- some excess noise reduced in logs
- add some checkpointing of icmp packets and timing
- minor dependency builder fixes
- allow sets to work in the root = object declaration

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.

pmacct is a small set of passive network monitoring tools to measure, account and aggregate IPv4 and IPv6 traffic; aggregation revolves around the key concept of primitives (VLAN id, source and destination MAC addresses, hosts, networks, AS numbers, ports, IP protocol and ToS/DSCP field are supported) which may be arbitrarily combined to build custom aggregation methods; support for historical data breakdown, triggers and packet tagging, filtering and sampling.

Aggregates can be stored into memory tables, SQL databases (MySQL or PostgreSQL) or simply printed to stdout. Data is collected from the network either using libpcap (and optionally promiscuous mode) or reading NetFlow v1/v5/v7/v8/v9 and sFlow v2/v4/v5 datagrams, both unicast and multicast.

IP accounting is the key in ISP/IXP network operations like billing, graphing network resources usage, live or historical traffic analysis, handling of network thresholds, provisioning and SLA monitoring. SNMP counters sometime are not this useful because of their coarse granularity.

Finer granularities become valuable if data are historical and match logical entities of interest such as Autonomous System Numbers, departmental or customer network chunks, specific traffic flows, etc. Further, actual large-scale networks are able to produce, in very short times, high amounts of data that become quickly difficult to be processed in a meaningful way

In this context, traffic aggregation and advanced filtering and sampling capabilities are requirements that cannot be missed anymore.

Either using memory or SQL tables as backend storage, pmacct can easily feed data to tools like MRTG, RRDtool, Cacti and Gnuplot among the others. A little scripting abilities are required to glue pmacct with external tools and a number of sample scripts and some tutorials are already available.

UPS monitor is a graphical monitoring application that lets users watch a your UPSs status in real time.
Main features:
- Saves your session if UPS switches to battery power
- Warns you when power is critically low
- Lets you monitor networked UPSes
- Remembers configuration and restarts when you log on
- Extremely easy to use

DNA (Deep Network Analyser) is an open, flexible, and extensible deep network analyzer server and software architecture for passively gathering and analyzing network packets, network sessions, and applications protocols.
Deep Network Analyser project is designed to be used for Internet security, network management, intrustion detection, protocol and network analysis, information gathering, and network monitoring applications.
Main features:
- Extensible Java based network sensor (processing layers 2-7)
Configurable processing and output:
- Packet flows like Ethereal
- IP Flows like CISCO netflow
- Stateful Sessions (client/server flow pairs)
- Application protocol element output
- Configurable and extensible application protocol element parsing.
- Application protocol parsing toolkit APIs allows for new protocol parser to be easily developed and extended
- Targeting based full session capture facility, like a realtime targeted TCPDump.
- Flexible targeting from IPAddr, Port tuple to Application sensitive targeting.
- Configurable and extensible output forwarding (file, DB, Streams, JMS, RMI, etc.)
- Extensible realtime collection portable to many OS/Packet processing environments
Easily adaptable to packet processing environments:
- Specialized linux drivers mechanismon
- Network Appliances
- Network Switches / Routers
- Highly mutithreaded for increased performance over multi processor environments
Enhancements:
- Adoption of OpenAdaptor(tm) as the Output Adapter mechanism.
- Support for local-only administration.
- A new targeted packet capture parser, new run scripts, and a new install mechanism.
- Many bugfixes.