Nintendo Zone - Revision history

LiquidFenrir: /* Beacon payload format */

2017-07-06T08:17:11Z

Beacon payload format

← Older revision		Revision as of 12:17, 6 July 2017
Line 51:		Line 51:
	\| 0x65		\| 0x65
	\| 1		\| 1
	\| AP crypto key type: 0) Open 1) WEP-64 2) WEP-128 3) WEP-152 7) WPA2-PSK (the encryption key field contains the AP passphrase)		\| AP crypto key type: 0) Open 1) WEP-64 2) WEP-128 3) WEP-152 4) WPA-PSK (TKIP) 5) WPA2-PSK (TKIP) 6) WPA-PSK (AES) 7) WPA2-PSK (AES) (the encryption key field contains the AP passphrase)
	\|-		\|-
	\| 0x66		\| 0x66

Nokonoko: /* Beacon payload format */

2015-04-11T10:28:53Z

Beacon payload format

← Older revision		Revision as of 14:28, 11 April 2015
Line 27:		Line 27:
	\| 0x00		\| 0x00
	\| 32		\| 32
	\| AP SSID.		\| AP SSID
	\|-		\|-
	\| 0x20		\| 0x20
	\| 10		\| 10
	\| ApNum, required for connecting to the server. This is used by the server to determine which retailer NZone you're using. Apnum structure: RSSCCTTLLL. R is the decimal region, SS is the decimal ServiceID. CC is the two-letter country-code, TT is the 2-letter country state/province code, and LLL is the decimal locationID. Regions: 0) JPN 1) USA 2/3) EUR 4) KOR 5) CHN. LLL is always zero for non-JPN deployments, however in JPN this is unique per NZone hotspot location.~~(TT is only used in JPN, elsewhere it's always zero)~~		\| ApNum, required for connecting to the server. This is used by the server to determine which retailer NZone you're using. Apnum structure: 10 digits or RSSCCTTLLL. R is the decimal region, SS is the decimal ServiceID. CC is the two-letter country-code, TT is the 2-letter country state/province code, and LLL is the decimal locationID. Regions: 0) JPN 1) USA 2/3) EUR 4) KOR 5) CHN. LLL is always zero for non-JPN deployments, however in JPN this is unique per NZone hotspot location.
	\|-		\|-
	\| 0x2a		\| 0x2a
Line 39:		Line 39:
	\| 0x2c		\| 0x2c
	\| 24		\| 24
	\| Some UTF-16 ~~ServiceName. "BestBuy"~~		\| Some ServiceName, either in UTF-16 or ASCII
	\|-		\|-
	\| 0x44		\| 0x44
	\| 32		\| 32
	\| AP crypto key, if any.		\| AP crypto key, if any
	\|-		\|-
	\| 0x64		\| 0x64
	\| 1		\| 1
	\| Unknown, not used by the DS(i) client. For 3DS this ~~is 0x1~~, for DS(i) this is 0x0.		\| Unknown, not used by the DS(i) client. For 3DS this value varies, for DS(i) this is 0x0.
	\|-		\|-
	\| 0x65		\| 0x65
	\| 1		\| 1
	\| AP crypto key type: 0) Open 1) WEP-64 2) WEP-128 3) WEP-152 7) WPA2-PSK(the encryption key field contains the AP passphrase)		\| AP crypto key type: 0) Open 1) WEP-64 2) WEP-128 3) WEP-152 7) WPA2-PSK (the encryption key field contains the AP passphrase)
	\|-		\|-
	\| 0x66		\| 0x66
	\| 1		\| 1
	\| ~~Unknown flags, for 3DS this is 0x1e, for~~ DS(i) ~~this is 0x3. Bits 0~~ and ~~1 don't seem to be used by~~ the ~~client. The DS(i) client uses bit2 unknown what for though.~~		\| Bit 0: Enables Nintendo Zone content on DS(i)<br>Bit 1: Enables friend list and online gaming<br>Bit 4: Enables Nintendo Zone Viewer on 3DS<br>Bit 7: Blocks the Nintendo eShop<br>Bits 2, 3, 5, 6: Unknown
	\|-		\|-
	\| 0x67		\| 0x67
	\| 5		\| 1
	\| Padding.		\| Bit 0: Blocks the internet browser<br>Bits 1 to 7: Unknown
			\|-
			\| 0x68
			\| 4
			\| Padding
	\|-		\|-
	\| 0x6c		\| 0x6c
	\| 2		\| 2
	\| Unknown, ~~with 3DS this is zero but for DS(i) this was~~ 0x428.		\| Unknown, seems to be always 0x428
	\|-		\|-
	\| 0x6e		\| 0x6e
	\| 2		\| 2
	\| CRC16 over the whole payload excluding CRC offset, initval is 0.		\| CRC16 over the whole payload excluding CRC offset, initval is 0
	\|}		\|}

