Using an unregistered IP address block is dumb, I'll agree. That's why I'm not doing that.
And as for why I don't change to an RFC 1918 block: you said it yourself, in that it took a lot of effort to change everything. I'm not willing to go through that just because some application developer thinks I should. It's my network, not Roku's.
"jmaynard" wrote:"twiceover" wrote:
It's appropriate what they are doing since, generally speaking, a roku shouldn't have a publicly routable IP address.
You don't have to have an RFC 1918 address in order not to be publicly routable. My address block has no RIP advertisements anywhere on the Internet. Anyone who tries routing to it will get "not reachable".
And what does the app scan? All of the RFC 1918 space? Or just the subnet the phone is on? Someone taking their phone to another place where a Roku box is connected will find that one?
Like I said...paternalistic attitude. Don't tell me you know how I should administer my network. "Be liberal in what you accept, be conservative in what you do" is a fundamental principle of the Internet. That goes for letting people set things up.
JMaynard, you don't know what you are talking about. I have a VALID IP address (not 10.x.x or the other two). I have dozens of nodes on my network and chose to use something different than 10.0.x.x. It is NOT public and can never be due to NAT. Why should I change 20+ devices, my DHCP and everything else to use one remote control app. It makes no sense. Roku users are more advanced than ChromeCast or AppleTV. Anyhow, Roku, please fix this.
My private network uses 192.168.5.x, and I am getting the "IP address not supported" message. I think maybe the app is checking for 192.168.0.x instead of 192.168.x.x. I wish there was a workaround for this.