iptrace?

[NoOp]

On 06/04/2008 02:47 AM, Dotan Cohen wrote:
> 2008/6/4 Cybe R. Wizard <cybe_r_wizard at earthlink.net>:
>> A short look at your screenshots reveals that your major packet losses
>> are attributable to bzeqint.net in several of their host addresses. I'd
>> think your problem might lie there.
>>
> 
> The ISP is Bezeq International. They say that such a response is
> normal due to packet priority. Makes sense.

That makes no sense at all. Those high packet losses on hops 3, 4, and 5
show that their network was screwed up at the time. I can (currently)
traceroute to 62.219.189.9 from California with 5% packet loss and the
packet loss was from my side (I am currently having DSL problems locally).

~$ mtr -r -c 20 62.219.189.9
HOST: [snip]                       Loss%   Snt   Last   Avg  Best  Wrst
StDev
  1. bras13-l0.pltnca.sbcglobal.n  0.0%    20   16.1  15.6  14.5  17.5   0.8
  2. 64.164.107.1                  5.0%    20   13.7  15.7  13.6  45.6   7.3
  3. bb1-g3-0.pltnca.sbcglobal.ne  0.0%    20   14.3  18.0  13.4  91.8  17.4
  4. ex2-p10-0.pxpaca.sbcglobal.n  0.0%    20   15.9  22.2  14.6 143.0  28.5
  5. asn6762-telecom-italia.pxpac  0.0%    20   15.5  18.6  14.5  77.7  13.9
  6. customer-side-bi-3-pal5.pal.  0.0%    20  230.5 230.6 230.0 231.7   0.5
  7. bzq-219-189-9.cablep.bezeqin  5.0%    20  230.8 231.4 230.8 232.4   0.4

As for the "tech" that asked you to do an iptrace, don't worry about it,
your mtr should have been more than sufficient for them to realize that
*they* had a problem with *their* network.

BTW: Next time you use mtr, use the -r & -c <count> commands as shown
above and that will give you a printout that you can then copy & paste.
-r is for report and -c is for count. So in the above I set it to send
20 packets and at the end 'print' the report to the terminal.