Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Its not Perl, but Ethereal is a great sniffer, especially if you need to do any analysis on traffic or individual packets. I havn't tried it for MSN, but it works great on AIM, as it sniff every packet going over the wires. You can also set up filters based on protocols, which should help keep your logs nice and clean.
ethereal (tetherreal) work fine with IMs - tried it on MSN was very "interesting" specially with the proper filter set. Only problem were files that are transmitted as MSN encrypts these and it gives you some weird stuff.
But otherwise you can lit. see the chat nicely formatted like in the orig client
All you probably need would be a daemon that watches your network for packages using the msg protocol (can't remember the name)
Perhaps this could be written as a extension for iptables (similar to snort inline)
this again calls the sniffer
as soon as the connection is dropped (no more of these packages)
parse the sniffers log and create the different log files
Doesnt sound to hard - does it. My advice start at the back in parsing the (t)ethereal log file.
If you get something working or need help with the (t)ethereal let me know
PS I assume with internal IP you mean the local IPs in your LAN
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.