Skip to Content.
Sympa Menu

ndt-users - Re: failed middlebox testing

Subject: ndt-users list created

List archive

Re: failed middlebox testing


Chronological Thread 
  • From: Richard Carlson <>
  • To: ,
  • Subject: Re: failed middlebox testing
  • Date: Tue, 30 Aug 2005 21:46:04 -0400

Hi Clayton;

At 11:10 AM 8/30/2005,

wrote:
I have previously configured and have the application operational. Upon setting up Web100 and NDT on another system, I am having what appears to be issues with the web100srv.

I am running kernel 2.6.12.5 with web100-2.5.4 web100_userland-1.5.4 and NDT-3.1.4a. Current version of java is 1.4.2_09, and I have tried with both the libpcap files that are provided by Fedora Core 4 and also compiling libpcap-0.9.3.

All of this sounds normal.

I have used the following options when running the web100srv client.

./web100srv -a -m -l /var/log/web100/web100srv.log.

OK, the -a says generate the admin view, the -m says let multiple clients run simultaneously, and the -l specifies the log file.

When running with -d I see the following:

# ./web100srv -d -m -l /var/log/web100/web100srv.log
Reading config file /etc/ndt.conf to obtain options
ANL/Internet2 NDT ver 3.1.4
Variables file = /usr/local/ndt/web100_variables
log file = /var/log/web100/web100srv.log
Debug level set to 1
server ready on port 3001
web100_init() read 69 variables from file

Upon starting a test I see the following:

Signal 17 received from process 6956

Signal 17 indicates that the child process 6956 was stopped or terminated.

successfully locked '/tmp/view.string' for updating
sending '0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,,' to tmp file
listening for Inet connection on sock2, fd=3
server ports 32778 32779
listening for Inet connection on sock3, fd=5
Middlebox test, Port 32779 waiting for incoming connection
Set MSS to 536, Window size set to 16777216KB

At this point the server should have ports 32778 and 32779 in a listen state. Is that true? Try running a "netstat -nat" command on the server. The ports should be in some state (WAITING, LISTEN, or something).

I then receive an error that the server failed middlebox testing.

On the working system, I see much more output when the test is began...

Any help would be appreciated on this issue, and if more information is needed, I can work on providing that as well.

What happens if you run without the "-m" flag? Does it work then?

What type of port security did you enable? Using the "-m" flag means that the NDT server will use ephemeral ports for the client connections. If you have "iptables" enabled, then the client may not be able to connect to the server.

I just tried using the "-m" on one of my test systems and it ran properly, so I'd suspect an iptables problem.

Regards;
Rich Carlson

Clayton Keller

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



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



Archive powered by MHonArc 2.6.16.

Top of Page