Re: Filtering on (negated) frame.time_relative filters out wrong frame.number

[Miroslav Rovis <miro.rovis () croatiafidelis hr>]

On 170317-11:29+0000, Graham Bloice wrote:
> On 17 March 2017 at 11:23, Peter Wu <peter () lekensteyn nl> wrote:
> > Can you try to prepare a smaller capture that can reproduce the
> > issue which does not contain sensitive passwords?

Posted:

The Test Sample for the (Imaginary or Not) Bug
http://www.croatiafidelis.hr/foss/cap/cap-170313-git-devuan-mail/git-devuan-mail-2.php

And I haven't done the testing yet. This is all preparation for what I
tested (and named the thread title by) at:

Filtering on (negated) frame.time_relative
https://www.wireshark.org/lists/wireshark-users/201703/msg00030.html

Now that needs to be done on this complete capture. Just this time,
since the original PCAP is posted
(
well, I just do the minimal anonymization of only some strings in the
PCAP:
https://github.com/miroR/uncenz/blob/master/dump_perl_repl.sh
)
I'd keep the original's PCAP name intact.

I tried to post this before the weekend it full blown (not because of
me)... but it is a lot of work...
-- 
Miroslav Rovis
Zagreb, Croatia
https://www.CroatiaFidelis.hr

Attachment: signature.asc
Description: Digital signature

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request () wireshark org?subject=unsubscribe