ISP question [ was traceroute , pls ]

[Collins Richey]

On Sat, Oct 18, 2008 at 11:21 AM, Michael Hipp <Michael at hipp.com> wrote:
> Collins Richey wrote:
>>
>> On Sat, Oct 18, 2008 at 7:33 AM, David A. Bandel <david.bandel at gmail.com>
>> wrote:
>>
>>> Then change the port.  I can't believe they'd be blocking all udp
>>> ports.  And if they are, you have the ability to traceroute via tcp
>>> (and I'm sure they're not blocking port 80).
>>>
>>> man traceroute
>>
>> Wow, that one's a keeper. A udp traceroute dies out after about 19
>> hops, but a -T traceroute (root only) gets to the destination. Take
>> that, Comcast.
>
> Okay, I'm feeling kinda dumb (not an unusual condition).
>
> My 'man traceroute' says nothing about using tcp and there's no -T option.
> Does my Ubuntu box have the Microsoft version or something?
>
> Could someone tutor me?
>
> NEVERMIND: Turns out you have to have 'tcptraceroute'. And 'man traceroute'
> won't help a bit learning that. What man doesn't know, google does. But it
> still doesn't have a -T option.
>

Hmm, my system is debian sid with traceroute-2.0.12-1, and here's the
extract from 'man traceroute'.

  tcp        -T
       Well-known modern method, intended to bypass firewalls.
       Uses the constant destination port (default is 80, http).

tcptraceroute is just a link (via alternatives) to traceroute, and
'man tcptraceroute' just points to the manpage for traceroute.

Don't know what the *buntu folks have done with this. I haven't been
there in over a year.

-- 
Collins Richey
     If you fill your heart with regrets of yesterday and the worries
     of tomorrow, you have no today to be thankful for.