Free pmacct fe software for linux

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, sampling.
Aggregates can be stored into memory tables, SQL databases (MySQL or PostgreSQL) or simply pushed to stdout. Data is collected either using libpcap (and optionally promiscuous mode of the listening interface) or reading Netflow v1/v5/v7/v8/v9 packets coming from the network.
IP accounting is the key for a range of operations like billing, pricing models application, live or historical traffic analysis, network thresholds handling, provisioning and SLA monitoring. Taking SNMP counters from network equipments sometime is not this useful because of their coarse granularity.
Finer granularities become valuable if available data match logical entities of interest such as Autonomous Systems, either departmental or customer networks, specific traffic flows, etc. and can be encapsulated into arbitrary timeframes (also referred as
However, 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 filtering capabilities are requirements that cannot be missed.
Either using memory or SQL tables as backend storage, pmacct can also easily feed data to tools like MRTG, RRDtool and Gnuplot among the others. A little scripting abilities are required to glue pmacct with external tools and a few sample scripts are already included.
Enhancements:
- Support for TCP flags has been introduced.
- Flags are ORed on a per-aggregate basis.
- A new nfacctd_sql_log directive enables the use of NetFlows First and Last Switched values as timeslot delimiters.
- sfprobe and nfprobe plugins are now able to propagate tags to remote collectors through sFlow v5 and NetFlow v9 protocols.
- pmacct memory client features a new -T command line switch to output either TopN statistics.
- The pre_tag_map_entries configuration directive now allows you to dynamically allocate the Pre-Tagging map.
- There are miscellaneous bugfixes.

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.

Santa Fe Desktop Linux is an easy to use desktop operating system. It puts some of the worlds best open source applications within the reach of non-technical users. It even runs right off the CD so you can try it without installing.
Santa Fe Desktop Linux was built following these design goals:
Make it familiar. Present the user a familiar interface where they dont have to guess which buttons do what.
Keep it small. The distribution should install and run from a single CD.
Make it useful to normal users. The distribution should be useful to a large non-technical audience.
Keep it fun. Make sure audio and video work to the best of their abilities so the users can play games and enjoy multimedia without hassle.
Leave the user alone. Hardware should always be automatically detected and configured without the users help. Software configuration should automatically have sane defaults.
Unlike other operating systems, Santa Fe is designed to automatically configure itself everytime it runs. It will auto-detect the right drivers for your hardware and configure it all to the best of its abilities. No more troublesome driver installs. Santa Fe works best in Plug and Play and DHCP environments.
Main features:
- A viable alternative to your current operating system (OS).
- Imagine if your OS came preinstalled with a fully featured photo editing and image creation program.
- Imagine if every OS included an animation and 3D graphics creation program.
- What if your OS came standard with finance management and desktop publishing applications?.
- Now imagine if all those things were available for $39.95.
- Santa Fe Linux offers the open source solution to the seemingly impossible dream described above. Santa Fe comes with a program called the GIMP, a fully featured digital photo editing and image/graphics creation program. Blender, another standard program, is a 3D graphics, animation, rendering, and post production program. Managing finances is easy with GNU Cash, an open source program that gets your finances organized quickly. Desktop publishing is simple with Scribus, a program that allows you to create everything from newsletters to a fully produced magazine.
- Also, Santa Fe features a full office suite that is compatible with Microsoft? Word, Excel, Powerpoint, and Outlook.
- Additional programs that come with Santa Fe Linux:
- Gnome Meeting: Video teleconferencing application.
- Audacity: Records, renders, and applies digital effects to audio.
- Kino: Digital video editor.
- XMMS: Audio player that supports a wide variety of audio file formats.
- Anjuta: Developers program which allows users to create their own applications/programs.
- Also, at a price of 82.99, Santa Fe is now available with Codeweavers Crossover Office. This program allows users to install the Microsoft? Office Suite including Word, Excel, Powerpoint, Outlook, and Access.

Audio::MFCC is a Perl module for computing mel-frequency cepstral coefficients.

SYNOPSIS

use Audio::MFCC;
my $fe = Audio::MFCC->init(%params)
$fe->start_utt;
my @ceps = $fe->process_utt($rawdata, $nsamps);
my $leftover = $fe->end_utt;

This module provides an interface to the Sphinx-II feature extraction library which can be used to extract mel-frequency cepstral coefficients from data. These coefficients can then be passed to the Speech::Recognizer::SPX::uttproc_cepdata function.
You might find this useful if, for example, you wish to do the actual recognition on a different machine from the audio capture, and dont have the bandwidth to send a full stream of audio data over the network.

Currently, Sphinx-II also uses delta and double-delta cepstral vectors as input to its vector quantization module, but the calculation of these values is done inside the recognizers utterance processing module.. In the future it may be possible to move the extraction of these features into the feature extraction library, or to use entirely different features as input (for example, LPC coefficients, though currently, mel-scale cepstra give the best recognition performance).

SIAR (Simple IP Account Reporter) is a plug-in for pmacct (Promiscuous Mode IP Accounting Package) for creating specific reports of traffic on a LAN.

SIAR plugin creates an overview of the total of traffic that passed through the interface, a top protocol table, a top listener table, a top talkers table, a total situation table, seek for an IP source, seek for an IP destination, seek for both, a top conversation table and a graph for a specific day

Installation:

After you have download the file, you have to decompress it in the web-server folder. I suggest to decompress it in /var/www/, infact if you decompress it in an another you will have problems with the code.

cd /var/www/
tar xfz < name >-x-y-z.tar.gz
cd < name >-x-y-z.tar.gz

The tool is now installed. Read the CONFIG file for the configuration.

Froody::QuickStart is a Perl module for the froody Quick Start tutorial.

At the core of Froody is the concept of Froody Methods, methods that you can call remotely over the web.

For example, we have a hypothetical method called "examples.myapi.greet" that can return us greetings. We need to pass it one parameter, called "who", that is the name of the person were greeting. These two things are passed as CGI parameters to a froody endpoint (a cgi script, a mod_perl server, whatever) sitting at "http://myserver.com/fe"

bash$ lwp-request http://myserver.com/fe?method=examples.myapi.greet&who=Mark
< ?xml version="1.0" encoding="utf-8"? >
< rsp stat="ok" >
< greeting >Hello Mark!< /greeting >
< /rsp >

We get a chunk of XML back that is the result of calling the function.

Mesh Viewer is an easy to use lightweight application to display triangular meshes from a variety of file formats (see 3D formats).
Mesh Viewer uses the OpenGL API to render the models. The program was born under the need for quickly displaying reconstructed triangulated meshes. The Mesh Viewer based on an idea and an early elementary implementation from Craig Robertson.
The current version was developed by Helmut Cantzler. Triangular meshes can be displayed texture mapped (optional with bilinear filtering), solid or as a skeleton (full or just the front lines).
The surface normals of the triangles can be displayed optionally. Features (from a different data file) like edges and points can be displayed into the mesh. Loaded models can be rotated, translated and scaled (all done with the mouse). The model is lighted by multiple light sources.
Viewpoints can be saved. Screenshots of the model can be taken (as BMP, JPEG, PNG and so on). The program is able to calculate the texture map for the 3D model (experimental!).
It can read:
- PMesh files (used at the Vision group of the University of Edinburgh)
- GTS files (from the Gnu Triangulation Library)
- Geomview files (only format "OFF")
- PLY files (only ASCII format)
- VRML 1 files (no texture mapping)
- VRML 2 files
- Feature file
- List file
File format descriptions:
The PMesh format begins optional with a header. The first header line consists of "#pmesh". The header ends with the first line not starting with a "#". The data starts with nv lines of the format "v float float float" for the vertices. Follows nf lines of the format "p 3 int int int" for the triangles. Each line contains the three indices of the vertices. The index of the vertices starts at one.
The GTS format is describe shortly. The first line contains three unsigned integers separated by spaces. The first integer is the number of vertices, nv, the second is the number of edges, ne and the third is the number of faces, nf. Follows nv lines containing the x, y and z coordinates of the vertices. Follows ne lines containing the two indices (starting from one) of the vertices of each edge. Follows nf lines containing the three ordered indices (also starting from one) of the edges of each face.
The Geomview formal starts with a header consisting of the format line "OFF" and a second line with three integer numbers. The first integer is the number of vertices, nv, the second is the number of polygons, np, and the third number is typically "0". Following are the nv lines of vertices (each consists of three floats). The other part of the file are np lines of polygons. The first number of each line stands for the size of the polygon. Mesh Viewer just reads polygons consisting of 2 or 3 vertices. Following are a number of indices of the vertices depending on the size of the polygon. The index of the vertices starts at zero.
VRML is only supported partly. The Mesh Viewer extracts only vertices and triangles from VRML files and ignores all other shapes. Shapes in VRML 2.0 are rotated, scaled and translated if necessary. The file name for JPEG texture and texture coordinates are read from VRML 2.0 files if existent.
The Feature file is used to store vertices and edges. A feature file can be loaded beside the mesh to display vertices or edges into the mesh. The first header line consists of "#list". The header ends with the first line not starting with a "#". The lines consists of either vertices or edges. A vertex line consists of the format "fv float float float". A edge line starts with "fe" followed by the x, y and z coordinates for the start and the end vertex.
The List file is only a text file listing n mesh files, which a loaded subsequently as different shapes into one mesh. Lists are useful for displaying a segmentation of a mesh. The first header line consists of "#list". The header ends with the first line not starting with a "#". The following n lines consists of the names for the mesh files (one per line).