Posted: Sun Dec 02, 2012 4:52 Post subject: E3000 Time problems
I have a E3000 flashed with the following DDWRT version:
DD-WRT v24-sp2 (04/07/12) big
(SVN revision 18946M NEWD-2 K2.6 Eko)
For some reason NTP fails to work and everytime the router is rebooted it loses the time settings causing issues with my openvpn since the cert goes bad.
Is there anyway to fix this issue so I don't have to log in and manually set the time every time it reboots?
Joined: 24 Feb 2009 Posts: 2026 Location: Sol System > Earth > USA > Arkansas
Posted: Sun Dec 02, 2012 16:49 Post subject:
What are your options set for "Time Settings" on your router? (The option is located at the bottom of the 'Setup' tab and 'Basic Setup' sub-tab.)
If you have something in the "Server IP/Name" option, try clearing it to see if that works then. _________________ E3000 22200M KongVPN K26
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2 [not used]
WRT54G v2 16214 BS K24 [access point]
Try Dropbox for syncing files - get 2.5gb online for free by signing up.
Read! Peacock thread
*PLEASE* upgrade PAST v24SP1 or no support.
It only has the NTP option which is turned off, even with it turn on however the time resets to 00:00:00 every time the router is rebooted.
I tested the settings with another router I have running DDWRT and neither the NTP works nor does it save the time. I wonder if it is something that is broke with DDWRT even though they are two different routers they are both linksys and broadcom routers.
Routers do not have realtime clocks ticking when the router is powered off.
The ntp client should have got you the correct time within 20-30 seconds after power on. _________________ Kernel panic: Aiee, killing interrupt handler!
Leave NTP blank. It should work then. However, I suspect your VPN problems are build related. See the forum announcements. _________________ SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor.
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
And choosing UTC time zone with no daylight savings solves most problems with having a wrong time on the router (i.e. after ntp sync). On a normal Linux system, system time is set to UTC with no dayligh savings, and uclibc does the translation to local time every time an application wants to know it. That's why Hackintosh users who also have Windows on their computer have to have a patch for time settings, otherwise the hardware time is set wrongly. _________________ 2 times APU2 Opnsense 21.1 with Sensei
2 times RT-AC56U running DD-WRT 45493 (one as Gateway, the other as AP, both bridged with LAN cable)
3 times Asus RT-N16 shelved
E4200 V1 running freshtomato 2020.8 (bridged with LAN cable)
3 times Linksys WRT610N V2 converted to E3000 and 1 original E3000 running freshtomato 2020.8 (bridged with LAN cable)
Use some NTP servers IPs from the part of the world you are living in. Some servers refuse connections outside their continent or country.
The idea is that you paste it in the cron section, activate cron and it should work after you reboot the router.
Also, if everything else fails, set the router to UTC time zone with no daylight savings. This should pass the correct system time to other programs. _________________ 2 times APU2 Opnsense 21.1 with Sensei
2 times RT-AC56U running DD-WRT 45493 (one as Gateway, the other as AP, both bridged with LAN cable)
3 times Asus RT-N16 shelved
E4200 V1 running freshtomato 2020.8 (bridged with LAN cable)
3 times Linksys WRT610N V2 converted to E3000 and 1 original E3000 running freshtomato 2020.8 (bridged with LAN cable)
