Help me figure out why my hacks aren't working

[lennier]

Hey everyone,

I'm getting back into the tivo-hacking game. I had a pretty-well hacked series-1 box that suffered hardware failure a while ago. I got my hands on an older 240-style series 2 box. The hacking of these is way more complicated than I remember the older series-1 stuff being.

I got the instructions from: http://homepage.mac.com/steventamm/tivo.html

So here's what i've done so far. I bought and downloaded the ptv upgrade LBA48 CD with enhancements from ptv. (I'm asking on this forum because you guys were a lot more helpful to me in my series 1 days!) This CD included pre-prepared killhdinitrd kernels.

I copied the killhdinitrd kernel to /var/hacks, and applied it with:
tpip -k newkernel.px -o oldkernel.px.bak /dev/hd? (where ? was the correct partition name)

I then created a /etc/rc.d/rc.sysinit.author file as instructed in the previous instructions.

After doing that, I still can't telnet into my tivo. the built-in series-2 webserver works (I can web to it) but I cannot telnet into it. I looked at /var/log/kernel, but I don't see any evidence of my rc.sysinit.author even being run.

so here's my 2 questions:
1) How do I know id I installed the killhdinitrd'd kernel properly?
2) Do the instructions above miss steps?

[cheer]

Probably. What version of the Tivo OS are you running?

If you pull the drive and your rc.sysinit.author is still there, then killhdinitrd'd kernel worked fine. (Also, what partition did you dd the kernel to? How did you verify that it was the correct one?)

Depending on your sw version, this could just be an iptables issue. IF you are running 7.x, you need to do the following:
Put the Tivo drive back in your pc
Boot up off the PTV Upgrade CD
Mount your root partition ("mkdir /mnt/tivo" "mount /dev/hd# /mnt/tivo") ("#" being the partition number of your active root)
Execute the following commands:cd /mnt/tivo/sbin
mv iptables iptables.old
echo -e '#!/bin/bash\nexit 0' > iptables
chmod 755 iptables
That will remove the firewall rules blocking you. Again, I am assuming you are running 7.x. If it's a different version, let us know and we can go from there.

[lennier]

Probably. What version of the Tivo OS are you running?

If you pull the drive and your rc.sysinit.author is still there, then killhdinitrd'd kernel worked fine. (Also, what partition did you dd the kernel to? How did you verify that it was the correct one?)

My /var/hacks was still there after several reboots, so according to this, at least, i'm golden.

I know the root partition was the one with a full /etc/ directory (not the one in /var with just resolv.conf in it)


Depending on your sw version, this could just be an iptables issue. IF you are running 7.x, you need to do the following:
Put the Tivo drive back in your pc
Boot up off the PTV Upgrade CD
Mount your root partition ("mkdir /mnt/tivo" "mount /dev/hd# /mnt/tivo") ("#" being the partition number of your active root)
Execute the following commands:cd /mnt/tivo/sbin
mv iptables iptables.old
echo -e '#!/bin/bash\nexit 0' > iptables
chmod 755 iptables
That will remove the firewall rules blocking you. Again, I am assuming you are running 7.x. If it's a different version, let us know and we can go from there.

It's 7.something. (i'm not at home right now) I'm going to try your suggestion and i'll let you know how it goes.

Does running /etc/netfilter-disable from sysinit.author not work for sw versions past 7x?

EDIT: I agree it's an ipfilter issue, as i'm not getting a TCP-RST when I attempt to connect, i'm just wondering why /etc/netfilter-disable didn't work

Thanks for the help!

[cheer]

No it doesn't -- you definitely need to do the iptables mod instead. Let us know how it goes.

[lennier]

No it doesn't -- you definitely need to do the iptables mod instead. Let us know how it goes.

Still didn't do it.
It still looks like there's a firewall up on the tivo: i can still get a response from port 443 and port 80, but nothing else.

EDIT: BAH. hdc4 was NOT my current root partition. Hdc6 was.

When I made the modifications to that partition, strangely enough it works now.

[cheer]

Hope you mean hdc7 -- hdc6 should be your kernel partition.