Yellows8: /* Hotspot list from NZone hotspot.conf */

2014-12-12T23:18:39Z

Hotspot list from NZone hotspot.conf

← Older revision		Revision as of 02:18, 13 December 2014
Line 270:		Line 270:
	\| Bestbuy \|\| WPA2-PSK \|\| USA \|\| Bestbuy \|\| \|\| After v1024		\| Bestbuy \|\| WPA2-PSK \|\| USA \|\| Bestbuy \|\| \|\| After v1024
	\|}		\|}

			See also [http://yls8.mtheall.com/ninupdates/3ds_nzonehotspots.php this].

	==== NZone hotspots only accessible via NZone beacons ====		==== NZone hotspots only accessible via NZone beacons ====

Yellows8 at 18:58, 24 July 2013

2013-07-24T16:58:06Z

← Older revision		Revision as of 20:58, 24 July 2013
Line 8:		Line 8:

	The NZone browser interface is similar to the regular [[Internet Browser]], the browser engine used here is completely different however. Unlike the regular [[Internet Browser]] which uses the socket/SSL services directly, the Nintendo Zone application uses the [[HTTP_Services\|HTTP]] service instead.		The NZone browser interface is similar to the regular [[Internet Browser]], the browser engine used here is completely different however. Unlike the regular [[Internet Browser]] which uses the socket/SSL services directly, the Nintendo Zone application uses the [[HTTP_Services\|HTTP]] service instead.
			3D stereoscopic videos are supported via html "<media>" tags, for 3D videos the "mediatype" attribute is set to "3D". For 2D videos videos the "mediatype" attribute is set to "2D". This uses Mobiclip with file extension .moflex, the magic number from the first word in the video file is 0xabaa324c(little-endian).

	The ~~NZone beacon encryption is same as before, except some unknown fields in the cleartext was changed where~~ 3DS ~~will only "detect"~~ NZone ~~/w NZone icon blinking/enabled when~~ the ~~beacons' fields are set this way. DSi will not detect these beacons. 3DS can use DS(i)~~ NZone, ~~but only~~ if the ~~NZone title is already enabled. With DS(i) beacons~~, ~~3DS connects to Internet but~~ the ~~NZone icon~~ will ~~not blink. However~~ the ~~NZone title will still work once launched. Different URL params are sent to the to the server than DSi, sending the wrong params via curl results in an error page being returned~~.		The 3DS NZone application immediately uses [[NIMS:CheckSysupdateAvailableSOAP]] once connected to the NZone AP, if an update is available and the user selects "Cancel" in the displayed dialog, the application will stop using the wifi AP.

	The ~~3DS NZone~~ application ~~immediately uses [[NIMS:CheckSysupdateAvailableSOAP]] once connected~~ to the ~~NZone AP, if an update is available~~ and the ~~user selects~~ "~~Cancel~~" in the ~~displayed dialog~~, the ~~application will stop using~~ the ~~wifi AP~~.		The user-agent used by the Nintendo Zone application is "NintendoZoneViewer/3.1". The URL parameters sent to the dsdl.* HTTPS server are the same as DSi(besides the value of the console-type parameter and the "ver" parameter value), except 3DS also sends additional headers in the request using the same data sent in the URL parameters. The zonebnr server requires three more request headers(extra URL parameters are not needed here), the first of these three headers is "ZoneUserID" where the unknown value is 16 hex-digits(8-bytes in binary). The last two headers of these additional three headers contain data which was originally sent with the dsdl server URL parameters.

	~~3D stereoscopic videos are supported via html "<media>" tags~~, ~~for 3D videos~~ the "~~mediatype~~" ~~attribute is~~ set ~~to "3D"~~. ~~This uses Mobiclip with file extension~~ .~~moflex~~, the ~~magic number from the first word in the video file~~ is ~~0xabaa324c~~(~~little-endian~~).		The NZone beacon encryption is same as before, except some unknown fields in the cleartext was changed where 3DS will only "detect" NZone /w NZone icon blinking/enabled when the beacons' fields are set this way. DSi will not detect these beacons. 3DS can use DS(i) NZone, but only if the NZone title is already enabled. With DS(i) beacons, 3DS connects to Internet but the NZone icon will not blink. However the NZone title will still work once launched.

	=== Beacon payload format ===		=== Beacon payload format ===

Yellows8 at 17:54, 24 July 2013

2013-07-24T15:54:51Z

← Older revision		Revision as of 19:54, 24 July 2013
Line 7:		Line 7:
	== Description ==		== Description ==

	The NZone browser interface is similar to the regular [[Internet Browser]], the browser engine used here is completely different however. The NZone beacon encryption is same as before, except some unknown fields in the cleartext was changed where 3DS will only "detect" NZone /w NZone icon blinking/enabled when the beacons' fields are set this way. DSi will not detect these beacons. 3DS can use DS(i) NZone, but only if the NZone title is already enabled. With DS(i) beacons, 3DS connects to Internet but the NZone icon will not blink. However the NZone title will still work once launched. Different URL params are sent to the to the server than DSi, sending the wrong params via curl results in ~~old content~~ being ~~retrieved~~.		The NZone browser interface is similar to the regular [[Internet Browser]], the browser engine used here is completely different however. Unlike the regular [[Internet Browser]] which uses the socket/SSL services directly, the Nintendo Zone application uses the [[HTTP_Services\|HTTP]] service instead.

			The NZone beacon encryption is same as before, except some unknown fields in the cleartext was changed where 3DS will only "detect" NZone /w NZone icon blinking/enabled when the beacons' fields are set this way. DSi will not detect these beacons. 3DS can use DS(i) NZone, but only if the NZone title is already enabled. With DS(i) beacons, 3DS connects to Internet but the NZone icon will not blink. However the NZone title will still work once launched. Different URL params are sent to the to the server than DSi, sending the wrong params via curl results in an error page being returned.

	The 3DS NZone application immediately uses [[NIMS:CheckSysupdateAvailableSOAP]] once connected to the NZone AP, if an update is available and the user selects "Cancel" in the displayed dialog, the application will stop using the wifi AP.		The 3DS NZone application immediately uses [[NIMS:CheckSysupdateAvailableSOAP]] once connected to the NZone AP, if an update is available and the user selects "Cancel" in the displayed dialog, the application will stop using the wifi AP.

Yellows8 at 17:40, 24 July 2013

2013-07-24T15:40:14Z

← Older revision		Revision as of 19:40, 24 July 2013
Line 10:		Line 10:

	The 3DS NZone application immediately uses [[NIMS:CheckSysupdateAvailableSOAP]] once connected to the NZone AP, if an update is available and the user selects "Cancel" in the displayed dialog, the application will stop using the wifi AP.		The 3DS NZone application immediately uses [[NIMS:CheckSysupdateAvailableSOAP]] once connected to the NZone AP, if an update is available and the user selects "Cancel" in the displayed dialog, the application will stop using the wifi AP.

			3D stereoscopic videos are supported via html "<media>" tags, for 3D videos the "mediatype" attribute is set to "3D". This uses Mobiclip with file extension .moflex, the magic number from the first word in the video file is 0xabaa324c(little-endian).

	=== Beacon payload format ===		=== Beacon payload format ===

Yellows8 at 16:33, 24 July 2013

2013-07-24T14:33:26Z

← Older revision		Revision as of 18:33, 24 July 2013
Line 8:		Line 8:

	The NZone browser interface is similar to the regular [[Internet Browser]], the browser engine used here is completely different however. The NZone beacon encryption is same as before, except some unknown fields in the cleartext was changed where 3DS will only "detect" NZone /w NZone icon blinking/enabled when the beacons' fields are set this way. DSi will not detect these beacons. 3DS can use DS(i) NZone, but only if the NZone title is already enabled. With DS(i) beacons, 3DS connects to Internet but the NZone icon will not blink. However the NZone title will still work once launched. Different URL params are sent to the to the server than DSi, sending the wrong params via curl results in old content being retrieved.		The NZone browser interface is similar to the regular [[Internet Browser]], the browser engine used here is completely different however. The NZone beacon encryption is same as before, except some unknown fields in the cleartext was changed where 3DS will only "detect" NZone /w NZone icon blinking/enabled when the beacons' fields are set this way. DSi will not detect these beacons. 3DS can use DS(i) NZone, but only if the NZone title is already enabled. With DS(i) beacons, 3DS connects to Internet but the NZone icon will not blink. However the NZone title will still work once launched. Different URL params are sent to the to the server than DSi, sending the wrong params via curl results in old content being retrieved.

			The 3DS NZone application immediately uses [[NIMS:CheckSysupdateAvailableSOAP]] once connected to the NZone AP, if an update is available and the user selects "Cancel" in the displayed dialog, the application will stop using the wifi AP.

	=== Beacon payload format ===		=== Beacon payload format ===

Yellows8 at 06:29, 24 July 2013

2013-07-24T04:29:33Z

← Older revision		Revision as of 08:29, 24 July 2013
Line 7:		Line 7:
	== Description ==		== Description ==

	The NZone browser interface ~~looks very~~ similar to the ~~main 3DS web browser~~, ~~so it's probably~~ the ~~same as that~~ browser ~~except modified~~.~~(and with video support, presumably mobiclip)~~ The NZone beacon encryption is same as before, except some unknown fields in the cleartext was changed where 3DS will only "detect" NZone /w NZone icon blinking/enabled when the beacons' fields are set this way. DSi will not detect these beacons. 3DS can use DS(i) NZone, but only if the NZone title is already enabled. With DS(i) beacons, 3DS connects to Internet but the NZone icon will not blink. However the NZone title will still work once launched. Different URL params are sent to the to the server than DSi, sending the wrong params via curl results in old content being retrieved.		The NZone browser interface is similar to the regular [[Internet Browser]], the browser engine used here is completely different however. The NZone beacon encryption is same as before, except some unknown fields in the cleartext was changed where 3DS will only "detect" NZone /w NZone icon blinking/enabled when the beacons' fields are set this way. DSi will not detect these beacons. 3DS can use DS(i) NZone, but only if the NZone title is already enabled. With DS(i) beacons, 3DS connects to Internet but the NZone icon will not blink. However the NZone title will still work once launched. Different URL params are sent to the to the server than DSi, sending the wrong params via curl results in old content being retrieved.

	=== Beacon payload format ===		=== Beacon payload format ===

Yellows8 at 04:33, 24 July 2013

2013-07-24T02:33:48Z

← Older revision		Revision as of 06:33, 24 July 2013
Line 44:		Line 44:
	\| 0x65		\| 0x65
	\| 1		\| 1
	\| AP crypto key type: 0) Open 1) WEP-64 2) WEP-128 3) WEP-152 7) WPA2-PSK		\| AP crypto key type: 0) Open 1) WEP-64 2) WEP-128 3) WEP-152 7) WPA2-PSK(the encryption key field contains the AP passphrase)
	\|-		\|-
	\| 0x66		\| 0x66
Line 97:		Line 97:
	\| SecurityKey		\| SecurityKey
	\| 0x40 (after decode)		\| 0x40 (after decode)
	\| Hotspot Base64-encoded encryption key. For encryption type7, WPA2-PSK is used, however the ~~data specified with~~ this ~~field~~ is ~~not~~ the ~~actual passphrase~~.		\| Hotspot Base64-encoded encryption key. For encryption type7, WPA2-PSK is used, however unlike the NZone beacon this is the 0x20-byte WPA-PSK.
	\|-		\|-
	\| SecurityMode		\| SecurityMode

Yellows8 at 15:36, 20 June 2013

2013-06-20T13:36:18Z

← Older revision		Revision as of 17:36, 20 June 2013
Line 1:		Line 1:
	'''Nintendo Zone''' is the successor to DS Download Stations, offering retailer exclusive content, game videos, screenshots, etc. As of February 6th 2012 demos are available for download, demos are downloaded from the eShop servers and installed to SD card. NZone demos are the same ones available on eShop, these are region-locked as trying to download them from other regions results in an error. ~~USA Best Buy and some other retailers have~~ NZone~~, this NZone seems to be~~ significantly different from the DS(i) [http://dsibrew.org/wiki/Nintendo_Zone NZone]. Most content available at ~~Best Buy~~ is already available on eShop, like the screenshots/videos, game info etc~~. The OK Go video is available from NZone however. The OOT video on NZone server is the one from eShop launch like most of the other videos~~.		'''Nintendo Zone''' is the successor to DS Download Stations, offering retailer exclusive content, game videos, screenshots, etc. As of February 6th 2012 demos are available for download, demos are [[NIM_Services\|downloaded]] from the eShop servers and installed to SD card. NZone demos are the same ones available on eShop, these are region-locked as trying to download them from other regions results in an error. The 3DS NZone is significantly different from the DS(i) [http://dsibrew.org/wiki/Nintendo_Zone NZone]. Most content available at NZone is already available on eShop, like the screenshots/videos, game info etc.

	Like DSi, when an open 3DS detects NZone the originally hidden NZone title appears and a notification about it appears. Like DSi this title is already stored on NAND, originally this title only became accessible from home-menu once the 3DS was in a range of a NZone at least once, however at some point with a system update this title became always-accessible. When NZone beacons are in range, 3DS only detects NZone when not connected to Internet already. Once connected to a NZone AP, the beacon payload is cached until disconnected from the AP.		Like DSi, when an open 3DS detects NZone the originally hidden NZone title appears and a notification about it appears. Like DSi this title is already stored on NAND, originally this title only became accessible from home-menu once the 3DS was in a range of a NZone at least once, however at some point with a system update this title became always-accessible. When NZone beacons are in range, 3DS only detects NZone when not connected to Internet already. Once connected to a NZone AP, the beacon payload is cached until disconnected from the AP.

	When modified DSi nzone beacons are broadcasted with the 3DS Best Buy ApNum, DSi launcher won't blink the NZone title icon but the title will still semi-work. NZone ~~title~~ would connect to the server, with buttons for demos, Best Buy, and WFC config displayed, but NZone will display an error a while after selecting "Best Buy" service after a bit of loading.(probably unsupported html tags etc)		When modified DSi nzone beacons are broadcasted with the 3DS Best Buy ApNum, DSi launcher won't blink the NZone title icon but the title will still semi-work. The NZone application would connect to the server, with buttons for demos, Best Buy, and WFC config displayed, but NZone will display an error a while after selecting "Best Buy" service after a bit of loading.(probably unsupported html tags etc)

	== Description ==		== Description ==
Line 10:		Line 10:

	=== Beacon payload format ===		=== Beacon payload format ===
	This seems to be identical to DS(i) NZone format except for the unknown fields~~, WPA2 isn't supported~~. 3DS NZone is not region-locked like DS(i).		This seems to be identical to DS(i) NZone format except for the unknown fields. 3DS NZone is not region-locked like DS(i).

	{\| class="wikitable" border="1"		{\| class="wikitable" border="1"
Line 44:		Line 44:
	\| 0x65		\| 0x65
	\| 1		\| 1
	\| AP crypto key type: 0) Open 1) WEP-64 2) WEP-128 3) WEP-152 7) ~~Unknown~~		\| AP crypto key type: 0) Open 1) WEP-64 2) WEP-128 3) WEP-152 7) WPA2-PSK
	\|-		\|-
	\| 0x66		\| 0x66
