ndt-users - Re: Middlebox test failed
Subject: ndt-users list created
List archive
- From: Rich Carlson <>
- To: Ben Carbery <>
- Cc:
- Subject: Re: Middlebox test failed
- Date: Fri, 16 Apr 2010 09:27:19 -0400
Hi Ben;
1st make sure the web100 patch got installed and you have booted into that kernel. Look for the /proc/web100 directory. Also run the web100 'readall' command as root.
If this is OK then try adding the '-4' option to the NDT server daemon (/usr/local/sbin/web100srv). This tells the server to use only IPv4 addresses. The NDT system uses mapped IPv4 addresses and it did tickle a bug in the web100 userland library. If that works, you can find a patch for the lib by searching this list archive.
Let us know what you find and we'll help you get going. As for the version numbers. The Java applet and the server daemon version numbers got out of sync during the development process. A few months ago I decided to merge them and I used the daemon version number as the base. This dropped the applet from 5.5.4a back to the 3.6.x number. (FWIW a 5.5.4a applet runs a 3.4.4a daemon.)
Rich
On 4/15/2010 7:29 PM, Ben Carbery wrote:
Hi NDTers,
I am installing an NDT server at our university here in Australia. We
are running the latest version which seems to be 3.6.2b (not sure why
other servers report 5.5.4a?).
This is the error we are getting when running tests on patched vanilla
kernel 2.6.18.8:
New connection received, waiting for accept() to complete
initialize_tests returned old/new client = 1, test_suite = 1 8 2 4
Line just before ChldRdy: label, did't get here via the goto statement!
___-------______ client process is ready for testing!
Telling client 26756 testing will begin now
Queue pointer=26756, testing=1, waiting=1, mclients=0, zombie_check=0
Waiting for new connection, timer running
Valid test sequence requested, run test for client=26756
run_test() routine, asking for test_suite = 1 8 2 4
Starting test suite:
> Middlebox test
> Simple firewall test
> C2S throughput test
> S2C throughput test
<-- 26756 - Middlebox test -->
-- port: 3003
*!!!!!!!!!!! test_mid() failed to get web100 connection data, rc=9*
Middlebox test FAILED!, rc=-3
<-- 26756 - Simple firewall test -->
-- port: 56085
Simple firewall test: Cannot find connection
Simple firewall test FAILED!, rc=-1
<-- 26756 - C2S throughput test -->
-- port: 3002
listening for Inet connection on testOptions->c2ssockfd, fd=7
Sending 'GO' signal, to tell client 26756 to head for the next test
Timer expired while waiting for a new connection
Can anyone help with where the problem lies?
regards,
--
________________________________________________________________________________
Ben Carbery (CCNP CCIP)
E-Mail:
Networks& Communications, DOI Phone : (02) 6125 9481 Mob : 0402 130
700
Leonard Huxley Building #56 Fax : (02) 6125 8199 Ext : 59481
Australian National University Canberra, ACT 0200 Time: AEST
GMT+10
- Middlebox test failed, Ben Carbery, 04/15/2010
- Re: Middlebox test failed, Rich Carlson, 04/16/2010
- Re: Middlebox test failed, Ben Carbery, 04/18/2010
- Message not available
- Re: Middlebox test failed, Ben Carbery, 04/19/2010
- Re: Middlebox test failed, Rich Carlson, 04/19/2010
- Message not available
- Re: Middlebox test failed, Ben Carbery, 04/18/2010
- Re: Middlebox test failed, Rich Carlson, 04/16/2010
Archive powered by MHonArc 2.6.16.