DrTeeth
Senior Member
Using the latest Merlin firmware, 3.0.0.4.270.26b. The comments below are NOT meant to be critical of the Merlin firmware at all, but the Asus code on which it is based.
It is a real pain to set the correct time. When I eventually get the time to be correct (having to manually fiddle with the DST settings*) the time is off in the logs by about an hour. It is not a major issue for me but I cannot see how the correct system time can result in a wrong log timestamp. I need the time to be correct so I can use the parental controls.
Thanks to Merlin's excellent support, I can set the time with his supplied command. It would be nice to be able to set it manually and take NTP out of the equation, at least for testing.
*These are less than intuitive as I cannot find what day '0' is. Could not a calendar system with regular dates be used?
The latest Asus beta (3.0.0.4.354) lists "Wireless time control related bugs" as one of the fixes, so I these time issues will be easier to manage.
Regards
DrT
It is a real pain to set the correct time. When I eventually get the time to be correct (having to manually fiddle with the DST settings*) the time is off in the logs by about an hour. It is not a major issue for me but I cannot see how the correct system time can result in a wrong log timestamp. I need the time to be correct so I can use the parental controls.
Thanks to Merlin's excellent support, I can set the time with his supplied command. It would be nice to be able to set it manually and take NTP out of the equation, at least for testing.
*These are less than intuitive as I cannot find what day '0' is. Could not a calendar system with regular dates be used?
The latest Asus beta (3.0.0.4.354) lists "Wireless time control related bugs" as one of the fixes, so I these time issues will be easier to manage.
Regards
DrT