Page 1 of 1
Incorrect Date
Posted: Sun May 25, 2014 1:15 pm
by Mrmandala
Hi,
Could anyone suggest why the date on a new Gargoyle installation is incorrect please. it's showing as 04.01.2001 under Status
As it stands bandwidth/quota management is not working and I suspect the date is the cause, everything else seems in order and connectivity is there, just not the quota management I was hoping for.
This is on a TP-Link TL-WDR3600 V1
Any suggestion appreciated,
Cheers.
Re: Incorrect Date
Posted: Sun May 25, 2014 11:37 pm
by DoesItMatter
Backup your current config
Reset to defaults and see if you can get the time/date to sync properly
If you can, then reload your old config
If the time/date goes wacky again - you have a corrupted config
and you have to again - reset to defaults, then reconfigure fresh
Re: Incorrect Date
Posted: Mon May 26, 2014 9:13 am
by Mrmandala
OK, thanks Doesitmatter, I'll give that a go
Re: Incorrect Date
Posted: Mon May 26, 2014 9:31 am
by tapper
Hi pleas look under system and then time and see if you have it set the write NTP Servers.
Re: Incorrect Date
Posted: Mon May 26, 2014 10:08 am
by Mrmandala
Thanks Tapper, this is what I have set. I have tried Doesitmatters suggestion, no change unfortunately.

- Time.png (38.62 KiB) Viewed 8143 times
Re: Incorrect Date
Posted: Mon Aug 04, 2014 6:35 pm
by larzeb
I have the same situation with a TLWDR3600 and Gargoyle 1.6.1. In fact, after hitting RESET it appears nothing changes.
Re: Incorrect Date
Posted: Tue Aug 19, 2014 10:01 am
by n0pin
Maybe NTP protocol port is blocked? Does time synchronization work on computers?
Re: Incorrect Date
Posted: Sat Oct 04, 2014 1:06 pm
by Mrmandala
Thanks for all suggestions, finally got this working by disabling the Internet/WAN setting and changing the LAN IPs, time was then immediately correct, bandwidth monitoring is now working and all should be good
Attached current config if of help to anyone in the future.
Setup is 4G router > TLWDR3600 and WIFI and LAN settings run from that. DHCP is from 4G router, haven't managed to change that yet, not too fussed though.