To use it as a distributed sniffer with the addition Perl module
Net::Pcap::Utils and distro NetPacket a sniffer client could be made in less
than 50 lines. As for the Perl2Exe part, the exe made would still need
WinPcap.
Jay Flowers
Integic Health Care
-----Original Message-----
From: Jeff Foster [mailto:jfoste@xxxxxxxxxxxx]
Sent: Friday, January 11, 2002 12:31 PM
To: 'Flowers, Jay'; 'ethereal-users@xxxxxxxxxxxx'
Cc: 'ethereal-dev@xxxxxxxxxxxx'
Subject: RE: [Ethereal-users] Port of Net::Pcap complete!!!
From: Flowers, Jay [mailto:Jay_Flowers@xxxxxxxxxx]
Sent: Friday, January 11, 2002 6:34 AM
> Second:
>
> We are porting Net::Pcap to widows to make a distributed NIDS that will
work
> on both Win32 and *nix platforms. If anyone would like to participate
small
> or large please send me an email.
>
> The general plan so far:
>
> Write the client and server app in Perl and then use something like
Perl2Exe
> to make and executable out of the scripts.
Do you plan or can this be extended to be a distributed sniffer? I'm more
interested in that to use it as a remote debugging tool. I've already
started
some design work and a little code work.
The perl2exe is a neat idea. How good is the code? Is the program statically
linked? The reason I ask is because I think that the client should be a
minimal
system with a small memory and disk footprint. It should load onto the
client
as a stand-alone program that doesn't require external libraries or DLLs.
Jeff Foster
jfoste@xxxxxxxxxxxx
***
The information in this e-mail is confidential and intended solely for the
individual or entity to whom it is addressed. If you have received this
e-mail in error please notify the sender by return e-mail, delete this
e-mail, and refrain from any disclosure or action based on the information.
****
