Wii vs DHCP

A while ago I was looking at my router’s log and noticed a funny thing related to DHCP entries, namely those of Nintendo Wii. Apparently Wii acts a little weird when it comes to DHCP, making constant queries to the server on short intervals.

My Wii has the WiiConnect24 on, so it should make Internet connections regularly, no problem there. There’s just no need to bombard the router with address queries every few minutes. Compared to other devices on my network, Wii sure makes itself heard.

If Wii has no IP-address set to it, the ideal procedure would be to make a query, accept the address and hold it until the lease expires or it’s otherwise necessary to make a new query. Wii seems to think this method is too obvious and keeps on making new queries when it feels like it. Now, once the server receives another query from Wii, it (naturally) gives it the same address again, since the address hasn’t expired and the client is the same one.

Wii is not still not satisfied, however, and continues this redundant process of DHCP queries. I noticed this behaviour a long ago, shortly after I bought Wii. Then I thought it might perhaps have something to do with the router or DHCP settings and didn’t give it much thought. However when I recently changed my primary router, Wii’s behaviour caught my eye once again.

The previous router is still working as a wireless access point, but no longer handles the DHCP-queries. Those duties now belong to the new router. Wii’s behaviour towards DHCP has remained the same despite the change in DHCP server. The IP-address lease period is 72 hours and after 36 hours have passed the client should try to renew the lease. Wii apparently doesn’t know how read a clock.

Here’s a portion of Wii’s network activity log of six hours, 13.00-19.00. Now, I’m not going to print the whole thing, would serve no purpose. I’ll clip a few entries from the between because – besides time – each entry is identical to the previous and following one.

10/16/2008 18:58:45 DHCP server assigns 192.168.11.10 to Wii
10/16/2008 18:47:44 DHCP server assigns 192.168.11.10 to Wii
10/16/2008 18:40:36 DHCP server assigns 192.168.11.10 to Wii
10/16/2008 18:36:42 DHCP server assigns 192.168.11.10 to Wii
10/16/2008 18:34:36 DHCP server assigns 192.168.11.10 to Wii
10/16/2008 18:32:41 DHCP server assigns 192.168.11.10 to Wii
[ 18.00-18.30 entries cut ]
10/16/2008 17:57:26 DHCP server assigns 192.168.11.10 to Wii
10/16/2008 17:55:15 DHCP server assigns 192.168.11.10 to Wii
10/16/2008 17:50:18 DHCP server assigns 192.168.11.10 to Wii
10/16/2008 17:40:08 DHCP server assigns 192.168.11.10 to Wii
10/16/2008 17:30:05 DHCP server assigns 192.168.11.10 to Wii
[ 17.00-17.30 entries cut ]
10/16/2008 16:59:56 DHCP server assigns 192.168.11.10 to Wii
10/16/2008 16:50:20 DHCP server assigns 192.168.11.10 to Wii
10/16/2008 16:49:51 DHCP server assigns 192.168.11.10 to Wii
10/16/2008 16:39:42 DHCP server assigns 192.168.11.10 to Wii
10/16/2008 16:36:39 DHCP server assigns 192.168.11.10 to Wii
[ 15.00-16.30 entries cut ]
10/16/2008 14:58:53 DHCP server assigns 192.168.11.10 to Wii
10/16/2008 14:51:52 DHCP server assigns 192.168.11.10 to Wii
10/16/2008 14:49:49 DHCP server assigns 192.168.11.10 to Wii
10/16/2008 14:48:52 DHCP server assigns 192.168.11.10 to Wii
10/16/2008 14:47:52 DHCP server assigns 192.168.11.10 to Wii
10/16/2008 14:45:47 DHCP server assigns 192.168.11.10 to Wii
10/16/2008 14:43:48 DHCP server assigns 192.168.11.10 to Wii
10/16/2008 14:38:46 DHCP server assigns 192.168.11.10 to Wii
[ 14.00-14.30 entries cut ]
10/16/2008 13:58:25 DHCP server assigns 192.168.11.10 to Wii
10/16/2008 13:55:23 DHCP server assigns 192.168.11.10 to Wii
10/16/2008 13:48:20 DHCP server assigns 192.168.11.10 to Wii
10/16/2008 13:44:18 DHCP server assigns 192.168.11.10 to Wii
10/16/2008 13:42:17 DHCP server assigns 192.168.11.10 to Wii
10/16/2008 13:29:11 DHCP server assigns 192.168.11.10 to Wii

