Difference between revisions of "Network"

From xboxdevwiki
Jump to: navigation, search
(Section moved to Xbox Live article due to significance and for possible growth)
(Moved to System Link article, as it is signifcant and will likely grow in the future)
Line 42: Line 42:
  
 
The setup disc is a CD[http://redump.org/disc/53586/]. It contains an XISO filesystem that contains only a "default.xbe" which contains a dashboard updater.
 
The setup disc is a CD[http://redump.org/disc/53586/]. It contains an XISO filesystem that contains only a "default.xbe" which contains a dashboard updater.
−
 
−
== System Link ==
 
−
 
−
=== Secured traffic ===
 
−
 
−
Xbox network traffic is secured through [[wikipedia:IPSec|IPSec]]. The implementation appears to be similar to [https://tools.ietf.org/html/rfc3948#section-2.1|RFC 3498, Section 2.1] from 2005 which was co-authored by Microsoft.
 
−
 
−
The protocol uses UDP port 3074 which is also registered with the IANA for use in the Xbox[https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=3074].
 
−
Each Xbox uses the IP 0.0.0.1, so addressing relies on MAC-addresses{{FIXME|reason=Confirm this}}.
 
−
 
−
The specific implementation in the Xbox uses TripleDES ([https://tools.ietf.org/html/rfc1851|RFC 1851]) for encryption, and SHA1-96 as [[wikipedia:HMAC|HMAC]].
 
−
 
−
==== Key derivation ====
 
−
 
−
The following keys are involved in generating the actual network crypto-keys:
 
−
 
−
* XboxLANKey (Kernel export)
 
−
* Game specific LAN Key (XBE Certificate Header)
 
−
 
−
The algorithm to generate the final keys, is this:
 
−
 
−
<pre>
 
−
LAN-Hash_1 = HMAC(XboxLANKey, concatenate(0x00, XBE-LAN-Key))
 
−
LAN-Hash_2 = HMAC(XboxLANKey, concatenate(0x01, XBE-LAN-Key))
 
−
 
−
LAN-Hash = concatenate(LAN-Hash_1, LAN-Hash_2)
 
−
 
−
LAN-SHA = LAN-Hash_0_to_15
 
−
LAN-DES = XcDESKeyParity(LAN-Hash_16_to_39)
 
−
</pre>
 
−
 
−
[[Kernel/XcDESKeyParity|XcDESKeyParity]] is the same as the respective function in the Xbox kernel.
 
−
 
−
==== Broadcast messages ====
 
−
 
−
Because no security association exists for broadcast messages, these are handled differently.
 
−
A common use case for broadcast messages is a server announce request / response.
 
−
 
−
Broadcast messages are send to 255.255.255.255 (MAC-address: FF:FF:FF:FF:FF:FF) using SPI 0xFFFFFFFF and Sequence Number 0xFFFFFFFF.
 
−
A random IV is chosen, but nothing prevents re-using an IV.
 
−
 
−
==== Security association ====
 
−
 
−
Most messages require an SA between devices{{FIXME|reason=Look into this}}.
 
−
 
−
=== XDK API ===
 
−
 
−
{{FIXME|reason=This probably shouldn't be here? there should be dedicated articles for the XDK APIs}}
 
−
 
−
{| class="wikitable"
 
−
|+XNet* Functions
 
−
|-
 
−
! function
 
−
! description
 
−
|-
 
−
|XNetCreateKey(&xnkid, &xnkey)
 
−
|
 
−
|-
 
−
|XNetRegisterKey(&xnkid, &xnkey)
 
−
|Register the session key
 
−
|-
 
−
|XNetXnAddrToInAddr( pxnaddr, pxnkid, &pseudoIP )
 
−
|Convert the address to a winsock usable format
 
−
|-
 
−
|XNetUnregisterKey( &xbc.SessionID )
 
−
|
 
−
|-
 
−
|XNetGetTitleXnAddr( &hostAddr )
 
−
|Gets your XNADDR. Used by syslink, and lots of other people.
 
−
|-
 
−
|XNetGetEthernetLinkStatus()
 
−
|
 
−
|}
 
  
 
== Heartbeat ==
 
== Heartbeat ==

Revision as of 19:07, 4 October 2018

The Xbox contains an Ethernet module and one RJ45 connector. Additionally, separate modem and wireless accessories were considered when developing the console. Eventualy an official wireless adapter was released based of a "D-Link 108AG Gaming Adapter" in the end of 2003.

The Xbox has a TCP/IP protocol stack complete with a DNS PPTP, DHCP clients.

Port 3074 UDP/TCP is reserved for Xbox communications.

Hardware

Integrated in the Nvidia Southbridge MCPX chip which is similar to the nForce chips. The Xbox Linux team used the binary drivers from Nvidia.

Wireless adapter

based on the "D-Link 108AG Gaming Adapter", the Xbox MN-740 Wireless Bridge bundled with a Xbox setup disc (wich would update the dashboard if necessary).

Hardware

The onboard 3 leds are: Power, Wireless and Xbox(called Ethernet on the PCB). The board seems to have Jtag and what apears to be Serial testpins exposed.

Firmware

This wireless bridge runs a closed source version of the"ThreadX JADE/Green Hills Version G4.0.4.0" RTOS. The firmware contains a copyright string of: "Copyright (c) Microsoft Corporation All Rights Reserved Device is Xbox Compatible"

latest firmware is seperated by a boot and runtime firmware [citation needed] :

  • MN740_01.03.00.0005_BOOT.bin, "Xbox Wireless Adapter (MN-740) boot firmware"
  • MN740_01.00.02.0022_RUNTIME.bin, "Xbox Wireless Adapter (MN-740) runtime firmware"
WPA2 support

The shipped firmware does not support WPA or WPA2. A "firmware" hack based on the D-Link firmware adds WPA support, rendering Dashboard support unfunctional and changing settings require connecting to the LAN port using a PC (or webbrowser capable application).

Software (Xbox setup disc)

The setup disc is a CD[1]. It contains an XISO filesystem that contains only a "default.xbe" which contains a dashboard updater.

Heartbeat

   Ethernet II, Src: Microsof_f2:00:00 (00:50:f2:f2:00:00), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
   MS Network Load Balancing
       Signature: Unknown (0x584f4258)
       Version: 1.1
       Unique Host ID: 3118682055
       Cluster IP: 167.102.81.132 (167.102.81.132)
       Host IP: 4.89.169.109 (4.89.169.109)
       Signature Data - Unknown (1481589336)


References and links

Retrieved from "https://xboxdevwiki.net/index.php?title=Network&oldid=6548"