Need for a How-To on Static Ip Configuration

[DeTer]

Would someone please be kind enough to post a how-to for various set-ups involving a static Ip. I have read most of the threads on this and I am still some what confused as some are dealing with having a router while others are using a cross-over cable going directly to a NIC. I am some what Linux & Networking challenged as I know others are as well. It was just a thought that one of our experts could come up with a how to for both ends of the network(pc end & dtivo end)....with & without a router.


Any takers?
thx
DeTer:confused:

PS: My wireless gatway just died and I can't extract my Seinfeld episodes:(

[captain_video]

Ok, first of all, if you have any sort of black box between your Tivo and your PC (e.g. router, switcher, or hub) you make all connections using a regular CAT-5 ethernet cable between each unit. If you are connecting directly from the Tivo to your PC, then you need a crossover cable.

If you are using a TurboNet or AirNet adapter in your Tivo (standalone or DTV model), download the latest software (check the 9th Tee site for links to the download site) and instructions for setting it up. Burn the image to a CD and set up your PC to make the CD the 1st boot device. Install your Tivo A drive as the secondary master and then boot from the CD. Follow the installation instructions and you will end up with a static IP address for your Tivo. If using a router you will need the IP address of the router to enter when prompted during the setup.

[DeTer]

Originally posted by captain_video
Ok, first of all, if you have any sort of black box between your Tivo and your PC (e.g. router, switcher, or hub) you make all connections using a regular CAT-5 ethernet cable between each unit. If you are connecting directly from the Tivo to your PC, then you need a crossover cable.

If you are using a TurboNet or AirNet adapter in your Tivo (standalone or DTV model), download the latest software (check the 9th Tee site for links to the download site) and instructions for setting it up. Burn the image to a CD and set up your PC to make the CD the 1st boot device. Install your Tivo A drive as the secondary master and then boot from the CD. Follow the installation instructions and you will end up with a static IP address for your Tivo. If using a router you will need the IP address of the router to enter when prompted during the setup.

Captain,

If you look through the threads you will notice what I meant about the need for the How To on this subject. I have been reading all of the threads and I am more confused now than I was when I started. What I would like to see is a How To set up a static IP on a fresh install of 25xtreme with Kravens upgrade added. It would also be nice if there was a How To to achieve this without Kravens upgrade installed.
In reading all the different threads there appears to be many different ways to accomplish the static IP. Now I am not totally Stupid but I really don't have a great handle on networking, but I will add that I have a better handle since I have been reading these threads on the subject.
Today I tried to accomplish the task and ended up trashing my DTiVo to the point where I now have my 2nd fresh load of 25xtreme & Kravens upgrade in the past 2 days.

Now for some questions on completing my task of the static IP

1) I know I have to edit my rc.remote-login to look like this: assuming a TiVo IP of 150:

#!/bin/bash

ifconfig net0 192.168.0.150 netmask 255.255.255.0
route.tivonet delete default 2> /dev/null
route.tivonet add default gw 192.168.0.1 netmask 255.255.255.0 dev net0

echo "Starting Telnet"
tnlited 23 /bin/bash -login &

echo "Starting fixdemo"
if [ -e /tvbin/fixdemo.tcl ]; then
/tvbin/fixdemo.tcl >> /dev/null &
fi

echo "Starting TiVoWeb"
if [ -e /tivoweb-tcl/httpd-tt.tcl ]; then
/tivoweb-tcl/httpd-tt.tcl >> /dev/null &
fi

echo "Starting TiVoFTPD"
if [ -e /tivo-bin/tivoftpd ]; then
/tivo-bin/tivoftpd >> /dev/null &
fi

2) I beleive that I have to have a rc.net that looks like this:

#!/bin/bash
# Copyright (c) 2001-2002 TiVo Inc.
#

if [ "$DEBUG_BOARD" != true -o "$dhcp" == true ]; then
if detectDynamicNet; then
mkdir -p /var/state/dhcp
# /sbin/dhclient -q "$DYNAMIC_NET_DEV" 2>/dev/null &
fi

/etc/rc.d/rc.remote-login &
fi

3) Now it is my understanding that I should rename:
dhclient to dhclient.bak

