Questions about this topic? Sign up to ask in the talk tab.
Difference between revisions of "TCP traceroute"
From NetSec
WillieArce (Talk | contribs) m |
|||
| Line 27: | Line 27: | ||
Same as above, only for [[Linux]]. | Same as above, only for [[Linux]]. | ||
| − | + | {{cleanup}}{{wrongPerson}}{{expand}}{{countermeasures}} | |
| − | + | ||
Revision as of 03:32, 16 May 2012
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
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
Same as above, only for Linux.
| This article contains too little information, it should be expanded or updated. |
|---|
Things you can do to help:
|
TCP traceroute is part of a series on countermeasures.
