North American Network Operators Group
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: UDP Badness [Was: Re: How to measure network quality&performance for voip&gameservers (udp packetloss, delay, jitter,...)]

  • From: tony sarendal
  • Date: Tue Mar 07 18:35:34 2006
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Fb3uG51+t3b9PEgUjOLu26QjQdEjjMsM1Xe00QmtbOS/ODzsnmHefWJduH8ZKyi420SaEprzaNlyYDnQC5b44p9iTN0vDYMKxXQU+tS6Ysp1EU0fwh0LJ2wKDt6PZddM6c+uXQOJB9QU5yVq+py6zrr7pV7p6uWKUXB//EpR/ZU=


On 07/03/06, Gunther Stammwitz <gstammw@gmx.net> wrote:

Well that's true but Iperf won't show you at which time a loss occured. It
will simply print out the results when the test has been finished. I need
something well more accurate that can also tell me which hop is causing the
problems.

Last I checked I got the time from Iperf, even if it was indirectly.
A tool that shows which hop in the network that has problems forwarding
certain traffic ? Awesome, I want one of those.

--
Tony Sarendal - tony@polarcap.org
IP/Unix
       -= The scorpion replied,
               "I couldn't help it, it's my nature" =-