Free probe software for linux

fprobe is a small NetFlow probe which will listen on a network interface. It isusing libpcap, aggregate the traffic and export NetFlow V5 datagram to a remote collector for processing. A flow is identified by ip protocol, source ip, source port, destination ip, destination port.
Right now only ethernet interfaces are supported. Support for more media types (tunnel, ppp etc) will be added in nex versions.
/fprobe -t IP:PORT [ -i interface ] [ -s scan ] [ expression ]
-t IP:PORT NetFlow collector address
-i interface interface to listen for traffic (default eth0)
-s scan interval in seconds between two flow tables scans (Default: 10)
-c file file with MAC definitions
-p dont put the interface in promisc mode
-b go in background (daemon mode)
-l file log file name
expression a bpf expresion to filter traffic (See libpcap/tcpdump)
For example:
./fprobe -i eth2 -t 127.0.0.1:8182
This will sniff the traffic on interface eth2 and will send the NetFlow data to localhost (127.0.0.1) on UDP port 8182.
Internal flow table is parsed every scan seconds for expired flows which are sent to remote collector.
Enhancements:
- can handle IP fragments
- can set the snmp interface ID based on source/destination MAC address
- fixed uptime in exported flows
- new hash function for internal storage
- delay between udp datagrams emited

mrtg-mica-probe is a Telebit MicaBlazer modem usage probe.
mrtg-mica-probe is a modem usage probe for the ITK NetBlazer 6100 (formerly Telebit MicaBlazer) 3.32. It is used to monitor the number of used modem and ISDN lines.
The latest release of mrtg-mica-probe can always be found on the web at http://pwo.de/projects/mrtg/ or via anonymous ftp at ftp://ftp.pwo.de/pub/pwo/mrtg/mrtg-mica-probe/.
mrtg.cfg-mica shows some sample mrtg.cfg entries.
Enhancements:
- added documentation to workaround a Telebit bug that might prevent SNMP from starting correctly.

mrtg-misc-probe probes different system features for mrtg to graph.
Currently it can probe:
- percent usage of disk space and inodes for UFS filesystems
- percent usage of disk space for VxFS filesystems
- incoming and outgoing mail messages on sendmail mail server
- total size of mail messages sendt and received on sendmail mail server
- network delay using NTP peers/servers
- number of ClearCase vobs and views
- number of available and used ClearCase and MultiSite licenses
- number of active and disconnected sessions of a Citrix Metaframe server
- number of reachable hosts in a given network range
- network device reachability (ping success)
Enhancements:
- New probes: ctxmf - number of active and disconnected Citrix Metaframe sessions; hostcount - scan given nmap-network-range and return number of hosts found.

Dynamic Probe Class Library (DPCL) is an object-based C++ class library that provides the necessary infrastructure to allow tool developers and sophisticated tool users to build parallel and serial tools through technology called dynamic instrumentation.
Dynamic Probe Class Library takes the basic components needed by tool developers and encapsulates them into C++ classes. Each of these classes provide the member functions necessary to interact and dynamically instrument a running application with software patches called probes.
Dynamic instrumentation provides the flexibility for tools to insert probes into applications as the application is running and only where it is needed.
Enhancements:
- This version is a minor update to DPCL that fixes a couple problems that have been reported since the v3.4.2 release

RobotFlow is a mobile robotics tookit based on the FlowDesigner project. FlowDesigner is a data-flow oriented architecture, similar to Simulink (Matlab) or Labview that is free (LGPL) and versatile.
The visual programming interface provided in the FlowDesigner project will help people to better visualize & understand what is really happening in the robots control loops, sensors, actuators, by using graphical probes and debugging in real-time.
The work on RobotFlow has begun in september 2001 as an University of Sherbrooke project in the Mobile Robotics and Intelligent Systems Laboratory (LABORIUS). The work on the project still continues and will become available to everybody through SourceForge as a LGPL project.
We hope with this toolkit to create a standard & open platform that all people from hobbyists to researchers could use and improve over time. It primarily supports Linux/Unix using the GNOME GUI.
The FlowDesigner & the Robotflow toolkit are written in C++ and provide fully customizable control and processing blocks :
- Drivers & interfaces for Pioneer2 Robots
- Vision processing algorithms (color training & tracking, etc.)
- Player / Stage simulator drivers for FlowDesigner/RobotFlow
- Signal processing algorithms (audio + video)
- Basic Behaviors
- Fuzzy Logic control
- Artificial Neural Networks
- Embedded super blocks (subnets, iterators)
- Basic networking (TCP/IP, broadcast)
- Device control (Sony EVI-D30, SICK lasers, etc.)
- Finite State Machine (beta)
Networks created with the visual interface called "flowdesigner" can also be run as scripts (with no graphical interface), enabling robots with lower resources to fully take advantage of FlowDesigner / RobotFlow. FlowDesigner provides an easy way to create your own data types/structures and blocks as toolkits.
Enhancements:
- This release was updated to work with FlowDesigner 0.9 and MARIE 0.4.
- A RobotFlow namespace was created.
- OpenCV 0.9.6 library support with image tracking (text, color, features) and face tracking algorithms was added.
- New behaviors are included.
- Configure scripts were updated.
- The SNCRZ30 RS-232 driver was fixed.

