ndt-users list created

[Peter Van Epp <>]

        Is there a known problem with copper GigE cards (note the one we are
using is also exhibiting odd UDP rate limiting on jumbo frames with an 
Apparant Networks sequencer)? I didn't see anything likely in the list 
archive.

On Tue, Jul 26, 2005 at 11:36:19AM -0700, Lixin Liu wrote:
> Just tried fibre to fibre (from .2 to .6) and it correctly reports the 
> connection is GigE, not 10GigE:
> 
> TCP/Web100 Network Diagnostic Tool v5.3.3e
> click START to begin
> Checking for Middleboxes . . . . . . . . . . . . . . . . . .  Done
> running 10s outbound test (client to server) . . . . . 990.11Mb/s
> running 10s inbound test (server to client) . . . . . . 989.22Mb/s
> The slowest link in the end-to-end path is a 1.0 Gbps Gigabit Ethernet 
> subnet
> 
> When using copper interface on blowfish (.6), we get
> 
> TCP/Web100 Network Diagnostic Tool v5.3.3e
> click START to begin
> Checking for Middleboxes . . . . . . . . . . . . . . . . . .  Done
> running 10s outbound test (client to server) . . . . . 989.60Mb/s
> running 10s inbound test (server to client) . . . . . . 989.50Mb/s
> The slowest link in the end-to-end path is a 10 Gbps 10 Gigabit 
> Ethernet/OC-192 subnet
> Information: The receive buffer should be 60595.70 Kbytes to maximize 
> throughput
> 
> 
> Lixin.
> 

Peter Van Epp / Operations and Technical Support 
Simon Fraser University, Burnaby, B.C. Canada