[Coral-dev] binary output format for crl_flow

[Chris Rapier]

Right, well, nevermind then. I'll try to suss it out on my own.

Ken Keys wrote:
> The preferred way to read them is with the Perl Traffic2 and Tables APIs,
> which are documented in the online docs that came with coral and at
> http://www.caida.org/tools/measurement/coralreef/doc/doc/index.html.
> Ryan will correct me if I'm wrong:  I think the binary file format is
> the same in 3.4.7 and 3.5, but 3.5 contains some improvements to the Perl
> APIs, as well as making the fast C++ backend for the Perl APIs available
> to everyone (not just caida members).
> 
> On Tue, Jun 17, 2003 at 03:52:37PM -0400, Chris Rapier wrote:
> 
>>Any chace you could be more explicit than that? I did lookin the source code 
>>and came up with a 54 byte structure but I'm starting to think that isn't 
>>quite correct. Like what is the 'length' field for? or the full_save? Do the 
>>binary files have any sort of preceeding header data? etc etc etc...
>>
>>
>>David Moore wrote:
>>
>>>On Tue, Jun 17, 2003 at 03:15:16PM -0400, Chris Rapier wrote:
>>>
>>>
>>>>Is there any documenation on the format of the binary output of crl_flow? 
>>>>This is for verions 3.4.7 if that makes a difference.
>>>
>>>
>>>No explicit documentation for it, but the header parts are all the
>>>same as the text format, only the table dump is in binary.  If you
>>>look at the source code for crl_flow at dump_binary_flow_table, it
>>>should be relatively clear what the size and format of each field is.
>>>Note everything is written in network byte order.
>>>
>>>-- david
>>>_______________________________________________
>>>Coral-dev mailing list
>>>Coral-dev at caida.org
>>>http://login.caida.org/mailman/listinfo/coral-dev
>>
>>
>>_______________________________________________
>>Coral-dev mailing list
>>Coral-dev at caida.org
>>http://login.caida.org/mailman/listinfo/coral-dev
> 
>