On Feb 11, 2004, at 12:45 AM, Pablo wrote:
I have tested it before but i have two problems:
it is true that ethereal reads a number of file formats,
including the file formats of AiroPeek but i can't save it
as libpcap format (when i click in save as i only can save
as AiroPeek trace (V9 file format).
I have also tested using editcap but an error message
appear: i put in the command line this:
C:\>editcap inputfile.apc outputfile.dmp
editcap: Can't open or create outputfile.dmp: Files from
that network type can't be saved in that format
The same message appear if i put:
C:\>editcap -F libpcap inputfile.apc outputfile.dmp
That's one problem, not two - the underlying problem is that we don't
support writing out that particular style of 802.11+radio information
in a libpcap capture.
I've checked in a change to do that, for now, by discarding the radio
information. At some point we'll choose one of the many different
802.11+radio header formats in libpcap and use that. (My favorite is
the BSD radiotap format, but I need to get that working in tcpdump
first - patches exist, but they depend on 64-bit integer support,
including printing 64-bit integers, and "%ll[dox]" does *NOT* work on
all platforms supported by tcpdump, *OR* all platforms supported by
Ethereal, for that matter - and should get libpcap able to handle at
least that flavor of variable-length link-layer header, which I think
might be a bit easier than Token Ring or full support for 4-MAC-address
802.11 as it doesn't involve conditional branches.)