PerlSufi: your reply about NetPacket would certainly help in the direction of implementing the 'tcpdump' approach the OP mentioned. May I also suggest the Net::Frame suite as I believe it is more complete based on number of CPAN results returned. That and I also have a bias as I use it (very easy) and have written a few extensions (IPv6 and extension headers, DNS, RIP/ng, etc...) for it.
Ultimately, I think the IO::Socket::Multicast route with your recommendation of a MIME package for emailing is the best way to go. But then again, TMTOWTDI! | [reply] |
VinsWorldcom: looking at the documentation, IO::Socket::Multicast looks great, indeed. :)
| [reply] |
Thank you for suggesting "Active State Perl". At this point I might use this, since I was a little lost at configuring CPAN on a company server. The latter is due to a number off errors being generated during the install of a package from CPAN, yet I did not fully understand the errors, which I suspect is due to being new with Perl and CPAN. Yet, I am very eger to learn Perl.
However, I will still need to learn CPAN, since the very end product will need to be installed on a CentOS6.3 box that is located at a very remote site.
thanks again
JJ | [reply] |
Yeah some module's dependencies are difficult to resolve.. usually you will get CPAN errors for things like that. Happy Perl-ing :)
| [reply] |