tcp equivalent to mtr, as tcptraceroute is to traceroute

Is there a simple command line tool that adds tcp-based functionality
to a system like mtr?

I love mtr, it's incredibly useful to me in my work, but it would be
even better if it could perform tcp-packet diagnosis instead of relying
on icmp (which can be filtered, deprioritized, etc.)

Hi,

may be you are looking for tcptraceroute?
Here is the more info on this

http://freshmeat.net/projects/tcptraceroute/

Thanks,
Sunil


maethlin wrote:
> Is there a simple command line tool that adds tcp-based functionality
> to a system like mtr?
>
> I love mtr, it's incredibly useful to me in my work, but it would be
> even better if it could perform tcp-packet diagnosis instead of relying
> on icmp (which can be filtered, deprioritized, etc.)

Sunil - I was looking for an mtr-equivalent of tcptraceroute.
Tcptraceroute is great, but it can not record results/statistics over
time like mtr can.

(E-Mail Removed) wrote:
> Hi,
>
> may be you are looking for tcptraceroute?
> Here is the more info on this
>
> http://freshmeat.net/projects/tcptraceroute/
>
> Thanks,
> Sunil
>
>
> maethlin wrote:
> > Is there a simple command line tool that adds tcp-based functionality
> > to a system like mtr?
> >
> > I love mtr, it's incredibly useful to me in my work, but it would be
> > even better if it could perform tcp-packet diagnosis instead of relying
> > on icmp (which can be filtered, deprioritized, etc.)

On 13 Sep 2006, in the Usenet newsgroup comp.os.linux.networking, in article
<(E-Mail Removed). com>, maethlin wrote:

>Is there a simple command line tool that adds tcp-based functionality
>to a system like mtr?

A google search (you tried that, right?) doesn't turn up anything
obvious. In the first five result for "mtr tcp" at google, I found
http://www.cs.columbia.edu/~hgs/internet/tools.html which may help.

>I love mtr, it's incredibly useful to me in my work, but it would be
>even better if it could perform tcp-packet diagnosis instead of relying
>on icmp (which can be filtered, deprioritized, etc.)

Probably your closest bet is going to be pchar (a massive rewrite of Van
Jacobson's pathchar utility). Problems are, 1) it's no longer under
active development (v1.5 was released in February 2005), and 2) it
only does UDP.

_A_ problem about using TCP is that it's a connection oriented service.
It expects a 3-way hand-shake, and let's get on with the data transfers.
But that assumes a server of some kind on the remote. Likewise, sending
a number of half-opens is likely to get the attention of the firewall
administrator as a DoS attack. Maybe not the best idea in the world.

What exactly are you trying to accomplish? In your top-posted reply to
Sunil (please learn to NOT top-post - some people killfile those who do),
you indicate recording results/statistics over time is desired. Why not
run tcptraceroute from a stupid script with appropriate redirects?

Old guy