任天堂乐园 - Revision history

T: update 对应英文版 http://3dbrew.org/w/index.php?title=Nintendo_Zone&oldid=7373

2013-06-22T06:57:01Z

update 对应英文版 http://3dbrew.org/w/index.php?title=Nintendo_Zone&oldid=7373

← Older revision		Revision as of 10:57, 22 June 2013
Line 1:		Line 1:
	'''Nintendo Zone''' 是 DS Download Stations 的延续，提供发售游戏的独家内容，游戏视频，截图等等。2012年2月6日之前，已经可以从这里下载demo游戏，demo游戏可以从eshop的服务器下载并安装到SD卡中。Nintendo Zone提供的试玩版与eshop相同，尝试下载其他锁区的应用时会出现错误。美国百思买和其他一些零售商拥有Nintendo Zone，它们看起来与 DS(i) [http://dsibrew.org/wiki/Nintendo_Zone NZone]~~不同。百思买那里可以访问到的大部分Nintendo~~ Zone内容是eshop已有的。		'''Nintendo Zone''' 是 DS Download Stations 的延续，提供发售游戏的独家内容，游戏视频，游戏截图等等。2012年2月6日之前，已经可以从这里下载demo游戏，demo游戏是[[NIM_Services\|downloaded]]从eshop的服务器下载并安装到SD卡的。Nintendo Zone提供的试玩版与eshop相同，尝试下载其他锁区的应用时会出现错误。Nintendo Zone与 DS(i) [http://dsibrew.org/wiki/Nintendo_Zone NZone]不同，访问到的大部分Nintendo Zone内容是eshop已有的。

	就像DSi一样，当你打开3DS时，主机会检查是否有隐藏的NZone（在美国NZone总是可用的），NZone 的 title 会提示发现了Nzone。DSi的title存储在NAND中，但是只在Nzone的覆盖范围时title才可见（即使拔掉SD卡也没关系）。3DS只有未连接互联网时，才会检查是否处于NZone覆盖范围。连接过一个NZone AP后, 标志就被缓存了，直到与AP断开连接。		就像DSi一样，当你打开3DS时，主机会检查是否有隐藏的NZone（在美国NZone总是可用的），NZone 的 title 会提示发现了Nzone。DSi的title存储在NAND中，但是只在Nzone的覆盖范围时title才可见（即使拔掉SD卡也没关系）。3DS只有未连接互联网时，才会检查是否处于NZone覆盖范围。连接过一个NZone AP后, 标志就被缓存了，直到与AP断开连接。

	修改DSi nzone广播的信标为3DS Best Buy ApNum后, DSi launcher中NZone的title图标不会闪烁，但是这个title仍然处于半工状态（semi-work）。 NZone title可以连接到服务器, 显示出demo按钮，百思买，WFC配置，但是选择百思买服务并加载一段时间后，NZone会显示一个错误。（可能有不支持的HTML标签之类的东西）		修改DSi nzone广播的信标为3DS Best Buy ApNum后, DSi launcher中NZone的title图标不会闪烁，但是这个title仍然处于半工状态（semi-work）。 NZone title可以连接到服务器, 显示出demo按钮，百思买，WFC配置，但是选择百思买服务并加载一段时间后，NZone会显示一个错误。（可能有不支持的HTML标签之类的东西）

			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. 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)

	* '''Nintendo Zone'''和"'nzone'" 暂译为"'任天堂乐园'"或者“‘天堂乐园’”。但是为了便于查阅，文中均未作翻译。		* '''Nintendo Zone'''和"'nzone'" 暂译为"'任天堂乐园'"或者“‘天堂乐园’”。但是为了便于查阅，文中均未作翻译。
Line 11:		Line 15:

	=== Beacon payload format ===		=== Beacon payload format ===
	除去未知部分,3DS Nzone应该是与DS(i) ~~NZone格式相同的, （不支持WPA2）。3DS~~ NZone不像DS(i)一样有锁区。		除去未知部分,3DS Nzone应该是与DS(i) NZone格式相同的）。3DS NZone不像DS(i)一样有锁区。


	{\| class="wikitable" border="1"		{\| class="wikitable" border="1"
Line 45:		Line 50:
	\| 0x65		\| 0x65
	\| 1		\| 1
	\| AP密钥类型: 0) 开放 1) WEP-64 2) WEP-128 3) WEP-152		\| AP密钥类型: 0) Open 1) WEP-64 2) WEP-128 3) WEP-152 7) WPA2-PSK
	\|-		\|-
	\| 0x66		\| 0x66
