Ethereal-users: RE: [Ethereal-users] Run Ethereal as a Windows Service

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

From: Jack Jackson <jack@xxxxxxxxxxxxxxx>
Date: Mon, 08 Aug 2005 09:52:10 -0700
There are various products available to do this. I haven't tried any of them, but here are some from download.com. None are free, but there might be free ones available too.

Application As Service: http://www.download.com/3000-2094-10338475.html

AppToService: http://www.download.com/AppToService/3000-2084_4-10229238.html?tag=lst-5-5


At 09:27 AM 8/8/2005, Chris Alton wrote:
I might attempt to just write a C# wrapper for tethereal and see how
that'll work.

-----Original Message-----
From: ethereal-users-bounces@xxxxxxxxxxxx
[mailto:ethereal-users-bounces@xxxxxxxxxxxx] On Behalf Of Guy Harris
Sent: Sunday, August 07, 2005 7:12 PM
To: Ethereal user support
Subject: Re: [Ethereal-users] Run Ethereal as a Windows Service

Chris Alton wrote:

> Having it run with no user logged on is exactly what I need. I have a
> server machine that I want to start sniffing packets as soon as the
> computer starts up. I want the exact functionality that tethereal has
> except I want it with a non-visual interface. i.e. no command window
> displayed.

Perhaps more correctly stated as "with no user interface at all, i.e. no
window displayed at all".

Do you really want the *exact* functionality that Tethereal has - that
functionality includes the full ability to dissect packets, and all the
taps to generate statistics - or do you just want something that
captures and writes to a libpcap-format file?

> I want to be able to pass the filters and other parameters to it and
> have it start logging when the computer starts.

What mechanism would you use to pass those parameters to it?  Presumably
this would be done by running some application that would set the
filters and other parameters, and either

        1) it would stop doing whatever capturing it was doing at the
time, and start with the new parameters - and would again use those
parameters after a reboot

or

        2) it would continue doing the capture it's doing at the time,
with the parameters it was already using, but would use the new
parameters after a reboot.