Hi,
If you look in the Folders tab
> in the Help->About Wireshark UI it'll show you where it is looking.
>
> If all else fails, you can always 'truss' (or the FreeBSD equivalent)
> Wireshark to see where it is looking for the plugins.
>
Thank you very much. Using truss and the info dialog, I foun
why is the ack number of several ack frame in tcp transmission the same?Is that
the ack of several tcp segments?if so,how to calculate the bytes of data that
been received every time?___
Sent via:Wireshark-dev mailing lis
On 4/6/14 4:47 PM, Matthew Parlane wrote:
> remote: Counting objects: 366552, done
> remote: Finding sources: 93% (340894/366552)
>
> The remote count process seems quite slow. In case you guys are not
> aware, you should run gc on gerrit every now and again to resolve the
> remote count slowd
Yep, instant now :) Thanks.
Matthew Parlane
On 8 April 2014 03:46, Gerald Combs wrote:
> On 4/6/14 4:47 PM, Matthew Parlane wrote:
> > remote: Counting objects: 366552, done
> > remote: Finding sources: 93% (340894/366552)
> >
> > The remote count process seems quite slow. In case you guys ar
On Monday, April 7, 2014, 2:33:08 PM, "ÎÒÏë²»ÎÞÁÄ" wrote:
> why is the ack number of several ack frame in tcp transmission the same?Is
> that the ack of several tcp segments?if so,how to calculate the bytes of data
> that been received every time?
Two possible reasons:
1) The data segments got
