Prepare a 1.0 release.
Merge pull request #307 from apenney/100-release

Prepare a 1.0 release.
Allow custom gemsource
Merge pull request #308 from hunner/dynamic_gemsource

Allow custom gemsource
Ignore .vagrant folder
Use iptables-save and parse the output

`iptables -S` didn't work on older OSs, so the tests have been adapted
for that.

There was one test for the NAT table that I'm not sure what the purpose
was, since it seemed to be testing munge instead. I edited it to get it
to pass.
Merge pull request #311 from hunner/fix_nobody

Use iptables-save and parse the output
Remove acceptance/basic_spec

This removes the legacy "basic_spec" that was used as an introduction to
module testing.  It assumes the FOSS path for the module dir.  Since the
default module dir changes in PE depending on whether or not the module
is distributed with PE or not, these basic specs have been removed from
other modules.
Merge pull request #309 from petems/ignore_vagrant_folder

Ignore .vagrant folder
Merge pull request #312 from justinstoller/maint/1.0.x/remove_basic_spec

Remove acceptance/basic_spec
Puppet-lint fix for > 80 character line
Fix various differences for rhel5

iptables 1.3.5 ships on rhel 5 and is really old. It doesn't support
`--comment` on ip6tables, doesn't support `-m socket` or `--random`, and
the format of netmasks uses subnet mask format instead of CIDR.
Merge pull request #314 from hunner/fix_cent5

Fix various differences for rhel5
Release 1.0.1

Bugfix: gracefully fail to manage ip6tables on iptables 1.3.x
Merge pull request #316 from hunner/release_1.0.1

Release 1.0.1
Add PE support.
Merge pull request #319 from apenney/add-pe

Add PE support.
Add PE support.
Bugfix: Account for rules sorted after unmanaged rules

The offset calculation assumed unmanaged rules are numbered 9000+ and
would be sorted to the end and didn't need to be accounted for. This
caused failures when people used9-numbered rules. This should fix that.

Additionally, for rules that are 9-numbered, they should be ordered
*after* unmanaged rules, so this fixes that too.

So when encountering unmanaged rules, the order will be something like
this:

- Managed rules that begin with 0 through 8
- Unmanaged rules (which are assigned 9-numbers)
- Managed rules that begin with 9 (but not numbered lower than the
  unmanaged rules)

Mixing unmanaged rules with managed rules is still not officially
supported, but at least we can try and behave with them.
Merge pull request #321 from hunner/fix_over_9000

Bugfix: Account for rules sorted after unmanaged rules