Ethereal-dev: Re: [Ethereal-dev] mergecap: How to merge Ethernet & Linux cookedcapture files?
Well supporting a (rw) file type that allows for several different
encapsulations to coexists in the same capture file would be great.
But, is the pcap-NG spec already usable?
ie. are we already at the point where future changes in the format
won't broke backwards compatibility?
On 2/22/06, Maynard, Chris <Christopher.Maynard@xxxxxxxxx> wrote:
> I suppose it depends on the amount of interest. If I am the only one
> who will benefit, then I'll probably just convert the cooked capture to
> Ethernet as Guy suggests below, since this is likely to be much easier
> to do, but if this is something that many others could benefit from as
> well, then I will look into the pcap-NG option. Is my problem a rather
> unique or are there other folks who would desire this functionality as
> well?
>
> -----Original Message-----
> From: ethereal-dev-bounces@xxxxxxxxxxxx
> [mailto:ethereal-dev-bounces@xxxxxxxxxxxx] On Behalf Of Guy Harris
> Sent: Wednesday, February 22, 2006 1:46 PM
> To: Ethereal development
> Subject: Re: [Ethereal-dev] mergecap: How to merge Ethernet & Linux
> cookedcapture files?
>
> Guy Harris wrote:
> > Maynard, Chris wrote:
>
> ...
>
> >> If not, then what
> >> would it take to be able to support this type of merge?
> >
> > Add support for pcap-NG format:
>
> ....or write a tool that converts Linux cooked capture headers to
> Ethernet headers (adding fake source or destination addresses), and run
> that tool on the Linux cooked capture, and then merge the two Ethernet
> capture files.
>
>
>
> -----------------------------------------
> This email may contain confidential and privileged material for the
> sole use of the intended recipient(s). Any review, use, retention,
> distribution or disclosure by others is strictly prohibited. If you
> are not the intended recipient (or authorized to receive for the
> recipient), please contact the sender by reply email and delete all
> copies of this message. Also, email is susceptible to data
> corruption, interception, tampering, unauthorized amendment and
> viruses. We only send and receive emails on the basis that we are
> not liable for any such corruption, interception, tampering,
> amendment or viruses or any consequence thereof.
>
>
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
>
--
This information is top security. When you have read it, destroy yourself.
-- Marshall McLuhan
