Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'd like to create a single rule in iptables (if possible) that uses multiple source IP addresses. Is this possible?

share|improve this question
// , You can do the same thing for ports, according to…. – Nathan Basanese Feb 22 at 20:16
up vote 9 down vote accepted

This is only possible if you can aggregate the source IP's you want into a contiguous range. eg

iptables -A INPUT -s -d -p tcp -j ACCEPT

If you cannot find a common netmask that covers the IP's you want, you'll have to write several identical rules to do what you want.

There are several iptables frameworks around which can deal with the low level of writing the iptables rules, allowing you to define your rules at a more symolic level. Shorewall is a common one that ships with most current linux distributions.

share|improve this answer
// , This is incorrect, according to…. – Nathan Basanese Feb 22 at 20:16

To add multiple sources in a single command I would do this:

iptables -t filter -A INPUT -s,, -j ACCEPT

iptables will automatically translate it into multiple rules.

share|improve this answer
Despite the lack of votes, this works and is the right answer to the question – phil-lavin Feb 16 '15 at 8:17
I'll bump it up!! Thanks for the correct answer. – Felipe Alvarez Aug 3 '15 at 3:05
// , Can you do the same with the ports? – Nathan Basanese Feb 22 at 19:47

you can use the iprange module in combination with '--src-range' like for e.x.:

-A INPUT -i eth0 -m iprange --src-range -j ACCEPT

Source: iptables 1.4.7 man page

   This matches on a given arbitrary range of IP addresses.

   [!] --src-range from[-to]
          Match source IP in the specified range.

   [!] --dst-range from[-to]
          Match destination IP in the specified range.

(i know this is like a 4 year old question, but just to answer for anyone who seeks this on the net)

share|improve this answer

You can define multiple chains such that you can combine independent lists of requirements. I doubt this is exactly what you want, but it's still pretty handy. We use this to define lists of valid user-types by IP, and then apply port restrictions to the source networks. So, for instance:

# Allow SMTP from anywhere
-A tcp_inbound -p tcp -m tcp -s 0/0 --dport 25 -j allowed
# Define the set of IP ranges we'll send to the tcp_user_inbound chain
-A tcp_inbound -p tcp -m tcp -s -j tcp_user_inbound
-A tcp_inbound -p tcp -m tcp -s -j tcp_user_inbound
-A tcp_inbound -p tcp -m tcp -s -j tcp_user_inbound
-A tcp_inbound -p tcp -m tcp -s -j tcp_user_inbound
-A tcp_inbound -p tcp -m tcp -s -j tcp_user_inbound
-A tcp_inbound -p tcp -m tcp -s -j tcp_user_inbound
# Ports we allow access to based on a source-address prereq.
-A tcp_user_inbound -p tcp -m tcp --dport 22 -j allowed
-A tcp_user_inbound -p tcp -m tcp --dport 5950:5958 -j allowed
# https
-A tcp_user_inbound -p tcp -m tcp --dport 443 -j allowed
share|improve this answer

In addition to the comment of Bòss King, you can also simply specify several addresses seperated with a comma:

[!] -s, --source address[/mask][,...]
      Source specification. Address can be either a network name, a hostname, a network IP address (with /mask), or a plain IP address. Hostnames will be resolved once only, before the rule is submitted to the kernel.  Please note  that  specifying
      any  name  to  be resolved with a remote query such as DNS is a really bad idea.  The mask can be either a network mask or a plain number, specifying the number of 1's at the left side of the network mask.  Thus, a mask of 24 is equivalent to  A "!" argument before the address specification inverts the sense of the address. The flag --src is an alias for this option.  Multiple addresses can be specified, but this will expand to multiple rules (when adding with  -A),
      or will cause multiple rules to be deleted (with -D).
share|improve this answer
From the shell like bash, I must escape the inversion with a backslash: \! -s ... – Marcos Sep 8 '14 at 10:46

Let's say for example that you only want to accept SMTP packets that come from or You can user the following rules:

  # create a new chain
  iptables --new-chain multiple_sources_smtp
  # send all SMTP connections to the new chain
  iptables --append INPUT --protocol tcp --dport 25 --jump multiple_sources_smtp
  # use the default INPUT rules for packets coming from allowed sources
  iptables --append multiple_sources_smtp --source --jump RETURN
  iptables --append multiple_sources_smtp --source --jump RETURN
  # drop packets from anywhere else
  iptables --append multiple_sources_smtp -j DROP

Or as the output of iptables-save

  # Generated by iptables-save v1.4.14 on Sat Dec  6 09:17:11 2014
  :INPUT ACCEPT [32:13325]
  :OUTPUT ACCEPT [25:3084]
  :multiple_sources_smtp - [0:0]
  -A INPUT -p tcp -m tcp --dport 25 -j multiple_sources_smtp
  -A multiple_sources_smtp -s -j RETURN
  -A multiple_sources_smtp -s -j RETURN
  -A multiple_sources_smtp -j DROP
  # Completed on Sat Dec  6 09:17:11 2014
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.