HMO almost there

[gsxrpilot]

OK I have searched until My eyes are red but...

I installed 4.0, sleepers monte, then superpatch-4all on my DVR-39 and HDVR2. HMO says it is active for all services and when I first had it, I could look at music and pictures from my PC (very cool, thanx a TON to all who helped make this possible) But for some reason this stopped working and I could never get multi room viewing to work. The DTIVOs see one another but when I select them in now playing, it says the one I am working on is not enabled for transfers. Also, it seems no matter how many times I run setmrvname successfully, it does not show up in the system information page (The DTIVOs are called by their service number in now playing) Also the TIVO publisher refuses to connect any more. I have tried endless combinations of network settings (auto, static IP. I first had my home network as 192.168.254.X but changed it back to 192.168.1.X since that seems to be the standard) I have 192.168.1.250 blocked on my router but before I did this I think the DTIVOs phoned home over the network (I got Best Buy music and stuff) Could this have disabled everything? Is my only choice to start from scratch and ensure it never phones (or telnets as it were) home? Any help would be greatly appreciated. Thanx

[DocTauri]

No need to rebuild, the problem will just happen again. This is typically caused by the box phoning home (ok, not really phoning, it's tcp/ip). They make this call every 15 minutes. If it successfully connects, it then asks Tivo about itself (i.e. What's my name). Not getting any info (or perhaps getting an "invalid account" response from Tivo), it resets it's name to it's S/N, and loses the ability to talk to the other Tivii on your network (btw: the name shown in System Info is obtained from this call home, NOT from anything you do w/setmrvname). On my boxes (HDVR2's), I just set a bad route to Tivo:
route add -host 204.176.49.2 gateway 192.168.1.253
forcing all traffic to Tivo through a non-existant machine/router.

This ensures that any attempt to phone home will fail. This has solved these issues for my 4 boxes. Do this, then setmrvname again and I'll bet it works.

Now, blocking your Tivo (I'm assuming that's the 192.168.1.250 box you referred to) from outbound access at the router should have worked, not sure why it's not, but try the above and see what happens.

Also, if you want to remove that route, do:
route delete 204.176.49.2

Doc

[gsxrpilot]

Thanx so much for the prompt reply. Would I want to put that route command in my rc.sysint.author file so that when the system reboots it retains this? Also, I'm not sure I configured my router correctly. Under the Filter menu I have the ability to enter IP addresses for :

IP Filters
TCP Port Filters
UDP Port Filters

I'm wondering which category I put My TIVOs IP addresses in order to block their outside access. Again thank you for your support.

[DocTauri]

Yes, that would be best, but I've found that you need to sleep for about 60 seconds before doing this, otherwise for some reason it doesn't stick.

As for your router, I'd imagine it's IP Filters. Mine is set up differently, and calls it "Filtered IP Private Range". Entering the IP (or range of IP's) here blocks them from outbound access and works equally as well as creating bad static routes. You would only want to do this on the router though if the Tivo has a statically assigned IP.

Doc

[gsxrpilot]

Its interesting because it seems routers all have differerent configuration menus that use different terminology. In my case I believe that I need to enable TCP port blocking for my tivo's IP's, blocking port 80. Maybe an IT expert can confirm this. Nonetheless, I added your route command to the end of my rc.sysinit.author after a sleep 60. I also added the setmrvname command at the end to ensure it should be called what I want. Thanks for your help.

[DocTauri]

Blocking port 80 would work as well, it all depends on how much control you'd want over it. A static route on the box like I showed you would be the least obtrusive, the box could still do anything you wanted on the net as long as it wasn't to that one IP. Blocking 80 would be next, the box could do most things, but would not be able to do any http to any address. Blocking the IP would be the most secure, stopping any and all outbound traffic from the Tivo.

Doc

[gsxrpilot]

Well, still no luck. I know I am blocking access because I tried to connect manually over the network and it said incorrect gateway (just as you would expect the route command to do) One theory I have is that once TIVO sees your unauthorized account, whatever they do disables it forever. The second theory I have is that the version of software I have is incompatible. I noticed everyone refers to 4.01b-240 and mine is 401b-230. I'm wondering if that might be the problem. I have been trying to get a new image on edonkey with no luck. If anyone cares to share the -240 image I would really appreciate it.

[NutKase]

I noticed everyone refers to 4.01b-240 and mine is 401b-230. I'm wondering if that might be the problem.

The 'b' images are differentiated like 4.0.1b-01 vs 4.0.1b-02.

The last three numbers, -140, -230, or -240 don't matter.


NutKase

[gsxrpilot]

The actual name from tivoweb is 4.0-01-2-230. Just out of curiosity, what might the 230 mean? I did a search and everyone seems to refer to -240.
So to confirm NutKase, you think my version should be OK for MRV? And thank you so much for your work with this.

[NutKase]

The actual name from tivoweb is 4.0-01-2-230. Just out of curiosity, what might the 230 mean? I did a search and everyone seems to refer to -240.
So to confirm NutKase, you think my version should be OK for MRV? And thank you so much for your work with this.

You're welcome.

Yes, you have 4.0, we refer to the software versions by everything up to the first -

Superpatch-4all works fine on 4.0.

I've forgotten what the last 3 are. mrblack51's posted some on it. Not worth a search because it doesn't matter.

-240 was from a 40hr standalone s2
-140 was from a 60hr standalone s2

no real pattern that I remember, as I said, I wouldn't worry about it.


NutKase

[DocTauri]

Well, still no luck. I know I am blocking access because I tried to connect manually over the network and it said incorrect gateway (just as you would expect the route command to do) One theory I have is that once TIVO sees your unauthorized account, whatever they do disables it forever. The second theory I have is that the version of software I have is incompatible. I noticed everyone refers to 4.01b-240 and mine is 401b-230. I'm wondering if that might be the problem. I have been trying to get a new image on edonkey with no luck. If anyone cares to share the -240 image I would really appreciate it.

I can confirm that the connection to Tivo doesn't permanently disable it. It took me a week to figure out why my name kept dropping off (set it, 30 min. later it's gone).

Now, you said, "I know I am blocking access because I tried to connect manually over the network and it said incorrect gateway"... Please clarify, from where (external to your network, internal to your network) did you try to connect to the Tivo, and what port?

[philhu]

Something wierd here

I have 4.01b-02 on 2 tivos

I have the hmo patch running AND both machines are subscribed and get guide data from Tivo. Both machine mrv/hmo each other just fine and the names have never changed.

Do you have a subscription? If so, just go to the web site, register the tivos and hmo will be on anyway. Set them each to the same names as your setmvrname script set them too.

[DocTauri]

Phil, you're on SA's, he's on DTivo's, so he doesn't actually have a tivo.com account (DTV handles that).

Doc

[gsxrpilot]

I tried connecting through the tivo menu itself, under settings, tcp/ip settings, I set up connect through network and when it tried to contact tivo i got the invalid gateway (thanks to your route command) I can still bash, ftp and tivoweb to the tivo internally so I know it it speaking ethernet. I think I will maybe go with my second theory about starting over with another image (another member very graciously provided me with the -240 version) I think this is about the 8th time I have re-imaged so I should be good at it. What is killing me is the first time I did it all, I had music and videos working with my PC and tivo server. I feel I'm so close but yet so far away....
Thanx again for your support.

[philhu]

Phil, you're on SA's, he's on DTivo's, so he doesn't actually have a tivo.com account (DTV handles that).

Doc

Ah, ok

I misread it. Sorry

[DocTauri]

You really shouldn't need to reimage... Let me verify, you did the bad route (and verified it's there by netstat -rn) on BOTH boxes?

