Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Feizhou <feizhou@linuxmail.org>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: netfilter@lists.netfilter.org
Subject: Re: Large number of repeated rules with only differing -s ipaddrs/cidrs
Date: Tue, 20 Apr 2004 22:36:39 +0800	[thread overview]
Message-ID: <40853577.5080803@linuxmail.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0404201608280.14290-100000@blackhole.kfki.hu>

Jozsef Kadlecsik wrote:
> On Mon, 19 Apr 2004, Feizhou wrote:
> 
> 
>>when will ipset be available in 2.6?
> 
> 
> It needs more, exhaustive testing. ippool was tested more widely than
> ipset.

Oh...those that mean both can actually be compiled in 2.6?
> 
> 
>>I presume ippool is going to become obsolete?
> 
> 
> Originally ipset was planned to be released as a new version of ippool.
> Unfortunately backward compatibility could not be preserved, so a new name
> had to be found. It extends ippool, yes, but that does not mean ippool is
> obsolete.
> 

Lovely. Does ippool/ipset take ips only or will they also take cidrs?

BTW...mail.so-net.com.hk is an ISP smarthost...could you block 
so-net.com.hk not coming from 203.99.142.22 instead of a domain rule 
block on rdns and sender addy?

And maybe all emails from 203.99.142.22 if sender addy not in 
so-net.com.hk...


  reply	other threads:[~2004-04-20 14:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-19 10:02 Large number of repeated rules with only differing -s ipaddrs/cidrs Feizhou
2004-04-19 11:42 ` Frank Gruellich
2004-04-19 13:44   ` Feizhou
2004-04-19 12:03 ` Jozsef Kadlecsik
2004-04-19 14:47   ` Feizhou
2004-04-20 14:16     ` Jozsef Kadlecsik
2004-04-20 14:36       ` Feizhou [this message]
2004-04-20 14:59         ` Jozsef Kadlecsik
2004-04-21  0:02           ` Feizhou
2004-04-19 12:12 ` Torsten Luettgert

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=40853577.5080803@linuxmail.org \
    --to=feizhou@linuxmail.org \
    --cc=kadlec@blackhole.kfki.hu \
    --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