Line 67:		Line 72:

	=== Hotspot.conf 格式 ===		=== Hotspot.conf 格式 ===
	AC系统applet从"conf:/hotspot.conf"加载NZone无线热点的列表,其中"conf:" 是 000400DB00010502 ~~文档的内容~~. 这是一个使用 LF换行的CSV文件,每个NZone的全部beacon信息也存储在这个文件中. 这个文件列出多至100个热点.(title版本v1024的hotspot.conf列出了52个热点). 这个格式可以使用[https://github.com/yellows8/hotspotconf-tool hotspotconf-tool]解析.		AC系统applet从"conf:/hotspot.conf"加载NZone无线热点的列表,其中"conf:" 是 000400DB00010502 文档的[[NCCH#CFA\|CFA]]. 这是一个使用 LF换行的CSV文件,每个NZone的全部beacon信息也存储在这个文件中. 这个文件列出多至100个热点.(title版本v1024的hotspot.conf列出了52个热点). 这个格式可以使用[https://github.com/yellows8/hotspotconf-tool hotspotconf-tool]解析.

	CSV开头部分是内部记录区域。在那之后的就是hotspot的记录，每行一个hotspot的区域。使用Base64加密的区域，行尾的补齐字符是'*'而不是'='。		CSV开头部分是内部记录区域。在那之后的就是hotspot的记录，每行一个hotspot的区域。使用Base64加密的区域，行尾的补齐字符是'*'而不是'='。
Line 98:		Line 103:
	\| SecurityKey		\| SecurityKey
	\| 0x40 (解码后)		\| 0x40 (解码后)
	\| 热点使用 Base64 编码的密钥		\| 热点使用 Base64 编码的密钥.但是加密方式7使用了WPA2-PSK,与此字段的值不符
	\|-		\|-
	\| SecurityMode		\| SecurityMode
Line 131:		Line 136:
	\| 1		\| 1
	\| 热点标志,0/1		\| 热点标志,0/1
			\|-
			\| IsZone
			\| 1
			\| 热点标志,0/1. 这是较新的 NZone hotspot.conf 才出现的.
	\|}		\|}

	=== 热点 ===		=== 热点 ===
	hotspot.conf 没有列出的热点也可以通过 NZone beacons 使用。下面的 flags是由 hotspot.conf文件中， "IsXXX"字段组合而来。（包括 IsSetToFW）. 下表中, "hotspot.conf版本"表示列表中增加热点的title版本 .(~~"None" 表示热点一直没有在 hotspot.conf 中列出,但是NZone beacons可用.~~ "Unknown" 表示在v1024中已经存在了,但是不清楚到底是在那个版本中添加的.)		hotspot.conf 没有列出的热点也可以通过 NZone beacons 使用。下面的 flags是由 hotspot.conf文件中， "IsXXX"字段组合而来。（包括 IsSetToFW）. 下表中, "hotspot.conf版本"表示列表中增加热点的title版本 .("Unknown" 表示在v1024中已经存在了,但是不清楚到底是在那个版本中添加的.)
			==== NZone hotspot.conf 的热点列表 ====
	{\| class="wikitable"		{\| class="wikitable"
	! SSID !! 加密类型 !! 地区 \|\| ServiceName !! Flags !! Hotspot.conf版本		! SSID !! 加密类型 !! 地区 \|\| ServiceName !! Flags !! Hotspot.conf版本
Line 243:		Line 253:
	\|-		\|-
	\| FREESPOT \|\| None \|\| JPN \|\| FREESPOT \|\| 1, 1, 1, 1, 1 \|\| Unknown		\| FREESPOT \|\| None \|\| JPN \|\| FREESPOT \|\| 1, 1, 1, 1, 1 \|\| Unknown
	\|-
	~~\| [http://webapp.7spot.jp/howtoconnect.html 7SPOT] \|\| 无 \|\| JPN \|\| 7-11 \|\| ? \|\| None (LAN-only hostname used)~~
	\|-		\|-
	\| [http://www.tsutaya.co.jp/tc/game/deds/about.html TSUTAYA] \|\| 无 \|\| JPN \|\| TSUTAYA \|\| ? \|\| Unknown		\| [http://www.tsutaya.co.jp/tc/game/deds/about.html TSUTAYA] \|\| 无 \|\| JPN \|\| TSUTAYA \|\| ? \|\| Unknown
	\|-
	~~\| noasp03 \|\| 无 \|\| USA \|\| NOA (Nintendo event at GDC) \|\| ? \|\| None~~
	\|-		\|-
	\| Wayport_Access \|\| 无 \|\| USA \|\| McDonalds \|\| ? \|\| After v1024		\| Wayport_Access \|\| 无 \|\| USA \|\| McDonalds \|\| ? \|\| After v1024
	\|-
	~~\| BestBuy \|\| 无 \|\| USA \|\| BestBuy \|\| ? \|\| None~~
	\|-		\|-
	\| Boingo Hotspot \|\| 无 \|\| USA \|\| Boingo \|\| ? \|\| Unknown		\| Boingo Hotspot \|\| 无 \|\| USA \|\| Boingo \|\| ? \|\| Unknown
Line 261:		Line 265:
	\|-		\|-
	\| [http://www.free-hotspot.com/ free-hotspot.com] \|\| 无 \|\| EUR \|\| free-hotspot.com \|\| ? \|\| After v1024		\| [http://www.free-hotspot.com/ free-hotspot.com] \|\| 无 \|\| EUR \|\| free-hotspot.com \|\| ? \|\| After v1024
			\|-
			\| Bestbuy \|\| WPA2-PSK \|\| USA \|\| Bestbuy \|\| \|\| After v1024
			\|}
	\|}		\|}

			==== 仅通过 NZone beacons 接入的 NZone hotspots ====
			{\| class="wikitable"
			! SSID !! Security !! Region/country \|\| ServiceName \|\| Notes
			\|-
			\| noasp03 \|\| None \|\| USA \|\| NOA (Nintendo event at GDC) \|\|
			\|-
			\| BestBuy \|\| None \|\| USA \|\| BestBuy \|\|
			\|-
			\| [http://webapp.7spot.jp/howtoconnect.html 7SPOT] \|\| None \|\| JPN \|\| 7-11 \|\| A LAN-only hostname used is for the retailer's site linked to from the NZone server.
			\|}
			The above hotspots can only be accessed by broadcasting NZone beacons which contain the encrypted Nintendo tag data.

			==== Hotspot Notes ====

	* 可以通过这些值,配置你的路由器/笔记本/手机为一个Nintendo Zone.		* 可以通过这些值,配置你的路由器/笔记本/手机为一个Nintendo Zone.

Syphurith: help translation

2013-03-31T07:15:11Z

help translation

← Older revision		Revision as of 11:15, 31 March 2013
Line 69:		Line 69:
	AC系统applet从"conf:/hotspot.conf"加载NZone无线热点的列表,其中"conf:" 是 000400DB00010502 文档的内容. 这是一个使用 LF换行的CSV文件,每个NZone的全部beacon信息也存储在这个文件中. 这个文件列出多至100个热点.(title版本v1024的hotspot.conf列出了52个热点). 这个格式可以使用[https://github.com/yellows8/hotspotconf-tool hotspotconf-tool]解析.		AC系统applet从"conf:/hotspot.conf"加载NZone无线热点的列表,其中"conf:" 是 000400DB00010502 文档的内容. 这是一个使用 LF换行的CSV文件,每个NZone的全部beacon信息也存储在这个文件中. 这个文件列出多至100个热点.(title版本v1024的hotspot.conf列出了52个热点). 这个格式可以使用[https://github.com/yellows8/hotspotconf-tool hotspotconf-tool]解析.

	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~~ '='.		CSV开头部分是内部记录区域。在那之后的就是hotspot的记录，每行一个hotspot的区域。使用Base64加密的区域，行尾的补齐字符是'*'而不是'='。

	IsBrowser, IsShop, IsGame 可能决定了是否能够使用 [[Internet Browser]], [[eShop]], 多人联机游戏的功能. IsSetToFW通常为0.		IsBrowser, IsShop, IsGame 可能决定了是否能够使用 [[Internet Browser]], [[eShop]], 多人联机游戏的功能. IsSetToFW通常为0.
Line 110:		Line 110:
	\| IsVendorIE		\| IsVendorIE
	\| 1		\| 1
	\| ~~热点 flag~~,0/1		\| 热点标志,0/1
	\|-		\|-
	\| IsBackground		\| IsBackground
	\| 1		\| 1
	\| ~~热点 flag~~,0/1		\| 热点标志,0/1
	\|-		\|-
	\| IsBrowser		\| IsBrowser
	\| 1		\| 1
	\| ~~热点 flag~~,0/1		\| 热点标志,0/1
	\|-		\|-
	\| IsShop		\| IsShop
	\| 1		\| 1
	\| ~~热点 flag~~,0/1		\| 热点标志,0/1
	\|-		\|-
	\| IsGame		\| IsGame
	\| 1		\| 1
	\| ~~热点 flag~~,0/1		\| 热点标志,0/1
	\|-		\|-
	\| IsSetToFW		\| IsSetToFW
	\| 1		\| 1
	\| ~~热点 flag~~,0/1		\| 热点标志,0/1
	\|}		\|}

T: /* 无线热点 */

2013-03-31T01:38:06Z

无线热点

← Older revision	Revision as of 05:38, 31 March 2013
(No difference)

T: /* Hotspots */

2013-03-31T01:19:22Z

Hotspots

Show changes

T at 01:54, 31 March 2013

2013-03-31T00:54:14Z

← Older revision		Revision as of 03:54, 31 March 2013
Line 11:		Line 11:

	=== Beacon payload format ===		=== Beacon payload format ===
	~~这些应该是DS~~(i) ~~NZone format except for the unknown fields~~, ~~（WPA2不支持）。3DS~~ NZone不像DS(i)一样有锁区。		除去未知部分,3DS Nzone应该是与DS(i) NZone格式相同的, （不支持WPA2）。3DS NZone不像DS(i)一样有锁区。

	{\| class="wikitable" border="1"		{\| class="wikitable" border="1"
Line 29:		Line 29:
	\| 0x2a		\| 0x2a
	\| 2		\| 2
	\| ~~This u16 was always one in all dumps~~, ~~unknown what this is. This isn't used by the client~~.		\| 这个u16在所有dump中相同,但是不清楚是什么.客户端没有使用它
	\|-		\|-
	\| 0x2c		\| 0x2c
	\| 24		\| 24
	\| ~~Some~~ UTF-16 ~~ServiceName~~. "BestBuy"		\| 一些 UTF-16 编码的服务名.比如 "BestBuy"
	\|-		\|-
	\| 0x44		\| 0x44
	\| 32		\| 32
	\| ~~AP crypto key, if any.~~		\| AP加密密钥(如果存在的话)
	\|-		\|-
	\| 0x64		\| 0x64
	\| 1		\| 1
	\| ~~Unknown~~, ~~not used by the~~ DS(i) ~~client~~. ~~For 3DS this is 0x1~~, ~~for~~ DS(i) ~~this is 0x0~~.		\| 未知,DS(i)客户端未使用.3DS的值为0x1, DS(i)的值为0x0.
	\|-		\|-
	\| 0x65		\| 0x65
	\| 1		\| 1
	\| ~~AP crypto key type~~: 0) ~~Open~~ 1) WEP-64 2) WEP-128 3) WEP-152		\| AP密钥类型: 0) 开放 1) WEP-64 2) WEP-128 3) WEP-152
	\|-		\|-
	\| 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.~~		\| 未知 flags, 3DS的值为0x1e,DS(i)的值为0x3. 客户端似乎没有使用第0位和第1位的值. DS(i)客户端使用了第2位的值,但是仍然不明白是什么. ( 第0/1/2位是二进制的地位,bit0/bit1/bit2)
	\|-		\|-
	\| 0x67		\| 0x67
	\| 5		\| 5
	\| ~~Padding.~~		\| 填充
	\|-		\|-
	\| 0x6c		\| 0x6c
	\| 2		\| 2
	\| ~~Unknown~~, ~~with 3DS this is zero but for~~ DS(i) ~~this was 0x428~~.		\| 未知.3DS为0, DS(i)为0x428.
	\|-		\|-
	\| 0x6e		\| 0x6e
	\| 2		\| 2
	\| ~~CRC16 over the whole payload excluding CRC offset~~, ~~initval is 0~~.		\| CRC偏移以外的整个payload的CRC16, initval为0.
	\|}		\|}

	== ~~Wi-Fi Hotspots~~ ==		== 无线热点 ==

	=== Hotspot.conf ~~format~~ ===		=== Hotspot.conf 格式 ===
	~~The list of NZone hotspots is loaded from~~ "conf:/hotspot.conf" ~~by the AC system applet~~, ~~where~~ "conf:" ~~is the~~ 000400DB00010502 ~~content archive~~. ~~This is a CSV file~~, ~~with LF-style newlines. All of the information stored in the NZone beacon is also stored in this file for each hotspot~~. ~~This file can list a max of 100 hotspots~~.(~~As of title version v1024, hotspot~~.~~conf lists 52 hotspots~~) ~~This format can be parsed by~~ [https://github.com/yellows8/hotspotconf-tool hotspotconf-tool].		AC系统applet从"conf:/hotspot.conf"加载NZone无线热点的列表,其中"conf:" 是 000400DB00010502 文档的内容. 这是一个使用 LF换行的CSV文件,每个NZone的全部beacon信息也存储在这个文件中. 这个文件列出多至100个热点.(title版本v1024的hotspot.conf列出了52个热点). 这个格式可以使用[https://github.com/yellows8/hotspotconf-tool hotspotconf-tool]解析.

	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 '='.

T: translate 10%

2013-03-30T10:54:18Z

translate 10%

New page

'''Nintendo Zone''' 是 DS Download Stations 的延续，提供发售游戏的独家内容，游戏视频，截图等等。2012年2月6日之前，已经可以从这里下载demo游戏，demo游戏可以从eshop的服务器下载并安装到SD卡中。Nintendo Zone提供的试玩版与eshop相同，尝试下载其他锁区的应用时会出现错误。美国百思买和其他一些零售商拥有Nintendo Zone，它们看起来与 DS(i) [http://dsibrew.org/wiki/Nintendo_Zone NZone]不同。百思买那里可以访问到的大部分Nintendo Zone内容是eshop已有的。

就像DSi一样，当你打开3DS时，主机会检查是否有隐藏的NZone（在美国NZone总是可用的），NZone 的 title 会提示发现了Nzone。DSi的title存储在NAND中，但是只在Nzone的覆盖范围时title才可见（即使拔掉SD卡也没关系）。3DS只有未连接互联网时，才会检查是否处于NZone覆盖范围。连接过一个NZone AP后, 标志就被缓存了，直到与AP断开连接。

修改DSi nzone广播的信标为3DS Best Buy ApNum后, DSi launcher中NZone的title图标不会闪烁，但是这个title仍然处于半工状态（semi-work）。 NZone title可以连接到服务器, 显示出demo按钮，百思买，WFC配置，但是选择百思买服务并加载一段时间后，NZone会显示一个错误。（可能有不支持的HTML标签之类的东西）

* '''Nintendo Zone'''和"'nzone'" 暂译为"'任天堂乐园'"或者“‘天堂乐园’”。但是为了便于查阅，文中均未作翻译。

== 概述 ==
NZone浏览界面看起来和3DS网络浏览器很相似，所以它可能由浏览器修改而来。（从视频支持，移动芯片推断）除去明文部分的未知变化，Nzone的信标加密方式与先前相同。3DS仅在信标正确才会检测并设置NZone /w NZone 图标闪烁/可用的状态。DSi不检查这些。3DS可用使用DS(i) NZone，但是只能在NZone的title允许时才行。有DS(i)信标时，3DS能连接到互联网而NZone图标不闪烁。NZone title载入之后也能工作，但是由于向服务器发送了与DSi不同的URL请求，所以会返回错误。

=== Beacon payload format ===
这些应该是DS(i) NZone format except for the unknown fields, （WPA2不支持）。3DS NZone不像DS(i)一样有锁区。

{| class="wikitable" border="1"
|-
! 偏移
! 大小
! 描述
|-
| 0x00
| 32
| AP SSID.
|-
| 0x20
| 10
| 请求连接到服务器的ApNum。这取决于你在使用哪个NZone。 Apnum的结构: RSSCCTTLLL. R是区域代码, SS是ServiceID. CC是国家代码（两个字母），TT是省/州代码（两个字母）, LLL是locationID。区域代码: 0)日本 1)美国 2/3)欧洲 4)韩国 5)中国. LLL在日本以外的地区均为0, 在日本境内就取决于具体的NZone热点了。TT仅在日本使用，其他地区为0
|-
| 0x2a
| 2
| This u16 was always one in all dumps, unknown what this is. This isn't used by the client.
|-
| 0x2c
| 24
| Some UTF-16 ServiceName. "BestBuy"
|-
| 0x44
| 32
| AP crypto key, if any.
|-
| 0x64
| 1
| Unknown, not used by the DS(i) client. For 3DS this is 0x1, for DS(i) this is 0x0.
|-
| 0x65
| 1
| AP crypto key type: 0) Open 1) WEP-64 2) WEP-128 3) WEP-152
|-
| 0x66
| 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.
|-
| 0x67
| 5
| Padding.
|-
| 0x6c
| 2
| Unknown, with 3DS this is zero but for DS(i) this was 0x428.
|-
| 0x6e
| 2
| CRC16 over the whole payload excluding CRC offset, initval is 0.
|}

