|
|
| (One intermediate revision by one other user not shown) |
| Line 1: |
Line 1: |
| − | = Overview =
| + | #REDIRECT [[traceroute#TCP_Traceroute]] |
| − | | + | |
| − | == vs. UDP/ICMP ==
| + | |
| − | | + | |
| − | The problem with [[Traceroute|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 ===
| + | |
| − | | + | |
| − | [http://winmtr.sourceforge.net/ 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 [[http://www.gentoo.org/ gentoo]]) allow you to run the [[traceroute]] command from the command line as follows:
| + | |
| − | | + | |
| − | traceroute -T -p 80 domain.tld
| + | |
| − | | + | |
| − | | + | |
| − | [http://www.bitwizard.nl/mtr/ mtr]
| + | |
| − | | + | |
| − | Same as above, only for [[Linux]].
| + | |
| − | {{wrongPerson}}{{expand}}{{merge|traceroute}}{{countermeasures}}
| + | |
