[96379] in North American Network Operators' Group
Re: barak-online.net icmp performance vs. traceroute/tcptraceroute, ssh, ipsec
daemon@ATHENA.MIT.EDU (Joe Shen)
Mon May 7 03:18:32 2007
Date: Mon, 7 May 2007 15:16:41 +0800 (CST)
From: Joe Shen <joe_hznm@yahoo.com.sg>
To: Joe Maimon <jmaimon@ttec.com>
Cc: NANGO <nanog@merit.edu>
In-Reply-To: <463E7268.7080104@ttec.com>
Errors-To: owner-nanog@merit.edu
I agree with Dale. The problem should be with e2e TCP
performance.
Maybe there is misconfigured firewall which block SYN
or ACK packet. Or, packet larger than 128B is dropped.
As you can find in your data, ping and traceroute show
different response speed.
Maybe you could try layer4 traceroute, and try packet
size bigger than 1000Byte. It will show you where the
problem may exist.
Joe
ICMP or traceroute usually use small packet.
--- Joe Maimon <jmaimon@ttec.com> wrote:
>
>
>
> Lincoln Dale wrote:
>
> >>traceroute/tcptraceroute show packet loss and MUCH
> higher rtt than the
> >>corresponding direct pings on the reported hop
> entries.
> >>
> >>Is this some sort of massaging or plain just
> "faking it"? Or is such
> >>things merely net-urban myth?
> >
> >
> > the vast majority of routers on the internet
> respond very differently to
> > traffic 'directed at them' as opposed to traffic
> 'routed through them'.
>
> Thanks for your reply.
>
> I did include icmp echo directly to each hop as a
> comparison.
>
>
>
____________________________________________________
Yahoo! Singapore Answers
Real people. Real questions. Real answers. Share what you know at http://answers.yahoo.com.sg
