JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for MAPPING-CYBERSPACE Archives


MAPPING-CYBERSPACE Archives

MAPPING-CYBERSPACE Archives


MAPPING-CYBERSPACE@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

MAPPING-CYBERSPACE Home

MAPPING-CYBERSPACE Home

MAPPING-CYBERSPACE  July 2004

MAPPING-CYBERSPACE July 2004

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Traceroute and firewalls

From:

Walter Stanish <[log in to unmask]>

Reply-To:

Mapping and visualising Internet infrastructure and Web space <[log in to unmask]>

Date:

Thu, 29 Jul 2004 01:55:56 +0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (44 lines)

In answer to your query ...

I think it is unlikely that the TTL exceeded reply has been
completely filtered, though it's possible. Another
possibility is that perhaps all outgoing packets are being
rewritten to have a higher TTL?

I suppose this would result in the start of all traceroutes
slowly timing out... but higher TTL values (the 10th, 15th
or 20th hop...) still being functional.

If you like, try my (somewhat buggy, but functional!)
traceroute implementation or another one that supports
skipping the first few hops - ie: starting the traceroute
from 6 hops away (TTL 6).

( http://pratyeka.org/ctrace/ - Perl based )

Otherwise, for the first few (8 or so?) hops you can set an
option in the header of a standard ICMP ping to 'record
route'. This is the -R option in standard unix traceroute.

-------------
me@laptop:~$ ping -R 18.5.86.13
PING 18.5.86.13 (18.5.86.13) 56(124) bytes of data.
64 bytes from 18.5.86.13: icmp_seq=1 ttl=253 time=491 ms
NOP
RR: 192.168.0.2
         18.5.31.217
         18.5.86.13
         18.5.86.13
         192.168.0.1
         192.168.0.2

64 bytes from 18.5.86.13: icmp_seq=2 ttl=253 time=493 ms
NOP (same route)

--- 18.5.86.13 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1007ms
rtt min/avg/max/mdev = 491.761/492.690/493.620/1.164 ms
-------------

- Walter

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2018
January 2018
March 2017
December 2016
September 2013
June 2011
November 2008
October 2008
September 2008
August 2008
April 2008
March 2008
February 2008
October 2007
August 2007
July 2007
June 2007
December 2006
October 2006
September 2006
August 2006
June 2006
April 2006
March 2006
January 2006
December 2005
November 2005
September 2005
July 2005
June 2005
May 2005
March 2005
February 2005
January 2005
December 2004
November 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000
October 2000
August 2000
July 2000
June 2000
May 2000
April 2000
March 2000
February 2000


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager