From: "U. George" <netbeans@gatworks.com>
To: netfilter@lists.netfilter.org
Subject: can this be written as one rule ?
Date: Sun, 01 Jul 2007 11:01:40 -0400 [thread overview]
Message-ID: <4687C1D4.3090704@gatworks.com> (raw)
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.124.176.0/20 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.124.32.0/20 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.127.64.0/17 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.128.94.0/24 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.130.126.128/26 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.132.194.0/24 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.139.164.0/24 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.139.198.0/24 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.141.9.0/24 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.142.125.0/24 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.142.3.128/25 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.145.21.128/25 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.146.201.0/24 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.152.32.0/24 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.153.78.0/24 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.153.98.0/24 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.155.196.0/25 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.158.66.128/25 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.16.0.0/13 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.224.0.0/12 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.24.0.0/14 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.254.15.0/24 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.32.0.0/14 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.36.0.0/16 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.36.64.0/18 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.51.0.0/16 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.54.208.0/20 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.54.224.0/20 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.55.128.0/20 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.55.144.0/20 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.55.160.0/20 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.55.64.0/20 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.68.0.0/14 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.88.32.0/20 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.88.64.0/20 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 121.96.0.0/15 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 122.0.128.0/17 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 122.100.48.0/20 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 122.169.0.0/19 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 122.169.100.0/23 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 122.199.106.0/22 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 122.199.90.0/23 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 122.2.0.0/15 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 122.202.128.0/17 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 122.254.128.0/17 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_IFACE -s 122.32.0.0/12 -j DROP
> $IPTABLES -t nat -A PREROUTING -i $INET_I
And so on ?
next reply other threads:[~2007-07-01 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-01 15:01 U. George [this message]
2007-07-01 15:04 ` can this be written as one rule ? Stephen Frost
2007-07-01 16:42 ` Mike Wright
2007-07-02 20:03 ` Clister
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=4687C1D4.3090704@gatworks.com \
--to=netbeans@gatworks.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