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

Zipper'd HR10-250, can't make daily call over eth?

Discussion in 'TiVo Underground' started by NickCat, Sep 17, 2006.

  1. Sep 21, 2006 #61 of 102
    Yog-Sothoth

    Yog-Sothoth MRV Junkie

    388
    0
    Jun 14, 2005
    Fountain, CO
    You have no reason to make a Daily Call now.
     
  2. Sep 21, 2006 #62 of 102
    HUGE2U

    HUGE2U New Member

    120
    0
    Jun 28, 2002
    I read over at DDB (I think) that you d/l a new set of logos on the first call out after the update.

    HUGE
     
  3. Sep 22, 2006 #63 of 102
    HUGE2U

    HUGE2U New Member

    120
    0
    Jun 28, 2002
    From another post:

    HUGE
     
  4. Sep 22, 2006 #64 of 102
    Finnstang

    Finnstang King of the North

    8,666
    0
    Sep 11, 2003
    Winterfell
    The DEBUG_BOARD value is on line 45.
     
  5. Sep 22, 2006 #65 of 102
    Yog-Sothoth

    Yog-Sothoth MRV Junkie

    388
    0
    Jun 14, 2005
    Fountain, CO
    Thanks for the 6.3 info; I'll check it out.
     
  6. Sep 23, 2006 #66 of 102
    Finnstang

    Finnstang King of the North

    8,666
    0
    Sep 11, 2003
    Winterfell
    Anyone know how to block the TiVo from dialing out other than running fakecall? Since the route add statements have been removed from the author file, I was curious if there is another way to do the same thing.
     
  7. Sep 23, 2006 #67 of 102
    tall1

    tall1 New Member

    207
    0
    Oct 12, 2004
    twin cities
    Why don't you want to run fakecall? There is a small fix in the FINALLY! thread at the other place to get it working.
     
  8. Sep 24, 2006 #68 of 102
    brj8826

    brj8826 New Member

    89
    0
    Nov 2, 2002
    I completed all of these steps but for some reason mine won't DL 6.3. How often should I redial?
     
  9. Sep 24, 2006 #69 of 102
    Yog-Sothoth

    Yog-Sothoth MRV Junkie

    388
    0
    Jun 14, 2005
    Fountain, CO
    The slices won't come down until early morning.
     
  10. Sep 24, 2006 #70 of 102
    Finnstang

    Finnstang King of the North

    8,666
    0
    Sep 11, 2003
    Winterfell
    I have already fixed my fakecall with the change from the other forum, I am just curious if there is another way to block the tivo's access to tivo like we did before with the route add statements.
     
  11. Sep 25, 2006 #71 of 102
    wasdvd

    wasdvd New Member

    6
    0
    Feb 15, 2004
    Thanks so much, guys. Making DEBUG_BOARD=true and commenting out the loopback routes WORKED!

    I had been trying to get my Zippered/tweaked 3.1.5f to make its call for several days, and these changes let it succeed and downloaded the 18 minute data in 5 minutes or less.

    My wife will be more than pleased that I am not rebooting HR10-250 all evening.
     
  12. Sep 25, 2006 #72 of 102
    Runch Machine

    Runch Machine New Member

    1,048
    0
    Feb 7, 2002
    Minneapolis
    For those interested in allowing daily calls over ethernet on 6.3 you need to make the following change:

    Edit /etc/rc.d/StageD_PreMfs/rc.Sequence_150.CheckForDebug.sh

    change:
    export DEBUG_BOARD=false

    to:
    export DEBUG_BOARD=true
    _________________________________

    I made the change above and now my HD Tivo reboots when I have it make the call. Any ideas? Do I still need ,#401 in dialing prefix? I still have it. I am on 6.3a.

    Is there any other changes needed to make this work besides editing the line shown above and adding ,#401 into the dialing prefix?
     
  13. Sep 26, 2006 #73 of 102
    ronkuba

    ronkuba New Member

    21
    0
    Feb 22, 2005
    I'm having the same problem. I'm on 6.3.
     
  14. Sep 26, 2006 #74 of 102
    Finnstang

    Finnstang King of the North

    8,666
    0
    Sep 11, 2003
    Winterfell
    ,#401 is not needed. Not sure if that is an issue or not, but it isn't needed.
     
  15. Sep 26, 2006 #75 of 102
    Runch Machine

    Runch Machine New Member

    1,048
    0
    Feb 7, 2002
    Minneapolis
    But I can't get rid of ,#401 because when it goes to test the new configuration it reboots. Is there a file I can edit to get rid of ,#401?
     
  16. Sep 28, 2006 #76 of 102
    Markman07

    Markman07 Active Member

    2,209
    0
    Jul 18, 2001
    Minnesota
    Mine still won't dial out over ethernet. I used the zipper and everything else works (telnet, ftp, twp). Still using version 3.5xxx. Read through the thread a few times now but no luck.

    I changed the debug_board value to true in my /etc/rc.d/rc.sysinit file.
    I noticed I had two author files (one in enhancements and one in /etc/rc.d). The copy in rc.d had the route values and I (#) commented out the top two values while leaving the gateway alone. Rebooted the TIVO a few times. Changed the prefix to ,#401 and it never gets past the dialing part. Says did not answer Verified both files and the prefix multiple times. Not sure where to go from here.
     
  17. Sep 28, 2006 #77 of 102
    Finnstang

    Finnstang King of the North

    8,666
    0
    Sep 11, 2003
    Winterfell
    Have you checked to make sure the change to rc.sysinit took?
     
  18. Sep 28, 2006 #78 of 102
    Markman07

    Markman07 Active Member

    2,209
    0
    Jul 18, 2001
    Minnesota
    Unless you mean something else, I have viewed the rc.sysinit file after the reboot and the value export DEBUG_BOARD=true is still there and looking good.
     
  19. Sep 28, 2006 #79 of 102
    Markman07

    Markman07 Active Member

    2,209
    0
    Jul 18, 2001
    Minnesota
    Don't ask me why. I tried multiple times last night. But today looking at TWP I see this SCREEN module I had never used before. I accessed the menus and forced a phone call and it went through. Amazing module. Too bad it won't work once the upgrade happens. But I think it is looking good now. Now on to step 2. (to leave or not to leave) the hacks when I upgrade it.
     
  20. Sep 29, 2006 #80 of 102
    Markman07

    Markman07 Active Member

    2,209
    0
    Jul 18, 2001
    Minnesota
    Try posting some of the recent activity from your tclient log file. Maybe someone can tell you more then...
     

Share This Page