Wireshark-users: Re: [Wireshark-users] Large numbers of lost packets, duplicate ACKs, and retrans
From: "Ian S. Worthington" <[email protected]>
Date: Tue, 27 Feb 2007 10:41:19 -0000
Thanks for your reply Muhammad.  I hadn't come across pathping, which is what
I think you mean?, before.  But it doesn't seem to get beyond the first hop
here.  Am I driving it wrong?


>pathping 190.24.114.111

Tracing route to adsl190-024114.dyn.etb.net.co [190.24.114.111]
over a maximum of 30 hops:
  0  700m [192.168.1.20]
  1     *        *        *
Computing statistics for 25 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           700m [192.168.1.20]
                              100/ 100 =100%   |
  1  ---     100/ 100 =100%     0/ 100 =  0%  700m [0.0.0.0]

Trace complete.


------ Original Message ------
Received: Tue, 27 Feb 2007 09:36:32 AM GMT
From: "Muhammad Ghazali" <[email protected]>
To: "Community support list for Wireshark" <[email protected]>
Subject: Re: [Wireshark-users] Large numbers of lost packets, duplicate ACKs,
and retransmissions?

> Duplicate acks and retransmission are the impact of the large number
> of lost packets. Lost packets could be caused by a bad link. Try to
> pingpath to the other end to see what's happening between you and your
> parents-in-law (hope you don't have any problem with them at least :)
> ).
> 
> On 2/26/07, Ian S. Worthington <[email protected]> wrote:
> > Hi --
> >
> > I'm very new at this, so please forgive me if this seems naive r is in
the
> > wrong place.
> >
> > I'm having problems connecting from the UK to a PAP2 box at my
parents-in-law
> > house in South America.
> >
> > A wireshark trace shows what seems to my eyes to be a large number of
lost
> > packets, duplicate ACKs, and retransmissions.
> >
> > I've put the trace up at http://isw.me.uk/content/view/18/28/ along with
some
> > capture of status reports from the modem.
> >
> > I'm trying to identify if there's a problem at their end (line quality?
bad
> > modem? bad configuration?), at my end, or somewhere in between (ISP
> > blocking).
> >
> > Is there anyone here who understands these things, or who can point me to
a
> > better resource?
> >
> > Thanks,
> >
> > ian
> > ...
> >
> >
> > Ian S Worthington
> > ...
> > Dulce et decorum est pro patria mori, sed dulcius pro patria vivere, et
> > dulcissimus pro patria biber. Ergo, bibiamo pro salute patriae.
> _______________________________________________
> Wireshark-users mailing list
> [email protected]
> http://www.wireshark.org/mailman/listinfo/wireshark-users



Ian S Worthington
...
Dulce et decorum est pro patria mori, sed dulcius pro patria vivere, et
dulcissimus pro patria biber. Ergo, bibiamo pro salute patriae.