[gsxrpilot]

Here's what I get on both:
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
204.176.49.2 192.168.1.253 255.255.255.255 UGH 40 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 40 0 0 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG 40 0 0 eth0

I'm assuming tivo.com is contacted at 204.176.49.2 port 80?

[NutKase]

I think I will maybe go with my second theory about starting over with another image (another member very graciously provided me with the -240 version) I think this is about the 8th time I have re-imaged so I should be good at it.

Please don't re-image. as Doctauri said, you shouldn't need to. As I said, the -230, -240, -140 or whatever doesn't matter.

You're about to confirm as a third case that this router don't talk to tivo is the problem DTivo's and when you do I can update the superpatch-4all release and get rid of this problem for all. I need confirmation and a good description of the problem though.

As a matter of fact... MODS, can you please append this to the superpatch-4all support thread? Thanks.


NutKase

[DocTauri]

Here's what I get on both:
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
204.176.49.2 192.168.1.253 255.255.255.255 UGH 40 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 40 0 0 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG 40 0 0 eth0

I'm assuming tivo.com is contacted at 204.176.49.2 port 80?

Let's try a different tact. When you set the name on both, can MRV at least for a while? Can you pull up the list of shows on the opposite box at all, or does it just plain never work?

[gsxrpilot]

MRV Just plain never works.

