[SATLUG] accessing satlug.org from GVTC's network.

Enrique Sanchez Vela esanchezvela at yahoo.com
Wed May 27 08:51:00 CDT 2009





--- On Tue, 5/26/09, Tweeks <tweeksjunk2 at theweeks.org> wrote:

> From: Tweeks <tweeksjunk2 at theweeks.org>
> Subject: Re: [SATLUG] accessing satlug.org from GVTC's network.
> To: satlug at satlug.org
> Date: Tuesday, May 26, 2009, 11:21 PM
> You can't use traceroute to test all
> the way through the Rackspace edge 
> devices.  We don't ICMP reply on our edges.. so it
> just times out.. Although 
> you can ping through.
> 
> Tweeks


the way traceroute works, at least the way I understood it, if I did understand it, is to create a series of packets increasing the TTL by one, if a packet does not return in a given time-out, it just prints * * * and continues up the chain, so a couple of firewalls or securely configured routers should not prevent the traceroute to arrive to the final destination.

here is another traceroute, using a different network than the previous one.

 1  10.205.40.2 (10.205.40.2)  1 ms  0 ms  0 ms
 2  <removed> (<removed>)  1 ms  1 ms  1 ms
 3  <removed> (<removed>)  2 ms  1 ms  1 ms
 4  * * *
 5  <removed> (<removed>)  6 ms  6 ms  5 ms
 6  cr2.n54ny.ip.att.net (12.122.130.134)  49 ms  49 ms  48 ms
 7  cr2.wswdc.ip.att.net (12.122.3.38)  49 ms  49 ms  48 ms
 8  cr1.attga.ip.att.net (12.122.1.173)  49 ms  49 ms  49 ms
 9  cr2.dlstx.ip.att.net (12.122.28.174)  49 ms  49 ms  49 ms
10  gar10.dlstx.ip.att.net (12.122.138.121)  49 ms  49 ms  49 ms
11  12.87.41.178 (12.87.41.178)  50 ms  50 ms  50 ms
12  vlan901.core1.dfw1.rackspace.com (72.3.128.21)  47 ms  48 ms  48 ms
13  aggr3a.dfw1.rackspace.net (72.3.129.11)  48 ms  48 ms  48 ms
14  satlug.org (72.3.226.68)  48 ms  48 ms  48 ms



--------------------------------------
Support the troops, bring them home.
http://therealnews.com/t/index.php?option=com_content&task=view&id=31&Itemid=74&jumival=2924

> 


      


More information about the SATLUG mailing list