Scott Behrens

Version: 02 16 2006

ResearchGear ID: 20060216_behrens

[1. Overview]

The goal of netlasso is to create a automation tool designed to test network bandwidth while gathering system and hardware data. By using both tcp and udp tests, netlasso can help clarify the best protocol and rate to send data over a link. Netlasso reports the test results in a number of files and statistically analyzies the data. Netlasso is developed in Python and does not require root access nor does it need to be compiled. This tool uses point to multipoint in a client server model where the client connects to servers to run application and networking tests. The tool that generates the data to send by using nuttcp and iperf, but furthers its capabilities by running multiple tests while gathering system information. Later implementations of netlasso will use newer protocols such as rbudp and LamdaStream as well as offer a data archiving format that can later generate rrd graphs.

[2. Requirements]

  • Linux Kernel 2.4 or greater
  • Python 2.3
  • Sendmail (optional, I know in some settings its turned off )
  • sshkeys set up on all hosts in test.

[3. Configuration]

I'll explain the configuration file by including a sample from the default config.

servers: nortel1 # This is where you define the machines the client will connect to
clients: # The client machine
port: 20000 # The port netlasso will use to transmit packets
window: null # This doesn't need to be adjusted!
duration: 10 # Duration of each test, should be greater than 10 (I suggest at least 60 seconds)
reporting: 2 # This doesn't need to be adjusted!
nbstreams: 1 # Number of streams to send (nuttcp tests only)
email: # Specify your email address if you would like to be notified of a completed test
sendlog: no # if you would like to recieve the raw data file, just put 'yes'!
(the logfiles are sometimes large, I would not recommend requesting them on tests
involving more than 2 servers)
[nortel1] # name of the host
ip: # ip of the host
login: cavern@ # login information for the host
  You should make sure you define the hosts before you make refrence for them in the [global] section.

[4. Flags]

There are a few flags such as verbose (-v) and brief (-b).

I would always suggest running the program with the brief tag, as it provides you with a summary of the tests in progress. It also provides you with a statistically analized output file.

The verbose flag will give you a lot of information going on. If you are really interested in observing the testing, turn on both the brief and verbose flags.

[5. Logs]

The logs will be generated by timestamps. If you select the brief option 2 logs will be created. One log will contain all the raw data and the other will contain system and statistical data.

[6. Bugs]

Fill me in! Scott Behrens

[7. Copyright]

Copyright notice:

 * NetLasso
 * Copyright (C) 2006 Electronic Visualization Laboratory,
 * University of Illinois at Chicago
 * This library is free software; you can redistribute it and/or modify it
 * under the terms of the GNU Lesser General Public License as published by
 * the Free Software Foundation; either Version 2.1 of the License, or
 * (at your option) any later version.
 * This library is distributed in the hope that it will be useful, but
 * WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
 * or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public
 * License for more details.
 * You should have received a copy of the GNU Lesser Public License along
 * with this library; if not, write to the Free Software Foundation, Inc.,
 * 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA

Relevant Links


EVL ResearchGear publishes preliminary software, technical reports, data or results that the Electronic Visualization Laboratory openly shares with the research community. The work presented here is preliminary and we are not responsible for any damages that may result from its use or misuse. If you would like to cite any of this information in your research papers, presentations, etc, please reference the ResearchGear ID above. Thank you, and we hope you find the information on this page useful.

Visit ResearchGear Home Page