Pocket Linux is an almost minimal, one floppy linux system designed to quickly convert PC workstation into secure linux-based workstation using ssh to connect to remote host (other networking clients are also supported).
It supports bootp for determining host IP and other network parameters (theres also manual configuration possible, but bootp is recommended).
In addition to workstations equipped with a network card (ethernet or arcnet), you can also use Pocket Linux on a PC equipped with a modem. Modem is automatically detected and then PPP connection is made.
The idea came up some time in 1996 or so. The distribution then was not perfect, but still it shown it was a great idea. It wasnt maintained for about year or so, until I took it up again in the early January 1998. After a complete rebuild Pocket Linux 2.00 was released. It soon gained a huge number of happy users, whose ideas helped its development.
The aim is to provide a small and efficient workstation that autoconfigures as much as possible and lets securely use the network from almost everywhere.
Current version is a nice attempt and future ones will enhance the automation and support for various network equipment and protocols, becoming a total solution. Future plans also include side projects like one floppy router.
In order to understand some of the config options its useful to know something about operations that are done during bootup (in order to automatically configure the network). These are, in order (the later attempts are made if the earlier ones dont set-up the network):
- attempt to setup the network using BOOTP
- attempt to reuse previous manual configuration
- modem detection
- attempt to setup modem conection
Most of the config options switches these operations on and off.
Main menu
You can choose the following network configuration commands from the main menu (only the ones that make sense in the present context are displayed):
- Options - allows setting few binary parameters controlling automatic network configuration and modem handling.
- BOOTP query - attempts to configure network (ethernet or arcnet) using BOOTP. Normally its automatically done during bootup, but this can be switched off.
- Manual configuration - allows manual setting of network configuration parameters (ethernet or arcnet).
- Detect modem - detects serial port the modem is on and its parameters (transfer rate, initialization commands).
- Dial PPP using predefined configuration - creates modem connection (PPP) using one of (up to ten) remembered configurations. By default only TPSA (0202122) configuration is remembered.
- Dial PPP using new configuration - creates new PPP configuration and sets up a modem connection using the newly created config.
- Disconnect PPP - disconnects modem connection.
- Mount /usr via NFS - mounts remote /usr filesystem via NFS. It will be automatically mounted during each Pocket Linux bootup if its turned on in configuration options.
- Exit - Do not config the network - exits the program without configuring the network.
Configuration options
There are following options available:
- Probe network with BOOTP - switches automatic BOOTP probing during bootup on and off. On by default.
- Reuse manual network configs - if on, an attempt is made to restore network configuration during bootup. Netconf remembers 10 most recent manual configurations along with network cards MAC addresses. If cards MAC address matches one of the remembered ones, assigned configuration is used. On by default.
- Automatically setup PPP - switches automatic attempt to create modem connection during bootup on and off. Its made with the first config on PPP configs list. On by default.
- Reuse modem configuration - if on, modem detection is not performed during bootup - instead most recently used modem configuration is used. Off by default.
- Pulse dialing - switches dialing mode used for modem connections between tone dialing (DTMF) and pulse dialing. Default is off (that is tone dialing).
- Automount disk partitions - switches on and off automatical disk partitions mounting (ext2 and vfat filesystems) and swap partition activation during bootup. On by default.
- Add swap file if low memory - switches on and off automatical swap file creation during bootup. Swap file is created if, and only if, theres less than 16 MB memory available (including potentially activated swap partitions) and theres a disk partition on which it could be created available. On by default.
- Automount NFS /usr - switches on and off /usr filestem mounting via NFS during bootup. NFS path to the filestem must be set using "Mount /usr filesystem via NFS" command in main menu. Off by default.
Manual network card configuration
You can enter network configuration parameters in this window:
- This machines IP - enter IP number for this computer here
- Network mask - enter netmask here. If omitted, mask will be calculated based on IP (which will not necessarily be right).
- Broadcast address - enter network broadcast address here. If omitted broadcast address will be calculated based on IP (not mask! - which will not necessarily be right).
- Default gateway - enter IP address of default network gateway (router) here.
- Nameserver IP(s) - enter one or more (separated by spaces) name servers IP addresses here. Can be omitted, but then domain names couldnt be used.
- Default domain(s) - you can enter one or more (separated by spaces) domain names to search host if incomplete domain names will be used. Its optional.
PPP configuration
You can enter modem connection configuration parameters in this window:
- Config name - config name (used in existing configuration selection menu).
- Phone number - phone number to dial (eg. 0w202122 for TPSA access modems).
- Username - username to send to remote server
- Password - password to send to remote server
- Nameserver IP(s) - enter one or more (separated by spaces) name servers IP addresses here. Can be omitted, but then domain names couldnt be used.
- Default domain(s) - you can enter one or more (separated by spaces) domain names to search host if incomplete domain names will be used. Its optional.
Because of permanent configuration that is kept on the floppy you should remember to:
- dont write protect the floppy
- dont remove the floppy from the drive (at least during network configuration)
Enhancements:
- bugfixes in netconf reuse code
- disk partitions automounting, swap partitions autoactivating
- automatic swap file creation
- extended support for NFS mountable /usr
- PS/2 mouse support
- new startup logo

cpufreqd is meant to be a replacement of the speedstep applet you can find on some other OS, it monitors battery level, AC state and running programs and adjusts the frequency of the processor according to a set of rules specified in the config file (see cpufreqd.conf (5)).
Installation:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system. If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute
`configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean. There is
also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Enhancements:
- implemented backward compatibility for the configuration file format (great!!)
- automatically load plugins (if not configured) and rely on plugins initialization to probe the necessary stuff
- the configure script now accepts --enable/disable options for plugns that need some sort of special support
- ported the PMU plugin
- added sensors plugin (youll need userspace libs from lm-sensors)
- fixed socket creation permissions
- added the ability to allow a certain group to read/write to the socket
- fixed looots of bugs
- beautified logs
- the "cpu" directive was wrong, now named "cpu_interval" run sed -i -e s/^cpu=/cpu_interval=/ /etc/cpufreqd.conf to fix things.
- reworked plugins post-configuration (might drop it actually), now plugins are correctly initialized even if their global section is missing