Printable View
It only used to block non-nz ftp addresses, so it should work.Quote:
Originally Posted by petestrash
You could try using Ethereal http://www.ethereal.com/
on you home machine and then try to do a ntpdate -b HOMEIP
You'll then see which protocol it uses and if it does get out of the tivo.
I have managed to get my Tivo to load the guide data now after following the advice from this thread.
The nztivo image I have does not include fixtivotime or rtimetz so I had to download these. I also updated the ntpdate file (don't know whether this was necessary or not) as when I ran ntpdate all I got was the cursor i.e.
[TiVo [p1] ~]# ntpdate -b 129.6.15.29
[TiVo [p1] ~]#
The warptime fix and fixtivotime command seemed to do the trick for me. However I noticed that it wasn't picking up on my 02113 Pacific code so I copied over the Auckland and postcodezones files and ran again but it made no difference.
I also tried to put a manual entry into the postcodezones file for 02113 Pacific/Auckland. Fixtivotime now found 02113 but my clock was now 12hrs out (not applying the GMT+12) so I undid it all and set my timezone to GMT+12.
The current ntpdate uses port 37.Quote:
Originally Posted by Wibble
Peter.
if you want to see what tz you have set tryQuote:
Originally Posted by Hoon
Peter.Code:[TiVo [p0] ~]# /bin/ntpdate -v
Our postcode is 06000. Found matching timezone Australia/Perth
Offset 28800 for timezone WST, daylight saving is 0
Failed to connect to any of the time servers
Ok, I set up Orac to also have port 37 open (tcp and udp) . And I've seen someQuote:
Originally Posted by petestrash
traffic on tcp 37.
So if people want to try /bin/ntpdate -b 210.48.107.133 again.
If that doesn't work, try
/bin/ntpdate -bu 210.48.107.133
the -u nmake ntpdate use an unpriviledged source port, which apparently has helped some people.
Hi All
Without sounding like a complete moron I am kind of lost as to what I should actually be doing with my time issue. I have been reading through the various posts but am getting confused and now I am back at "failed while preparing data" again.
In a nutshell......
I have 2 TiVos running the 1.4 image (1 is at the in-laws). Neither network/internet connection/router or ISP have changed since we have had the 1.4 image. Everything used to be working fine and then a few months back I got the "warped clock" issue. The first few times this occured though was able to be fixed by the timestamp & force index commands.
A couple of weeks ago though when it happened I couldn't fix it untill I cleared all guide data from the TiVo and downloaded it from scratch again. This fixed the gudie data but my season passes etc haven't worked for quite some (presumably because when I look at the logs the warped clock issue never came right). After downloading data again for the last week though it has stopped again.
I don't get the expected reply from any of the ntpdate commands (It just jumps back to the standard prompt as mentioned in earlier posts).
This is getting very frustrating and probably mainly due to my lack of knowledge editing the image etc it would appear.
My in-laws TiVo has only suddenly gone down the same path as mine this week after working fine for months.
What should I be doing (in nice basic steps :o please).
Appreciated
Muzza.
I'd like to help, but I'm currently running 1.3, so I can't replicate the problem.Quote:
Originally Posted by Muzza
You could try the following and post the output
ntpdate -b -ddd 210.48.107.133
if that doesn't work
ntpdate -bu -ddd 210.48.107.133
This should turn all the debugging on and we can work out what it's doing.
If somebody with a working 1.4 could do the same that would be great.
I can confirm orac works for me now. Could someone with troubles (using extra) try and see if it works for them.Quote:
Originally Posted by Wibble
Peter.
Those commands won't work with this version of ntpdate, the only syntax is ntpdate [-B] [-b] [d] [-q] [-v] server [server ...]Quote:
Originally Posted by Wibble
But Muzza should try /bin/ntpdate -b 210.48.107.133 and see if it works any better than the other servers.
Peter.
Here's my results......
[TiVo [p0] ~]# ntpdate -b -ddd 210.48.107.133
[TiVo [p0] ~]#
[TiVo [p0] ~]# ntpdate -bu -ddd 210.48.107.133
ntpdate: invalid option -- u
[TiVo [p0] ~]#
and.....
[TiVo [p0] ~]# /bin/ntpdate -b 210.48.107.133
[TiVo [p0] ~]#
[TiVo [p0] ~]#
Not very helpful is it. :(