I would think that the numbers have a meaning but, for internal network purposes, those meanings are pretty much irrelevant.
They do, and you're right that the meanings are pretty much irrelevant for most home users. For those interested in arcane networking trivia however, wikipedia explains:http://en.wikipedia.org/wiki/Private_ne ... ess_spaces
Doesn't that only apply to the first two however? I know on my router I can change the third part to anything from 00-99 and the last part is a table that can be restricted.
I changed to 192.168.42 simply because 42 is the meaning of life and the universe so my network reflects that.
I had a feeling there was a Adams-esque explanation for that address
. I'm not sure what you mean by 'only apply to the first two', but there are specific ranges set aside for private networks, we can't just pick any numbers and expect things to work. Most home routers work in the 192.168 range, but it's not the only possible private range. My work network (which I control) uses a 10.1.1.1-10.10.255.255 range. Potentially I could go all the way to 10.255.255.255, but I just don't need that many addresses
. I use the second octet to designate different classes of devices such as: all 10.5.x.x addresses are printers. Although I've never seen it in use, apparently 172.16-172.32 is available as well. While not very common, it's very possible that a home business owner will be using a Roku with a business-class router(or other dhcp server) that hands out 10.x.x.x addresses, so it's something Remoku can't take for granted when setting up the scanning.
What would be really nice (and probably not something that will ever happen) is if Roku created an API where their Roku devices call the mothership at roku.com whenever the private address changes; then third party apps and web services can register with Roku to let authorized users share that info (think of it as similar to facebook logins for third party sites). Then I could securely request the addresses of all the rokus you own directly from roku.com and not have to mess around with all the network scanning stuff(only at your request and with your consent, of course). And once all that stuff is in place, there are other possibilities for interesting interaction between a roku device, the roku service, and third party websites(for instance: stuff like mog.com being able to tell the roku what album to start playing). Even Roku's own app has trouble detecting the ssdp announcements under certain network conditions, and this would be a more sure-fire way to enable the same end result.