Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 9820] graphs for Delay and packet losses

Date: Thu, 06 Mar 2014 05:09:10 +0000

Comment # 11 on bug 9820 from
Actually i done all things on VMware machines...... and that traffic has been
captured. as of my knowledge, there are time stamps for every packet. for the
sake of simplicity, take it as RTT, time to send a packet and receiving its
response. i want to check the delay of each packet in graphical for plus i also
wana check whether there is some throughput or not (packet losses to be more
specific)(In reply to comment #10)
> (In reply to comment #7)
> > i have a file that is a real time call, definitely it contains the
> > information of sending time and receiving time of a packet. i am calling the
> > time that a packet took from caller to callee as "network delay". and its
> > kind of general thing, not for a specific group of packets (like SIP, RTP
> > etc)
> > my idea is to find the over all time that a packet take from caller to
> > callee. the intermediate hopes (UAS caller side, UAS callee side etc) are
> > kind or irrelevant.
> > i am interested in the time that a packet takes from UAC(caller) to the
> > other UAC(callee), they could be registered on same UAS or different.
> > 
> > hope my statement is clear now
> 
> Nope. :)
> 
> How does a capture file contain the time a packet was sent by the sender and
> the time it was received by the far end?
> 
> I mean a capture file contains packets seen at a specific location/spot. 
> The timestamp is just whenever that location/spot saw the packet.
> 
> Did you merge two capture files, one from the caller, and one from the
> callee?  For example did you use remote capture devices at each end, or run
> wireshark on both ends, and merge their files?


You are receiving this mail because:
  • You are watching all bug changes.