Protocol Error Ndt
Info Admin Archive Post RSS Shared documents Language Selection Català Czech Deutsch Greek, Modern (1453-) English Español Estonian Finnish Français Magyar Italiano 日本語 한국어 Bokmål Nederlands occitan Polish Portuguese (Brazil) Russian Swedish Turkish Vietnamese 简体中文 繁體中文 ndt-users list created Text archives Help NDT "Protocol error" Chronological Thread < Chronological > < Thread > From: Matt Crawford < > To: Cc: Vladimir Bravov < > Subject: NDT "Protocol error" Date: Thu, 14 Jun 2007 13:01:26 -0500 We've updated NDT and now see "protocol error" messages. Does the following fit a known syndrome? TCP/Web100 Network Diagnostic Tool v5.4.12 click START to begin Connected to: shasta.fnal.gov -- Using IPv4 address 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]) . . . . . 11.51Mb/s running 10s inbound test (server-to-client [S2C]) . . . . . . Protocol error! click START to re-test NDT "Protocol error", Matt Crawford, 06/14/2007 Re: NDT "Protocol error", Richard Carlson, 06/15/2007
Info Admin Archive Post RSS Shared documents Language Selection Català Czech Deutsch Greek, Modern (1453-) English Español Estonian Finnish Français Magyar Italiano 日本語 한국어 Bokmål Nederlands occitan Polish Portuguese (Brazil) Russian Swedish Turkish Vietnamese 简体中文 繁體中文 ndt-users list created Text archives Help Re: NDT and protocol error on S2C check Chronological Thread < Chronological > < Thread > From: Carlos Vicente < > To: ndt-users < > Subject: Re: NDT and protocol error on S2C check Date: Tue, 21 Apr 2009 08:45:37 -0700 The other question I have is: isn't web100_userland-1.7 supposed to have the v6 bug fixed? Running https://lists.internet2.edu/sympa/arc/ndt-users/2007-06/msg00002.html without '-4' does not work at all. What do I need to tweak to make tests over IPv6 work? Thanks, cv > Carlos Vicente wrote: > > Hi Rich and others, > > > > I just installed NDT here at UO. > > > > I'm running with: > > > > /usr/local/sbin/web100srv -a --snaplog --tcpdump -4 > > > > The problem is that I'm getting a https://lists.internet2.edu/sympa/arc/ndt-users/2009-04/msg00006.html protocol error when running the S2C > > test (this is from my Ubuntu desktop machine): > > > > # sudo web100clt -4 -l -n netspeed.uoregon.edu > > Testing network path for configuration and performance problems -- > > Using IPv4 address > > Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done > > checking for firewalls . . . . . . . . . . . . . . . . . . . Done > > running 10s outbound test (client to server) . . . . . 901.99 Mb/s > > Protocol error! > > S2C throughput test FAILED! > > Protocol error! > > > > This happens with some clients and not with others. Testing with a > > laptop running MS Vista, using Firefox, I get no errors. > > > > Here are the different versions of things on the server: > > > > RedHat AS 5.3 > > Linux kernel 2.6.20-10.3web100smp > > ndt 3.5.0 > > web100_userland-1.7 > > javac 1.6.0_13 > > > > I tried disabling iptables on both the server and the client, but that >
Sign in Pricing Blog Support Search GitHub This organization NDT NDT is a tool that provides network performance testing, using web100 to provide protocol error more information about the cause of poor performance http://software.internet2.edu/ndt ndt-user@internet2.edu Repositories People 1 Filters Sources Forks C 38 19 ndt Network Diagnostic Tool Updated Oct 11, 2016 JavaScript 1 protocol error ndt 4 ndt-javascript-client forked from collina/ndt-javascript-client NDT client written in javascript for a browser. Updated Apr 14, 2015 Java 0 0 samknows-client Updated Mar 31, 2015 Java 0 2 android-client Updated Mar 31, 2015 1 People pgesek Paweł Gesek Contact GitHub API Training Shop Blog About © 2016 GitHub, Inc. Terms Privacy Security Status Help You can't perform that action at this time. You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.