ndt-users list created

Rich

Thanks your explain, now I know what do these message mean.
As you said, I didn't tune the TCP and NDT server because I
don't how to tune them. after seeing your post I search some
methods to tune the TCP setting. I follow the step of the the
site below
https://lists.ubuntu.com/archives/ubuntu-users/2007-November/129976.html
but the test result still shows that server is the bottleneck

I guess my link speeds is up to 10MB or more (Academic Network)
and the CPU is AMD Athlon 3000+, the following is one of the test
result

**********************************************************************
WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . .  Done
checking for firewalls . . . . . . . . . . . . . . . . . . .  Done
running 10s outbound test (client-to-server [C2S]) . . . . . 90.71Mb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 93.49Mb/s

        ------  Client System Details  ------
OS data: Name = Windows XP, Architecture = x86, Version = 5.1
Java data: Vendor = Sun Microsystems Inc., Version = 1.6.0_17

        ------  Web100 Detailed Analysis  ------
100 Mbps FastEthernet link found.
Link set to Full Duplex mode
No network congestion discovered.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 4.63 msec; the Packet size = 1460 Bytes; 
and 
No packet loss - but packets arrived out-of-order 1.09% of the time
This connection is receiver limited 16.90% of the time.
This connection is sender limited 82.50% of the time.
This connection is network limited 0.59% of the time.

Web100 reports TCP negotiated the optional Performance Settings to: 
RFC 2018 Selective Acknowledgment: ON
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: OFF
RFC 1323 Window Scaling: ON; Scaling Factors -  Server=-1, Client=-1

Server '140.113.240.183' is not behind a firewall. [Connection to the 
ephemeral port was successful]
Client is not behind a firewall. [Connection to the ephemeral port was 
successful]
Packet size is preserved End-to-End
Server IP addresses are preserved End-to-End
Client IP addresses are preserved End-to-End
*********************************************************************

Lize