tcpspray.ndisc6(1) [debian man page]

TCPSPRAY(1)							   User's Manual						       TCPSPRAY(1)

NAME

       tcpspray - TCP/IP bandwidth measurement tool (Discard and Echo client)

SYNOPSIS

       tcpspray [-46ev] [-b block_size] [-d wait_us] [ -f filename] [-n count] <hostname> [port]

DESCRIPTON

       tcpspray  uses  the Discard resp. Echo protocol (RFC 863 resp. RFC 862) to perform bandwidth measurements of TCP sessions between the local
       system, and a Discard resp. Echo server.

       Unix-based hosts can provide a Discard and/or Echo servers with the Internet super-server inetd. On Windows NT, the simple  network  proto-
       cols optional component will do the same.

       The  name  or  address  of  the server node must be specified. tcpspray will automatically try to use IPv6 when available. If not, or if it
       fails, it will fallback to IPv4. However, tcpspray4 resp. tcpspray6 only try to use IPv4 resp. IPv6.

OPTIONS

       -4 or --ipv4
	      Force usage of TCP over IPv4.

       -6 or --ipv6
	      Force usage of TCP over IPv6.

       -b block_size or --bsize block_size
	      Send block of the specified byte size (default: 1024).

       -d wait_us or --delay wait_us
	      Waits for the given amount of microseconds after any given was sent before attempting to send the next one. There  is  no  delay	by
	      default.

       -e or --echo
	      Use  the Echo protocol instead of Discard. tcpspray will measure the time required to send data and receive it back, instead of sim-
	      ply sending it.

       -f filename or --fill filename
	      Read data from the specified file to fill sent blocks with. If the file is smaller than the size of blocks, or if no file were spec-
	      ified, the remaining trailing bytes are all set to zero.

       -h or --help
	      Display some help and exit.

       -n block_count or --count block_count
	      Send the specified amount of data blocks for the measurements (default: 100).

       -V or --version
	      Display program version and license and exit.

       -v or --verbose
	      Display  more verbose informations. In particular, tcpspray will print a dot each time a block is sent. If the Echo protocol is used
	      (option -e), dots will be erased as data is received back.

DIAGNOSTICS

       If you get no response while you know the remote host is up, it is most likely that it has no Discard/Echo service running, or  that  these
       services  are  blocked  by  a firewall. Running tcptraceroute6(8) resp.	tcptraceroute(8) toward the IPv6 resp. IPv4 remote host might help
       detecting such a situation.

SECURITY

       tcpspray does not require any privilege to run.

SEE ALSO

       tcp(7), inetd(8), tcptraceroute6(8), tcptraceroute(8)

AUTHOR

       Remi Denis-Courmont <remi at remlab dot net>

       $Id: tcpspray.1 658 2010-10-31 20:56:30Z remi $

       http://www.remlab.net/ndisc6/

tcpspray				      $Date: 2010-10-31 22:56:30 +0200 (dim. 31 oct. 2010) $				       TCPSPRAY(1)

Check Out this Related Man Page

MIREDO-SERVER.CONF(5)					      System Manager's Manual					     MIREDO-SERVER.CONF(5)

NAME

       miredo-server.conf - configuration for miredo-server

SYNOPSIS

       miredo-server.conf

DESCRIPTON

       miredo-server.conf    is  the  configuration file for miredo-server.  Each configuration directive consists of one directive name, possibly
       followed by one or several spaces and a value for the directive.  White spaces, empty lines and lines starting with '#' are ignored.

       Directives are case-insensitive. A comprehensive list of the supported directives follows:

SERVER OPTIONS

       ServerBindAddress server_ip
	      Specifies the primary IPv4 address of the Teredo server.	miredo-server will bind to UDP/IPv4 port 3544 on this  address	and  waits
	      for packets from Teredo clients. It will advertise the Teredo prefix which is defined with the Prefix directive.

	      A  Teredo  server  needs two subsequent IPv4 addresses. It will wait for UDP IPv4 packets on port 3544 on both addresses.  server_ip
	      specifies the lowest of both IPv4 addresses, which is known as the primary IPv4 server address. The secondary IPv4 address should be
	      server_ip + 1 and must also be assigned to the server.

       ServerBindAddress2 server_ip2
	      It  is  possible	to specify a secondary IPv4 server address manually.  However, Miredo clients will need manual configuration (with
	      the ServerAddress2 directive in miredo.conf). Other Teredo clients are believed not to support such setup.

       Prefix teredo_prefix
	      This directive specifies the Teredo prefix which the Teredo relay and/or server will advertise.  teredo_prefix must be a valid  IPv6
	      prefix.

	      The  default  value  is 2001:0000::.  A 32-bits prefix is required to use this option. Since you do not have such big an IPv6 prefix
	      YOU WILL NOT USE THIS OPTION.  Moreover, certain third party Teredo client implementations require the default prefix.

       InterfaceMTU mtu
	      This directive overrides the value of the MTU that is advertised to Teredo clients. The default value is 1280 bytes and  should  not
	      be changed if the default Teredo prefix is used.

	      YOU MUST NOT USE THIS OPTION with the default prefix.  This would break interoperability with most Teredo relays.

       SyslogFacility facility
	      Specify  which syslog's facility is to be used by miredo-server for logging.  Possible values are: daemon (the default), local0, ...
	      local7, kern and user (see syslog(2)).

SEE ALSO

       miredo-server(8)

AUTHOR

       Remi Denis-Courmont <remi at remlab dot net>

       http://www.remlab.net/miredo/

miredo								   February 2008					     MIREDO-SERVER.CONF(5)

Linux and UNIX Man Pages

tcpspray.ndisc6(1) [debian man page]

Check Out this Related Man Page