[DocTauri]

MRV Just plain never works.
But they show each other in the now playing list (at least by serial number) right? And after doing setmrvname do they ever show the name, or always just the s/n?

[gsxrpilot]

Always just the SN. BTW, on another drive I re-imaged with -240 and the setmrv worked. Of course, this time I made sure my cable modem was unplugged to insure no phone home calls were made. This seems to work a lot better so I think the version of the software is a factor.

[NutKase]

Always just the SN. BTW, on another drive I re-imaged with -240 and the setmrv worked.

I've already posted, more than once... the -230, -240, -140 or -999 HAS NO EFFECT WHATSOEVER as far as this board knows... err... and it knows quite a bit. :)

The set_mrv_name updated by alldeadhomiez, and linked into the release is the proven correct one.

The other variables ARE important and everything you do can help everyone get to the bottom of the difficulties... SO, keep posting and help us.

Of course, this time I made sure my cable modem was unplugged to insure no phone home calls were made.

This proves that there are other issues at work. Primarily the DNS or 'phone home calls'.

We're getting there. Thanks to folks like you.


NutKase

[NutKase]

It appears that I can't keep myself from trying to help and troubleshoot here, in this thread...

I really wish this information was in the 'superpatch-4all, support thread'

It doesn't really matter though... If we figure it out, I'll link it :)...


NutKase

[gsxrpilot]

I noticed my version of -240 has no menu backgrounds (video remains on in background) If that might be a factor.

[NutKase]

I noticed my version of -240 has no menu backgrounds (video remains on in background) If that might be a factor.

Problems with menu backgrounds or animations...

OR

problems that make you have to 'pause' live TV...

are the result of incomplete tivo backup images (.mfs or .bak) that were backed up using LESS than '-f 9999' with mfstools.

It's NOT a problem with the -240, -230, or -140 tivo software versions.


NutKase

[DocTauri]

Early on, I accidentally backed up a S2 drive using S1 commands (i.e. omitting the -f4138 so it was only mfsbackup -6so ...), this caused exactly what you're experiencing.

Doc

[gsxrpilot]

So it would seem even though we are all working with essentially the same version of core software (4.01b) there are many different images we are starting with which probably used different and eroneous methods of backing up. So I guess I have a couple questions and possibly solutions to the different behaviors we have seen:

1. Should all versions and backups of 4.01b be using the same tivoapp?
2. Is all that superpatch does is modify tivoapp?
3. If so, couldn't we all just use one version of tivoapp which has what we need after restoring whichever image?

I know I have spent countless hours restoring different images to 4 different tivos, then meticulously setting them up for my home network, extractions, tivoweb, hmo, etc. only to discover that the image I started with was deficient (something which I had no control over and can only be discovered through trial and error) So to save me and possibly others hours of restoration and re-building, couldn't we just use a known good patched version of tivoapp? (although I must say I have learned much in the process)
I suppose there are some grey areas about sharing this file which could provide roadblocks but it seems logical to me. Let me know what you guys think.

[NutKase]

1. Should all versions and backups of 4.01b be using the same tivoapp?

All 4.0.1b tivoapp versions have an md5sum which is the same.

2. Is all that superpatch does is modify tivoapp?
Yes.

3. If so, couldn't we all just use one version of tivoapp which has what we need after restoring whichever image?

Yes.


NutKase