Superhub : superhub2 - did customer service rip me off?

[Sephiroth]

Originally Posted by Kushan

Are you sure about that? I thought ToD was required for correct negotiation of the DOCSIS config?

TOD synch between modem and CMTS is necessary AFAIK - read it in the DOCSIS specs.

[Kushan]

Originally Posted by qasdfdsaq

It may be, I don't know.

But it's not required for DNS, DHCP or SSL (or rather the Superhub doesn't do SSL).

Not sure if we're debating whether time is required for those services in general or for the superhub.

I do know that the superhub must establish TOD for the network authorisation to complete properly, this is something at the DOCSIS/Network level rather than at the service level. I don't know how much leeway you have with this as I don't know much about the DOCSIS authentication, just that TOD is necessary for it. I imagine it must use something similar to SSL/TLS in that there are signed certificates at work, which will be timestamped and will break if the date is off by a significant amount.

That all being said, this is probably why a TOD failure is a critical event. It might not knock the hub offline or anything right away, but it could cause major issues later if the time goes too far out of sync.

[mmm]

Thanks - re reason TOD is important, have had problems in past with connecting laptops to a domain network which wasn't properly time synched. Time is important to Kerberos protocol.

But doubt superhub2 any different from 1 in this respect.

[Sephiroth]

No difference - both models correctly follow the DOCSIS requirements otherwise they wouldn't be able to register when powered on. The Synch is part of the initialisation.

[Kushan]

Originally Posted by mmm

Thanks - re reason TOD is important, have had problems in past with connecting laptops to a domain network which wasn't properly time synched. Time is important to Kerberos protocol.

But doubt superhub2 any different from 1 in this respect.

Indeed, this is what I was saying earlier - time is important for a lot of things.