Change from modem to broadband

Printable View

06-02-2007, 12:56 PM
meanderingmac

Change from modem to broadband

I'm looking for a bit of help - had the tivo a few years now (sigh - and what a beauty she is) but am of the "if-aint-broke-don't-fix-it" ilk - which usually happens when shifting houses (and internet setup, etc). As a result, knowledge retention on the old workings of tivo are not that fabulous.

so...its a Philips:
Software System: 3.0-01-1-000
Kernel Information
Version 2.1.24-TiVo-2.5
Compile #1 Tue Sep 7 02:27:11 EST 2004

Has a network card connected via cable to an ADSL wireless firewall router for network connection.
Guide data up to now has been via modem. Unfortunately (perhaps the line quality in this rural area) when dialing in it at this property it has always returned a wrong number error message - unless I am listening on the phone (my Tivo may have issues!), so I would network connect via pc and select "make daily call" once a week or so, while listening to it connect, which worked fine for six months or so. The last successful call was Tuesday, Feb 06 at 2:25 pm. Since then I get a "service not answering" error message.

Not sure what is causing this (Aunty Teressa at may have changed the Xtra dial-up??), but I would like a fully automated setup anyway, so looked to get guide data via broadband (which I have always had available here).

So I telneted and rw to Read Write.

Replaced the tclient.conf in etc/ containing the dial up, account name and password using aceFTP with:

# This is for the server emulator on minnie.
127::210.48.107.133:8000:::

Telnet ro to read only.

Then set Pal guided setup mode and rebooted. Went through the setup, but when it goes to dial it comes up with "Failed. No dial in number chosen". Tried the ,#401 prefix, same result.

Any suggestions for automating either broadband or dial-up guide data would be much appreciated...

...Embarassed in anticipation of the simple solution...
06-02-2007, 02:21 PM
Darren King

Quote:

Originally Posted by meanderingmac

Has a network card connected via cable to an ADSL wireless firewall router for network connection. Guide data up to now has been via modem.

Huh? You have ADSL but choose to make calls via dialup for guide data? Why don't you simply use the ADSL connection over the network to get guide data?
06-02-2007, 03:44 PM
Wibble

A couple of thing to check, do you have your ADSL router setup as the gateway on your tivo.
(use route to find out)

Also try:
wget http://210.48.107.133
you should get something like this: (in which case your connectivity is ok)
--17:39:57-- http://210.48.107.133/
=> `index.html'
Connecting to 210.48.107.133:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1,858 [text/html]

The other thing to check is the line endings on tcclient.conf. But I'm not sure if it matters.
06-02-2007, 04:57 PM
meanderingmac

Ahuh. Had the Tivo up and running here for sometime before I set the wireless network up, so started with dail up and... didn't break, so didn't fix it...

The wget provides the response exactly as listed - so connectivity is okay. How do I check that the router is the gateway on the tivo (you may have guessed that IT is not my occupation)?
06-02-2007, 08:27 PM
petestrash

Might be best to paste your tclient.conf and rc.net files here.

Peter.
07-02-2007, 07:50 AM
meanderingmac

Thanks Peter.

tclient in etc/ contains

# This is for the server emulator on minnie.
127::210.48.107.133:8000:::

rc.net in etc/rc.d/ contains

#
#!/bin/sh
#

if /sbin/insmod -f /lib/modules/turbonet.o macaddr=101010 timing=3 ; then
export DYNAMIC_NET_DEV=eth0
mkdir -p /var/state/dhcp
/sbin/dhclient -q eth0 2>/dev/null &
fi
07-02-2007, 11:35 PM
petestrash

the MAC address looks a little funky, I would have expected octlets like 00:0B:AD:21:2A:1B. But it seems to work for your wget test.

might just want to run though the basic tests here which will also check your gateway amongst other things.

If you want to make any changes use nic_config_tivo.

Peter.
11-02-2007, 03:53 PM
meanderingmac

...finally got a bit of time to check this out...

Here are the checks

[TiVo [p0] ~]# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 coll:0

eth0 Link encap:Ethernet HWaddr 00:0B:AD:10:10:10
inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:45 errors:0 dropped:0 overruns:0 frame:0
TX packets:31 errors:0 dropped:0 overruns:0 carrier:0 coll:0
Interrupt:29

Looking good....

[TiVo [p0] ~]# route
route_info, afname=inet, options=33
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0

another goodie...

[TiVo [p0] ~]# ping -c 5 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=1.9 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.7 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.7 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.7 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.7 ms

--- 192.168.1.1 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.7/0.9/1.9 ms

going fine... even tried the google 216.239.37.99 in California - no problems.

[TiVo [p0] ~]# wget http://131.244.9.101/index.html
--17:37:06-- http://131.244.9.101/index.html
=> `index.html.4'
Connecting to 131.244.9.101:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 7,388 [text/html]