Now after completing 1 & 2 do I need to chmod +x the files?

thx
DeTer

[zabs]

Deter,

1) Looks good.

2) Again looks good. I also commented out the mkdir command. Why make a state directory for the dhcp if you're not going to use it? But it won't hurt anything having it there.

3) You shouldn't have to rename the dhclient binary, as you commented it out in #2 so it shouldn't be running. But again, it also won't hurt to do it. (just remember you did do it, if you ever decide to use dhcp.)

You shouldn't have to chmod +x the files after editing them, as they should already be executable. And should look something like:

bash-2.02# ls -l /etc/rc.d
total 34
-rwxr-xr-x 1 0 0 1762 Jun 30 2001 finishInstall.tcl
drwxr-xr-x 2 0 0 1024 Nov 8 08:35 init.d
-rwxr-xr-x 1 501 501 3985 Dec 5 07:10 rc.arch
-rwxr-xr-x 1 501 501 257 Jan 5 03:07 rc.net
-rwxr-xr-x 1 0 0 1132 Dec 5 07:18 rc.remote-login
-rwxr-xr-x 1 501 501 19989 Dec 5 07:10 rc.sysinit
bash-2.02#

[zabs]

Just noted this (and it may have just been a typo in your post)

1) be sure to have a 0 (zero) after net for this line:

route.tivonet add default gw 192.168.0.1 netmask 255.255.255.0 dev net0

[DeTer]

Originally posted by zabs
Just noted this (and it may have just been a typo in your post)

1) be sure to have a 0 (zero) after net for this line:

route.tivonet add default gw 192.168.0.1 netmask 255.255.255.0 dev net0


Zabs

Most of what I had there was a copy and paste from what I have read in other threads. So hopefully I will try this tomorrow and all will be OK. Thx for the input.
DeTer

PS: Just waiting for my gatway to come back, it died on me and I figured I would try this to see if my extraction speed i any better. It takes me about 22 - 24 minutes for a Seinfeld episode.

[captain_video]

I'm no expert on networking and I'm certainly no expert on Linux. I've never had to edit the rc.remote-login file or any other file to get a static IP address. All I ever did was download the TurboNet software, burn it to a CD, and follow the instructions for setting it up. I've set up at least three different DTivos using this method and all of them have had a static IP address without doing anything extra. I've been able to telnet and perform extractions flawlessly with each and every one of them. All this crap about editing files for a static IP is ridiculous (I suppose some find it easier and less daunting than having to install your Tivo drive in a PC for the TurboNet SW installation). You also don't need Kraven's upgrade to get a static IP. In fact, Kraven's upgrade sets up your DTivo to act as a DHCP client, which is why there are so many posts about editing the rc.remote-login file after the fact. I installed the TurboNet software AFTER I installed Kraven's upgrade and all my DTivos are running fine with static IPs. It may seem like more work to pull your Tivo drive for installation of the SW in a PC but it's a snap to set up and doesn't take but a few minutes to do. The installation instructions are the How To on this installation as no other is necessary. It seems to me that trying to edit the rc.remote-login file is where everyone experiences pitfalls in the set up. Why complicate things when the TurboNet SW installation is the least painful way to go.

[zabs]

That seems a bit long for a 30 min tv ep.

I get about 1.5 megs per second or around 10 minutes for a full 1 hour show.

[DeTer]

Originally posted by captain_video
I'm no expert on networking and I'm certainly no expert on Linux. I've never had to edit the rc.remote-login file or any other file to get a static IP address. All I ever did was download the TurboNet software, burn it to a CD, and follow the instructions for setting it up. I've set up at least three different DTivos using this method and all of them have had a static IP address without doing anything extra. I've been able to telnet and perform extractions flawlessly with each and every one of them. All this crap about editing files for a static IP is ridiculous (I suppose some find it easier and less daunting than having to install your Tivo drive in a PC for the TurboNet SW installation). You also don't need Kraven's upgrade to get a static IP. In fact, Kraven's upgrade sets up your DTivo to act as a DHCP client, which is why there are so many posts about editing the rc.remote-login file after the fact. I installed the TurboNet software AFTER I installed Kraven's upgrade and all my DTivos are running fine with static IPs. It may seem like more work to pull your Tivo drive for installation of the SW in a PC but it's a snap to set up and doesn't take but a few minutes to do. The installation instructions are the How To on this installation as no other is necessary.



