Tod esablished
 

hello
ive been a customer for about 2 weeks now on the 60mb plan and so far its been great always getting 60+

but i noticed in the logs i always get TOD not esstablished and tod established straight after.. one of them is unable to aquire a time but the other seems tocome after.. any idea why this is?
ill take a picture next time it happens

https://www.cableforum.co.uk/images/...2012/08/33.png

---------- Post added at 23:31 ---------- Previous post was at 23:30 ----------

seems to happen everyday there are MAC addresses i belive .. it says MAC which i have blanked out.. could it be other wifi laptops just disconnecting and reconeting with issues?
im on ethernet by the way

Re: Tod esablished
 

I think what you are seeing is the "invalid field in DHCP response" message is being logged by the Superhub before the device has established date/Time. That's logical as in order to query a time server it needs an IP address. Since this is a message about the DHCP response the fact it hasn't establish other comms a that point is what you would expect.

Once it has an IP address the next thing it appears to do is query the time servers to establish Time of Day and you are seeing that logged as the next message. Quite why it reports that with an error code at level Critical though is surprising - I'd have thoguth it would be logged as Informational.

Re: Tod esablished
 

i am having this issue after the R36 firmware
I think is something to do with the SH reporting wrong dates in the logs
Here one similar post from USA
http://www.dslreports.com/forum/remark,9611205

Also got this quote

Re: Tod esablished
 

Ok so there is nothing to worry about i presume. was worrying a bit when i see it pop up and see critical level.. thanks

Re: Tod esablished
 

Nothing to worry about. The SH firmware is at fault. Like mine, your date is wrong.

VM do have a TOD server and they do synchronise modem with CMTS. It's reported wrongly.