Re: Strange Network Problem (TTL?)

[Paul van Empelen <paul@non-existent.net>]

On Wed, Mar 08, 2000 at 08:07:23PM +0000, Fraser Campbell wrote:
> Paul van Empelen wrote:
> 
> > Can you show us some traceroutes. And can you ping from the other side?
> 
> Sorry I was a little short on information.  We can ping other hosts on the
> remote network without problems.  For example www.galileo.com is on the
> same class C as vpn.galileo.com ... we can reach www.galileo.com
> consistently from all of our computers (Linux and Win98/NT/2000).  This is
> why I think the problem is with the remote host and not our (or even their)
> network.

Hi,

I think you're right that it is their end. The TTL is very low, so they
probably screwed up something.  I did some pinging as well.  Glad that
they left their DNS open ;-)

[661 pandora]# ping airpacific.galileo.com
PING airpacific.galileo.com (12.17.202.88): 56 data bytes
64 bytes from 12.17.202.88: icmp_seq=0 ttl=233 time=209.4 ms

[662 pandora]# ping asatej.galileo.com
PING asatej.galileo.com (12.17.202.80): 56 data bytes
64 bytes from 12.17.202.80: icmp_seq=0 ttl=233 time=219.4 ms

There is also something strange with ping; you can't ping it with
the 'record route' option:
[664 pandora]# ping vpn.galileo.com
PING vpn.galileo.com (12.17.202.16): 56 data bytes
64 bytes from 12.17.202.16: icmp_seq=0 ttl=20 time=209.5 ms
64 bytes from 12.17.202.16: icmp_seq=1 ttl=20 time=209.9 ms

[665 pandora]# ping -R -v vpn.galileo.com
PING vpn.galileo.com (12.17.202.16): 56 data bytes

--- vpn.galileo.com ping statistics ---
9 packets transmitted, 0 packets received, 100% packet loss


This looks oke.

There is no way you can traceroute beyond the 12.125.84.38 box. Not even
from a nearby looking glass site in the same AS:

#################### route-server.ip.att.net ##########################

route-server>traceroute 12.17.202.88

Type escape sequence to abort.
Tracing the route to 12.17.202.88

  1 white_dwarf.cbbtier3.att.net (12.0.1.1) [AS 7018] 0 msec 0 msec 4 msec
  2 12.126.0.30 [AS 7018] 16 msec 44 msec 12 msec
  3 gbr1-a31s2.n54ny.ip.att.net (12.127.0.22) [AS 7018] 4 msec 8 msec 8
msec
  4 gbr3-p70.n54ny.ip.att.net (12.122.1.149) [AS 7018] 4 msec 4 msec 4
msec
  5 gbr3-p10.cgcil.ip.att.net (12.122.2.2) [AS 7018] 28 msec 24 msec 20
msec
  6 12.122.2.153 [AS 7018] 64 msec 60 msec 60 msec
  7 gbr1-p20.sffca.ip.att.net (12.122.1.162) [AS 7018] 60 msec 60 msec 56
msec
  8 ar7-a3120s1.sffca.ip.att.net (12.123.12.173) [AS 7018] 60 msec 60 msec
60 msec
  9 12.125.84.38 [AS 7018] 88 msec 84 msec 84 msec
 10  *  *  * 
 11  *  *  * 
 12  *  *  * 
 13 

Again, it's probably a problem on their end.

HTH,
Paul.