Free traffic grapher software for linux

Traffic Prioritizer is designed to run on a Linux router and prioritize users traffic by their bandwidth consumption.

It is aimed to shape the "bandwidth greedy" clients (P2P, YouTube, IPTV, etc.) so that the ones who are just browsing do not lack bandwidth.

TrafficWatch is a system for accounting Internet traffic in a residential college or school type of environment. It consists of a set of scripts and web pages for accounting for internet usage by volume, and is capable of accounting for both Squid proxy traffic and direct IP traffic. It was designed primarily for the use of the colleges of the University of Melbourne, and has been in use in others colleges there since 2001.

TrafficWatch is licensed under the GNU General Public License v2

Network Traffic Analyzer analyzes the network traffic on multiple network devices and creates HTML statistics with some network usage graphs. Sometimes it is good to know, how the network is used, how many bytes were received and how many bytes were sent.Therefore, here is Network Traffic Analyzer, which creates simple network usage statistics.


Such statistics can tell you, how good your network connection really is (who cares about what Internet provider say, when was the network down, which time is the best time for downloading large packages of data etc. etc. Or with this software you can just better imagine, how many traffic can your home computer generate.

Equation Grapher is a 2D implicit equation grapher.

Equation Grapher allows you to plot equations of the form f(x,y) = g(x,y), with all of the standard operators (log, exp, sqrt, ...) as well as differentiation.

Example equations:

y = sin(x)
x = sin(y)
(xy)^2 = sin(cos(x^2 + y^2))
y = deriv(exp(-x^2/2),x)

Python Traffic Analyzer is a Python base class and sample driver script written to retrieve and manipulate images from the TrafficLand cameras and calculate a numeric value representing the current traffic flow.

PyTrAn, an example driver script, an image collector and an image mask creator are available for download from the link shown at the bottom. To use the PyTrAn package begin by choosing a camera that you wish to analyze, for this example well use the camera captioned above.

We want to construct a mask over the area of the image that we are interested in, namely the road. In this particular example the road takes up the majority of the image but that is not always the case.

We will apply the mask over captured images to fine tune the area over which we are looking for movement. To create the mask we will first need to collect a sequential series of snapshots from the target camera. The image_collector.py script was written for this task:

$ mkdir mask_200003
$ cd mask_200003
$ ../image_collector.py 200003 30
Collecting 30 images...
30

Done.

The script is hard coded to capture images on a 2-second delay. The delay is necessary to ensure the image has changed. I believe 2-seconds to be the absolute minimum. Once complete, 30 images numbered 1 through 30 will be created in the current directory.

We construct a mask from these captured images by creating a diff-image for each sequential image pair and then adding each diff-image together. Naturally, a script was written to automate this task as well:

$ ../mask_maker.py 1 30
Creating a diff for each sequential image pair.
Diffing 29

Creating the initial mask from the first image pair.

Adding the rest of the diffs to the mask.
Masking 29

Done.

A number of .diff files are generated in this process. These files repesent the movement between individual sequence pairs.

The .diff files are simply intermediary files, the important bit is the mask file, which is generated as the sum of all differences.

The mask file may be dirty (as in this case) and require manual cleanup. The basic shape of the road however is clearly visible, evidence that we can with minimal effort automate the mask generation process. Also, this run was conducted at night, day-time images yield better results.

There are a few final steps we need to take before we can use the example PyTrAn driver script. First we need to convert the mask to ASCII (noraw) format:

$ pnmnoraw mask > mask_200003.ascii

Then we need to open an ImageMagick display window and get its X-window-ID using xwininfo. Finally, update camera_id and window_id in pytran_sampling.py and launch the driver:

$ ../pytran_sampling.py
DEBUG> grabbing frame from camera 200003
DEBUG> rotating image: pytran.this > pytran.last
DEBUG> refreshing image in 3 secs
taking a 5 minute sample at various thresholds.
DEBUG> grabbing frame from camera 200003
DEBUG> generating frame diff on pytran.last, pytran.this
DEBUG> displaying image: pytran.diff
DEBUG> converting pytran.diff to ascii
DEBUG> calculating traffic ratio...
ratio[5]: 55%
DEBUG> calculating traffic ratio...
ratio[10]: 52%
...
...
5 minute sample[5]: 67.88
5 minute sample[10]: 42.66
5 minute sample[15]: 30.57
5 minute sample[20]: 23.03
5 minute sample[25]: 18.39
5 minute sample[30]: 14.79
5 minute sample[35]: 12.42
5 minute sample[40]: 10.53
5 minute sample[45]: 9.06
5 minute sample[50]: 7.85

The sampling script will take 5 minute samples at varying color thresholds. The optimal threshold must be manually chosen. Furthermore, you will need to sample the traffic ratios during both heavy and light traffic times to get a good feel for your acceptable range. Also, keep in mind that the traffic ratio value is simply the percent change detected, or in other words the movement detected within the masked region. This means that a completely empty road will register similar values to a road so congested it looks like a parking lot. The time of day can be combined with the traffic ration to determine the logical truth.

With this task implemented and abstracted more complex systems can be built. When I find the time Id like to create a system that will take multiple potential travel routes and times, and during the travel time e-mail the traveler with the best route to take. Another idea I had would be to record the traffic flow values for each camera, for each day and for each half hour interval. Travelers and other interested parties can then analyze traffic patterns to determine the fastest route dependant on date/time.

Squid Graph is a free, simple, yet powerful Squid v2 native logfile analysis tool that generates reports with graphical representation of the proxy servers traffic.
Squid Graph is distributed under the GNU General Public Licence (GPL), which means it is FREE FOR USE AND DISTRIBUTION.
Squid Graph was developed using the Linux operating system running kernel versions ranging from 2.2.x to 2.4.x with PERL 5.6.0. It should work on all other similar operating systems with PERL 5.6 and above installed.
Some platforms which have been reported to run Squid Graph successfully are FreeBSD, OpenBSD, Sun Solaris and most Linux kernel versions and distributions.
Enhancements:
- No algorithm changes, mostly changes to contact information etc. due to hand-over of project to SecurLogic.
Installation:
Extracting the Tarball
- Extract the Squid Graph tarball file after you have downloaded it. Those with Redhat Linux (or other similar distributions) can do this: -
$ tar -zxvf squid-graph-x.x.tar.gz
- Alternatively, those with UNIX-like operating systems can do this: -
$ zcat squid-graph-x.x.tar.gz | tar -xvf -
Gathering the Pre-requisites
- As of version 3.0, Squid Graph requires the GD perl module. You can download it from http://stein.cshl.org/WWW/software/GD/ or you can use the included GD-1.3.3.tar.gz file in the extras/ directory.
- Follow the intructions in the GD perl module to get it installed correctly before you proceed.
Compiling
- Squid Graph runs out of the box. You dont have to compile it.
Putting it in the Right Place
- You might not prefer to have Squid Graph lying around in your current directory, so you should just move it to a directory which makes sense, such as /usr/local/squid-graph. e.g.
$ mv squid-graph-x.x /usr/local/squid-graph
Runing Squid Graph:
Quickstart
First, get yourself into the bin/ directory, for example: -
$ cd /usr/local/squid-graph/bin
Next, you run Squid Graph with the default options. The bare minimum for Squid Graph to run is the --output-dir option. The output directory is where the generated HTML reports and image files would be written.
$ ./squid-graph --output-dir=/var/www/html/reports < /usr/local/squid/logs/access.log
NOTE: Please check your directory permissions of your output directory!
Usually you would want the output to be generated into a directory which your web server is configured with access to. In the above example, /usr/local/squid/logs/access.log is your Squid logfile.
Where you store your Squid logfile differs from system to system. For default Redhat Linux installations, it should be in /log/squid/access.log. For those who compiled and installed Squid with the default options, it should be in /usr/local/squid/logs/access.log.
Removing the TCP or UDP Graphs
Most of you wont use cache ICP or log cache ICP, so there wont be any UDP messages in your logfiles. Disabling UDP is a good idea. You can do this by specifying the --tcp-only command line option.
$ ./squid-graph --tcp-only --output-dir=/var/www/re...
Likewise, if you only want to see UDP statistics, you can specify the --udp-only option.
$ ./squid-graph --udp-only --output-dir=/var/www/re...
Generating Cumulative Graphs
As of version 3.0, Squid Graph comes with a new feature to generage cumulative curves instead of the normal graphs. This can be done by specifying the --cumulative option.
$ ./squid-graph --cumulative --tcp-only --output-dir=/var/www/re...
To have a better understanding of what cumulative curves are, take a look at the output examples. Do note that enabling cumulative graphs disables the Average Transfer Duration graph automatically.
Disabling Average Transfer Duration Graphs
You can disable the Average Transfer Duration Graph by specifying the --no-transfer-duration option.
$ ./squid-graph --no-transfer-duration --output-dir=/var/www/re...
Specifying the Start/End Time
By default, Squid Graph generates reports based on the current time. It starts analyzing from 24 hours before the current time until the current time. Sometimes we cycle logfiles so it is necessary to specify when you want Squid Graph to start looking at your log files. This is done by specifying the --start option.
$ ./squid-graph --start=991353612 --output-dir=/var/www/re...
Likewise, you can specify the end time and Squid will automatically calculate the start time for you. This is done by specifying the --end command line option.
$ ./squid-graph --end=991352122 --output-dir=/var/www/re...
To get the last line of the Squid logfile, simply use tail -n1 logfile.log
Note that the start value is a numerical value which represents the number of seconds since 1970, NOT the conventional hh:mm:ss dd/mm/yyyy format. The reason why we did this is because Squid logs its time in this format, and we can easily use head -n1 logfile.log to view the first line of the log file to determine the start time.
Enhancements:
- Updated links after moving project to Sourceforge
- Updated links to incorrect GPL license in documentation
- Updated links to outdated GD Perl module
- Simplified package directory structure and removed old files
- No algorithm / logic changes

Traffic Control Super Script implements traffic shaping for IP traffic passing through a NAT/bridge box with a single configuration file with one line per host.
Traffic Control Super Script can manage bandwidth to user-specified speeds based on the u32 classifier, and can identify traffic by source, destination, source and destination port, protocol, and ToS field. It then limits the rate of connection in either a single or a bidirectional fashion.
Enhancements:
- This release adds multiple interface support.
- It adds an option to choose between flat file and MySQL rules databases.
- It fixes bug #1469742 (duplicate group breaking child / parent relationships when direction=bi on group definitions).
- Various minor bugs have been fixed.
- There are major code cleanups, and major documentation updates on the Web site.