Re: iptable time module following incorrect time

["J. Bakshi" <bakshi12@gmail.com>]

On Mon, 27 Feb 2012 01:52:46 -0700
Bob Proulx <bob@proulx.com> wrote:

> Dom wrote:
> > From man iptables:
> > 
> > "All times are interpreted as UTC by default."
> 
> Aha!  This is a change beween Squeeze and Wheezy.
> The Squeeze version says:
> 
>        --localtz
>               Interpret the times given for --datestart, --datestop,
>               --timestart and --timestop to be local kernel
>               time. (Default)
> 
> But the Wheezy/Sid version does say utc as you indicate.  And the
> --utc and --localtz options have been removed.  So this is a behavior
> change between the Squeeze and Wheezy.
> 
> Bob

Many many thanks to all of you for pointing out the issue.
When I look into squeeze I get " --localtz" 
BUT
in wheezy I get " --kerneltz"

In wheezy it also warns that

`````````````````````
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.

`````````````````

So I am continuing with UTC , once again thanks to all of you.