There. Based on the logs it would seem that Wii queries IP-address from the server more than 10 times per hour. Generally the interval is less than 10 minutes.

As a comparison, here’s iPod Touch’s entires from the same time period:

10/16/2008 19:52:49 DHCP server assigns 192.168.11.7 to iPod-Touch
10/16/2008 19:52:49 DHCP server assigns 192.168.11.7 to iPod-Touch
10/16/2008 19:52:49 DHCP server assigns 192.168.11.7 to iPod-Touch
10/16/2008 19:52:49 DHCP server assigns 192.168.11.7 to iPod-Touch
10/16/2008 18:52:43 DHCP server assigns 192.168.11.7 to iPod-Touch
10/16/2008 17:52:43 DHCP server assigns 192.168.11.7 to iPod-Touch
10/16/2008 16:52:34 DHCP server assigns 192.168.11.7 to iPod-Touch
10/16/2008 15:52:44 DHCP server assigns 192.168.11.7 to iPod-Touch
10/16/2008 14:52:44 DHCP server assigns 192.168.11.7 to iPod-Touch
10/16/2008 13:52:44 DHCP server assigns 192.168.11.7 to iPod-Touch

We can see that iPod Touch makes a DHCP query for the server approximately every hour. While even this is much considering the lease period, in this light Wii’s behaviour is rather odd. Especially since the DHCP server has no special settings for either device.

Then we come to the million dollar questions, what’s the point of all this & who cares? To be frank, the answers to these are probably “nothing” and “no one”. Just a curiosity, although I’m not the only one who’s wondered the same thing.

This makes me wonder if the behaviour is simply a flaw in Wii’s DHCP client, an intentional choice by Nintendo or something completely different. Let’s face it, iPod Touch makes 10 DHCP requests on the same time period where Wii makes well over 60 queries.

Makes also wonder how this affects router performance in a situation where, let’s say multiple Wii’s have the WiiConnect24 on and keep on pounding the same DHCP server constantly. Nonetheless, the traffic is redundant and keeps on filling my router log files for no good reason.

>> Return to games
> Return to main page

Loki

Asioita nyt myös suomeksi, yllä olevan otsikon alla. Jahka jaksan innostua lisää kirjoittamaan siis.

That Disc Sure Is Dirty

When compared to today’s console games, the 20 year old ones might look like crap, but they have a few aces up their sleeve (such as quality and playability). Still, I’m not here to start rambling about modern games with no soul or challenge. I’m here to ramble on modern games not working, introducing the modern players to such joys as freezing, requiring constant updates and bugs.

Granted, these have been issues PC-gamers – myself included – are used to, hardware incompabilities, crashes, flawed code and such. Consoles used to be carefree – never heard of anyone not completing, like, Super Mario Bros because the game kept exiting to title screen every time you picked up a mushroom. That just didn’t happen on consoles.

Continue reading

Just Make Them Work

When compared to today’s console games, the 20 year old ones might look like crap, but they have a few aces up their sleeve (such as quality and playability). Still, I’m not here to start rambling about modern games with no soul or challenge. I’m here to ramble on modern games not working, introducing the modern players to such joys as freezing, requiring constant updates and bugs.

Granted, these have been issues PC-gamers – myself included – are used to, hardware incompabilities, crashes, flawed code and such. Consoles used to be carefree – never heard of anyone not completing, like, Super Mario Bros because the game kept exiting to title screen every time you picked up a mushroom. That just didn’t happen on consoles.

That Disc Sure Is Dirty

