Skip to Content.
Sympa Menu

ndt-users - cockpit error or problem with 5.5.4b vs. 5.5.4a?

Subject: ndt-users list created

List archive

cockpit error or problem with 5.5.4b vs. 5.5.4a?


Chronological Thread 
  • From: Larry Vaden <>
  • To:
  • Subject: cockpit error or problem with 5.5.4b vs. 5.5.4a?
  • Date: Tue, 2 Nov 2010 04:13:38 -0500
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=xngs9ZER583MMe0Zslt2iVXf8bgt6SoIZb+yhIrkVzhKZ+3npkQ4+IukzjgA63Zxi8 fwEKHpazcTxYnUQCZll7YvHRBLTMPWTUJVaB8h42vq7A8PDQoBsnXT0Vi+OqxiCNn7zx bFKbm6UTCsOE9BHpNMjHh7VhWpH5FtoutceI8=

Hello NDT-users,

The test is performed against ndt.anl.gov:7123 and fails; the test
does not fail when performed against ndt.ucsc.edu:7123.

Verizon dry DSL --- ActionTec GT704WGB dsl modem --- MikroTik RB750
--- XP laptop

The ActionTec obtains a public IP address from Verizon.

The MikroTik diverts only RFC1918 space via L2TP tunnel to our network
(texoma.net, ASN 4963).

Everything seems to function OK (public address space, RFC1918 address
space suffers ~ 2 msec latency).

NDT takes ~ 2 min to complete the 10 second C2S test, then has
problems with the S2C test.

Double NATing is occurring.

Is this likely a cockpit error on my part?

THANKS for such a great tool --- we use it often to find problems in
our rural wireless network.

kind regards/ldv

Larry Vaden, CoFounder
Internet Texoma, Inc.
Serving Rural Texomaland Since 1995
We Care About Your Connection!

===== testing against ndt.internet2.edu

TCP/Web100 Network Diagnostic Tool v5.5.4b
click START to begin

** Starting test 1 of 1 **
Connected to: ndt.anl.gov -- Using IPv4 address
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 370.0kb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . Protocol error!
S2C throughput test FAILED!
Protocol error!

click START to re-test

** Starting test 1 of 1 **
Connected to: ndt.anl.gov -- Using IPv4 address
Another client is currently being served, your test will begin within
135 seconds
Another client is currently being served, your test will begin within 90
seconds
Another client is currently being served, your test will begin within 45
seconds
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 371.0kb/s
Error in parsing tests results!

click START to re-test

===== testing against ndt.ucsc.edu:7123


TCP/Web100 Network Diagnostic Tool v5.5.4a
click START to begin

** Starting test 1 of 1 **
Connected to: ndt.ucsc.edu -- Using IPv4 address
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 372.0kb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 760.80kb/s
Your PC is connected to a Cable/DSL modem
[S2C]: Packet queuing detected

click START to re-test



Archive powered by MHonArc 2.6.16.

Top of Page