SixXS::Sunset 2017-06-06

AICCU and non-fatal login errors
[us] Shadow Hawkins on Sunday, 03 March 2013 05:02:49
Any chance that an AICCU developer could pull in this patch? I am running AICCU on a device with no hardware clock, so time is fetched from NTP, but it's a pain to make sure NTP has fixed the clock before starting AICCU. It'd be nice if AICCU waited a bit and tried to log in again if the clock was too wrong.
AICCU and non-fatal login errors
[ch] Jeroen Massar SixXS Staff on Monday, 04 March 2013 07:55:15
Any chance that an AICCU developer could pull in this patch?
No, as clearly explained in the ticket at OpenWRT and that caused that patch to be reverted. Note that the patch is missing from current SVN. We do not want even more clients hammering on our TIC servers to effectively DoS them. Rate limiting is now in place because of that though.
I am running AICCU on a device with no hardware clock, so time is fetched from NTP, but it's a pain to make sure NTP has fixed the clock before starting AICCU.
Fixing your platform is the only way to go. It is actually very simple with something short like:
ntpclient 0.openwrt.pool.ntp.org
See also: http://wiki.openwrt.org/doc/uci/ntpclient or
rdate 0.openwrt.pool.ntp.org
If you do not have a proper time on your system a lot of things will be wrong, eg DHCP lease times will break too. As such, fix the real issue, do not try to work around it in other ways and hurt other people's services by hammering on their servers.

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker