All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro David Galera Ruiz <alejandro.galera@gmail.com>
To: netfilter-devel@lists.netfilter.org
Subject: [PATCH] Time match in mangle/POSTROUTING?
Date: Tue, 19 Dec 2006 16:08:30 +0100	[thread overview]
Message-ID: <1166540910.13355.0.camel@palocortado> (raw)

[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]

I'm trying to use netfilter with classify and temporal filters. Due to I
realised that POSTROUTING wasn't supported in mangle table, I decided to
patch ipt_time module following Brad Fisher's PATCH.

I've tried to update this patch for kernel 2.6.17 and the lastest
version of patch-o-matic (20061213).
It's my first contribution to this project, I hope to be a little bit
useful for your great project.

Using: 
Patch-o-matic 20061213

Modifications:

* Time modification (the same from Brad Fisher
http://lists.netfilter.org/pipermail/netfilter-devel/2003-December/013367.html) 

> >Brad Fisher wrote:
> >
> >* I don't see any reason why the above approach 
> >  wouldn't work in any chain, so I
> >  removed the check from checkentry.

* I think it could be more deffensive and flexible in the future if we
add NF_IP_POST_ROUTING checking to checkentry function instead of quit
any verification.
* System message according to let POST_ROUTING.
* System warning message specifying invalid argument is due to time
higher than 24h (it also has been taken from Brad Fisher's patch)

All your suggestions, indications or tests will be wellcome
Thanks in advance

[-- Attachment #2:  ipt_time-pom-20061213.patch --]
[-- Type: text/x-patch, Size: 1811 bytes --]

--- ipt_time.c.old      2006-12-14 19:21:10.000000000 +0100
+++ ipt_time.c  2006-12-14 19:12:20.000000000 +0100
@@ -79,8 +79,15 @@
 
        /* ... check the time now */
        packet_time = (currenttime.tm_hour * 60) + currenttime.tm_min;
-       if ((packet_time < info->time_start) || (packet_time >
info->time_stop))
-               return 0;
+       if (info->time_start <= info->time_stop) {
+               /* normal order: start <= stop */
+               if ((packet_time < info->time_start) || (packet_time >
info->time_stop))
+                        return 0;
+        } else {
+               /* reversed order: stop < start */
+                if ((packet_time < info->time_start) && (packet_time >
info->time_stop))
+                        return 0;
+        }
 
        /* here we match ! */
        return 1;
@@ -104,9 +111,9 @@
 
        /* First, check that we are in the correct hooks */
        if (hook_mask
-            & ~((1 << NF_IP_PRE_ROUTING) | (1 << NF_IP_LOCAL_IN) | (1
<< NF_IP_FORWARD) | (1 << NF_IP_LOCAL_OUT)))
+            & ~((1 << NF_IP_PRE_ROUTING) | (1 << NF_IP_LOCAL_IN) | (1
<< NF_IP_FORWARD) | (1 << NF_IP_LOCAL_OUT) | (1 << NF_IP_POST_ROUTING)))
        {
-               printk("ipt_time: error, only valid for PRE_ROUTING,
LOCAL_IN, FORWARD and OUTPUT)\n");
+               printk("ipt_time: error, only valid for PRE_ROUTING,
POST_ROUTING, LOCAL_IN, FORWARD and OUTPUT)\n");
                return 0;
        }
 
@@ -120,7 +127,7 @@
        if ((info->time_start > 1439) ||        /* 23*60+59 = 1439*/
            (info->time_stop  > 1439))
        {
-               printk(KERN_WARNING "ipt_time: invalid argument\n");
+               printk(KERN_WARNING "ipt_time: invalid argument: start
or stop time greater than 24h\n");
                return 0;
        }

             reply	other threads:[~2006-12-19 15:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-19 15:08 Alejandro David Galera Ruiz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-12-19 11:54 [PATCH] Time match in mangle/POSTROUTING? Alejandro David Galera Ruiz
2006-12-18 17:19 Alejandro David Galera Ruiz
2006-12-19 12:10 ` Patrick McHardy
2006-12-19 13:24   ` Alejandro David Galera Ruiz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1166540910.13355.0.camel@palocortado \
    --to=alejandro.galera@gmail.com \
    --cc=netfilter-devel@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.