20010131: twisters ip address and ldm stats

------- Forwarded Message

>To: Unidata Support <address@hidden>
>cc: address@hidden
>From: Jeff Weber <address@hidden>
>Subject: Re: 20010131: twisters ip address and ldm stats
>Organization: UCAR/Unidata
>Keywords: 200101311648.f0VGmOg09065

David, I suspect when the page regenerates twister will show up. There is
a little quirk about the latency page in that without a reconnect from
your feed your machine does not show up. So if your connect has been
stable for a long time, it does not re-generate to the latency page. I
will check with Robb to see the times and dates of this generation and
then we can see if twister is showing up. I do not know if masking the IP
via the router will/should make any difference. I will check on that. I
will keep you posted on your latency data..

-Jeff
____________________________                  _____________________
Jeff Weber                                    address@hidden
Unidata Support                               PH:303-497-8676 
NWS-COMET Case Study Library                  FX:303-497-8690
University Corp for Atmospheric Research      3300 Mitchell Ln
http://www.unidata.ucar.edu/staff/jweber      Boulder,Co 80307-3000
________________________________________      ______________________

On Wed, 31 Jan 2001, Unidata Support wrote:

> 
> ------- Forwarded Message
> 
> >To: address@hidden
> >From: David Fitzgerald <address@hidden>
> >Subject: twisters ip address and ldm stats
> >Organization: UCAR/Unidata
> >Keywords: 200101311620.f0VGKIX03045
> 
> I noticed we are not showing up on the routing/latency pages.  This is
> probably due to an experiment we've been doing here at MU to bypass our
> congested campus network.  We've contraced with another ISP to provide
> us with a T1 DSL line for use just for twister, our IDD/LDM server.
> The ISP put a router on campus with one side on my subnet and the other
> on their network.  This way I didn't have to change twisters' IP
> address, however the router will mask twisters' IP address to be the IP
> address of the router on the  ISP side.  The thinking here is that all
> I have to do is run the `route` command to get to our upstream sites
> through the DSL line.  I asked Rutgers to put an allow line in their
> ldmd.conf file for the ISP IP address and things work great!  No data
> loss at all for the data coming from Rutgers (finally!)  But I don't
> see statistics for us on your web pages. I'm guessing I need to tweak
> my configuration to give you statistics, but I'm not sure how since
> twisters' IP didn't change. Plus I wanted to
> 
> The IP address that twister is being "masked to" is: 207.44.114.42 What
> do I have to do to keep stats flowing to you?
> 
> 
> Dave
> ++++++++++++++++++++++++++
> David Fitzgerald   
> System Administrator            Phone: (717) 871-2394  
> Millersville University       Fax: (717) 871-4725 
> Millersville, PA 17551                E-mail: address@hidden
> 
> 
> ------- End of Forwarded Message
> 
> 


------- End of Forwarded Message