I would just want the ability to log the packets to a file that the
ethereal GUI could read after the fact. I'd also want the ability that
the GUI has where you can log X amount of Megabytes and have it start a
new file. Also the ability to pass a filter to it like the GUI accepts
would be nice. I would not use the command line for the dissection of
the packets though. I would still use the GUI to do all that after the
file had been created.
The configuration of the service could be done via a config file. If I
needed to change the parameters of the service I would have to restart
it to get the changes to take affect. That's the way most
daemons/services work right :)
-----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.
_______________________________________________
Ethereal-users mailing list
Ethereal-users@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-users
