ndt-users list created

[Jason Zurawski <>]

Hey Matt;

Aaron Brown (cc'ed) will mail his patch to the discussion list ASAP.  We 
haven't thoroughly tested this beyond a couple of users currently.

Thanks;

-jason

On 3/1/11 3:27 PM, Matt Mathis wrote:
> Please send your library fix with a little summary to 
> .
>
> Thanks,
> --MM--
> -------------------------------------------
> Matt Mathis    Home/Cell:412.654.7529
>
> On Mon, Feb 28, 2011 at 2:52 PM, Jeremy 
> Palmer<>
>   wrote:
> > Fist thing to do is to make sure your server is actually listening on the
> > appropriate NDT ports on V6. See below examples.
> >
> > - This port for fakewww is listening on IPV6.
> > # netstat -anp | grep 7123
> > tcp        0      0 :::7123                     :::*
> > LISTEN      27107/fakewww
> >
> > - This port for web100srv is only listening on IPV4.
> > # netstat -anp | grep 3001
> > tcp        0      0 0.0.0.0:3001                0.0.0.0:*
> > LISTEN      27100/web100srv
> >
> > In the above example, I can connect to the NDT page over v6 but would not be
> > able to run a NDT test since web100srv/3001 is only listening on V4.
> >
> > Also, I believe there are at least two bugs related to IPV6 in the current
> > implementation of the PerfSonar toolkit (assuming you are running the 
> > toolkit).
> >
> > - The first bug appears to be a redirect issue to the toolkit homepage itself.
> > For example if I go to the IPV6 base URL of one of my PSToolkit boxes:
> > http://[2600:3000:2400::10]
> > I get an "Unable To Connect" error in FFox. I believe this is because its 
> > trying
> > to redirect to "/toolkit" with a IPV4 URL. I'm assuming Ffox wont follow a v4
> > redirect when accessed via a v6 URL (just a guess). The workaround is to use
> > /toolkit at the end of the v6 URL so it doesn't try to redirect:
> > http://[2600:3000:2400::10]/toolkit/
> >
> > - The second bug appears to be related to NDT and the web100 userland libs. My
> > issue is if I enable IPV6 in the WEB100SRV_OPTIONS in /etc/sysconfig/ndt, NDT
> > tests over V6 works fine, but when trying to run tests over v4 I get the
> > infamous "protocol error!". Switching NDT back to ipv4-only cures the error 
> > but
> > disables V6 testing. According to a response to my post on this issue, there 
> > is
> > an unsupported but fixed version of the web100 userland libs available:
> >
> > > I've got an web100 userland RPM with a bugfix that seems to fix this issue on
> > the hosts here. If you don't mind being a guinea pig, you can grab the RPM 
> > from
> > http://software.internet2.edu/branches/aaron-testing/rpms/i386/RPMS.main/web100_userland-1.7-4.el5.i386.rpm
> > . Install it by running "rpm -Uvh web100_userland-1.7-4.el5.i386.rpm" as root.
> > Then, restart NDT by running "/sbin/service ndt restart". In testing locally,
> > we've found that this new RPM seems to fix this "protocol error" issue on our
> > dual-stack hosts. Let us know if it works for you.
> >
> > Hope this helps!
> >
> > On 2/28/2011 6:59 AM, 
> >
> >  wrote:
> > > Hi all ,
> > >
> > > I have try to  using ipv6 address instead of a DNS name  and start fakewww ,
> > > web100srv -4 and web100srv -6,  But cann't  open the ndt site with ipv6 
> > > address.
> > >
> > > I have try to using the format http://[ipv6-addr]:port to connect my ndt 
> > > server
> > > site, But still can't connect .
> > >
> > >
> > >
> > >
> > >
> > > Am I missing anything ? any hint ?
> > >
> > >
> > >
> > >
> > >
> > > Thanks and best regards
> > >
> > >
> > >
> > >
> > >
> > > Matt