Author Topic: WinMx Joining System (Read 3496 times)

GhostShip · « **on:** September 22, 2005, 01:47:34 pm »

WinMX Joining System

   When connnecting to Frontcode/Winmx Technologies the interaction is as follows:

   1) The WinMX Client will attempt to connect to the Peer Cache Server at

   216.127.74.62 utilising ports 7950 - 7952

   2) The Peer Cache Server Server sends down 0x38 or in ASCII "8" to the client indicating WinMX Logon Ok.
   3) The WinMX Client sends its Encryption Key to the Peer Cache Server using the following formula
   WPNP KEY IDs
      0x0050   : Primary Client
      0x0051   : Primary Server
      0x0052   : Secondary Client
      0x0053   : Secondary Server
0x0054 : Cache Node List
      0x0057   : Chat Client
      0x0058   : Chat Server

      (IN) Crypt Key ID.
      pBlock   : (OUT) Key Block ( 16 bytes )

       BYTE KeyBlock[16];
      CreateCryptKeyID(WPN KEY ID, KeyBlock);

   4) Peer Cache Server sends Encryption Key to the WinMx client (16 bytes also )

   5) WinMXClient and WPN Server now process and use the encryption keys swapped to generate and receive further messages from WPN connected clients.

   6) Peer Cache Server now sends down a list of valid primariy IP,s from the Cache in blocks of 10 using the 0x0054 client ID

   132 bytes in length

   7) WinMX Client now contacts other primaries and exchanges IPs by using a special packet type, a peer cache can also utilise these packets when primaries with open slots are being sought by the Peer Cache Server although alternative options are more favourable.

I hope this help someone

~~Josh~~ · « **Reply #1 on:** February 12, 2006, 05:57:48 am »

doesn't help at all

GhostShip · « **Reply #2 on:** February 12, 2006, 09:24:56 am »

I,m sorry to hear that Josh, perhaps you would like to describe the problem your having here and then maybe someone can help you out ?

There are many folks that may be able to help, so please fill in a little detail and perhaps some one may be able to get you rolling.