1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

tivo remote access tool - pre BETA

Discussion in 'TiVo Underground' started by tivoupgrade, Aug 22, 2006.

I am testing the tool on the following platforms:

  1. Series1 Standalone Unit

    13.1%
  2. Series1 DirecTV Unit

    3.4%
  3. Series2 DirecTV SD Unit

    48.0%
  4. Series2 DirecTV HD Unit

    20.4%
  5. Series2 Standalone Unit

    25.6%
Multiple votes are allowed.
  1. Aug 22, 2006 #1 of 498
    tivoupgrade

    tivoupgrade Sponsor

    2,494
    0
    Sep 27, 2000
    Chicago, IL...
    Folks...

    Been working on a little 'skunkworks' project and need some testers of what I'm hoping will be considered a cool new tool / service for folks with networked TiVo systems.

    The idea is to make it quick and simple for folks who already have networked units to access TiVoWeb or TiVoWebPlus from anywhere on the Internet. We know this can be done today, but there are headaches associated with dynamic IP following, port mapping on routers, and management of multiple TiVoWeb instances by running the app on different ports.

    Here's the summary:

    • Start with one or more networked Series1 / Series2 TiVo that has telnet/ftp and TiVoWeb / TiVoWebPlus already installed
    • Create an account on a secured server and register one more TiVo systems by service ID and description (the information is kept private)
    • Access each of your TiVo's locally (from your home network) and install a small client application (this can be done with telnet or bash session and by typing a few simple commands)
    • Start the client application (or restart your TiVo)

    Result: You'll now be able to remotely access any or all registered TiVo systems through our server without doing any port-mapping or knowing your public IP address. If you are running multiple TiVoWeb instances, you do not need to run each of them on different ports.

    The implementation is intended to be completely secure, and the installation of the client, for folks who already have networked units, very simple (as long as you follow the instructions). Moving forward we hope to encourage folks to simply include the client in their own utilities so that access becomes even simpler.

    So, if you are interested, please do the following:

    1. Go here and create an account for yourself; you will need to use a valid email address; don't worry, we keep the info private.
    2. Register as many networked TiVo boxes as you have (the current limit is three) and install the client. Full instructions are on the site (you won't see them until you register), but I will reprint them here.

    That is pretty much it; once you've got your TiVo registered, the client installed and running, you should be able to access each of your units by simply selecting them and clicking appropriately. Most functions within TivoWeb seem to work fine, but you may experience timeouts when trying to do operations that take more than a few minutes (like viewing a really big log file).

    The purpose of this thread, and this pre-beta is to lure some of the more technical folk into banging on this stuff a bit and finding any bugs, security holes (there should be none of those), and of course getting some meaningful and constructive criticism.

    If you have questions or problems, please take some time to provide details such as the type of TiVo you have, the methods you've used to network it (eg. I have a Philips DSR704, networked using a PTVnet drive kit, or I have a Philips HDR212 with a TurboNet card and the latest silicondust drivers, etc...) so that we can get to the root of any architecture-specific problems.

    Lastly, we've tested this stuff on Series1 standalone and DirecTV boxes, as well as Series2 SD and HD boxes. We don't have any prom-modded Series2 SA units so I'm not sure whether the apps will work or not.

    So with that, hang on, I will post the client install instructions for review here, you remotely install the client using a telnet session on your networked TiVo (this can be done without registering your system with the server).

    Please let me know what questions you have and I will do best to answer them. Very interested in early experiences and feedback.

    [update 10/1/06] - We've updated the client install package with a new watchdog application which I think will address some of the spurious disconnect issues. The installation process is exactly the same, so just follow the documentation below.

    [update 10/11/06] - We've updated the client install with a modified version of the watchdog application. The basic client has not changed, however the utils which support the watchdog (netcat, in particular) have been modified so that they will run on 6.3a and 7.X on HR10-250 and Series2 SA standalone platforms, respectively.


    [update 10/19/06] - Updated client to fix bug in watchdog process on Series1 units...


    [update 9/5/07] - Please see this newly created thread for some tweaks, and an alternate version of the client that seems to work better for some folks.

    [update 2/12/07] - For those running 6.3 on the HR10-250 and who are manually installing the client (ie, not using PTVnet): There is a bug with http_get, please see the next post for specifics on replacing it. This may also be an issue for Series2 DirecTiVo SD units, as well.

    [update 2/12/07] - For those concerned about high CPU utilization on Series2 systems and interested in a few tweaks that have been introduced by another helpful user, steveT whose contributions are linked above, I've released a new test version of the client. If it all works well, we'll set it up as the default. Just follow the installation instructions below except use b_install-1.2.sh instead of b_install.sh. To date, I've only got it working in a mode where you have to run the client manually; I'm looking into that further.


    Thx,

    Lou
     
  2. Aug 22, 2006 #2 of 498
    tivoupgrade

    tivoupgrade Sponsor

    2,494
    0
    Sep 27, 2000
    Chicago, IL...
    If you have a networked TiVo that does not already have the gotomydvr client for your TiVo, you will need to manually install it using the following instructions. If you do not have a networked TiVo, you will need to get networked before you can do any of the following or use the gotomydvr service. Please check with our main site for more information and on how to determine whether your TiVo can be networked and how to do it.

    1. Your TiVo must be networked using one of our preconfigured networking kits or in any other manner which gives you telnet and ftp access to your unit.
    2. You will need to know the IP address of your TiVo on your network. It will often look something like 192.168.1.XXX, but the numbers will vary based upon the type of router you have and the way your network is configured. You can find your exact IP address by using your router's administrative menus to view DHCP clients, or use an IP scanning program such as angry IP.
    3. Open a telnet session from your computer to your TiVo. You can do this using a free program like TeraTerm Pro, or by simply running telnet from a shell window or using the windows start and run command as shown here.
    4. Now, simply type the following commands into your telnet session; we highly recommend you simply copy and paste them, one at a time, to avoid any errors.

      Code:
      http_get -T 0 -C 0 -D /var/tmp -U http://68.178.174.173:80/b_install.sh
      sh /var/tmp/b_install.sh
      sync; reboot &
      
    5. At this point, the gotomydvr client should be installed and running. If you receive an error like this ***No response from connection server *** then the client is installed properly, but your TiVo is probably not properly registered with our server. Type crypto -gsn to display your service ID and then verify you've registered properly on the page.
    6. Proceed to the Select TiVo page, pick out the TiVo you want to access remotely and have fun!

    [update: 10/11/2006]
    The aforementioned instructions and client tools have been tested and proven to run as-is on the following TiVo types:

    Series1 Standalone and DirecTiVo units running version 3.5 of the OS
    Series2 DirecTV DirecTiVo units running version 6.2 of the OS
    Series2 DirecTV HD DirecTiVo (HR10-250) running verison 3.1.5f of the OS

    If you have a Series2 DirecTV HD HR10-250 running any version 6.3 of the OS or a Series2 Standalone unit running version 7.X of the TiVo OS, the client can be run, however you will need to replace http_get in your /tvbin directory with the one we've attached, then go through the installation as documented.


     

    Attached Files:

  3. Aug 22, 2006 #3 of 498
    rbautch

    rbautch User

    3,629
    0
    Feb 5, 2004
    Chicago, IL
    This looks pretty cool. I'll give it a shot.
     
  4. Aug 22, 2006 #4 of 498
    cheer

    cheer Registered Offender

    1,406
    0
    Nov 13, 2005
    Gurnee, IL
    Lookin' good both for my HR10-250 and my SD-DVR80s. Much simpler than messing with multiple ports and/or using a bouncepage of some type. Thanks, Lou! Any particular scenarios you'd like tested? (Weirdo ports, etc...)
     
  5. Aug 22, 2006 #5 of 498
    cheer

    cheer Registered Offender

    1,406
    0
    Nov 13, 2005
    Gurnee, IL
    Silly me, I see you've asked for a better description on the units used and the tests I've tried. Well I'm off to bed but I'll post you a more detailed writeup tomorrow.
     
  6. Aug 22, 2006 #6 of 498
    SteelersFan

    SteelersFan "On Welfare"

    819
    0
    Sep 6, 2004
    Saugus, CA
    I've installed this on 3 units (DSR7000, DSR704, SD-DVR40 - all Zippered). All are working from my LAN. I have Road Runner cable feeding a Thompson cable modem feeding a Vonage Motorola VT1000 feeding a LinkSys BEFW11S4 V4 router. All units are hardwired with NetGear FA120's. I'll try from work tomorrow and post results.

    BTW, Thanks so much for this great app. I've tried for a long time to get remote access the "old" way and had given up hope. Not sure why I couldn't get in, maybe something to do with my Vonage adaptor or my work blocking access.
     
  7. Aug 23, 2006 #7 of 498
    msommer

    msommer Card's Fan

    86
    0
    Apr 4, 2005
    Installed flawlessly on three S2 Dtivo's.

    2 - Hughes dvr40. Hacked using the Zipper. LAN connection - wireless G bridges

    1 - Hughes dvr80. Hacked using the Zipper. LAN connection - wired Netgear FA120

    Linksys WRT54G router on Centurytel's DSL Network - speed 1.5 M

    So far, everything is working fine. Have successfully deleted shows from now playing list, setup manual recordings, and even did a remote reboot.

    Outstanding service!! :up: :up:

    Is there any way to show the name of the TIVO you are viewing on the main screen?
     
  8. Aug 23, 2006 #8 of 498
    tivoupgrade

    tivoupgrade Sponsor

    2,494
    0
    Sep 27, 2000
    Chicago, IL...
    Excellent. Good to see that initial tests have been good so far; please beat on things as much as possible and one thing I'm very curious about is the ability of the TiVo to maintain its connectivity through the server.

    What I've seen during internal testing is the potential for the client to lose connectivity from time-to-time so that when you log in from the server, you will get a "tivo disconnected" error. Usually, a reboot of the TiVo, or a manual restart of the client solves the problem, but as far as I'm concerned, that is not a good solution.

    What i'm hoping is that its just been the server development work and mucking around with the database that has caused those problems - so folks, if you receive any "disconnected" messages, please keep track and see if you notice any patterns that may cause the problems (changes of ip addresses on your router, power outages, other hacks, etc.).

    Thanks again; I'll monitor this thread as much as possible and post any updates as they unfold!
     
  9. Aug 23, 2006 #9 of 498
    tivoupgrade

    tivoupgrade Sponsor

    2,494
    0
    Sep 27, 2000
    Chicago, IL...
    That is something I'd like to do, as well. Let me look into that further.
     
  10. Aug 23, 2006 #10 of 498
    willardcpa

    willardcpa QUASI-OMNISCIENT

    2,686
    0
    Feb 23, 2001
    Eugene, OR USA
    Re showing the tivos name on TWP. Go into httpd-tt.itcl in the root directory of your TWP installation. The first few lines in the file are concatenated together, and read by default:
    variable NAME "TivoWebPlus Project"
    variable VERSION "1.0"
    This give you "TivoWebPlus Project - v1.0" (or whatever version you are on). You see in the heading for TWP screen.
    You can go into the line and modify it to
    variable NAME "TivoWebPlus Project - Living Room"
    and it will say that in the heading of TivoWebPlus.
    It works great, I have it on five boxes and it is indispensible in determining which is which.
    I gotta give credit to JohnSorTivo for this in a post he did way back in July of 2004, if anybody feels the need to verify my posting (done at after midnight). ;)
     
  11. Aug 23, 2006 #11 of 498
    Gunnyman

    Gunnyman Just a boring dude

    30,750
    2
    Jul 10, 2003
    !Texas
    Works great on my S2 DTivo Lou.
    Nice work.
     
  12. Aug 23, 2006 #12 of 498
    cheer

    cheer Registered Offender

    1,406
    0
    Nov 13, 2005
    Gurnee, IL
    OK, my scenario and thoughts.

    First, my SD-DVR80 test box. Running 6.2, manually hacked with killhdinitrd'd 3.1.1c kernel. Static IP, configured via the netconfig.tcl script. The usual "stuff" on it -- superpatch, mfs_ftp, vserver, TWP 1.2.2. Also running monte to a custom kernel with netfilter disabled and using the latest backport drivers and mfs_* tools.

    This box works just fine with the gotomydvr service. Been using it off and on since last night without issue.

    Next, my HR10-250. Running 3.1.5f, manually hacked with killhdinitrd'd 3.1.5 kernel. Static IP, configured via ifconfig in rc.sysinit.author. The usual "stuff" on it -- tivoapp patches, mfs_ftp, vserver, TWP 1.3.0. Was running TWP 1.2.2 last night but TWP on this box tended to hang after a day or so (and had done last night), so I upgraded to the latest. I verified that the client is running on the DTivo, but the gotomydvr site claims that my Tivo is disconnected. Rebooted the box -- no change.

    Finally, a comment. For the most part I love it, but my one criticism would be with the page format. It's very small! This may not be noticeable to people with a 1024x768 screen but on my 1440x900 laptop it's very noticeable. Look here to see what the gotomydvr page looks like on my laptop, and look here to see what TWP looks like when used directly.

    I'll futz some more with my HR10-250 and see if I can get it working.
     
  13. Aug 23, 2006 #13 of 498
    SteelersFan

    SteelersFan "On Welfare"

    819
    0
    Sep 6, 2004
    Saugus, CA
    Works great here at work. I went through a number of TWP functions: ToDo, Now Showing, Info, Whats On, Search, Manual Record. I set up a manual recording with no issues and verified it worked by checking the ToDo list.

    The only thing I've seen so for that looked out of the ordinary is I got a message at the bottom of a screen that said something like "Tivo appears to be disconnected". I think it was after I did a "Whats On" search that this message showed up at the bottom of that results list. After I saw that I clicked on a number of TWP functions without problem.
     
  14. Aug 23, 2006 #14 of 498
    tivoupgrade

    tivoupgrade Sponsor

    2,494
    0
    Sep 27, 2000
    Chicago, IL...
    Wow. OK, you are definitely a power user; thats a very big screen layout you've got, and you are right, the way we are displaying that makes it very frustrating. We'll have to look at some alternative ways of displaying things, perhaps with another link that can be selected. What I can't see from your screenshot is whether or not there is a horizontal scrollbar presented - is there? If not, would that be an acceptable alternative?

    With you permission, I'd like to access your unit remotely so we can look at the screens from here. If that's ok, please PM me with your login info and I'll have our programmer take a look.

    As for your HR10-250, please post any follow-up details. If you are familiar with any unix commands, you can use ps -aux to view running processes and look for rc.gotomydvr and dbclient in the running process list. If you don't see them, then there is an issue and you'd need to manually startup the client and see if there are any errors -- the startup commands are in rc.sysinit.author.

    Note - if you don't have a proper route table, that can cause problems. If that ends up being the issue, or you think it may be let me know and I can tell you what to do.
     
  15. Aug 23, 2006 #15 of 498
    tivoupgrade

    tivoupgrade Sponsor

    2,494
    0
    Sep 27, 2000
    Chicago, IL...
    Excellent. That message you saw was due to a "timeout" -- there is a timer on the server that will run out after a period of waiting and finally give up on querying your unit. I have increased the timeout from 60 seconds to 120 seconds. Hopefully there is no downside to that.
     
  16. Aug 23, 2006 #16 of 498
    SeanC

    SeanC ECT

    9,616
    6
    Dec 30, 2003
    Someplace
    Lou,

    Awesome, just awesome!

    Just happened to catch the thread, remoted to my home machine and installed it on my S1.

    Working great, no problems.
     
  17. Aug 23, 2006 #17 of 498
    SteelersFan

    SteelersFan "On Welfare"

    819
    0
    Sep 6, 2004
    Saugus, CA
    Lou,
    Is the server down? I get a message for all 3 of my units that they are disconnected.
     
  18. Aug 23, 2006 #18 of 498
    danny7481

    danny7481 Tivo Addict

    381
    0
    Dec 6, 2005
    Mississippi
    i had it working at first
    then i closed out my telnet session and now its says "tivo appears to be disconnected", try again later.

    let me make sure im doing this right, after installation, all i have to do i go to gotomydvr.com, login, and select my tivo, correct?
     
  19. Aug 23, 2006 #19 of 498
    tivoupgrade

    tivoupgrade Sponsor

    2,494
    0
    Sep 27, 2000
    Chicago, IL...
    The server is up and has been up. My units have been fine - but I have seen this before. The client should attempt to re-establish its connection automatically. However, if its no longer running, it would need to be restarted.

    Try doing a "ps -aux" on one of your units and see if its still running. Also, when re-attempting to connect via the site, make sure you do a "shift-reload" to ensure that its not a cached browser page.

    I have seen this before - and I'm not sure of the cause of it -- if we can pin it down, though - I'm sure it can be fixed...

    Lou
     
  20. Aug 23, 2006 #20 of 498
    tivoupgrade

    tivoupgrade Sponsor

    2,494
    0
    Sep 27, 2000
    Chicago, IL...
    Pretty much that's it - you do need to ensure the client is started up, of course. depending on how you started it up, closing the telnet session may have killed the process - you might want to telnet back in and verify that its running:

    ps -aux | grep gotomydvr

    should do the trick.
     

Share This Page