Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Leonardo Rodrigues Magalhães" <leolistas@solutti.com.br>
To: paul@pitbull-racing.com,
	"Net Filter (E-mail)" <netfilter@lists.netfilter.org>
Subject: Re: Groups in iptables
Date: Sat, 29 Nov 2003 16:06:01 -0300	[thread overview]
Message-ID: <001301c3b6ab$d569cf10$8b00000a@casa> (raw)
In-Reply-To: 000301c3b69e$3e4122d0$6400a8c0@pfontenot


    Source and destination addresses cannot be given as a 'group of IPs'.
It's true that source and destination addresses CAN be always written as
net.work.address/mask, thus allowing you to specify a whole C
(your.net.work.0/24 ) network of even networks with different masks.

    In your case, 192.168.0.25, 192.168.0.26 and 192.168.0.27 cannot be
written as network/mask. So you CANNOT write one SINGLE rule to do what you
want. You'll probably need to write a single rule for each address.

    But if you're one of those who are not afraid of source code and
recompiling things, you may wanna try iprange iptables module that can be
found on patch-o-matic. This module makes possible to specify any given
range of IPs as source and/or destination.

[root@firewall root]# iptables -m iprange --help
iptables v1.2.9
[ ..... looooooots of information ...... ]

iprange match v1.2.9 options:
[!] --src-range ip-ip        Match source IP in the specified range
[!] --dst-range ip-ip        Match destination IP in the specified range


    Anyway, neither iprange can be used if your IP addresses are completly
different from each other (192.168.0.20, 10.10.2.1, 172.16.3.1,
200.201.202.203) .... in this case you'll for sure have to give several
rules, one for each address.

    Hope this helps you :)

    Sincerily,
    Leonardo Rodrigues


----- Original Message ----- 
From: "Paul Fontenot" <paul@pitbull-racing.com>
To: "Net Filter (E-mail)" <netfilter@lists.netfilter.org>
Sent: Saturday, November 29, 2003 2:28 PM
Subject: Groups in iptables


> I would imagine the answer to this is yes, but I haven't found anything on
> the subject. If you wanted to limit outbound traffic for a certain port to
> certain group of servers is that possible?
>
> For example, can I create a group:
>
> MAILSERVERS = 192.168.0.25, 192.168.0.26, 192.168.0.27
>
> and use that in a ruleset:
> -A INSIDE_ACCESS_OUT -s $MAILSERVERS -p tcp -m tcp --dport 25 --tcp-flags
> SYN,RST,ACK SYN -j ACCEPT
>
> and then drop the rest:
> -A INSIDE_ACCESS_OUT -p tcp -m tcp --dport 25 -j DROP
>
>
>



  reply	other threads:[~2003-11-29 19:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-29 17:28 Groups in iptables Paul Fontenot
2003-11-29 19:06 ` Leonardo Rodrigues Magalhães [this message]
2003-11-29 22:24   ` Chris Brenton
  -- strict thread matches above, loose matches on Subject: below --
2003-11-29 17:18 Paul Fontenot

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='001301c3b6ab$d569cf10$8b00000a@casa' \
    --to=leolistas@solutti.com.br \
    --cc=netfilter@lists.netfilter.org \
    --cc=paul@pitbull-racing.com \
    /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