Well, Nicholas and Natasha got a Nintendo Wii for Christmas. It really is a very interesting gaming console. The basic console is not that unusual, but the remote unit uses an accelerometer to steer the pointer and there are some games that capitalize on this nicely.
It also supports internet connectivity, but this is not uses to much effect. Setting it up caused a few problems (erro 51130, 52230, etc.).
To allow it to use the internet, I had to disable WEP on our wireless box. It is capable or WEP, but there is clearly something "funny" about it; I am pretty sure it needs the WEP key in hexadecimal, and I was entering it in ASCII.
The error 52230 seems to be a result of the Wii sending a TCP SYN request to conntest.nintendowifi.net on port 80 (the usualy port for HTTP), but not getting a response SYN-ACK response back. This is a typical symptom of a failed internet connection. Such an error is probably not due to a firewall rule, but can be caused by other kinds of router security such as restrictions on access to only registered computers.
When it connects it looks for conntest.nintendowifi.net (connection testing) and gets a simple test HTTP page. A bit later is asks for wiinat.available.gs.nintendowifi.net, which it contacts using UDP -- this may only happen if the above fails. After that, it asks for wiinat.natreg1.gs.nintendowifi.net (as well as natreg2 and netreg3).
Later it does a bunch of UDP traffic to 207.28.11.12-13, which I
think it looked up from the previous UDP traffic.
The wii shop is at the web site oss.shop.wii.com. Communication with it seems to place via https (encrypted http). The weather connection seems to be with weather.wapp.wii.com Simply vising this site shows nothing, but my wii asks for "http://weather.wapp.wii.com/1/018/forecast.bin" and gets an actual file (which I can not decipher yet).
