mailing list archives
[iptables] Zone based rules
From: Jimmy Thrasibule <thrasibule.jimmy () gmail com>
Date: Tue, 09 Apr 2013 17:41:39 +0200
I've got a Linux box sitting between different local networks. I'd like
to set up access policies between each network so I though about a zone
Each zone is responsible of its incoming and outgoing traffic. However
this role is played by the same box and if a packet is accepted by a
zone, it cannot be denied by another zone.
Let me give you an example:
| Marketing |---------
----------- | eth0
| Firewall |
--------- | eth1
| Servers |-----------
Marketing wants to reach a server. However, marketing is very large on
its outgoing traffic (allows everything) on the server side however we
would reject any SSH connection coming from marketing.
Here are the iptables rules I would go for:
# Zones creation.
# Traffic coming from the zones.
-A FORWARD -i eth0 ZONE_MRKT
-A FORWARD -i eth1 ZONE_SRV
# Traffic to the zones.
-A FORWARD -o eth0 ZONE_MRKT
-A FORWARD -o eth1 ZONE_SRV
# Let's look at marketing.
-A ZONE_MKRT -i eth0 -s mar.ket.ing.net/mask -d any/0 -j MRKT_OUT
# Marketing allows any outgoing traffic.
-A MRKT_OUT -j ACCEPT
-A ZONE_SRV -o eth1 -s any/0 -d ser.ver.s.net/mask -j SRV_IN
-A SRV_IN -s mar.ket.ing.net/mask -p tcp --dport 22 -j DROP
In this example traffic leaving a zone is checked first so any traffic
from marketing is allowed while the servers zone denies traffic from
In can change the rules order but this will not solve the problem.
Another solution would be to mark the packet and then check the mark at
the end to decide on whether to accept or reject. But how about
performances on a large set of rules as the firewall will have to go
through all of them before taking a decision?
How would you manage such a case?
firewall-wizards mailing list
firewall-wizards () listserv icsalabs com
- [iptables] Zone based rules Jimmy Thrasibule (Apr 09)