Speedtouch TG585v7 - updating firmware

[Ted]

I notice today that the Zen logo has gone from the Router pages, so it was probably a cached image that cleared on reboot. Also the Software Variant is AA which confirms 8.2.6.5 as a generic firmware. Software Variant FN points to a Locked firmware.

[dudwell]

Thanks Ted. Why is 8.2.6.5 better than 8.2.2.5 in your opinion? I certainly found I couldn't log in to Telnet when I tried to change back to OpenDNS (since accomplished by other means). Is this a reason for your preference?

I think I'll be sticking to 8.2.2.5 for a while anyway, I'm finding it all a bit stressful!

[Ted]

I wouldn't think there was too much in it with regard to performance, I know some of the earlier firmwares were said to bit a bit flaky, although I can't say there was any noticeable issues with 7.4.4.7 the original firmware. I prefer the generic firmware because there is no branding or isp relavant settings, makes it easier to set up. Also I'm not too keen on Zen's policy on the Administrator password or the inability to login with Telnet. If that's not an issue for you, there's not much reason to change.

I read with interest that there is an r8.2.7.7 firmware, lurking around the internets *somewhere*. Will keep my eyes open, and like someone said earlier "if it ain't broke, you're not trying hard enough".  

[Rik]

You're just a masochist, Ted.

[Ted]

You're just a masochist, Ted.

Pain is my middle name! 

[Rik]

 

Well, if you will have two daughters...

[dudwell]

I've discovered that since updating the firmware to 8.2.2.5, "Event logging" in the router's webpages records every five and a bit minutes an event like "09 days 21:36:58 (since last boot) SNTP Unable to contact server: 212.23.8.6"

What does it mean? Does it matter and, if so, what should I do about it?

Everything seems to work perfectly well, but then so it did before I updated.

[Rik]

It sounds like it can't get a time check from the server it's looking at. See if you can change the servers anywhere.

I use ntp1.npl.co.uk, ntp2.npl.co.uk, ntp1.pipex.net and ntp2.pipex.net.

[dudwell]

Thanks Rik, I wouldn't have had a clue about this without your speedy assistance. I found the way to reconfigure to your recommendations and now the event log shows:-

Nov 12 19:29:16 SNTP Synchronised to server: 139.143.5.30

Nov 12 19:29:17 SNTP Systemtime update: time setting 22:03:03 > new time setting: 19:29:17

So I guess that's a success

[Rik]

They never fail for me. Usually, router's look to the manufacturer's site, which I find is often flaky.