Interestingly enough, the normal “off” with the Wii, is actually more like “standby” and is live on the network, checking for messages, and doing whatever Wiis do. This will be interesting a little later on.
While dorking around with my laptop in the living room doing some of my typical nerd things, I notice that I keep disassociating with my wifi network. There’s a bunch of competing wifi networks here, so I’ve become accustomed to a fair amount of fail related to it. Wifi is a convenience, but it was happening so much I thought that someone was using a deauthentication attack on my client.
I pulled the logs on my AP and saw this:
Well that looked a little slow for a typical attack. What else was happening?
The key was getting rotated every couple minutes and all the active clients were resetting their connections. What gives? What’s going on here?
Ok. So I threw laptop in passive mode and snooped on network traffic. So who’s this guy that’s flapping it’s connection every 10 seconds?
A Nintendo manufacturer MAC prefix? My Wii in suspended mode is breaking my WPA2 network? What the hell?
So apparently the Wii uPnP requests two TCP and one UDP ports on the router repeatedly, while in suspend mode, and the Apple Airport Extreme (that’s an 802.11n AP in mixed g/n mode) freaks out. This is clearly a new feature as I only updated my Wii’s firmware last week and would have been too annoying for me to miss previously.
In case you were wondering why your Wii was freaking out on your Airport or Airport Extreme network, hopefully you’ll have been able to find this and can troubleshoot further.
It might be the uPnP support for NAT port mapping, but my fix is to turn off the Wii fully when not in use. Hold down the power button until the LED is red instead of orange. I’m sure more people will complain and one or the other will update their firmware to compensate soon enough.