ndt-users list created

[Richard Sanger <>]

Hi Daniel,

I've looked into this and it's not just you - you're setup sounds correct.
The short answer is to run the server with the --ipv4 option for now and it'll hopefully work, there is a bug in ndt-web10g.

sudo modprobe tcp_estats_nl

sudo ./web10gsrv -ddddd --ipv4

Yip tcp_estats_nl is the one you want along with web10g-userland-2.0.4. Sorry for the confusion about this.

Ok so listconns wasn't actually the the tool I was thinking of :), rather than readconn (then to add to your confusion readconn was been renamed to readvars in newer web10g-userland).

ndt-web10g doesn't use listconns directly, so it doesn't need to be in PATH or anything like that, its just the code use within ndt-web10g is almost identically to listconns. So its useful to run listconns to check connections are showing up there.

Details on what actually broke

Dominic's latest commit changed the socket handling code and this has broken the Web10G socket matching.

Sockets are now coming through as IPv4-compatible IPv6 address (Didn't even know these existed myself).
So when we're matching a socket with a Web10G connection number, the socket appears to be IPv6 however but it represents a IPv4 address but I'm only matching this with IPv6 connections in the Web10G tables.

This is fixable I'll work on the patch when I get time in the next couple of days. I'll also look into why ndt-web10g branch isn't building because it should.

Cheers,
Richard

On Wed, Apr 10, 2013 at 3:52 AM, Daniel A. Ramaley <> wrote:

Hello again. I did a "modprobe tcp_estats_nl" (that was the module with
the closest name to "tcpe_estats") but get the same result. I don't have
readconn installed, so suspect i might've not installed enough stuff
yet.

I got the kernel patch from http://web10g.org; i downloaded a file named
web10g-estats-0.1-3.2.tar.gz and inside it found the patch, which was
named estats-nl-0.1-3.2.patch. There were a few other patch files in the
tarball, but after consulting the README i thought the estats-nl-*.patch
was the correct one.

After compiling a patched kernel, i went to http://web10g.org again and
downloaded web10g-userland-2.0.4.tar.gz, then compiled and installed it.
As far as i can tell, estats (and readconn?) were part of a package
called estats-userland, but that package was replaced with the web10g-
userland package that i installed. Do i need the older estats-userland
as well?

After that i grabbed web100_userland-1.8.tar.gz from
http://www.web100.org and installed it. Then i installed
bwctl-1.4.tar.gz from http://software.internet2.edu; the bwctl package
seems to provide I2util which is needed by NDT.

Finally, i compiled and installed NDT with the web10g patch. I
downloaded my copy of NDT from trunk a couple days ago.

With this process, is there anything obvious that i missed, any other
packages that i should have installed? And should i install estats-
userland even though i already have the newer web10g-userland?

Thanks,
Dan

On 2013-04-08 at 19:33:38, Richard Sanger wrote:
>Hi Daniel,
>
>Yeah java problem would have been a typo, I had a single patch which I
>split out into two and I must of missed that.
>

>Yes *test_min() failed to get web10g connection data, rc=0* is the

>significant line.
>This appears to be another typo on my behalf test_min() -> test_mid()
>as in middebox.
>
>The most likely cause is that the Web10G module isn't loaded.
>from memory something like this:
>user@machine~modprobe tcpe_estats
>
>If that is loaded, use the estats tool readconn to check that the
>connection is showing up when you run the ndt test.
>There should be two connections one to the server on port 3003 which
>is for the middlebox test and another on port 3001 which handles
>results.
>
>The error means that the tcp_socket/connection on server port 3003
>(which the client has connected to) cannot be matched to the list
>returned by readconn.
>Or if it is there, we've got a bug in the matching.
>
>Cheers,
>Richard
>
>
>On Tue, Apr 9, 2013 at 6:59 AM, Daniel A. Ramaley
>
><>wrote:
>> I have NDT compiled and installed now, with the web10g patches. And
>> it gets a little further than it did before, but still is not
>> working correctly. Here's what is displayed in the web browser:
>>
>>
>>
>> TCP/Web100 Network Diagnostic Tool v3.6.5.2
>> Click START to start the test
>>
>> ** Starting test 1 of 1 **
>> Connection to 'ndt01.drake.edu' [ndt01.drake.edu/10.11.1.5] to run
>> test Connected to: ndt01.drake.edu-- Using IPv4 address
>> Checking for Middleboxes  . . . . . . . . . . . . . . . . . .
>>
>>
>>
>> Before doing any of the Web10g patches, it didn't display the
>> Middleboxes line. Now it does that and then hangs.
>>
>> I've pasted the output below from running ndtd with "-dddd"; i
>> think the relevant bit is "failed to get web10g connection data".
>>
>> Any ideas on what i should try next?
>>
>>
>>
>> ANL/Internet2 NDT ver 3.6.5.2
>>
>>         Variables file = /usr/local/ndt/web100_variables
>>         log file = /var/log/web100srv.log
>>         Admin file = /usr/local/ndt/admin.html
>>         Debug level set to 4
>>
>> server ready on port 3001 (family 0)
>> Reading line: Signal 17 received by process 3805
>>
>> Reading line: Web100srv (ver 3.6.5) process (3805) started Mar 26
>> 15:21:28
>>
>> Reading line: Signal 17 received by process 3805
>>
>> Reading line: Signal 13 received by process 3805
>>
>> Reading line: Signal 17 received by process 3822
>>
>> Reading line: Web100srv (ver 3.6.5) process (3822) started Mar 26
>> 15:22:25
>>
>> Reading line: Signal 17 received by process 3822
>>
>> Reading line: Signal 13 received by process 3822
>>
>> Reading line: Signal 2 received by process 3822
>>
>> Reading line: Web100srv (ver 3.6.5) process (3834) started Mar 26
>> 15:26:08
>>
>> Reading line: Unexpected signal (18) received, process (3834) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (3834) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (3834) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (3834) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (3834) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (3834) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (3834) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (3834) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (3834) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (3834) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (3834) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (3834) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (3834) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (3834) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (3834) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (3834) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (3834) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (3834) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (3834) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (3834) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (3834) may
>> terminate
>>
>> Reading line: Web100srv (ver 3.6.5) process (2859) started Mar 27
>> 10:14:40
>>
>> Reading line: Unexpected signal (18) received, process (2859) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2859) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2859) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2859) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2859) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2859) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2859) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2859) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2859) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2859) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2859) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2859) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2859) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2859) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2859) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2859) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2859) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2859) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2859) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2859) may
>> terminate
>>
>> Reading line: Web100srv (ver 3.6.5) process (2792) started Apr  5
>> 14:51:11
>>
>> Reading line: Web100srv (ver 3.6.5) process (2825) started Apr  7
>> 13:13:48
>>
>> Reading line: Web100srv (ver 3.6.5) process (2791) started Apr  7
>> 13:32:42
>>
>> Reading line: Unexpected signal (18) received, process (2791) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2791) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2791) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2791) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2791) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2791) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2791) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2791) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2791) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2791) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2791) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2791) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2791) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2791) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2791) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2791) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2791) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2791) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2791) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2791) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2791) may
>> terminate
>>
>> Reading line: Web100srv (ver 3.6.5.2) process (2838) started Apr  8
>> 10:17:18
>>
>> Reading line: Unexpected signal (18) received, process (2838) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2838) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2838) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2838) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2838) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2838) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2838) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2838) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2838) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2838) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2838) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2838) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2838) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2838) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2838) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2838) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2838) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2838) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2838) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2838) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2838) may
>> terminate
>>
>> Reading line: Web100srv (ver 3.6.5.2) process (2825) started Apr  8
>> 11:15:09
>>
>> Reading line: Unexpected signal (18) received, process (2825) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2825) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2825) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2825) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2825) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2825) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2825) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2825) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2825) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2825) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2825) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2825) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2825) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2825) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2825) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2825) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2825) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2825) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2825) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2825) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2825) may
>> terminate
>>
>> Reading line: Web100srv (ver 3.6.5.2) process (2829) started Apr  8
>> 12:54:58
>>
>> Reading line: Unexpected signal (18) received, process (2829) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2829) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2829) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2829) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2829) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2829) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2829) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2829) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2829) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2829) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2829) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2829) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2829) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2829) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2829) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2829) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2829) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2829) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2829) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2829) may
>> terminate
>>
>> Reading line: Unexpected signal (18) received, process (2829) may
>> terminate
>>
>> Reading line: Web100srv (ver 3.6.5.2) process (2795) started Apr  8
>> 13:09:44
>>
>> Reading line: Apr  8 13:10:56  10.11.1.18 port 52134
>>
>> Reading line: Apr  8 13:36:10  10.11.1.25 port 49564
>>
>> Reading line: Apr  8 13:40:10  10.11.1.25 port 49893
>>
>> Signal 17 received by process 3284
>> 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 Generated iflist with device=eth0 and if_speed=3
>> nothing in queue
>> Timer not running, waiting for new connection
>> New connection received, waiting for accept() to complete
>> New connection received from 0x67c280 [10.11.1.18] sockfd=5.
>> Child thinks pipe() returned fd0=6, fd1=7 for pid=0
>> Client connect received from :IP 10.11.1.18 to some server on socket
>> 5 initialize_tests returned old/new client = 1, test_suite = 1 8 2
>> 4 32 Line just before ChldRdy: label, did't get here via the goto
>> statement! ___-------______  client process is ready for testing!
>> Telling client 3288 testing will begin now
>> Queue pointer=3288, testing=1, waiting=1, mclients=0, zombie_check=0
>> Waiting for new connection, timer running
>> Valid test sequence requested, run test for client=3288
>> Child process 3288 started
>> run_test() routine, asking for test_suite =  1 8 2 4 32
>>
>> Starting test suite:
>>  > Middlebox test
>>  > Simple firewall test
>>  > C2S throughput test
>>  > S2C throughput test
>>  > META test
>>
>>  <-- 3288 - Middlebox test -->
>>
>>   -- port: 3003
>>
>> test_min() failed to get web10g connection data, rc=0
>> Middlebox test FAILED!, rc=-3
>> Child 3288 returned non-zero (-3) from run_test() results some test
>> failed! Processing SIGCHLD signal for active web100srv process [0],
>> sig17=0 Signal 17 received by process 3284
>> Timer expired while waiting for a new connection
>> Queue pointer=3288, testing=1, waiting=1, mclients=0, zombie_check=0
>> Processing SIGCHLD signal for active web100srv process [0], sig17=1
>> wait3() returned status=0 for PID=3288
>> wexitstatus = '0'
>> Main test process 3288 terminated, remove from queue
>> Attempting to clean up child 3288, head pid = 3288
>> Removing Child from head, decremented waiting/mclients 0/0
>> Timer not running, waiting for new connection
>>
>> __
>> Daniel A. Ramaley
>> Network Engineer 2
>>
>> Dial Center 112, Drake University
>> 2407 Carpenter Ave / Des Moines IA 50311 USA
>> Tel: +1 515 271-4540
>> Fax: +1 515 271-1938
>> E-mail:
__
Daniel A. Ramaley
Network Engineer 2

Dial Center 112, Drake University
2407 Carpenter Ave / Des Moines IA 50311 USA
Tel: +1 515 271-4540
Fax: +1 515 271-1938
E-mail: