Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Ming-Ching Tiew" <mingching.tiew@redtone.com>
To: netfilter@lists.netfilter.org
Subject: Re: Simple question about ipset
Date: Mon, 25 Sep 2006 04:34:27 +0800	[thread overview]
Message-ID: <000701c6e018$d791c790$02bca8c0@freelance> (raw)
In-Reply-To: Pine.LNX.4.58.0609201549540.31176@blackhole.kfki.hu

From: "Jozsef Kadlecsik" <kadlec@blackhole.kfki.hu>
> 
> > I hope my understanding is correct. Perhaps the docs should explain it more
> > clearly.
> 
> Yes, the docs are terse. Patches against the docs are (also) always
> welcomed.
> 

If my understanding is correct ( which I am still not very sure at this moment ),
perhaps may I suggest the syntax be changed such that only one flag is 
allowed ( and necessary ) and the value can be 'dst', 'src', or 'both' ?

  eg,
             iptables -A FORWARD -m set --set servers dst -j ACCEPT
             iptables -A FORWARD -m set --set servers src -j ACCEPT
             iptables -A FORWARD -m set --set servers both -j ACCEPT

                or if the keyword 'both' is left out, it is then implied :-
 
           iptables -A FORWARD -m set --set servers -j ACCEPT

The nature of relationship is that it will be hard to form a meaningful
relationship where the flags could be heterogeneous, so why don't
just implement a simplied syntax ?

Cheers

 




  reply	other threads:[~2006-09-24 20:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-20 13:38 Simple question about ipset Ming-Ching Tiew
2006-09-20 13:57 ` Jozsef Kadlecsik
2006-09-24 20:34   ` Ming-Ching Tiew [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-09-20  6:54 Ming-Ching Tiew

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='000701c6e018$d791c790$02bca8c0@freelance' \
    --to=mingching.tiew@redtone.com \
    --cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox