On Apr 18, 2021, at 10:18 PM, Eugène Adell wrote:
> probably the guy writing this considered the "Epochalypse" problem.
Or wanted *some* test to help rule out files that are probably not ConnView NCF
files (there is no file header, so there's no file magic number, and there's no
packet magic
Hello,
probably the guy writing this considered the "Epochalypse" problem.
See https://en.wikipedia.org/wiki/Year_2038_problem if necessary.
best regards
E.A.
Le lun. 19 avr. 2021 à 04:18, Richard Sharpe
a écrit :
>
> Hi folks,
>
> I just came across this validation check in the commview
On Apr 18, 2021, at 2:33 PM, Richard Sharpe wrote:
> I am thinking of writing a wtap module to read ComView WLAN Analyzer
> and Decoder NCFS format files.
>
> They are a little like PCAP files with a radiotap header,
...and a bit more like CommView NCF files, which we already support.
> One
CORRECTION: I omitted the troublesome steps (underlined) when describing
the problem:
git clone https:// wireshark
cd wireshark
git checkout wireshark-3.4.4
cd wireshark/epan/dissectors
*cp ~/myfoo.tgz . #copy dissector code into wireshark clone*
*tar xvf myfoo.tgz #extract the dissector code
Hi folks,
I just came across this validation check in the commview wiretap code:
if (... cv_hdr.year < 1970 || cv_hdr.year >= 2038 || ...)
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:
Hello Wireshark-dev community,
Apparently, I still don't have the correct sequence of steps necessary for
first time generation of "packet-myfoo.c" and "packet-myfoo.h" for a new
ASN.1-based dissector called myfoo. Details follow.
I would like to understand (much better than I do) how to add an
Hi folks,
I am thinking of writing a wtap module to read ComView WLAN Analyzer
and Decoder NCFS format files.
They are a little like PCAP files with a radiotap header, but their
format is quite different from the radiotap format. It contains much
of the same info but it is in a different format.