0% [ ] 7,388 0.00G/s ETA 00:00

Last-modified header invalid -- time-stamp ignored.
17:37:08 (0.00 GB/s) - `index.html.4' saved [7388/7388]

Now let me know if I'm wrong... that tells me the network is operating fine and needs no changes. There should be no connectivity problems through the ADSL and its firewall??

Heres where I think the problem is...:(

[TiVo [p0] ~]# dbget /State/PhoneConfig DialPrefix
{}
[TiVo [p0] ~]#

the dialprefix needs to be ,#401 so...

[TiVo [p0] ~]# dbsetx /State/PhoneConfig DialPrefix ',#401'
/State/PhoneConfig DialPrefix val was: {}
/State/PhoneConfig DialPrefix set to : ,#401
[TiVo [p0] ~]#

all is sweetness...

nic_config_tivo

TiVo TurboNet/AirNet/CacheCard on Tivo Configure - 20041218

Copyright 2002-2004 Silicondust Engineering Ltd. All rights reserved.

Detecting TiVo hard drive...

Detecting TiVo partitions...
Active kernel partition = /dev/hda3.
Inactive kernel partition = /dev/hda6.
Active root partition = /dev/hda4.
Inactive root partition = /dev/hda7.
Var partition = /dev/hda9.

Determining software version...
Philips HDR Series Stand Alone TiVo running 3.0-01-1-000

Remounting root partition...
Root successfully remounted as writable.

Checking installation type...
Configuring TurboNet installation.

Checking script...
Complete.

Current/New Configuration:
timing setting = optimal
mac address = 00:0B:AD:10:10:10
ip address = dhcp
ip subnet mask = dhcp
ip gateway = dhcp
debug level = off

Options
1: Change timing setting
2: Change MAC address
3: Change IP address/gateway
4: Change debug logging option
9: View/extract log file
0: Apply and exit
!: Exit without saving

[0..6]? 0

Updating script...
Complete.

Clear the log file on the tivo [y/n]? y

Clearing log file...
Complete.

Remounting root partition...
Root successfully remounted as readonly.

Configuration update complete, reboot for changes to take effect.

and I reboot.

Then, to check to see if the setting is retained...

[TiVo [p0] ~]# dbget /State/PhoneConfig DialPrefix
{}
[TiVo [p0] ~]#

Doh! Any ideas why this is not retained? I checked by forcing a daily call but get the error message "Failed No dial in number chosen".

Can I manually change the file which contains this parameter? Which is it?:confused:
11-02-2007, 04:46 PM
petestrash

On current Australian images /State/PhoneConfig DialPrefix is set in /etc/rc.d/rc.sysinit around line 890. But I don't know if this is the same for NZ images.

Peter.
11-02-2007, 05:53 PM
meanderingmac

Cheers Peter.

Had a look in there...

# This will make TiVo try a daily call over the network or modem depending on
# the setting in /etc/oztivo.conf.
if [ "$modem" = "1" ] ; then
dbrm /State/PhoneConfig DialPrefix
# This will make the modem behave better in Oz
dbsetx /State/PhoneConfig DialToneCheck 0
#dbsetx /State/PhoneConfig CallWaitingPrefix *44 # #87 for Optus and *11*3# for faxtream duet
#dbsetx /State/PhoneConfig TollFreeNum 99990000
#dbsetx /State/PhoneConfig DialInNum 99990000
else
dbsetx /State/PhoneConfig DialPrefix ',#401'
fi

When modem = 1 in the etc/oztivo.conf the tivo appears to use the modem. How do I set the modem to 0? The oztivo.conf looks like

# OzTiVo menu configuration settings file
# Please do not edit this file
# Put the TiVo disk back in your PC to reconfigure
nic=TurboNet
ip=DHCP
mac=00:0B:AD:10:10:10
hostname=oztivo
modem=1
pppondss=0
phone=086767000
username=myusername
password=mypassword

(with username and password changed to protect the innocent?!?)
I note that it says please don't edit this file. So this is set elsewhere?
Also, I'm a little confused as the phone number, username and password are old (were used at a property I lived at 6 months ago) so it must pick up the current one from tclient.conf?? But not the modem setting?

Shall I be naughty and set the modem to 0 in oztivo.conf, see what happens?
11-02-2007, 06:06 PM
meanderingmac

I was naughty. It did change the dialprefix, and after rebooting I went through the screen menu but it still returns a "Failed. No dial-in number chosen". I'll revert to the previous oztivo.conf methinks.

Not sure where to go from here. Any suggestions?
11-02-2007, 07:59 PM
petestrash

Did the dial prefix remain ,#401 though?

if not, a drity method to fix it would be just to add
dbsetx /State/PhoneConfig DialPrefix ',#401'

As the last line of rc.sysinit.author

Peter.
11-02-2007, 09:46 PM
meanderingmac

Yep, the dial prefix did remain,#401 however the machine still expected a phone number for the modem. I reverted back to the initial oztivo.conf.

I tried your suggestion of of the addition to rc.sysinit.author with the same result - the network dial prefix remained, and show up on the on-screen guided setup, but the error message "Failed. No dial-in number chosen" still comes up.

It must be something more fundamental I've not done. Somewhere else it is getting the parameter to use the modem.
11-02-2007, 11:39 PM
petestrash

If the dial prefix remained originally, then you don't need the extra line in rc.sysinit.

Can you post your tclient.log after trying a daily call. You may need to zip it if it's too big.

Peter.
12-02-2007, 06:46 AM
meanderingmac

Can do (possibly). Which directory will I find the log file in?
12-02-2007, 02:02 PM
petestrash

/var/log

or use TW(P) if it's working for you.

Peter.
13-02-2007, 05:46 AM
meanderingmac

1 Attachment(s)

Here 'tis.
13-02-2007, 09:20 AM
petestrash

can you please paste a zip of your rc.sysinit.author

And change /etc/rc.net/rc.net so it contains

#
#!/bin/sh
#

if /sbin/insmod -f /lib/modules/turbonet.o macaddr=00:0B:AD:10:10:10 timing=3 ; then
export DYNAMIC_NET_DEV=eth0
mkdir -p /var/state/dhcp
/sbin/dhclient -q eth0 2>/dev/null &
fi

Peter.
13-02-2007, 10:26 AM
meanderingmac

1 Attachment(s)

/etc/rc.net/rc.net was already exactly as you had listed it, no change needed.

zip of rc.sysinit.author is attached...
13-02-2007, 01:29 PM
petestrash

Quote:

Originally Posted by meanderingmac

/etc/rc.net/rc.net was already exactly as you had listed it, no change needed.

Ok, that is different to what you showed in post #6. The MAC address was funky.

Now change /etc/tclient so it contains

# This is for the server emulator on minnie via emuproxy2.
127::127.0.0.1:8000:::

Then reboot and try forcing a daily call again.

Peter.
13-02-2007, 08:52 PM
meanderingmac

I did the tclient change (though that would be the ozzie guide data?) and ran through the setup. Nope, no joy. It just wants a phone number. It seems to be ignoring the ,#401 and going for the modem.

Thanks anyway for your help Peter. Much appreciated. I'll think on it a while.

I'm surprised no one else is having a problem with the dial-up for guide data. If mine stopped getting through, others must have the same problem.
I changed the tclient back to dial up (and hashed out the ,#401 in the author file) and ran the guided setup. It dial out fine, and I can hear it trying to connect, comes up onscreen "connecting", then disconnects and displays the "failed, service not answering" message. Why did it work a week ago (for six months), and not now?

Maybe I'll buy a radio. Now thats just crazy talk!
13-02-2007, 09:59 PM
petestrash

Quote:

Originally Posted by meanderingmac

I did the tclient change (though that would be the ozzie guide data?)

Not quite, changing the address in tcilent, made your TiVo use emuproxy2 as you have already setup in rc.sysinit.author. The NZ server is also setup in that file.

Quote:

Originally Posted by meanderingmac

I'm surprised no one else is having a problem with the dial-up for guide data. If mine stopped getting through, others must have the same problem.
I changed the tclient back to dial up (and hashed out the ,#401 in the author file) and ran the guided setup. It dial out fine, and I can hear it trying to connect, comes up onscreen "connecting", then disconnects and displays the "failed, service not answering" message. Why did it work a week ago (for six months), and not now?

If you don't have any recordings you need to keep, why not just start with a clean install of the latest OzTiVo image which supports NZ.

It would make it easier for us to support as a lot of mechanisms have changed and I can't remember all the old methods.

Peter.
14-02-2007, 06:33 AM
meanderingmac

Yes, I think you might be right. Starting clean with the latest image may be the go.

Thanks again for your efforts Peter. I'll let you know how it goes.

Paul