@theuser86 I had my phone in WiFi and opened the Tablo app. It connected. I then went to settings and scrolled down to Remote access. How do you pair locally? I thought by having my phone in WiFi and use Connect that it does pair. If it does, then why waw the remote still saying I had to configure my router? Should I have closed Tablo app, turn Wifi off, and open the Tablo app and see if it worked prior to unchecking and rechecking? Hopefully I don’t lose power again any time soon.
I’ve seen this happen and my “fix” is/was to uncheck and recheck the Tablo remote access box.
Sure would be a lot less trouble with a system generated code or password for a limited number of remote clients. I say limited number of users/clients because I realize the potential for abuse beyond immediate households.
I would try to just increase the lease time if your router does not support static assignments. If the pool is large enough not to have to recover addresses often, then you should never run into devices getting different addresses. If it still ends up being a problem, I would focus on getting a different router or moving the DHCP services for your network to a different device that has more features. It is much easier to manage all IPs from your DHCP server vs touching each device manually.
“How do you pair locally? I thought by having my phone in WiFi and use Connect that it does pair.”
–> This is correct. Connecting to your Tablo locally (aka on the same network) pairs the phone with the Tablo.
“Should I have closed Tablo app, turn Wifi off, and open the Tablo app and see if it worked prior to unchecking and rechecking?”
–> Yes, you should have tried this first. It usually still works after re-pairing even if it gives you the error as long as the Internal IP has remained unchanged.
Static IP is a basic option in my opinion. I know that some DHCP server allow for reservation. I’m using DHCP off a Cisco 3750G switch and that doesn’t have that option.
Maybe only make it available for the wired versions…
A switch does not have a DHCP server which assigns IP addresses so may be you’re looking at the wrong networking device to configure it. Which device is your router?
Maybe dumb or unmanaged switches don’t… Managed switches can do a bunch of things.
Well if that is the manual to your switch, it does in fact have the capability to setup DHCP Reservation. I quote “DHCP server port-based address allocation is a feature that enables DHCP to maintain the same IP address on an Ethernet switch port regardless of the attached device client identifier or client hardware address.”
Go to the Section “Understanding DHCP Server Port-Based Address Allocation”.
A cheap $10 consumer router has DHCP reservation, I’m sure an enterprise grade switch can muster up the effort to do the same.
On some routers, yes. Not all routers.
And anyway there are some situations where even if the address-reservation approach is possible, it is not the best way to go. There does need to be a non-DHCP option in the Tablo.
I can sort of imagine why the Tablo engineers are being stubborn about this. Every time you add any feature, there is the risk that a user will misuse that feature. And then you are stuck trying to work out what the user did wrong. Resetting a Tablo that has had a static IP address set probably means doing a factory reset and then a very unhappy user who does not like having lost all of those precious recordings and settings. Probably the smart way to go would be to have a system reset that turns DHCP back on without losing all of the other settings. But that requires an extra reset button? Or a reset button that does something different depending on whether you push it for five seconds instead of ten seconds?
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.
1 Like
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.
FlyingDiver
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?
theuser86
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?
theuser86
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.
-Scott
1 Like
My nephew (a networking something or other, but he does like a pint so he’s not a total berk) says, generally, never mix on-device static ip settings with dhcp, because you can end up with duplicate addresses and then everything goes to pot. If a router can’t do dhcp reservations then it probably can’t restrict the addresses for dhcp either. Dhcp reservation is bog standard, and if your router can’t do it then bin the manky thing.
He was rather going on so I stopped listening… But he did say you might find this handy: http://www.dd-wrt.com/wiki/index.php/Static_DHCP
I have two subnets. Tablo is getting a dhcp reservation from router A. Unfortunately, I would like to use router B as the gateway.
Sounds like you should be using VLANs to assign that device to the right subnet.
For those expecting infrastructure components to have static ip addresses in small networks, you’d be confused by my hp 24 port semimanaged switch, which happily obtains its own administration address from the dhcp server resident on my standard issue centurylink consumer grade router, which happily makes the ip to mac reservation.
I learned my lesson once that the dhcp server has a better memory than I do, and is a better system of record than any document I could maintain.
So i use it whenever possible.
Setting up dhcp reservations once has worked for me in my Archer TP Link C7 router.
Because your ISP may change IP addresses on you, you could use something like dynDNS, it costs to have, but then you get a URL to go to that is registered to the IP of your router and when it changes, the URL is updated with the new IP so you are able to reach your device. Have not tried it as I am new to Tablo myself, but have background in networking and have used it elsewhere.
This is 100% correct, the lack of such a basic networking tool, such a setting a static IP on the device, is maddening.
I think there are two things being said. There’s the idea that the thing likely never under your control (for most home users), that is, your external IP address from your ISP. And the other is the LAN IP address which right now is set by DHCP, which is more or less “the norm” for appliance like devices on a home LAN. The latter is ultimately in the hands of control of the home user though. Which means that a home user could have the option of not running IPv4 DCHP at all. And that, indeed, is a case where being able to set a static IP on the Tablo device would be needed.
If, we ignore that case, and go back to home DHCP, then by nature of the protocol, we can create IP reservations based on the hardware MAC address of the Tablo device to ensure that for that given LAN, it will get the same IP, even via DHCP. This does assume that a given LAN DHCP implementation provides “a way” (easy?) for the home user to setup these reservations.
Anyhow, there are two IPs I think being discussed a bit too closely. They are different.
For Tablo, the more problematic IP is the setting of the IP of the Tablo device on the local LAN. Which again, is most problematic (can’t work) in a LAN with no DHCP. Such a configuration setting would be nice. Introduces other variables, but again, at this point, we’re talking to people that supposedly understand what they are doing.
1 Like
I’m sorry, I don’t have the same grief.
Routers can assign static IP addresses for those devices, and they’re more easily managed.
I have Tablo, Roku, Rainforest Eagle ZigBee Gateway, Google Pixel 4a, Google Chromocast with Google TV, Google Hub, Google Nest Doorbell, Google Nest Thermostat…
Can’t set static IP for any of those devices on the devices themselves.
If I want any of those devices to have static IPs, my router does a great job handling that.
2 Likes