All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Eastep <teastep@shorewall.net>
To: Netfilter users list <netfilter@lists.netfilter.org>
Subject: Re: about iprange
Date: Tue, 25 Jan 2005 09:08:40 -0800	[thread overview]
Message-ID: <41F67D18.4060100@shorewall.net> (raw)
In-Reply-To: <1106671920.5306.50.camel@jasiiitosh.nexusmgmt.com>

John A. Sullivan III wrote:

> 
> We found we needed to accommodate solutions both ways within ISCS, i.e.,
> if a gateway supports iprange, we write iptables rules with ranges.  If
> not, we use the logic found in SubnetCreator
> (http://subnetcreator.sourceforge.net) to break the range into subnets
> and then create rules for the resultant subnets.

FWIW, Shorewall takes the same approach although Shorewall has it's own
code for converting a range into a list of subnets.

-Tom
-- 
Tom Eastep    \ Nothing is foolproof to a sufficiently talented fool
Shoreline,     \ http://shorewall.net
Washington USA  \ teastep@shorewall.net
PGP Public Key   \ https://lists.shorewall.net/teastep.pgp.key


  reply	other threads:[~2005-01-25 17:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-20 20:07 using with big ban lists (peerguardian and so) jdf [zionarea.org]
2005-01-20 20:29 ` Jason Opperisano
2005-01-21 19:30   ` jdf [zionarea.org]
2005-01-25 13:45     ` about iprange jdf [zionarea.org]
2005-01-25 16:51       ` John A. Sullivan III
2005-01-25 17:08         ` Tom Eastep [this message]
2005-01-25 17:51         ` jdf [zionarea.org]
2005-01-20 20:29 ` using with big ban lists (peerguardian and so) Samuel Jean

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=41F67D18.4060100@shorewall.net \
    --to=teastep@shorewall.net \
    --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 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.