Changes

Jump to navigation Jump to search
28 bytes added ,  04:29, 8 June 2011
no edit summary
Line 8: Line 8:  
The 3DS broadcasts beacons with Nintendo tag vendor 0009bf. This includes the 3DS user-name, and possibly some consoleID? The DSi authenticates/associates with some binary SSID. The rest uses cleartext ntr/twl multi-cast communications, a lot of keep-alive frames are sent.
 
The 3DS broadcasts beacons with Nintendo tag vendor 0009bf. This includes the 3DS user-name, and possibly some consoleID? The DSi authenticates/associates with some binary SSID. The rest uses cleartext ntr/twl multi-cast communications, a lot of keep-alive frames are sent.
   −
The DSi will then send its username and serial number to the 3DS, 3DS will send its username/serial# to DSi as well.
+
The DSi will then send its country code, username, and serial number to the 3DS, 3DS will send its country-code/username/serial# to DSi as well.
 
The 3DS seems to query the shop server /w SOAP for the list of DSiWare that the DSi owns, as well as titles that are allowed to be transferred? The 3DS sends this title list to the DSi. When the user selects which title to transfer, DSi sends the banner of that title to the 3DS and many frames later the titleID.
 
The 3DS seems to query the shop server /w SOAP for the list of DSiWare that the DSi owns, as well as titles that are allowed to be transferred? The 3DS sends this title list to the DSi. When the user selects which title to transfer, DSi sends the banner of that title to the 3DS and many frames later the titleID.
  

Navigation menu