Can someone name any other networking device that requires port forwarding and doesn't give you the OPTION to set up a static IP?
Why is Tablo so obstinate about adding what is a standard optional setting for every single device that acts as a server for decades on the network when every other aspect of their product is so clearly well thought out and amazing? No one is asking for DHCP to be removed and require every user to setup static IP tables, just give us the option to specify a static IP. They say to setup a DHCP reservation which they admit not every router has but more importantly they deviate from what has been a standard practice without giving a valid reason why. This makes me question if they are going to be this stubborn with all aspects of future product development. I might be saving myself tons of future frustration and headaches when they decide on a whim to deviate from networking norms in some other fashion.
I just recently got a Tablo, setup remote access. My router uses dd-wrt firmware, which has a bug when you first create a port forward it doesn't actually forward that port until you restart the router. So I created a forward to the dhcp assigned address, restarted the router. When I went to work the next day, tried out Tablo connect, it didn't work. Got home and saw that my router had given it a new address, so I forwarded to the new address, restarted, new IP address,. I don't have to deal with this issue on the other 10+ devices (IP cameras, Raspberry Pi's, IP NVR) on my network that I port forward to because they all follow decades long standard practice and allow you to set a static IP address.
What's the use case for preferring a true static IP address (vs DHCP reservation). I can't think of one, other than a really old router that doesn't support reservations. And I don't think that case warrants the change.
Oh just decades of it being standard practice. Also, how about every single person both on this board having issues because the option to configure this most basic settings is missing. What is the use case for not having it?
@philsoft May '15
All other devices I have seen that are similar network infrastructure allow for statc IP assignment.
Roku doesn't allow you to assign a static IP either. I think it is becoming more and more the standard as networking becomes more and more necessary for the average Joe.
Roku doesn't act a server that needs ports forwarded to it, so that is completely irrelevant. I have several rokus, they work great and don't have that setting because I'm don't need to access them from outside my network.
@theuser86 May '15
What does not work because you cannot set a static IP for the Tablo? The only thing I can think of is Tablo Connect.
Umm, yeah, Exactly! Why ask a question when you already know the answer?
That is a very expensive piece of hardware. Is it actually lacking such a basic function of DHCP reservation?
The Tablo is an expensive piece of hardware, is it actually lacking such a basic function of setting a static IP?
Most routers these days have UPnP, if you leave that enabled on your router then it does not matter whether the IP address is assigned dynamically or is static.
That is terrible advice. Yeah sure just let anything on your network open up random ports whenever they want. Please don't give such myopic advice online if you don't fully understand the consequences.
www.forbes.com/sites/andygreenberg/2013/01/29/disable-a-protocol-called-upnp-on-your-router-now-to-avoid-a-serious-set-of-security-bugs/#7a3f75005246 "security researcher Rapid7 released an advisory warning that UPnP allows the remote discovery of between 40 and 50 million UPnP routers, printers, servers and other machines"
securityweek.com/attackers-abuse-upnp-devices-ddos-attacks-akamai-warns "PLXsert found 4.1 million Internet-facing UPnP devices that could be used in this type of reflection DDoS attack."
Why are people making excuses for Tablo developers, who otherwise are making a fantastic product, when it is apparent that many people are having issues and having to jump through all these hoops to work around what would NEVER be an issue if an OPTION to set a static IP was available.
This has been an awesome product and user experience until coming across this baffling decision to leave out this setting. I can understand if the product was released before the Tablo Connect feature was added, so a static IP was completely unnecessary and wouldn't be baked in by default but now it is just disappointing.