Captain

Thanks for the reply as you have just answered a question I was wondering about but forgot to ask and that was if you could run the Turbonet install Cd after already having Kravens upgrade installed. yes it is more of a hastle to pull the drive but in trying it the other way I've had to pull it twice and re-install 25xtreme. kinda like the faster I go the behinder I get!
:)
BTW the only reason i'm interested in the static IP is because of my crashed gateway, will probably go back to dhcp assigned unless the extraction speed is really a lot faster.

thx again
DeTer

[zabs]

Captain I think as ussual you've hit it on the head.

The reason people are editing rc.remote-login etc. is because they have already installed Kraven's update.

I installed it because I am lazy/busy and I didn't want to pull the drives out of the tivo (I'm paying for it at the moment cuz my static ip settings are working after a reboot) I knew it would set the tivo up for DHCP and that I would need to change some things around to fix that.

I think alot of people are just installing Kraven's because they think it is "necesary" to get their turbonet card working. It might not be a bad idea to note something about the Turbonet software in the Kraven's Inside Sticky to let new folks know they have other options...

[BubbleLamp]

Running the turbonet installer puts the commands at the end of rc.sysinit I believe. It may also use eth0, not net0. (I don't know, I never used the installer.) Take a look at the end of your rc.sysinit and see what's there.

[captain_video]

It does use eth0 instead of net0 at the end of rc.sysinit. This doesn't make a difference to me as I have a router set up to block the IP address of both of my DTivos from accessing the internet so they can't dial out. Neither unit has ever taken an update and they have never been connected to a phone line. Performing the rc.remote-login file edit may be required for those that need to make this change from eth0 to net0 to prevent their DTivos from connecting to Tivo/DTV HQ and taking updates via ethernet. I operate both of my DTivos without covers and the drive racks aren't fastened down so pulling the drives is a quick task for me.

For a while, I was pulling them almost on a daily basis to perform some sort of upgrade or mod in my early stages of hacking. I hardly ever have to mess with them anymore but I still keep the cover off for cooling purposes. The hard drives seem to run much cooler that way and I don't find them at all noisy. I suppose I've gotten used to the sound to the point where it just becomes white noise and disappears into the background.

[BubbleLamp]

Originally posted by captain_video
It does use eth0 instead of net0 at the end of rc.sysinit. This doesn't make a difference to me as I have a router set up to block the IP address of both of my DTivos from accessing the internet so they can't dial out. Neither unit has ever taken an update and they have never been connected to a phone line. Performing the rc.remote-login file edit may be required for those that need to make this change from eth0 to net0 to prevent their DTivos from connecting to Tivo/DTV HQ and taking updates via ethernet. I operate both of my DTivos without covers and the drive racks aren't fastened down so pulling the drives is a quick task for me.

It may make no difference to you, but that's why you should NOT use the turbonet installer with Kraven's update, you create a conflict with the drivers and routing info being attempted twice.

[captain_video]

I've never had a problem connecting to either DTivo but you're telling me that there is a potential conflict by reinstalling the TurboNet drivers over Kraven's upgrade? Wouldn't the new installation overwrite any previous setup? If not, would it be recommended to edit the rc.remote-login file or whatever to eliminate any such conflict? If so, what needs to be changed?

[BubbleLamp]

Originally posted by captain_video
I've never had a problem connecting to either DTivo but you're telling me that there is a potential conflict by reinstalling the TurboNet drivers over Kraven's upgrade? Wouldn't the new installation overwrite any previous setup? If not, would it be recommended to edit the rc.remote-login file or whatever to eliminate any such conflict? If so, what needs to be changed?

Yes, Kraven loads the NIC drivers in rc.arch, then assigns it an IP in rc.net, then loads stuff like noscramble and sc.tcl in rc.remote-login. He also checks to see if eth0 is already loaded BEFORE he tries to load the driver in rc.arch, but this check will fail, since turbonet puts it at the end of rc.sysinit. On top of all that, the driver Kraven used is hardcoded for net0. This means that if you are going to fix the lines manually because you want to keep the Kraven stuff working, you must remote the stuff Turbonet installs at the end of rc.sysinit, AND modify Kraven's scripts by adding a net0 or devicename=net0 where appropriate.

PS This is all based on reading his scripts, since I don't run his update. If there is something erroneous in my description, please feel free to correct it.

[DeTer]

Well I finally had success in assigning a static IP address to my DTiVo. I didn't use all of what I had posted earlier. Infact if you follow what Kraven had put in his readme file found in the upgrade and rename your /sbin/dhclient to /sbin/dhclient.bak you should have yourself a working static IP address.


How To for clean 25xtreme install with Kraven update:

Note: I used a static IP of 150 for the TiVo.

1) If you want use a static address on their turbonet or tivonet just needs to add the following line to the top of rc.remote-login:
Note: before playing with my rc.remote-login file I made a copy of it, and saved it as rc.remote-login.bak

