Skip to content


Subversion checkout URL

You can clone with
Download ZIP
branch: master
Fetching contributors…

Cannot retrieve contributors at this time

220 lines (168 sloc) 6.889 kB
modules/shorewall/manifests/init.pp - manage firewalling with shorewall
Puppet Module for Shorewall
This module manages the configuration of Shorewall (
This module requires the concat module, you can find that here:
Copyright (C) 2007 David Schmitt <>
adapted by immerda project group - admin+puppet(at)
adapted by Puzzle ITC - haerry+puppet(at)
Copyright (c) 2009 Riseup Networks - micah(shift+2)
Copyright (c) 2010 intrigeri - intrigeri(at)
See LICENSE for the full license granted to you.
Based on the work of ADNET Ghislain <> from AQUEOS
Merged from:
- git://
- git://
- check if shorewall compiles without errors, otherwise fail !
If you need to install a specific version of shorewall other than
the default one that would be installed by 'ensure => present', then
you can set the following variable and that specific version will be
installed instead:
$shorewall_ensure_version = "4.0.15-1"
The main shorewall.conf is not managed by this module, rather the default one
that your operatingsystem provides is used, and any modifications you wish to do
to it should be configured with augeas, for example, to set IP_FORWARDING=Yes in
shorewall.conf, simply do this:
augeas { 'enable_ip_forwarding':
changes => 'set /files/etc/shorewall/shorewall.conf/IP_FORWARDING Yes',
lens => 'Shellvars.lns',
incl => '/etc/shorewall/shorewall.conf',
notify => Service[shorewall];
NOTE: this requires the augeas ruby bindings newer than 0.7.3.
If you need to, you can provide an entire shorewall.conf by passing its
source to the main class:
conf_source => "puppet:///modules/site_shorewall/${::fqdn}/shorewall.conf.${::operatingsystem}",
NOTE: if you distribute a file, you cannot also use augeas, puppet and augeas
will fight forever. Secondly, you will *need* to make sure that if you are shipping your own
shorewall.conf that you have the following value set in your shorewall.conf otherwise this
module will not work:
see also:
The shorewall::rules::torify define can be used to force some outgoing
TCP traffic through the Tor transparent proxy. The corresponding
non-TCP traffic is rejected accordingly.
Beware! This define only is part of a torified setup. DNS requests and
IPv6, amongst others, might leak network activity you would prefer not
to. You really need to read proper documentation about these matters
before using this feature e.g.:
The Tor transparent proxy location defaults to and can
be configured by setting the $tor_transparent_proxy_host and
$tor_transparent_proxy_port variables before including the main
shorewall class.
Example usage follows.
Torify any outgoing TCP traffic originating from user bob or alice and
aimed at or
shorewall::rules::torify {
users => [ 'bob', 'alice' ],
destinations => [ '', '' ];
Torify any outgoing TCP traffic to
shorewall::rules::torify {
destinations => [ '' ];
When no destination nor user is provided any outgoing TCP traffic (see
restrictions bellow) is torified. In that case the user running the
Tor client ($tor_user) is whitelisted; this variable defaults to
"debian-tor" on Debian systems and to "tor" on others. if this does
not suit your configuration you need to set the $tor_user variable
before including the main shorewall class.
When no destination is provided traffic directed to RFC1918 addresses
is by default allowed and (obviously) not torified. This behaviour can
be changed by setting the allow_rfc1918 parameter to false.
Torify any outgoing TCP traffic but connections to RFC1918 addresses:
shorewall::rules::torify {
Torify any outgoing TCP traffic:
shorewall::rules::torify {
allow_rfc1918 => false;
In some cases (e.g. when providing no specific destination nor user
and denying access to RFC1918 addresses) UDP DNS requests may be
rejected. This is intentional: it does not make sense leaking -via DNS
requests- network activity that would otherwise be torified. In that
case you probably want to read proper documentation about such
matters, enable the Tor DNS resolver and redirect DNS requests through
Example from node.pp:
node xy {
startup => "0" # create shorewall ruleset but don't startup
shorewall::rule {
'incoming-ssh': source => 'all', destination => '$FW', action => 'SSH(ACCEPT)', order => 200;
'incoming-puppetmaster': source => 'all', destination => '$FW', action => 'Puppetmaster(ACCEPT)', order => 300;
'incoming-imap': source => 'all', destination => '$FW', action => 'IMAP(ACCEPT)', order => 300;
'incoming-smtp': source => 'all', destination => '$FW', action => 'SMTP(ACCEPT)', order => 300;
class config::site_shorewall($startup = '1') {
startup => $startup
# If you want logging:
#shorewall::params {
# 'LOG': value => 'debug';
shorewall::zone {'net':
type => 'ipv4';
shorewall::rule_section { 'NEW':
order => 100;
shorewall::interface { 'eth0':
zone => 'net',
rfc1918 => true,
options => 'tcpflags,blacklist,nosmurfs';
shorewall::policy {
sourcezone => '$FW',
destinationzone => '$FW',
policy => 'ACCEPT',
order => 100;
sourcezone => '$FW',
destinationzone => 'net',
policy => 'ACCEPT',
shloglevel => '$LOG',
order => 110;
sourcezone => 'net',
destinationzone => '$FW',
policy => 'DROP',
shloglevel => '$LOG',
order => 120;
# default Rules : ICMP
shorewall::rule {
source => 'all',
destination => '$FW',
order => 200,
action => 'AllowICMPs/(ACCEPT)';
Jump to Line
Something went wrong with that request. Please try again.