Ethereal-users: R: [Ethereal-users] Re: R: [Ethereal-dev] Remote online packet capture?

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

From: "Loris Degioanni" <loris@xxxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 25 Oct 2000 11:43:19 +0200
Perhaps other solutions are better than this one.
What about "\\machine\inerfacename"?

Loris.

-----Messaggio Originale----- 
Da: Guy Harris <guy@xxxxxxxxxx>
A: Loris Degioanni <loris@xxxxxxxxxxxxxxxxxxxxxxx>
Cc: Mark Atwood <mra@xxxxxxxxx>; <ethereal-dev@xxxxxxxxxxxx>; <ethereal-users@xxxxxxxxxxxx>
Data invio: martedì 24 ottobre 2000 1.10
Oggetto: [Ethereal-users] Re: R: [Ethereal-dev] Remote online packet capture?


> > This allows to the applications written over winpcap/libpcap to
> > transparently capture from a remote host if linked with this remote
> > version: they need only to specify the name of the adapter with a proper
> > syntax (for example "machinename:adaptername") in pcap_open_live, and
> > the capture is routed to the remote agent.
> 
> The Ethereal code to get a list of interfaces skips addresses that begin
> with "dummy", or that included a ":", saying that the latter are
> "Solaris virtuals"; I infer from
> 
> http://bugs.apache.org/index.cgi/full/1540
> 
> that the syntax of a Solaris virtual interface is "<interface name>:<number>".
> 
> This means that a "machinename:adaptername" syntax *might* be
> indistinguishable from a virtual interface name, although I don't know
> whether Ethereal omits the virtual interfaces because you can't capture
> on them, because you wouldn't want to capture on them, or for some other
> reason, so I don't know whether simply treating all device names with
> colons as remote interface names would work.
> 
> _______________________________________________
> Ethereal-users mailing list
> Ethereal-users@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-users
>