-----Original Message-----
From: Gordon Smith [mailto:gordon@morenet.net.nz]
Sent: Friday, 25 October 2002 12:29 PM
To: 'Chris Hellberg'
Subject: RE: adsl ran quality

Well, to be more specific, the IPNet network uses RFC1918 address space,
and ADSL is one of TCNZ's products that use that network. It also uses
RIP as its routing protocol.... I won't go into my opinions on exposing
RFC 1918 address space in this manner (or the use of rip...) :-)

An ICMP echo / echo-reply will only give total transit time between the
origin and the endpoint, which makes its use as a diagnostic tool quite
limited. Something like fping provides more functionality, and when
combined with a tool such as smokeping, becomes quite useful in
detecting trends.

For a user to expect "ping" to provide useful information about the
network they are transiting, without any knowledge of that network at
all, is a big ask. A few considerations would be: packet size, policy
routing, asymmetrical routes, QoS, traffic shaping, to name a few.

A TCP trace will yield more useful information, but unless the user has
an understanding of the underlying network topology, the results
probably won't mean much to them.

I wonder how many would even understand the cell tax overhead imposed by
ATM...

BTW, nice kernel mirror - very quick.

Cheers,

Gordon Smith CCNA
Network Operations Manager

MoreNet Ltd

> -----Original Message-----
> From: Chris Hellberg [mailto:odysseus@soa.co.nz]
> Sent: Thursday, 24 October 2002 11:06 PM
> To: gordon@morenet.net.nz
> Subject: Re: adsl ran quality
>
>
> All ADSL customers route through RFC1918 address space, so
> yes, he will have a route to some 1918 space somewhere along his path.
>
> Ping has great uses even though it was coded up in a few
> hours by Van Jacobson twenty-odd years ago. Getting an ICMP
> echo and an echo reply is exactly what ping was designed for,
> there's no failing in that. It's how you interpret it is the
> important bit.
>
> Chris
>
> On Thu, Oct 24, 2002 at 09:14:01PM +1300, gordon@morenet.net.nz wrote:
> > Quoting Fran <fran@mobilecomputing.co.nz>:
> >
> > >
> > > I get this.....
> > >
> > > PING 192.168.253.225 (192.168.253.225): 56 octets data
> > >
> > > --- 192.168.253.225 ping statistics ---
> > > 16 packets transmitted, 0 packets received, 100% packet loss
> > >
> > > Fran
> > > :):):)
> > > --
> >
> > *Sigh*
> >
> > Did it occur to you that you may not have a route to an RFC1918
> > address? Ping is not a a good diagnostic tool to use. All
> it tells you
> > is that it sent an ICMP echo, and got a reply. Do a tcp trace to a
> > real world address....
> >
> >
> >
> > Todays quote:
> >
> > > SELECT * FROM user WHERE clue > 0;
> > > 0 rows returned
> >
> >
> > -------------------------------------------------
> > This mail sent through IMP: http://horde.org/imp/
> > --
> > This message is part of the NZ ADSL mailing list.
> > see http://unixathome.org/adsl/ for archives, FAQ,
> > and various documents.
> > To unsubscribe: send mail to majordomo@lists.unixathome.org
> > with "unsubscribe adsl" in the body of the message
> >
>

-- 
This message is part of the NZ ADSL mailing list. 
see http://unixathome.org/adsl/ for archives, FAQ, 
and various documents. 
To unsubscribe: send mail to majordomo@lists.unixathome.org 
with "unsubscribe adsl" in the body of the message