From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sebastian Arcus Subject: Re: Iptables "-m time" option doesn't update when the clock changes Date: Thu, 29 Mar 2012 11:21:55 +0100 Message-ID: <4F7437C3.5060306@open-t.co.uk> References: <4F7426FA.2060902@open-t.co.uk> <4F742BAD.20002@open-t.co.uk> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: netfilter-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Cc: netfilter@vger.kernel.org Hi Jan On 29/03/12 11:00, Jan Engelhardt wrote: > > > The caveat with the kernel timezone is that Linux distributions may > ignore to set the kernel timezone, and instead only set the system > time. Even if a particular distribution does set the timezone at boot, > it is usually does not keep the kernel timezone offset - which is what > changes on DST - up to date. ntpd will not touch the kernel timezone, > so running it will not resolve the issue. As such, one may encounter a > timezone that is always +0000, or one that is wrong half of the time of > the year. As such, using --kerneltz is highly discouraged. > Thanks for taking the time to give a detailed reply. Just to make sure I understand correctly - would this mean that there is no reliable way to run time based iptables rules and have them keep up with DST changes correctly and automatically - without restarting the machine when the DST kicks in or out? Sebastian