On Tue, May 05, 2020 at 10:42:24AM +0200, Jasper Bongertz wrote:
> > On a related note, to address one of the use cases that prompted for the
> > new field, I added expert info to mark connections where the server
> > accepted TCP Fast Open (TFO) data. Is that useful to have?
>
> Yes, that's usef
Hello Peter,
Tuesday, May 5, 2020, 1:46:13 AM, you wrote:
>> To avoid cluttering the TCP tree with redundant fields: can we only show the
>> absolutes if the relatives are also displayed? I don't think it's useful to
>> show the absolutes twice.
> Sure! The fields will be hidden in the view, but
Hi Jasper,
On Tue, May 05, 2020 at 01:24:33AM +0200, Jasper Bongertz wrote:
> Hello Peter,
>
> > A request was filed earlier to add a new "tcp.ack_rel" field to ensure
> > that color filters can be created that always work on the relative
> > sequence numbers independent of the "Relative sequence
Hello Peter,
> A request was filed earlier to add a new "tcp.ack_rel" field to ensure
> that color filters can be created that always work on the relative
> sequence numbers independent of the "Relative sequence numbers" option.
> Instead of adding a new field, I propose to change the existing one
Hi all,
A request was filed earlier to add a new "tcp.ack_rel" field to ensure
that color filters can be created that always work on the relative
sequence numbers independent of the "Relative sequence numbers" option.
Instead of adding a new field, I propose to change the existing ones.
My propos
