Changes

== 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. The Best Buy NZone uses the same authentication parameter at all stores /w NZone. Accessing the server via curl does not work correctly, the server returns old content. This is likely because the NZone title sends new/different params to the server.

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. The Best Buy NZone uses the same authentication parameter at all stores /w NZone. 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 ===

| 0x2c

| 0x2c

| 24

| 24

| Some UTF-16 retailer ID string can include the country, unknown what this is but it's not used by the client DS(i). "BestBuy"

| Some UTF-16 ServiceName. "BestBuy"

|-

|-

| 0x44

| 0x44

== Wi-Fi Hotspots ==

== Wi-Fi Hotspots ==

{| class="wikitable"

{| class="wikitable"

|}

|}

* These can be configured on you own router/laptop/phone to identify as a nintendo zone.

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

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

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

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