Superpatch / MRV on dtivo's

[grazit]

Hi,
I have two patched dTivos, a HDVR2 and a RCA40. Both have been build from instantcake and PTVnet followed by Superpatch. Everything works fine on both, I have FTP WebTivoPlus telnet etc. They both show the music and picture entry on the main menus and non of the scripts I ran ever reported an error. The really strange part (or at least the part I don't understand) is although the both see my pc running tivoserver as DVR they can tranfer video from the do not see each other. Is there something I can check or can someone suggest something I can do to understand why they can see my PC on the network but not each other. Ps Same network, same subnet for all three devices. Thanks in advanced for the help.

Grazit

[PlainBill]

How did you set the network address? Also, read here (http://www.dealdatabase.com/forum/showthread.php?t=43375) for networking issues under 6.2.

PlainBill

[grazit]

all the networking is default PTVnew i.e. Dynamically assigned by the router on the same (only) subnet. No filtering by the firewall within the local network.
Thanks for the quick reply. I've browsed the link but I'll dig in and work it through those suggestions and come back and either report success to close this thread or ask for more help...

[fantmn]

How did you set the MRV name of the Tivos? After superpatch there is a step required to set the Tivo name. If you telnet to the Tivos can you ping one tivo from the other? DNS issues can also cause the Tivos not to see each other. The Tivos should see each other in the Now Playing list. I use static addresses on my Tivos.

[grazit]

I ran the script provided as part of the Superpatch to set the name. Now that you bring it up even though I ran that script when I looked at my router tables I saw the correct IP assigned to each mac address (correct because I can telnet or FTP to that IP and log in) but It does not show a name associated with the IP (as it does with my PC for example). I'll try pinging as soon as I get home. Should I be able to ping both the DNS assigned IP AND the name I set in the superpatch script?

[cheer]

The name assigned in the Superpatch (actually, in the set_mrv_name) script isn't an IP/DNS name but a Tivo MRV name. So no, you won't be able to ping by name.

[grazit]

thanks guys,
I'll be back after I do my homework

[fantmn]

Just to state the obvious, I assume you did a reboot after the set_mrv_name on each tivo. I seem to remember that my tivos showed up in the now playing list even before I ran the set_mrv_name script just with the last 4 characters of the service number as the name. There is another script around that removes HMO/MRV certificates issued by tivo (DTV) details here. (http://www.tivocommunity.com/tivo-vb/showthread.php?p=3115144&&#post3115144) I think set_mrv_name should take care of this but it does not hurt anything if you run it and nothing is there.

[eastwind]

Are you allowing the DTiVos to make daily calls?

ew

[grazit]

Update after following some of the suggestions made here.
1. both boxes can ping each other

2 . reading the tivolog
No entry on either box containing the word tivoconnect which
I would have expected after having read some of the message threads

IN tvlog from box A

Mar 10 21:59:39 (none) KnownHostListener[183]: Entry changed: 999365663613219 "ThomPC" tcd/Series2 4.0.1-01-2-240 broadcast @ 192.168.1.14 : 136131/-1

IN tvlog from box B
Mar 10 21:59:38 (none) KnownHostListener[184]: Entry changed: 999365663613219 "ThomPC" tcd/Series2 4.0.1-01-2-240 broadcast @ 192.168.1.14 : 74392/-1

ThomPC is my PC running tivoserver

from dhclient leases (same on both boxes except for the local ip)
and correct
}
lease {
interface "eth0";
fixed-address 192.168.1.4;
option subnet-mask 255.255.255.0;
option routers 192.168.1.1;
option domain-name-servers 71.243.0.12,68.237.161.12;
option dhcp-lease-time 86400;
option dhcp-message-type 5;
option dhcp-server-identifier 192.168.1.1;
renew 6 2006/3/11 09:31:08;
rebind 6 2006/3/11 18:31:08;
expire 6 2006/3/11 21:31:08;
}

It looks to me like tivoconnect is never started (run) . How can I check this?

No local calls allow
Many reboots after running set_mrv_name over the last two days.

[Jamie]

There is a good summary here (http://www.dealdatabase.com/forum/showpost.php?p=222641&postcount=24) on this issue and possible solutions for you.

To reiterate what's been asked before: how are you setting up your network? "Whatever PTVnet does by default" is not a sufficient answer, since few if any of us here use PTVnet or know how it operates. Are you (aka PTVnet) installing the modules and running dhclient yourself, or are you letting the tivo software take care of it? The best approach with 6.2 is to let the tivo software do all the network setup and config.

[grazit]

Guess I forgot you guys might be more hands on than using newbie tools like PTVnet. PTVnet gives you two options on install. 1.create a static IP or
2. allow the ip to be set via DHCP. I'm using DHCP as reccommened in the link you provided.

All startup scripts including (I assume) the one that starts dhclient are set by the PTVnet install process, my userstanding is they are pure Tivo native scripts but if someone can tell me what directory to look at or what the normal startup scripts are called I'll research what they do and in what order they do it. I did read the link you provided earlier. That where I got the idea to search the tvlog for things like "Added TiVoConnect broadcast address " etc. I wasn't sure it all applied since it was referencing the 4.x superpatch and of course I used SuperPatch67. I'll reread.
Thanks

[Jamie]

Guess I forgot you guys might be more hands on than using newbie tools like PTVnet. PTVnet gives you two options on install. 1.create a static IP or
2. allow the ip to be set via DHCP. I'm using DHCP as reccommened in the link you provided.

All startup scripts including (I assume) the one that starts dhclient are set by the PTVnet install process, my userstanding is they are pure Tivo native scripts but if someone can tell me what directory to look at or what the normal startup scripts are called I'll research what they do and in what order they do it. I did read the link you provided earlier. That where I got the idea to search the tvlog for things like "Added TiVoConnect broadcast address " etc. I wasn't sure it all applied since it was referencing the 4.x superpatch and of course I used SuperPatch67. I'll reread.
ThanksThat thread and post is specifically about superpatch67.

The startup scripts start with /etc/rc.d/rc.sysinit. Fairly early on it runs /test.conf, if present. Towards the end, it runs /etc/rc.d/rc.sysinit.author. The 6.2 rc.sysinit process is heavily modularized, with many subscripts in the /etc/rc.d/Stage* subdirectories.

In general, folks here don't want to play an unpaid support roll for PTVupgrade. It's sometimes a sensitive subject. If PTVnet does what you want, use it, and go to PTVupgrade.com for support. If it doesn't do what you want, consider hacking yourself instead. It's hard to fix and extend things without understanding how your tivo was hacked in the first place.

[grazit]

I can understand that you guys have already supplied a lot of time and all your getting is a lot of replies from me with "thanks" in them, In fact the networking that the PTV*** program setup seems to be working fine. I can FPT, telnet run TivoWebPlus etc with no problem and thats all they promised, the only thing that's not working is the MRV which is why I ran Superpatch. The SuperPatch problem may well be related to the the way PTV*** setup its networking. I don't know that but I've read a lot of success stories both here and at the other site so I know they can work. I'm only looking for ways to determine why the SuperPatch didn't do what I expected. I'll plow through the startup scripts you mentioned and any logs I find and see where that takes me...
Thanks again.

[Jamie]

I can understand that you guys have already supplied a lot of time and all your getting is a lot of replies from me with "thanks" in them, In fact the networking that the PTV*** program setup seems to be working fine. I can FPT, telnet run TivoWebPlus etc with no problem and thats all they promised, the only thing that's not working is the MRV which is why I ran Superpatch. The SuperPatch problem may well be related to the the way PTV*** setup its networking. I don't know that but I've read a lot of success stories both here and at the other site so I know they can work. I'm only looking for ways to determine why the SuperPatch didn't do what I expected. I'll plow through the startup scripts you mentioned and any logs I find and see where that takes me...
Thanks again.Look for anything loading kernel modules (insmod), setting ip parameters (ifconfig), or running dhclient. It's probably in /test.conf or in /etc/rc.d/rc.sysinit.author, but it could be anywhere. Hopefully they've marked and commented their changes well.

[grazit]

All set, a long all nite session trying to apply some of what I learned doing korn shell scripting few years ago to this stuff and a lot of the reading you guys reccommended and I now have everything working. Thanks for the help. If I can get some sleep I'll review the 12 pages of notes I made and post something that will be useful for someone else.

Thanks Again