From: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
To: "Knight, Steve" <Steve.Knight@bskyb.com>
Cc: "'netfilter@lists.netfilter.org'" <netfilter@lists.netfilter.org>
Subject: Re: quick syntax query
Date: Mon, 07 Jun 2004 07:54:21 -0400 [thread overview]
Message-ID: <1086609260.21179.4.camel@localhost> (raw)
In-Reply-To: <FDB52A0429DFD31196FB0008C7D972D51259E6CF@OST_EXCH_USR5>
On Mon, 2004-06-07 at 06:53, Knight, Steve wrote:
> Hi there
>
> Can one use syntax other than CIDR notation when defining things like
> networks?
>
> i.e. it's common to see
>
> LAN_RANGE="192.168.0.0/24"
>
> in rule bases, but I would like to use
>
> DODGY_RANGE="192.168.0.1-5"
> GOOD_RANGE="192.168.0.6-30"
> BAD_BAD_RANGE="192.168.31-40"
>
>
> a la `nmap` syntax.
>
> Is this something netfilter can handle?
>
<snip>
Yes, besides using CIDR and Dotted Decimal notation, one can apply the
IPRange patch-o-matic patch and use a rule such as
iptables -A FORWARD -m iprange --src-range 192.168.1.10-192.168.1.20 -j
ACCEPT
We use it all the time in the ISCS project.
If you do not want to patch, you can use SubnetCreator
(http:subnetcreator.sourceforge.net) to turn a range into a list of
subnets and then make rules for each of the subnets. If you are using
Qt, it also provides a series of routines to do this programatically.
--
John A. Sullivan III
Chief Technology Officer
Nexus Management
+1 207-985-7880
john.sullivan@nexusmgmt.com
---
If you are interested in helping to develop a GPL enterprise class
VPN/Firewall/Security device management console, please visit
http://iscs.sourceforge.net
prev parent reply other threads:[~2004-06-07 11:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-07 10:53 quick syntax query Knight, Steve
2004-06-07 11:06 ` Raileanu Grigore
2004-06-07 11:54 ` John A. Sullivan III [this message]
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=1086609260.21179.4.camel@localhost \
--to=john.sullivan@nexusmgmt.com \
--cc=Steve.Knight@bskyb.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