Forge Home


disables iptables


6,294 latest version

4.6 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 0.1.15 (latest)
released Apr 25th 2017
This version is compatible with:
  • , , , , , ,

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'eyp-iptables', '0.1.15'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add eyp-iptables
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install eyp-iptables --version 0.1.15

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.



eyp/iptables — version 0.1.15 Apr 25th 2017


PRs Welcome

Table of Contents

  1. Overview
  2. Module Description
  3. Setup
  4. Usage
  5. Reference
  6. Limitations
  7. Development


Disable iptables

Module Description

This module is intended to disable iptables by setting an empty rule set (IPv4 only)

To be able to manage logrotate files it needs eyp-logrotate


What iptables affects


  • package
  • service (SLES11SP3 disables SuSEfirewall2)
  • files:
    • RedHat:
      • /etc/sysconfig/iptables
    • Debian:
      • /etc/iptables/rules.v4
    • SLES 11 SP 3
      • does not manage any files

Setup Requirements

This module requires pluginsync enabled

Beginning with iptables

class { 'iptables': }


Put the classes, types, and resources for customizing, configuring, and doing the fancy stuff with your module here.



  • ensure: (default: running)
  • enable: (default: true)
  • manage_docker_service: (default: false)
  • manage_service: (default: true)
  • manage_logrotate: add logrotate config file (default: true)
  • logrotate_rotate = '4',
  • logrotate_compress = true,
  • logrotate_missingok = true,
  • logrotate_notifempty = true,
  • logrotate_frequency = 'weekly',


Tested on:

  • CentOS 5
  • CentOS 6
  • CentOS 7
  • Ubuntu 14.04
  • SLES 11 SP3


We are pushing to have acceptance testing in place, so any new feature must have tests to check both presence and absence of any feature


  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Added some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request