BigRedPimp no DSDev

Recently, I bought myself a Buffalo Tech WHR-G54S router so I could fix some connection issues I was having with my old router as well as giving myself a new toy to play with. I decided on Buffalo not only because of some good reviews I’ve read but also the fact that it supports their AOSS technology. AOSS might sound familiar to those of you who read my Nintendo Wi-Fi post some months back. AOSS allows you to configure any supporting client device at the touch of a button (or 2). Why am I bringing this up now? I’d like to show off one of the little-used features of the NDS’s WFC config screen.

To give you an idea how it works, let me step you through the process I used.

1. Install the host device (in this case, the router)
2. Tweak your network settings as you see fit
3. Go into your NDS’s WFC config screen (my game of choice was Lost Magic but any WFC-enabled game will do) and select an empty profile
4. You should have 3 buttons (duh) but the only one that is of interest to you is the AOSS one
5. Tap the button and then hold the AOSS button on your host device
6. The host and the NDS will start talking to each other to make sure they both support AOSS
7. Once they’re done, the host will send over the Wi-Fi connection config data and store it in the selected profile
8. The NDS will then verify that the connection works
9. That’s it, unless there was some sort of funky error. For that, see your manual/tech/guru/etc

That’s it, really. Now onto the reason for this post.

When setting up my AOSS profile, I noticed that instead of the normal “Ready” text on the button, it had an AOSS icon. This made me believe that somewhere in the profile data lies an identifier that says if the profile is AOSS or not. Oh how I didn’t expect to find as much as I did.

Using the information from the User Settings page of the NDSTech Wiki, I decided to dive in head first. There was a good chunk of information missing and I figured I could find the identifier myself. Turns out that instead of finding just the identifier, I completed a good chunk of the missing information (about 69 bytes worth), thanks to AOSS. Rather than just dancing around the subject, I’ll post my findings here until they can be added to the Wiki. There’s still a bit more left to figure out (for instance, the 14 bytes starting at 0xF0 bother me) but that’ll come in due time. Follow the link below for the technical stuff.

0×00 - 64 bytes - 00s
0×40 - 32 bytes - SSID
0×60 - 32 bytes - SSID for WEP64 on AOSS host (each security level has its own SSID)
0×80 - 16 bytes - WEP key #0
0×90 - 16 bytes - WEP key #1
0xA0 - 16 bytes - WEP key #2
0xB0 - 16 bytes - WEP key #3
0xC0 - 04 bytes - IP Address
0xC4 - 04 bytes - Gateway
0xC8 - 04 bytes - Primary DNS
0xCC - 04 bytes - Secondary DNS
0xD0 - 01 bytes - Subnet Mask
0xD1 - 20 bytes - WEP64 key on AOSS host (see WEP64 SSID note above)
0xE5 - 01 bytes - ??
0xE6 - 01 bytes - WEP Mode
0xE7 - 01 bytes - Status (0×00 - normal, 0×01 - AOSS, 0xFF - deleted)
0xE8 - 07 bytes - ??
0xEF - 01 bytes - Seems to be randomly set, may be priority
0xF0 - 14 bytes - ??
0xFE - 02 bytes - CRC16 of 0×00 through 0xFD

Tags: General //