| 1 |
************************************************************************* |
| 2 |
You need the following software installed on your system: |
| 3 |
|
| 4 |
- perl 5.003 |
| 5 |
http://www.perl.com/perl/info/software.html |
| 6 |
- MRTG 2.1 |
| 7 |
http://www.ee.ethz.ch/~oetiker/webtools/mrtg/mrtg.html |
| 8 |
- gcc to successfully compile tcpblast.c |
| 9 |
|
| 10 |
************************************************************************* |
| 11 |
mrtg-blast has been tested successfully under: |
| 12 |
|
| 13 |
Linux 2.0.25 (S.u.S.E. 4.3) |
| 14 |
|
| 15 |
(other versions / OSes might work, but have not been tested.) |
| 16 |
------------------------------------------------- |
| 17 |
The latest version should always be available from |
| 18 |
|
| 19 |
ftp://ftp.inside.ch/pub/mrtg-blast |
| 20 |
|
| 21 |
If you create a new version, please send it to me so I |
| 22 |
can keep the archive up to date. |
| 23 |
************************************************************************* |
| 24 |
|
| 25 |
YOU NEED TO CHANGE THE FOLLOWING: |
| 26 |
tcpblast: |
| 27 |
1 - Type 'make tcpblast' to compile the tcpblast executable |
| 28 |
2 - Copy tcpblast to your mrtg binary directory |
| 29 |
|
| 30 |
In mrtg-blast: |
| 31 |
1 - Line 1: Adjust perl path to your system |
| 32 |
2 - Line 55: Adjust tcpblast path to where you put tcpblast |
| 33 |
3 - Copy mrtg-blast to your mrtg binary directory |
| 34 |
|
| 35 |
Edit your mrtg-blast.cfg file to add statements for the devices you want to |
| 36 |
blast. See mrtg-blast.cfg for an example. |
| 37 |
|
| 38 |
PLEASE NOTE: Blasting causes traffic, which it inherently does. ;) So please |
| 39 |
don't flood the whole wide world, keep it as local as possible. |
| 40 |
Blasting can't be that bad though, considering internet radio and tv... at least |
| 41 |
it tells us something: How fast our next video conference will pass, for example. |
| 42 |
|
| 43 |
The program returns traffic estimates which can be off sometimes. Use with care, |
| 44 |
caution and much love. |
| 45 |
Here are some estimates I tested at our site locally. Your mileage will most |
| 46 |
definitely vary, but as a guideline I always use 500 packets if I'm close to |
| 47 |
the site being blasted otherwise 200 is good enough. |
| 48 |
|
| 49 |
Link: 256 kbps = 32 kB/s |
| 50 |
|
| 51 |
#of packets: bandwidth as estimated |
| 52 |
by tcpblast [kB/s]: Error in %: |
| 53 |
|
| 54 |
100 50 +53 % |
| 55 |
200 38 +16 % |
| 56 |
300 35 +5 % |
| 57 |
400 34 +4 % |
| 58 |
500 32 0 % |
| 59 |
800 32 0 % |
| 60 |
|
| 61 |
You should decide yourself how accurate you're trying to be. Once again: |
| 62 |
Your mileage will vary. |
| 63 |
|
| 64 |
Have fun! |
| 65 |
|
| 66 |
Balthasar Indermuehle <[email protected]>, March 12, Early in the morning... |
| 67 |
|
| 68 |
|
| 69 |
|