On Mon, Mar 18, 2019 at 03:17:45PM +0530, Karuna Grewal wrote:
> Signed-off-by: Karuna Grewal <karunagrewal98@xxxxxxxxx>
> ---
> tests/py/any/meta.t | 3 +++
> tests/py/any/meta.t.json | 12 ++++++++++++
> tests/py/any/meta.t.payload | 5 +++++
> 3 files changed, 20 insertions(+)
>
> diff --git a/tests/py/any/meta.t b/tests/py/any/meta.t
> index d69b8b4e..3d23dc75 100644
> --- a/tests/py/any/meta.t
> +++ b/tests/py/any/meta.t
> @@ -205,3 +205,6 @@ meta iif . meta oif vmap { "lo" . "lo" : drop };ok;iif . oif vmap { "lo" . "lo"
>
> meta random eq 1;ok;meta random 1
> meta random gt 1000000;ok;meta random > 1000000
> +
> +meta time 100;ok;meta timestamp 1m40s
I think the important thing here is to support for dates.
I remember Florian mentioned we need a new datatype for this, to
express dates.
Still we need support for time range, ie. hh:mm[:ss]-hh:mm[:ss],
monthdays and weekdays.
We should _not_ support --kerneltz, that broken. We should just
provide an alternative that works with UTC. Hopefully daylight saving
will be removed everywhere soon (EU is planning for this), so we won't
need --kerneltz.
Talking by looking at what I see in man iptables-extensions when I
look for the `time' match.
Will you work on this?