Line 70:		Line 70:
	Beginning the CSV file is the Interval record and field. Following that is the hotspot records on one line, and the fields for each hotspot on individual lines. Some fields are Base64-encoded, for those the Base64 padding character '*' is used instead of '='.		Beginning the CSV file is the Interval record and field. Following that is the hotspot records on one line, and the fields for each hotspot on individual lines. Some fields are Base64-encoded, for those the Base64 padding character '*' is used instead of '='.

	IsBrowser, IsShop, and IsGame might determine whether the [[Internet Browser]], [[eShop]], and games' online multi-player may be used~~. IsSetToFW is normally 0~~.		IsBrowser, IsShop, and IsGame might determine whether the [[Internet Browser]], [[eShop]], and games' online multi-player may be used.

	==== Records ====		==== Records ====
Line 97:		Line 97:
	\| SecurityKey		\| SecurityKey
	\| 0x40 (after decode)		\| 0x40 (after decode)
	\| Hotspot Base64-encoded ~~binary~~ encryption key		\| Hotspot Base64-encoded encryption key. For encryption type7, WPA2-PSK is used, however the data specified with this field is not the actual passphrase.
	\|-		\|-
	\| SecurityMode		\| SecurityMode
Line 260:		Line 260:
	\|-		\|-
	\| [http://www.free-hotspot.com/ free-hotspot.com] \|\| None \|\| EUR \|\| free-hotspot.com \|\| ? \|\| After v1024		\| [http://www.free-hotspot.com/ free-hotspot.com] \|\| None \|\| EUR \|\| free-hotspot.com \|\| ? \|\| After v1024
			\|-
			\| Bestbuy \|\| WPA2-PSK \|\| USA \|\| Bestbuy \|\| \|\| After v1024
	\|}		\|}