All of lore.kernel.org
 help / color / mirror / Atom feed
From: varun <varun@rocsys.com>
To: Sven-Haegar Koch <haegar@sdinet.de>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: iptables doubt
Date: Fri, 14 Apr 2006 09:03:46 +0530	[thread overview]
Message-ID: <443F181A.6070506@rocsys.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0604131801560.4261@mercury.sdinet.de>

Yeah it is true but this can done only after safe but not dynamically? 
Is there a way to do dynamically?

Varun







Sven-Haegar Koch wrote:

> On Thu, 13 Apr 2006, varun wrote:
>
>>                         The features i want to implement like that 
>> priority for policy is that imagine a scenario where user added some 
>> policies and then for some reason wants one policy to be checked 
>> before checking others then he would have to add the policy again and 
>> delete the old policy isint it?
>
>
> Every iptables rule change is loading the whole ruleset into 
> userspace, modifying it, and copying the result back into kernelspace.
>
> So you should be able to fetch the rules (f.e. with iptables-save), 
> modify them as you like, and push them back (iptables-restore).
>
> c'ya
> sven
>

  reply	other threads:[~2006-04-14  3:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-12 13:54 iptables doubt varun
     [not found] ` <443E21C1.9090508@info.ucl.ac.be>
     [not found]   ` <443E341F.1080206@rocsys.com>
2006-04-13 12:24     ` Sebastien Tandel
2006-04-13 13:01       ` varun
2006-04-13 13:16         ` Sebastien Tandel
2006-04-13 13:53           ` varun
2006-04-13 14:16             ` Sebastien Tandel
2006-04-14  3:42               ` varun
2006-04-13 16:04             ` Sven-Haegar Koch
2006-04-14  3:33               ` varun [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-04-13 10:14 Sebastien Tandel
2006-04-13 16:57 Sebastien Tandel
2006-04-26  7:09 varun

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=443F181A.6070506@rocsys.com \
    --to=varun@rocsys.com \
    --cc=haegar@sdinet.de \
    --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.