LEGO wrote:
I need ideas on how to handle the .stk files (ethereal won't use
them, I hate the very same Idea behind these files). These as you
might know describe the protocol stack used by each source.
I haven't been able to infer if or how the encapsulation used for each
source is written to the file.
I.e., you don't know the format of the .stk files yet?
I temporarily worked arround this issue by using the USER0-15
encapsulations, these are handled by the DLT_USER00-15 "dissectors" I
checked in yesterday, in whose preferences one can set which
protocol(s) is(are) carried by each encapsulation.
By now each .stk file used by the file is mapped to an USER encap
starting from USER0 in the order they appear in the file.
So is there more than one .stk file per .rf5 file?
And are the .stk files written by users, by the K12xx, or by Tektronix
(with a fixed set of .stk files)?
The current implementation handle timestamps using 64bit integers. I
want to do it without 64 bit arithmetic as not every plattform
supports it.
Ethereal - including Wiretap - now require support for int64 and uint64,
so you can just use those. *Printing* them requires some work, but look
for PRIu64 in packet-rsvp.c for an example of how to handle that.