blob: 5834160c94bb9f8686b7e2beb80804840c229c94 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
|
--- dox/netpipe.1.orig 2007-05-11 01:29:09.000000000 +0900
+++ dox/netpipe.1 2008-04-15 00:24:20.000000000 +0900
@@ -26,7 +26,7 @@
.IB E valuator
.SH SYNOPSIS
-.B NPtcp
+.B "NPtcp|NPtcp6"
[\c
.BI \-h \ receiver_hostname\fR\c
]
@@ -124,9 +124,9 @@
-.SH TESTING TCP
+.SH TESTING TCP/TCP6
.PP
-NPtcp can now be launched in two ways, by manually starting NPtcp on
+NPtcp can now be launched in two ways, by manually starting NPtcp or NPtcp6 on
both systems or by using a nplaunch script. To manually start NPtcp,
the NetPIPE receiver must be
started first on the remote system using the command:
@@ -147,7 +147,9 @@
Any options used must be the same on both sides. The \-P parameter
can be used to override the default port number. This is helpful when
running several streams through a router to a single endpoint.
-
+.PP
+The NPtcp6 program is launched in a similar manner.
+.PP
The nplaunch script uses ssh to launch the remote receiver
before starting the local transmitter. To use rsh, simply change
the nplaunch script.
@@ -376,6 +378,11 @@
.ne 3
.TP
+.BI \-P \ \fIport\fR
+Set the port number used by the TCP and TCP6 tests to \fIport\fR.
+.ne 3
+
+.TP
.B \-r
This option resets the TCP sockets after every test (TCP module only).
It is necessary for some streaming tests to get good measurements
|