ifconfig net0 192.168.1.150 netmask 255.255.255.0
route.tivonet delete default 2> /dev/null
route.tivonet add default gw 192.168.0.1 netmask 0.0.0.0 dev net0


this will make your rc.remote-login file look like this, or atleast this is what my rc.remote-login file looks like:

#!/bin/bash

ifconfig net0 192.168.0.150 netmask 255.255.255.0
route.tivonet delete default 2> /dev/null
route.tivonet add default gw 192.168.0.1 netmask 255.255.255.0 dev net0

echo "Starting Telnet"
tnlited 23 /bin/bash -login &

echo "Starting fixdemo"
if [ -e /tvbin/fixdemo.tcl ]; then
/tvbin/fixdemo.tcl >> /dev/null &
fi

echo "Starting TiVoWeb"
if [ -e /tivoweb-tcl/httpd-tt.tcl ]; then
/tivoweb-tcl/httpd-tt.tcl >> /dev/null &
fi

echo "Starting TiVoFTPD"
if [ -e /tivo-bin/tivoftpd ]; then
/tivo-bin/tivoftpd >> /dev/null &
fi



2) use this command to rename your dhclient in your /sbin directory:

mv /sbin/dhclient /sbin/dhclient.bak


After this I rebooted my TiVo with /tvbin/reboot after bootup all was well, I didn't realize that I would have TiVoWeb afterwards as I didn't have it when I was running through my gateway with dhcp IP


Well that is how I managed to get my static IP, lots of thanks go out to many people from the various threads that were discussing methods of accomplishing this, and there appears to be several different ways. This is just a summary of how I did it as it appeared to me to be the simplest way, less edits.

Thx all, and I hope this helps others
DeTer




:D

[captain_video]

Glad to hear you've got it set up and working. Sorry if I supplied any misinformation about loading the TurboNet drivers on top of Kraven's upgrade. Thanks to BL for setting me straight on a few things (I told you Linux wasn't my strong suit). At least now I know why noppv.tcl and a few other scripts aren't being run at bootup. It seems I may have inadvertently buggered them by doing the TurboNet install after Kraven's. I've gotten so used to running them manually after a reboot that it just didn't phase me anymore. I've been considering a reload of Xtreme to correct this so now I know what NOT to do so it'll work next time around. Live and learn.

[strakajagr]

OK, so I have read all of this and am desperately trying to understand...

I have a router and I want to set up my DirecTivo as a DHCP client... I am also running v2.5.2...

Will the 3.0 turbonet drivers work with DirecTivo? The website says they are only for SA tivos... If they WILL, well then it's probably game time... Sounds like I just need to install them of the CD and I'll be in business...

If anyone can answer that, happy days! Thanks.

[strakajagr]

damn... nevermind... there are no such drivers... the most recent turbonet drivers that can be run off of CD are nic_install_20020907, and the read me explicitly states that they won't work for DHCP... so i am again back where i started... damn... i think i am going to use kraven's upgrade

[strakajagr]

damn... nevermind... there are no such drivers... the most recent turbonet drivers that can be run off of CD are nic_install_20020907, and the read me explicitly states that they won't work for DHCP... so i am again back where i started... damn... i think i am going to use kraven's upgrade