General Questions

I am using public NTP servers in Croatia to sinc clock. In version 1.233 my NTP server is zg1.ntp.carnet.hr and region Europe/Zagreb and time is accurate but in 1.3b11 I must set region ETC/GMT-2 to get accurate time. Seting it to Europe/Zagreb give me 2 hours less than it is.

I am usig that NTP server to sinc all my servers (.NIX and Windows) and some windows clients and there is no problems with them.

Is it a bug or

Sasa

I have this problem as well, the log entries are two hours behind.
This is in both 1.3b13 and 1.3b9 (that my Alix came with preinstalled).

I have Europe/Oslo in time zone and I tried setting NTP server to no.pool.ntp.org, no change.

I have noticed this also, but of course the numbers are different for me, being in the USA.

I think I had this figured as having the hardware clock set to whatever the correct local time is. Then when setting the correct time zone in m0n0wall, the reported times in the logs are wrong.

But with the hardware time set to UTC time, and the correct time zone set in m0n0wall, the times reported in the logs are correct.

So my question/suggestion is what time is set in your m0n0wall's PC hardware (BIOS) clock? If it's not UTC time, try changing it to UTC time.

So my question/suggestion is what time is set in your m0n0wall's PC hardware (BIOS) clock? If it's not UTC time, try changing it to UTC time.

Ah ha, I didn't think of that, thanks

My m0n0wall is an Alix though, is it possible to set the clock on it?
I got it from the UK and they are two hours behind us here in Norway IIRC so maybe they set the clock on the unit before they shipped it?

I don't beleive the Alix board comes with a RTC battery so every time you power it off it loses its time.

CS...

I don't beleive the Alix board comes with a RTC battery so every time you power it off it loses its time.

That's true but isn't that what the NTP sync is for?

Using Europe/Oslo the timestamps on my system is two hours behind.

I guess I'm either somewhat retarded and/or this isn't a common problem since this post was the only one I found about it here

I've found the problem: in m0n0wall's /usr/share/zoneinfo.tgz, there were various hard links (e.g. between Europe/Oslo and Arctic/Longyearbyen, or between Europe/Belgrade and various other cities, including Europe/Zagreb). tar has problems extracting just one hard linked file, leading to a 0 byte /etc/localtime, which means that the system will fall back to UTC. The reason why most other zones worked is that not all zones are hard linked (only those that share exactly the same timezone data).

This problem was probably introduced in 1.3b6; it will be fixed in the next release. Thanks for letting us know!

This problem was probably introduced in 1.3b6; it will be fixed in the next release. Thanks for letting us know!

Good news!
I tried a few different time zones but the results were not consistent as you can imagine, making my issue even more strange

Thanks for m0n0wall, Manuel!