That was then. Nowadays console games are almost as bad as their computer counterparts. Here’s a few games I remember seeing crashing recently, much to my delight.

  • Lost Odyssey (XBOX 360)

    Constant read errors on scene changes. Sometimes not fatal (like music not loading on battle, but game returns normal after the battle ends), but often the game claims the disc is dirty or otherwise faulty. Usually the game can be resumed right away by just launching it again. No need to even open the tray and clean the (supposedly) dirty disc.

    Sometimes it hangs up the entire console, forcing a system reset. Especially common on the 4th disc. Shame, as the game itself was rather good. Fortunately I managed to complete it despite the errors, probably because they seemed completely random.

  • Samurai Warriors 2 (XBOX 360)

    Occasional disc read errors that crash the game. Sometimes unable to load the music track, but that did not affect gameplay itself. I also stumbled on a bizarre bug on one of the campaigns, where scripted event failed to occur where it should. As a result I was unable to advance, which was awfully nice.

  • Ninety-Nine Nights (XBOX 360)

    Notorious for disc read errors, web filled with similar stories. Despite of scratch free, clean disc, successful loading seems to depend on the position of the moon and weather conditions.

    I liked the game, but trying to get it run properly proved to be an added challenge I couldn’t completely solve.

  • Xenosaga 2 (PS2)

    Classic freezing issues. Not too often, but enough for me to remember them. Nothing compared to the titles above, though, and did not get in the way of completing the game.

  • Twilight Princess (WII)

    The initial US version had a bug which made it impossible to advance in the game on certain situation. This was fixed on later shipments and did not affect the European version, but still.

To Proceed You Must…

Internet-features brought game consoles even closer to PC gaming by adding the fun of updating to the mix. Current generation of consoles does this well, and as a bonus, they make sure if there’s an update, you won’t miss it.
Force-feeding patches is an idea that probably looked good on paper, but really sucks in real life. I own all three major consoles and use them online. As a reward, I get to download something almost every time I turn one of them on. If it’s not a system update, then it’s an update to the game I intended to play. If I’m really lucky, it’s both.

I recently decided to download the demo of Super Stardust on PS3. After the initial download I thought everything was set. My wishes and reality did not match, as I was told that I need to update the game before I can play it. Hilarious, isn’t it? Here I’m required to update the game I downloaded a minute ago. Just because it was too difficult to include the patch to the initial download?

Even better is that I don’t even get to choose if I want to update or not. I’m not able to play it UNLESS I update!

It’s Not the Outcome, It’s the Means

Why not give the players a choice? Let the user update later if he or she wished unless it’s absolutely necessary. Little transparency wouldn’t hurt either, tell what the update does and fixes as well. I’m tired of buying a game only to be faced with mandatory download of sometimes a couple hundred megabytes.
Add a slow update installing process to the mix and you start with a really positive attitude towards the software. Okay, I could probably yank the network cable from the console to prevent this, but when the entire system is designed to be online, it’s really handy to switch between online and offline constantly.

Software’s a tricky thing, sometimes the finalized product turns out to have issues that need fixing. That’s what patches are for. I’m not totally against them, sometimes games even get new features, but I just wonder how often they are a result of developers being cheap on the testing phase. I also think that the current-gen consoles’ way of handling the update process is far from ideal.

Let’s hope it changes as the systems mature. I’d like the idea of trying a new game right away instead of applying an update. If the released version is not in a playable state, it’s been published too soon. The concept of quick play is sure going down the drain.

I Am Not Worthy

One thing that always seems to rain on my iPod Touch’s parade is iTunes. Not only it backs up the software for ages every time I sync with my desktop computer, it also plays its mind games with me when it comes to applications. It sticks already uninstalled apps back, messes your updates, anything to make your life easier. Fortunately the upgrades can be installed from iPod as well.

Still, I can’t remember how many times I’ve actually managed to update apps succesfully with iTunes, but I bet it’s not a very large number.

Usually it pulls the good ‘ol 5 step jedi mind trick:

  1. App Store on iPod informs that updates for few apps available
  2. I need to sync anyway, so let’s update them on iTunes
  3. There are no updates for you. You do not need to update anything.
  4. Oh… If you say so, ok…
  5. Open App Store on iPod after sync and what do you know: missing updates staring right back at you.

Besides this, there’s also the “gotcha”-game: let the user think everything is in order after he or she presses the “update everything”-button. Bonus points if the user finds out that nothing’s been done only much later. Scored big yesterday.

In all seriousness, my wishlist for year 2009 includes reliable app update and uninstall process on iTunes and I hope I don’t need to pay for another firmware upgrade just to see it…