== Wi-Fi Hotspots ==

=== Hotspot.conf format ===
The list of NZone hotspots is loaded from "conf:/hotspot.conf" by the AC system applet, where "conf:" is the 000400DB00010502 content archive. This is a CSV file, with LF-style newlines. All of the information stored in the NZone beacon is also stored in this file for each hotspot. This file can list a max of 100 hotspots.(As of title version v1024, hotspot.conf lists 52 hotspots) This format can be parsed by [https://github.com/yellows8/hotspotconf-tool hotspotconf-tool].

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.

==== Records ====
{| class="wikitable" border="1"
|-
! Record name
! Field max len
! Field data
|-
| Interval
| Arbitrary
| Decimal interval, unknown (usually 20)
|-
| ServiceName
| 0x40 (after decode)
| Hotspot Base64-encoded ASCII ServiceName
|-
| Url
| 0x80 (after decode)
| Hotspot Base64-encoded URL (usually unused, optionally links to the retailer's website)
|-
| Ssid
| 32 (after decode)
| Hotspot Base64-encoded SSID
|-
| SecurityKey
| 0x40 (after decode)
| Hotspot Base64-encoded encryption key
|-
| SecurityMode
| 1
| Decimal hotspot encryption type (0 for none)
|-
| ApNum
| 10
| Hotspot ApNum, see above NZone beacon info
|-
| IsVendorIE
| 1
| Decimal hotspot flag, can be either 1 or 0
|-
| IsBackground
| 1
| Decimal hotspot flag, can be either 1 or 0
|-
| IsBrowser
| 1
| Decimal hotspot flag, can be either 1 or 0
|-
| IsShop
| 1
| Decimal hotspot flag, can be either 1 or 0
|-
| IsGame
| 1
| Decimal hotspot flag, can be either 1 or 0
|-
| IsSetToFW
| 1
| Decimal hotspot flag, can be either 1 or 0
|}

=== Hotspots ===
Hotspots not listed in hotspot.conf can only be used via NZone beacons. The below flags is the combined "IsXXX" fields from hotspot.conf, excluding IsSetToFW. The below hotspot.conf version specifies what title version that hotspot was added to the list, if at all.("None" indicates that it's not listed in hotspot.conf at all and can only be used with NZone beacons. "Unknown" indicates that the hotspot is present in v1024, but it's unknown whether it was in the previous version.)
{| class="wikitable"
! SSID !! Security !! Region/country || ServiceName !! Flags !! Hotspot.conf version
|-
| wifine || None || JPN || [http://wifine.jp/ Wifine] || 1, 1, 1, 1, 1 || Unknown
|-
| NintendoSpotPass1 || None || EUR || Nintendo || 1, 1, 1, 1, 1 || Unknown
|-
| NintendoSpotPass2 || None || EUR || Nintendo || 1, 0, 0, 0, 1 || Unknown
|-
| attwifi || None || USA || AT&T || 1, 1, 1, 1, 1 || Unknown
|-
| SIMON WiFi || None || USA || Simon Malls || 1, 1, 1, 1, 1 || Unknown
|-
| noasp01 || None || USA || NOA (Nintendo events) || 1, 1, 1, 1, 1 || Unknown
|-
| noasp02 || None || USA || NOA (Nintendo events) || 1, 1, 1, 1, 1 || Unknown
|-
| Telekom || None || EUR (Germany) || Telekom || 1, 0, 0, 0, 1 || Unknown
|-
| Telekom_ICE || None || EUR (Germany) || Telekom || 1, 0, 0, 0, 1 || Unknown
|-
| Guglielmo || None || IT || Guglielmo || 1, 1, 1, 1, 1 || Unknown
|-
| ASTRO || None || IT || Guglielmo || 1, 1, 1, 1, 1 || Unknown
|-
| Banca Sella WiFi Clienti || None || IT || Guglielmo || 1, 1, 1, 1, 1 || Unknown
|-
| confindustria || None || IT || Guglielmo || 1, 1, 1, 1, 1 || Unknown
|-
| Grand || None || IT || Guglielmo || 1, 1, 1, 1, 1 || Unknown
|-
| Guglielmo Rimini WiFi || None || IT || Guglielmo || 1, 1, 1, 1, 1 || Unknown
|-
| GuglielmoDallaRosaPrati || None || IT || Guglielmo || 1, 1, 1, 1, 1 || Unknown
|-
| Hotels || None || IT || Guglielmo || 1, 1, 1, 1, 1 || Unknown
|-
| L.Bettolo || None || IT || Guglielmo || 1, 1, 1, 1, 1 || Unknown
|-
| LecceWireless || None || IT || Guglielmo || 1, 1, 1, 1, 1 || Unknown
|-
| P.zza Nicoloso || None || IT || Guglielmo || 1, 1, 1, 1, 1 || Unknown
|-
| PortoDiTrieste || None || IT || Guglielmo || 1, 1, 1, 1, 1 || Unknown
|-
| Comune-Na Piazze WIFI || None || IT || Guglielmo || 1, 1, 1, 1, 1 || Unknown
|-
| WiFi_Stampa || None || IT || Guglielmo || 1, 1, 1, 1, 1 || Unknown
|-
| KPN || None || EUR (NL) || KPN || 1, 1, 0, 1, 1 || Unknown
|-
| METEOR || None || FR || Meteor || 1, 0, 0, 0, 1 || Unknown
|-
| MCDONALDS || None || FR || Meteor || 1, 0, 0, 0, 1 || Unknown
|-
| AREA_by_METEOR || None || FR || Meteor || 1, 0, 0, 0, 1 || Unknown
|-
| PATaPAIN_by_METEOR || None || FR || Meteor || 1, 0, 0, 0, 1 || Unknown
|-
| CASINO_by_METEOR || None || FR || Meteor || 1, 0, 0, 0, 1 || Unknown
|-
| all_seasons_by_METEOR || None || FR || Meteor || 1, 0, 0, 0, 1 || Unknown
|-
| ADAGIO_by_METEOR || None || FR || Meteor || 1, 0, 0, 0, 1 || Unknown
|-
| PULLMAN_by_METEOR || None || FR || Meteor || 1, 0, 0, 0, 1 || Unknown
|-
| Best_Western_by_METEOR || None || FR || Meteor || 1, 0, 0, 0, 1 || Unknown
|-
| CreditAgricole_by_METEOR || None || FR || Meteor || 1, 0, 0, 0, 1 || Unknown
|-
| IBIS_by_METEOR || None || FR || Meteor || 1, 0, 0, 0, 1 || Unknown
|-
| MERCURE_by_METEOR || None || FR || Meteor || 1, 0, 0, 0, 1 || Unknown
|-
| Telefonica || None || ES || Telefonica || 1, 0, 0, 1, 1 || Unknown
|-
| GOWEXWiFi || None || ES || Gowex || 1, 0, 0, 1, 1 || Unknown
|-
| OurenseWiFi || None || ES || Gowex || 1, 0, 0, 1, 1 || Unknown
|-
| RED_LIBRE_AVILES_WILOC || None || ES || Gowex || 1, 0, 0, 1, 1 || Unknown
|-
| GIJON WIFI || None || ES || Gowex || 1, 0, 0, 1, 1 || Unknown
|-
| 01MIERESWIFI || None || ES || Gowex || 1, 0, 0, 1, 1 || Unknown
|-
| 01EibarWifi || None || ES || Gowex || 1, 0, 0, 1, 1 || Unknown
|-
| WIFIBUR || None || ES || Gowex || 1, 0, 0, 1, 1 || Unknown
|-
| ValladolidWiFi || None || ES || Gowex || 1, 0, 0, 1, 1 || Unknown
|-
| 01PuertoDelRosarioWiFi || None || ES || Gowex || 1, 0, 0, 1, 1 || Unknown
|-
| PT-WIFI || None || PT || PTWiFi || 1, 0, 0, 0, 1 || Unknown
|-
| FON_ZON_FREE_INTERNET || None || PT || ZON || 1, 0, 0, 0, 1 || Unknown
|-
| [https://www.thecloud.net/free-wifi/support/faqs/ WiFi Zone - The Cloud] || None || EUR (GB) || [https://www.thecloud.net/ The Cloud] || 1, 1, 1, 1, 1 || Unknown
|-
| [https://www.thecloud.net/free-wifi/support/faqs/ Mycloud] || None || EUR (GB) || [https://www.thecloud.net/ The Cloud] || 1, 1, 1, 1, 1 || Unknown
|-
| [https://www.thecloud.net/free-wifi/support/faqs/ WLAN Zone - The Cloud] || None || EUR (GB) || [https://www.thecloud.net/ The Cloud] || 1, 0, 0, 0, 1 || Unknown
|-
| [https://www.thecloud.net/free-wifi/support/faqs/ _The Cloud] || None || EUR (GB) || [https://www.thecloud.net/ The Cloud] || ? || After v1024
|-
| FREESPOT || None || JPN || FREESPOT || 1, 1, 1, 1, 1 || Unknown
|-
| [http://webapp.7spot.jp/howtoconnect.html 7SPOT] || None || JPN || 7-11 || ? || None (LAN-only hostname used)
|-
| [http://www.tsutaya.co.jp/tc/game/deds/about.html TSUTAYA] || None || JPN || TSUTAYA || ? || Unknown
|-
| noasp03 || None || USA || NOA (Nintendo event at GDC) || ? || None
|-
| Wayport_Access || None || USA || McDonalds || ? || After v1024
|-
| BestBuy || None || USA || BestBuy || ? || None
|-
| Boingo Hotspot || None || USA || Boingo || ? || Unknown
|-
| ibahn || None || USA || iBAHN || ? || Unknown
|-
| BELLWIFI@MCDONALDS || None || USA (Canada) || Bell || ? || After v1024
|-
| [http://www.free-hotspot.com/ free-hotspot.com] || None || EUR || free-hotspot.com || ? || After v1024
|}

* These can be configured on you own router/laptop/phone to identify as a Nintendo Zone.
* You will need an available Internet connection to be able to connect to the servers.
* After connecting the Wi-Fi network, the page displayed will be of the device's region. (Some regions, such as Australia, will not be redirected to a local Nintendo Zone page as there are no plans to introduce Nintendo Zone(s) to that region. If a 3DS has its region set to one of these regions where there are no plans to introduce a Nintendo Zone, they will be brought to the Nintendo Zone of the region of the SSID)
* If you intend to create a permanent, private, Nintendo Zone WiFi spot. It is recommended that you enable MAC address filtering to only allow your devices. As using any form of encryption will prevent the Nintendo Zone WiFi spot from working with your 3DS.