Re: Would using iptables limit my number of possible hops?

On Aug 30, 8:11 pm, buck <b...@xxxxxxxxxxx> wrote:
There is a way to limit the number of hops with iptables, but it is
doubtful that it is implemented. If you have doubts, turn off the
firewall during your trace. And use tcptracert -n DEST PORT rather
than tracepath / traceroute.

http://michael.toren.net/code/tcptraceroute/

Hi Buck; thanks for your reply.

Oooh, I hadn't heard of tcptracert before. Nice new tools! Thanks for
the link (for the innocent bystanders in this thread, it's in Ubuntu,
and therefore presumably Debian: sudo apt-get install tcptraceroute).

However, the good news ends there:

$ tcptraceroute -n 213.171.216.230 80
Selected device eth0, address 192.168.11.10, port 45415 for outgoing
packets
Tracing the path to 213.171.216.230 on TCP port 80 (www), 30 hops max
[...]
4 62.12.70.157 37.928 ms 99.411 ms 37.867 ms
5 194.42.135.46 48.708 ms 58.069 ms 38.322 ms
6 217.27.49.90 41.557 ms 54.884 ms 58.748 ms
7 194.42.133.139 63.019 ms 62.079 ms 58.319 ms
8 194.42.143.27 62.238 ms 62.076 ms 58.077 ms
9 217.27.35.113 59.418 ms 64.806 ms 62.257 ms
10 217.27.47.26 139.315 ms 118.668 ms 123.422 ms
11 * 213.248.104.81 119.929 ms 137.001 ms
12 80.91.250.209 118.331 ms 120.699 ms 116.717 ms
13 213.248.64.93 125.581 ms 119.391 ms 135.511 ms
14 80.91.254.22 121.862 ms 122.924 ms 130.701 ms
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *

The odd thing is that everything else seems to be working just fine.
It's just so odd and inexplicable.

Cheers,

Dom

.

Quantcast