Forge Home

10,482 downloads

9,720 latest version

2.9 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.0 (latest)
  • 0.0.2
  • 0.0.1
released May 20th 2013

Start using this module

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

Add this module to your Puppetfile:

mod 'thias-ipset', '0.1.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add thias-ipset
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install thias-ipset --version 0.1.0

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.

Download

Documentation

thias/ipset — version 0.1.0 May 20th 2013

puppet-ipset

Overview

Manage IP sets in the Linux kernel. Support in Red Hat Enterprise Linux has been introduced in the RHEL 6.2 kernel (run modinfo ip_set to check).

  • ipset : Main definition to create and manage IP sets.
  • ipset::iptables : Definition to manage IP set related iptables rules.
  • ipset::base : Base class for the common parts.
  • ipset::params : Base class for distribution specific parameters.

Once you have your IP sets in place, you'll want to manage iptables rules which make use of those IP sets.

This module is mostly a hack. The proper way to implementing IP sets would be to create a clean system service script which would be run before iptables.

Examples

Create a new my_blacklist IP set from a custom file :

file { '/path/to/my_blacklist.txt': content => "10.0.0.1\n10.0.0.2\n" }
ipset { 'my_blacklist':
  from_file => '/path/to/my_blacklist.txt',
}

Insert an iptables REJECT rule on-the-fly which ses the my_blacklist IP set :

ipset::iptables { 'my_blacklist':
  chain   => 'INPUT',
  options => '-p tcp',
  target  => 'REJECT',
}

Similar, but logging 80/tcp traffic from the raw table's PREROUTING chain :

ipset::iptables { 'my_blacklist-log':
  table   => 'raw',
  chain   => 'PREROUTING',
  ipset   => 'my_blacklist',
  options => '-p tcp --dport 80',
  target  => 'LOG --log-prefix "MyList: "',
}