Jump to content


XLink Kai 7.4 Beta released

  • Please log in to reply
19 replies to this topic

#16 freyyr890


    X-S Enthusiast

  • Members
  • 23 posts
  • Xbox Version:v1.0
  • 360 version:v1 (xenon)

Posted 02 July 2008 - 01:45 AM

Hmm, can't edit my post. Anyway, this is what I've learned so far with my noobish protocol analysis skills, using Halo 3 as a base.

When the xbox is searching for games, it broadcasts 42 bytes of data over UDP, from a source address of to the IPv4 broadcast address on port 3074. Pretty standard LAN play with UDP. (If anyone wants this capture PM me, but it's pretty useless).

I'm assuming that when it gets a reply to this is when the exchange occurs. However I can't test this because I don't have two 360s, nor do I have the network hardware to do a proper capture.

However, if anyone well-enough equipped were to take some captures and post them, others could analyze them.

Edited by freyyr890, 02 July 2008 - 01:46 AM.

#17 Altima NEO

Altima NEO

    X-S Freak

  • Members
  • PipPipPipPipPip
  • 1,404 posts
  • Interests:Gaming, XBox, 360, PSP, Dreamcast, 3D Graphics & Animation
  • Xbox Version:v1.4
  • 360 version:v1 (xenon)

Posted 02 July 2008 - 04:35 AM

As sweet as Kai is, theres hardly anyone playing anything other than Halo 2.

#18 llnk


    X-S Enthusiast

  • Members
  • 4 posts

Posted 02 July 2008 - 06:38 PM

MeanMF wrote this on the teamxlink forums last year. He also wrote the code for the new XLink 7.4 engine.


"Diffie-Hellman. It's not an encryption method, it's a way for the two Xboxes to come up with an encryption key to use for that connection. The actual keys change every time you connect to a host, and possibly more frequently. It's more or less the same thing that SSL uses when you connect to a secure web site.

The Xbox never actually measures the ping times. The Diffie-Hellman key exchange thing is a back-and-forth conversation between the two boxes. They give it a certain amount of time to complete, and if it doesn't then you can't connect. Sending the packets over the internet is enough delay to cause it to fail. 20ms is FOREVER in computer time.

Diffie-Hellman by itself is vulnerable to a "man in the middle" attack - you intercept every packet, make up your own keys, then decrypt and reencrypt every packet going back and forth. But they've added authentication to the mix, so the Xbox on the other end would know that you're not the real thing. SSL does the same thing - if you try to connect to a fake server it'll tell you that the server's SSL certificate doesn't match the site's URL.

The system prevents you from tampering with network traffic in system link games. It's there so you can't cheat by changing or looking at packets on the network. The original Xbox used basically the same system, but the time limit just wasn't there. It was trivial for them to add that check in."

Source: http://www.teamxlink...pic.php?t=27823

It sounds like the only way around the M$ Ping limits is modding the 360. I know it will eventually happen, the question is... when. Get on it boys! biggrin.gif

#19 agibby5


    X-S Young Member

  • Members
  • Pip
  • 30 posts
  • Location:PA
  • Xbox Version:v1.6
  • 360 version:unknown

Posted 02 July 2008 - 11:26 PM

I'm under Ubuntu 8.04. When I try to run /bin/kaiengine, I get a error message saying "No network interfaces were detected". I do, in fact, have a network interface. Does running this create a config file? If so, where is it so that it can be tweaked. Thanks.

#20 freyyr890


    X-S Enthusiast

  • Members
  • 23 posts
  • Xbox Version:v1.0
  • 360 version:v1 (xenon)

Posted 02 July 2008 - 11:50 PM

I had this problem too. Turns out kaiengine needs root privileges.

Run "sudo kaiengine" (assuming kaiengine is in your path) and see where that gets you.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users