The MxSniffer Tool

This is the definitive logging tool to use if you need/want to view all the different packet types and general traffic passing across the WPN or just want to monitor the traffic for statistical purposes.

You will need a copy of the MxSniffer Program in English from here

To make this tool work you will need it to be placed in the same folder as the WinMX executable as shown here using the open sourced "Unique" Dll Patch from here , if you are using an old ws2_32.dll patch this will mean renaming the WinMX patch dll to ws2_32o.dll besides these or using ahost file there should be no known problems using any of the standard winmxgroup patches.

Please remember you will need to have WinMX closed when you place the "Sniffer" files in the WinMX folder.

Once you start the tool up (by starting WinMX) you will be able to see another WinMX window that is sitting in the Task Bar and this splash screen appears.


The window has very few controls and no logging to file facility, but that's not such a bad thing as you will be able to see the results live as they are happening.
One of the buttons will Pause the screen activity for you and the other will Clear the screen to enable you to focus on only the packets your actually interested in.


I suggest to start off with you use a secondary connection as a primary connection will become rapidly clogged and perhaps rather frustrating as it jumps from connection to connection.

As you can see there is plenty of activity going on with information being send rapidly between users and if you join a chat room you will see how the user list is sent which looks rather different from the client side I think you'll agree.  

Ok, so that's the basic setup and you will I hope, understand some of the numbers and their meanings and perhaps endeavour to see how many different ones there are as no published full listing of the many types of packet and their format exist presently.
While using the sniffer you may notice that it is sometimes hard to keep the data stable on the screen especially in the case of a primary connection, patience is advised.

For Linux users:
Although this is a customised winsock file there are only two further dependencies for this file the KERNEL32.DLL and the USER32.dll, although when run as described above you will not need to bother with adding any additional libraries.

My thanks to Nushi@2SN for the use of his "MxSniffer" tool used in this guide.

©2005-2020 All rights reserved. Page last updated Tue Apr 29 2008