...
You can run a server with:
Wiki Markup [ytl@nettest5:/opt/ndt/current/sbin\]$ sudo ./web100srv -a}}
You can run a client with
...
on the server, we get
!!!!!!!!!!! web100_middlebox() failed to get web100 connection data, rc=4middlebox() failed to get web100 connection data, rc=4
something's gone wrong! dunno what.
The last dmesg does show that it has initiated:
| Code Block |
|---|
Web100: initiailizing hash table of size 65536 (order 6)
Web100 2.5.11 200606191556 net100: Initialization successful
|
And the /proc/web100 does exist:
| Code Block |
|---|
[ytl@nettest5:/proc/web100]$ ls -lah
total 0
dr-xr-xr-x 11 root root 0 Aug 25 16:55 .
dr-xr-xr-x 97 root root 0 Aug 25 09:04 ..
dr-xr-xr-x 2 root root 0 Aug 30 17:38 15744
-r--r--r-- 1 root root 0 Aug 30 17:42 header
|
And the web100-readall program does work (but need's to be ran with root permissions).
| Code Block |
|---|
[ytl@nettest5:/proc/web100]$ sudo /opt/web100/current/bin/readall 15744
|
Forcing debugging from the server application shows:
| Code Block |
|---|
[ytl@nettest5:/opt/ndt/current/sbin]$ ./fakewww -l /opt/ndt/current/log/fakewww.log &
[1] 9890
[ytl@nettest5:/opt/ndt/current/sbin]$ sudo ./web100srv -ddd
ANL/Internet2 NDT ver 3.3.12
Variables file = /opt/ndt/current//ndt/web100_variables
log file = /opt/ndt/current//ndt/web100srv.log
Debug level set to 3
server ready on port 3001
web100_init() read 69 variables from file
nothing in queue
Timer not running, waiting for new connection
New connection received, waiting for accept() to complete
Telling client 9898 testing will begin now
Queue pointer = 9898, testing = 1, waiting = 1
Waiting for new connection, timer running
Starting test suite:
> Middlebox test
> Simple firewall test
> C2S throughput test
> S2C throughput test
<-- Middlebox test -->
-- port: 3003
Middlebox test, Port 3003 waiting for incoming connection (fd=3)
Set MSS to 536, Receiving Window size set to 262142KB
Sending Window size set to 262142KB
!!!!!!!!!!! web100_middlebox() failed to get web100 connection data, rc=2
Signal 17 received by process 9895
now = 1156985218 Process started at 1156985218, run time = 0
Queue pointer = 9898, testing = 1, waiting = 1
Received SIGCHLD signal for active web100srv process [9895]
wait3() returned 65280 for PID=9898
wexitstatus = '255'
Waiting for new connection, timer running
now = 1156985221 Process started at 1156985218, run time = 3
Timer expired while waiting for a new connection
Queue pointer = 9898, testing = 1, waiting = 1
Waiting for new connection, timer running
now = 1156985224 Process started at 1156985218, run time = 6
Timer expired while waiting for a new connection
Queue pointer = 9898, testing = 1, waiting = 1
Waiting for new connection, timer running
now = 1156985227 Process started at 1156985218, run time = 9
Timer expired while waiting for a new connection
Queue pointer = 9898, testing = 1, waiting = 1
Waiting for new connection, timer running
...
|
Doesn't appear to offer any extra details....
An email from Richard suggests that the problem lies in the Web100 v1.6 userland libraries. He also suggests putting in the '-4' option as part of the web100 server argument list:
This is running from my desktop machine on the local LAN (different VLAN).
something's gone wrong! dunno what.
Web Server
A web server to house to the java applet for ndt testing is supplied. It defaults to run on port 7123/tcp It can be run with
...
Now the NDT page is set up and a server and the fakewww server are both running: going to http://nettest5:7123 gives...
something has gone wrong?
This was found to be due to a bug in the web100 v1.6 userland library. Suppplying '-4' as part of the web100srv argument list resolves this issue.
Script Install
System init scripts can be installed automatically. Under the distribution package (ie tar'd file), there are numerous files in the conf directory which are not copied over during the system install.
...