Kitz Forum

Broadband Related => Broadband Hardware => Topic started by: Windows10User on January 18, 2020, 02:51:49 PM

Title: HG612 not Y2K20 compliant?
Post by: Windows10User on January 18, 2020, 02:51:49 PM: Hi,

After 2020 rolled around, I think the custom firmware: B030SP08 isn't Y2K20 compliant. I found this out the other day after I checked the logs on the modem. It went from 2019-12-24 to 2000-01-01. As seen in the attached screenshot.

I was wondering if anyone else has experienced this and is there a way to force the modem to get the correct date.
Title: Re: HG612 not Y2K20 compliant?
Post by: jelv on January 18, 2020, 04:07:29 PM: I hadn't spotted this, but on checking mine is also saying 2000.

Does it actually matter?
Title: Re: HG612 not Y2K20 compliant?
Post by: Windows10User on January 18, 2020, 04:32:17 PM: Quote from: jelv on January 18, 2020, 04:07:29 PM
I hadn't spotted this, but on checking mine is also saying 2000.

Does it actually matter?
I'm not sure if it matters or not, maybe it's just a minor inconvenience whenever you check the logs or maybe it will snowball into a bigger issue, who knows? :shrug2:
Title: Re: HG612 not Y2K20 compliant?
Post by: displaced on January 18, 2020, 04:41:18 PM: Mine looks fine. No logs over 24th/25th Dec, but shows it rolling over to the new year without a problem.

My HG612's configured to pull the time via ntp from my pfSense router, so I'll only see the default '2000-01-01' timestamp once or twice early on in the boot process.
Title: Re: HG612 not Y2K20 compliant?
Post by: Alex Atkin UK on January 18, 2020, 05:47:15 PM: Mine doesn't seem to be picking up NTP either, I had noticed but couldn't remember if it ever had. To be fair, it shouldn't really matter if used merely as bridge modem.
Title: Re: HG612 not Y2K20 compliant?
Post by: displaced on January 18, 2020, 05:59:35 PM: Quote from: Alex Atkin UK on January 18, 2020, 05:47:15 PM
Mine doesn't seem to be picking up NTP either, I had noticed but couldn't remember if it ever had. To be fair, it shouldn't really matter if used merely as bridge modem.

Agreed - I doubt it matters at all. I only set it up for NTP because I saw it had an option for one, and I run an NTP server on my firewall.
Title: Re: HG612 not Y2K20 compliant?
Post by: Alex Atkin UK on January 18, 2020, 06:20:47 PM: Quote from: displaced on January 18, 2020, 05:59:35 PM
Agreed - I doubt it matters at all. I only set it up for NTP because I saw it had an option for one, and I run an NTP server on my firewall.

Same here, not sure why its not picking it up.
Title: Re: HG612 not Y2K20 compliant?
Post by: dee.jay on January 20, 2020, 04:13:25 PM: Yeah mines 2000 too. But, I had logging turned off, shows how interested I am in seeing the logs :D
Title: Re: HG612 not Y2K20 compliant?
Post by: Alex Atkin UK on January 20, 2020, 05:57:50 PM: Ah its just the logs.

Quote
# date
Mon Jan 20 17:57:03 UTC 2020
Title: Re: HG612 not Y2K20 compliant?
Post by: Windows10User on January 25, 2020, 11:14:53 PM: I've got it to roll over now in the logs! :)

So what I've done is to create a local time server on the LAN (in this case it's my Windows Server 2016 system) and tell it to sync from it by pointing a local IP.

So what I'm guessing is happening is that the modem for whatever reason doesn't want to set time via an external time server so changing it to an internal one would allow it to sync.
(Thanks displaced for giving me the idea to try this)
Title: Re: HG612 not Y2K20 compliant?
Post by: burakkucat on January 25, 2020, 11:26:50 PM: If the HG612 is being used as a modem bridge, then there is no way that it can synchronise with a remote time-server via the WAN interface.

So, as has been shown, set up a local time server and have the HG612 synchronise with it via the LAN interface.