I’m glad the App Store software on iPhone/iPod supports installing all updates on single click instead of the tedious separate click for each update-scheme it had going early on. Saves me from iTunes. Oh, and I’m also glad they added a setting for turning off the text prediction feature. Yay, no more me sounding like a Swedish chef (although I admit that writing sometimes in both english and finnish might be too much for it to handle reasonably)!

App Store

Not Built In A Day

A while ago I praised the iPhone/iPod Touch Software 2.0. Despite of its share of problems, the software update unleashed the true potential of the iPhone/iPod Touch software platform.

Now it’s been a few months since the App Store was opened and since then Apple has managed to release a few software updates. The latest software version currently is 2.1 and the updates have fixed a few problems, but the package is still far from being ideal. Nonetheless, progress has been made. How is the mobile OSX doing now?

Read the state of the iPod

State of the iPod

iPod Touch

What’s happening now?

A while ago I praised the iPhone/iPod Touch Software 2.0. Since then Apple has released a few updates, the latest software version being 2.1.

The updates have fixed a few problems, such as the backup process happening on every sync. This previously took ages to complete, but the updates have improved it to just being slow. That I can deal with.

Apple has also worked on the general stability of the system, reducing the constant crashing quite a bit. From what I’ve experienced, the third-party apps rarely crash anymore. This is huge concerning that nearly every app had random crashes with the old software. Actually the most crash-prone app for me now is Mobile Safari, which usually calls it quits at least once per day. Not too nice. Fortunately it saves the session information, so all is not lost.
The software seems to be especially unstable and unresponsive when listening to music – I’ve had a few occasions where the entire iPod has hung up, not responding to anything. Fortunately after restart we were back in business.

As I’m writing this, my #1 annoyance is the text recognizition. It works with a completely opposite logic from mine. From where I see it, it would make sense to require user to tap on the suggested word IF he/she wishes to use it. No. Instead the software automatically replaces the words unless the user taps on the suggested word to remove it. This is both highly inefficient and frustrating as I have to constantly tap between the words I write and the on-screen keyboard. Although by listening to music while writing and tapping around the screen at the same time gives me a kind of a Guitar Hero/Tap Tap Revenge experience. Sweet. I hear the next update allows to turn text recognizition off, so there is still hope.

Text recognizition makes me sound like a Scandinavian character from some Monty Python sketch.

Wai not try text recognizition toi ease joor life?Imagine this with a hilarious accent and you’re all set.

Issue #2: STILL no copy & paste. You know what’s fun? Writing down a parcel tracking code from your inbox to a piece of paper and then write it to Safari just because there’s no proper way of transferring it from Mail otherwise. I can think of few more reasons to continue whining, but this is the most recent one.

Issue #3: About those language-specific characters (such as ä, ö and their friends)… Accessing them by eg. first holding down letter A and selecting from the pop-up menu makes typing fast and fun. Why indeed include them straight to corresponding international keyboard when you can implement them like this? Slow and steady wins the writing race. This makes me glad I don’t have an iPhone, writing text messages would be smooth.

Much rejoicing

Concerning software, things are looking rather good for the App Store. Even with my “cheap bastard”-policy of trying only freeware apps, I’ve found a plenty of useful and fun programs.

In fact, the sheer amount of programs on few most popular categories forces Apple to soon rethink either the categorization or the way the programs are listed on App Store. Unless someone there really thinks that scrolling around 400+ programs on the same list view is a good idea for you or your index finger…

WordPress. I’m using it to write this, actually. Works rather well for small updates like this and writing drafts. I would like to have a horizontal mode for writing, though.

Currency. Currency converter, no more, no less. Does its job well and looks good. Minus-points for ads and slow startup, although the startup-time has been improved significally on later versions.

WeekOtY: Displays the current week number and other week numbers you might need. Why? Because the official Calendar-application can’t do this. Ideally there shouldn’t be need for apps like this, but since there is, thanks for the developer for making it possible to see when that week 42 Friday appointment takes place.

Ping (lite). Network tools Ping and Traceroute on your pocket. Comes really handy especially on home networks.

Wikipanion. Access Wikipedia from a stand-alone app. Handy every now and then, especially if you don’t want to access (and crash) Safari just to quickly check something out.

WeekOtY screenshot