Tracing a UDP Route

If you are experiencing connectivity problems and suspect a firewall issue, mtping can trace the route that packets are following to isolate where your data is being blocked.

By adding the -t option, mtping will behave much like the unix traceroute utility, except that mtping sends actual MTP datagrams.  Firewalls which are blocking MTP traffic on the selected port can be identified by the point where the trace stops receiving responses.

Below is an example trace which suggests a router near mtping may be blocking MTP on port 8080:

host-3: mtping -t florida.mtpip.net:8080 ACT_PING florida.mtpip.net (69.60.121.178:8080) 1 65.69.251.126 11ms "TTL Exceeded" 2 151.164.23.131 7ms "TTL Exceeded" 3 * 6000ms "No Response" 4 * 6000ms "No Response" ^C

Next is an example trace showing that no MTP application is running on port 8081 of the given machine:

host-4: mtping -t california.mtpip.net:8081 ACT_PING california.mtpip.net (66.28.209.5:8081) 1 65.69.251.126 9ms "TTL Exceeded" 2 151.164.23.130 8ms "TTL Exceeded" 3 151.164.23.241 9ms "TTL Exceeded" 4 151.164.240.102 13ms "TTL Exceeded" 5 151.164.191.118 177ms "TTL Exceeded" 6 151.164.40.29 154ms "TTL Exceeded" 7 151.164.242.42 14ms "TTL Exceeded" 8 154.54.12.69 16ms "TTL Exceeded" 9 154.54.2.137 13ms "TTL Exceeded" 10 66.28.4.38 23ms "TTL Exceeded" 11 66.28.4.209 80ms "TTL Exceeded" 12 66.28.4.69 54ms "TTL Exceeded" 13 66.28.4.94 102ms "TTL Exceeded" 14 38.112.39.122 55ms "TTL Exceeded" 15 38.112.22.222 88ms "TTL Exceeded" 16 66.28.209.5 79ms "Unreachable: No Application on that Port" 17 66.28.209.5 62ms "Unreachable: No Application on that Port" ^C

Not all systems will send or receive the "Unreachable" message.  Therefore it may not be clear from mtping's output whether a firewall is blocking access near the server or no server is running.