ndt-users list created

[Clayton Keller <>]

Is it possible to add the -m switch with the current switches in place?

/usr/local/sbin/web100srv -4 -a -m -l /var/log/web100/web100srv.log

Like the above, or is there going to be an issue with the -m? I did a 
quick test and now am getting a protocol error again now that the -m is 
in place, but could this be a firewall issue?

Also, is there a place to specify the max number of simultaneous tests. 
I apologize for all the questions, but it's been about 3 years since the 
last configuration, and the documentation on my part was less than stellar.

Clay

Clayton Keller wrote:
> It's running now, thanks Rich! I'll continue my tests.
>
> Are there known issues with IPv6 and the current release?
>
> Clay
>
> Richard Carlson wrote:
> > Hi Clay;
> >
> > What happens if you force the web100srv process to us IPv4 addresses 
> > (add the "-4" option to the command line?
> >
> > Rich
> >
> > At 03:44 PM 8/27/2007, Clayton Keller wrote:
> > > I am working on my VMWare based installation.
> > >
> > > I have recompiled the kernel with the web100 patches:
> > >
> > >         # grep Web /var/log/dmesg
> > >         Web100: initiailizing hash table of size 32768 (order 5)
> > >         Web100 2.5.12 200609221010 net100: Initialization successful
> > >
> > >         # cat /proc/web100/header
> > >         2.5.12 200609221010 net100
> > >         <snip>
> > >
> > > When I am trying to perform the test, I get the following output:
> > >         TCP/Web100 Network Diagnostic Tool v5.5.1
> > >         click START to begin
> > >         Connected to: 192.168.213.128  --  Using IPv4 address
> > >         Checking for Middleboxes . . . . . . . . . . . . . . . . . 
> > > ..Protocol error!
> > >         Middlebox test FAILED!
> > >         checking for firewalls . . . . . . . . . . . . . . . . . . .  
> > > Protocol error!
> > >         Simple firewall test FAILED!
> > >         running 10s outbound test (client-to-server [C2S]) . . . . . 
> > > Protocol error!
> > >         C2S throughput test FAILED!
> > >         running 10s inbound test (server-to-client [S2C]) . . . . . . 
> > > Protocol error!
> > >         S2C throughput test FAILED!
> > >         Protocol error!
> > >
> > > The following ports are opened up on the firewall:
> > >
> > > -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 
> > > 3001 -j ACCEPT
> > > -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 
> > > 3002 -j ACCEPT
> > > -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 
> > > 3003 -j ACCEPT
> > > -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 
> > > 7123 -j ACCEPT
> > >
> > > And the services are being ran as such:
> > >
> > >         /usr/local/sbin/web100srv -a -l /var/log/web100/web100srv.log
> > >         /usr/local/sbin/fakewww -l /var/log/web100/fakewww.log
> > >
> > > I removed the -m option to keep the issue of random ports needing to 
> > > be opened for multiple connections while I am still in this initial 
> > > testing phase.
> > >
> > > I am using the following software versions:
> > >
> > >         web100-2.5.12-200609221010
> > >         web100_userland-1.6
> > >         ndt-3.4.1
> > >
> > > Any help would be appreciated, if I'm needing to run some debug I'd 
> > > be happy to do so, but I'm just curious what I should be looking for 
> > > at this point.
> >
> > ------------------------------------
> >
> >
> >
> > 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