If your class is about security of communications then I'd strongly suggest that you use RawIP. Much more can be done to manipulate communications and break security if one can introduce as well as observe traffic in Man-in-the-Middle scenarios. Even if that is not what your current assignment would require, you'd already have the experience working with RawIP for when you do need to inject or intercept and rewrite packets. It is probably obvious from my nym that I am working on doing that for SIP and the VoIP systems dependent on it.
If one is trying to use Net::RawIP, the example that is best to follow is the traceroute. I'm not even sure some of the others will work with recent versions of perl. I have a version of traceroute where I made detailed comments on what was supposed to be happening for my own understanding, please ask if you'd like a copy before I get it cleaned up enough to submit to the RawIP author.
Net::RawIP is not supported by Activestate on Windows and will require a C compiler to build. If anyone has built it and can share the binaries, please let me know. I will get to it someday, but if someone can beat me to it, it's one less thing to do.
HTH, Sip Phreak
In reply to Re: perl IP packet sniffer
by sipphreak
in thread perl IP packet sniffer
by gri6507
For: | Use: | ||
& | & | ||
< | < | ||
> | > | ||
[ | [ | ||
] | ] |