The official reply from Tablo follows, and the IANA/ICANN standard for the internet. (which I do not follow on my private network):
It looks like because your Tablo and client(s) are on atypical subnets, it’s causing an authentication issue for LAN communications. We have made some security improvements in the 2.2.26 firmware, which is why this is only apparent now.
The Internet Assigned Numbers Authority (IANA) reserves the following IP address blocks for use as private IP addresses:
10.0.0.0 to 10.255.255.255
172.16.0.0 to 172.31.255.255
192.168.0.0 to 192.168.255.255
I use an address range outside these ranges. Tablo 2.2.26 restricts local clients to the above address ranges. ( I am behind my own firewall, I can address how I want. NAT takes care of the rest.)
All of my other devices allow me to program their adresses, subnets, and gateways, therefor I had no problems. Becase I am behind a router and firewall under my control, this had not been an issue before the update.
So when I updated to 2.2.26 and had the Tablo’s remote access turned on, the Roku’s kept working through the Tablo’s remote LAN port, but the ripper could not authenticate because of it’s non-supported IP address. Once I turned off the remote access port on the Tablo the Roku’s also stopped working leaving me dead in the water. Nothing worked.
After Tablo support realized what had happened (see above) I was backed out to 2.2.24 and everything is working again.
Thank You Tablo for tightening security!
Request: give your Tablos configurable IP adressing.
My 15 year HP printer has this as standerd!