Questions about this topic? Sign up to ask in the talk tab.

TCP traceroute

From NetSec
Revision as of 00:24, 8 August 2012 by LashawnSeccombe (Talk | contribs)

Jump to: navigation, search

Overview

vs. UDP/ICMP

The problem with traceroutes nowdays is that most CPE and routing devices filter out unsolicited UDP packets, some even DROP the incoming packet so that it receives no icmp-port-unreachable reply, thus giving the famous * * *.

What you can do

Windows

WinMTR

 mtr combines the functionality of the 'traceroute' and 'ping' programs in a single network diagnostic tool.
 As mtr starts, it investigates the network connection between the host mtr runs on and a user-specified destination host. After it determines the address of each network
 hop between the machines, it sends a sequence ICMP ECHO requests to each one to determine the quality of the link to each machine. As it does this, it prints running
 statistics about each machine. 

Linux

Some distributions (including [gentoo]) allow you to run the traceroute command from the command line as follows:

 traceroute -T -p 80 domain.tld


mtr

 Same as above, only for Linux.   
This article was written using inappropriate person, but has otherwise good content. Please forgive (but preferrably correct) uses of I, we, us, you, etc.

This article contains too little information, it should be expanded or updated.
Things you can do to help:
  • add more content.
  • update current content.
TCP traceroute is part of a series on countermeasures.