ndt-users list created

[Richard Carlson <>]

Hi Matt;

I think this is a NDT version problem.  There have been 4 major releases of 
the NDT code.  The original series just ran a Java client.  There was a 
major redesign of the server code when the command line client was 
added.  About a year later I added some new features to the system and this 
required some major changes to the server and client code.  I managed to 
make this change backward compatible so the new client could talk to old 
servers, but old clients would fail when talking to new servers.  About 6 
months ago there was another major change that caused another 
incompatibility between clients and servers.  This time I was unable to 
make the client backward compatible.  We are currently working on another 
change that may cause another incompatible change.

So the upshot is, you need to grab the right client to talk to the existing 
server.  The Miranda server is running the 3.1.4b server so you should be 
able to grab the NDT tarball from the 
http://e2epi.internet2.edu/ndt/download.html web site.  The CVS site 
contains the 3.1.7 version and this is why the client fails when talking 
with the miranda server.

That doesn't answer the question about the EPIPE signal.  Try the 3.1.3 or 
3.1.2 client.  The client does very little work and these older versions 
are compatible with the 3.1.4b server.

Rich

At 08:38 PM 7/17/2006, 

 wrote:
> I'm using NDT from SourceForge's CVS 
> (http://ndt.cvs.sourceforge.net/ndt/ndt/src/web100clt.c?view=log) on 
> FreeBSD 4.11-STABLE and it fails with the following error:
>
> read failed read 'Go' flag
>
> Here is the debug output:
>
> $ ./web100clt -dddddd miranda.ctd.anl.gov
> Testing network path for configuration and performance problems  --  Using 
> IPv4 addresses
> read 1 octets '0'
> Test port numbers not received, read 2nd packet to get them
> Testing will begin using port 3003 and 3002
> connecting to 146.137.222.101:3003
>
> Send buffer set to 32768, Receive buffer set to 57344
> Checking for Middleboxes . . . . . . . . . . . . . . . . . .  CWND limited 
> speed = Inf Kbps
> Done
> read failed read 'Go' flag
>
>
> Is there a better version of NDT that I should be using?  I tried the 
> version linked from the E2EPI website (3.1.4b), but that fails with an 
> EPIPE error.
>
> $ ./web100clt -dddddd miranda.ctd.anl.gov
> Testing network path for configuration and performance problems
> read 1 octets '0'
> Test port numbers not received, read 2nd packet to get them
> Testing will begin using port 3003 and 3002
>
> Send buffer set to 32768, Receive buffer set to 57344
> Checking for Middleboxes . . . . . . . . . . . . . . . . . .  Done
> running 10s outbound test (client to server) . . . . .
> Send buffer set to 32768, Receive buffer set to 57344
> Broken pipe
>
> Thanks in advance for your help.
>
>
> --
> Matt

------------------------------------



Richard A. Carlson                              e-mail: 

Network Engineer                                phone:  (734) 352-7043
Internet2                                       fax:    (734) 913-4255
1000 Oakbrook Dr; Suite 300
Ann Arbor,  MI  48104