Wireshark-dev: [Wireshark-dev] Stop Button Doesn't Work with our setup & Question about the tim
From: "Varuna De Silva" <[email protected]>
Date: Sat, 20 Oct 2007 11:58:57 +0530
Hello,

We developed Signaling capturing platform from TDM lines.
Now when we do our live capture, it works properly.That is it
reads the packets correctly. But we have some issue with the
stopping a live capture.

While we do a live capture when we try to press the Stop Button
it does not work, that is the capture dont stop. it goes on until either the
C Drive fills up or until we stop the process of wireshark.exe

But when we set in the options to stop the capture in say 10s or so,
it stops it at that time. Below is our muwis_platform_close() function

static void muwis_platform_close(pcap_t *p) {
    FT_Close(p-> md.ftHandle);
   
}

Here we release the ftHandle which is the handle to our device, from which we
read.

We also have another pertinent question to our case. This is the timestamp question.
Now we read in two TDM lines i.e. TX and RX, the messages on these two lines are
being Timestamped by the Hardware. But with our read function these packets may be
read in at different times. But on the pcap_header we give the time generated by the
HW.

But while doing so some thing like the following might take place. That is a packet
captured at time 0 from the TX line might be read in and be callback() after a packet
captured at time 1 from the RX line. But the original time stamp will be given when it
is callback().

Now my question is that, will those packets be shown in the GUI according to the
timestamp provided to it or according to the sequence of  reading them and doing
the callback().

If it uses the timestamp for this purpose of, displaying packets our problem is solved.
In which case Wireshark has an internal Buffer? ( Please Correct me )

Ultimately what we want is to show the correct flow diagram from the

Statistics -> Flow Graph... in wireshark.

Because if not the flow graph provides less useful information for us.
for example IAM message displayed after ACM, in a typical ISUP call setup.

Kindly help out these two problems of us. As possibly soon as any one can.
We are running to our project demos on Monday. Thank you again for the
wonderful support you all have rendered to us till now.

Thanks in advance

Varuna De Silva