GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages


Manual Reference Pages  -  RUDE (8)

NAME

rude - real-time UDP data emitter

CONTENTS

Synopsis
Description
Options
Configuration File
Todo
Bugs
Authors

SYNOPSIS

rude -s file [ -h ] [ -v ] [ -P 0-90 ]

DESCRIPTION

Rude sends UDP data into network as configured in the script file. Currently CONSTANT bitrate and TRACE type of flows are supported. The CONSTANT bitrate is specified by configuring the packet size (UDP data size in bytes) and rate (packets per second). The TRACE type of flow configuration is given as a separate text file, which can be generated from e.g. a tcpdump(8) trace. It consists of two columns where the first column describes the packet size and the second column time to wait before the next transmission.

OPTIONS

-s The script file describing the flows to be sent by the rude program. See ../rude/DOC/example.cfg, for an example.
-h Print a short help.
-v Print the version information.
-P Set the process in real-time round-robin scheduling with the given priority. Needs root permission. Use with care.

CONFIGURATION FILE

Every configuration file should contain at least three (3) commands: the START , one flow ON and one flow OFF command. If that requirement is not met or the parser can not recognize all the given commands in the file, the configuration file will be considered corrupted and the program will exit without any further action.

Lines starting with ’#’ or empty lines are treated as comments (i.e. are not processed). Configuration file can hold any number of comment lines anywhere in the file.

The START command must be the 1st command in the configuration file. It may be preceded with comment lines, but nothing else. If your config file has more than one (1) START command, the parsing will fail and the program will exit with error.

Configuration file should hold at least two commands for each flow: the ON and OFF commands. Between the ON and OFF commands can be random/any number of MODIFY commands, which alter the flow behaviour. Note that MODIFY commands are not available for every flow type.

Commands for each flow must be ordered according to the time - i.e. the ON command must be the 1st command for the specific flow and the MODIFY commands must be ordered by the time-field. The OFF command must be the last command for the flow. The commands for each flow can be "mixed" or each flow can have their configuration on different segment in the file. See ../rude/DOC/README.rude for detailed information on the configuration file.

TODO

Support more flow types.

BUGS

I hear them crawling in my head.

Please report any other bugs to the authors.

AUTHORS

Juha Laine, TUT <james@cs.tut.fi> and Sampo Saaristo, TUT <sambo@cs.tut.fi> and Rui Prior, <rprior@inescporto.pt>

SEE ALSO

crude(8)
Search for    or go to Top of page |  Section 8 |  Main Index


RUDE (8) -->

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with manServer 1.07.