Ethereal-dev: Re: [Ethereal-dev] Capturing from multiple interfaces, and why we need this.

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: Guy Harris <guy@xxxxxxxxxxxx>
Date: Sun, 1 Feb 2004 12:16:20 -0800
On Sun, Feb 01, 2004 at 12:19:39PM +0100, Olivier Biot wrote:
> Additionally, we could add support for remote capturing and for
> network taps via an API similar to the libpcap or wiretap API.

How about adding them to an API identical to the WinPcap 3.01 API?

	http://winpcap.polito.it/301a/docs/group__remote.html

If that's done in libpcap/WinPcap, it's available to more programs than
just Ethereal.

> As a result, Ethereal would indeed only know about display filters (which I
> *really* want to be renamed to *dissection filters* as I think that's
> a more intuitive name for those), and the interaction with packet
> capturing would be hidden by the file descriptor.

What do you mean "know about"?

Presumably if a user's capturing with Ethereal, they'd supply a capture
filter expression to Ethereal.