Fixed bug which arbitrarily limited iniface and outiface parameters

[lejonet]

Setting ingoing and outgoing interfaces are allowed in all chains, even own defined chains are allowed to have rules which specify in- and outgoing interfaces.

[vgeyer]

+1

[web-mi]

+1

[cyberious]

Please give details on what Platforms you are trying to fix with this issue.
@itze88 @Lexance @lejonet , just want to make sure we test on ALL Platforms to not break other users who may not have the issue on there platform of choice.

[lejonet]

Mainly it is the linux platform, with netfilter and iptables. But in general, I
haven't seen a firewall solution which only allows you to specify in- or
outgoing interface in the input, for ingoing, and output, for outgoing, chains.

[puppetcla]

Waiting for CLA signature by @lejonet

@lejonet - We require a Contributor License Agreement (CLA) for people who contribute to Puppet, but we have an easy click-through license with instructions, which is available at https://cla.puppetlabs.com/

Note: if your contribution is trivial and you think it may be exempt from the CLA, please post a short reply to this comment with details. http://docs.puppetlabs.com/community/trivial_patch_exemption.html

[vgeyer]

My platform is Debian Linux 7, with iptables v1.4.14, and puppetlabs/firewall module on v1.0.2.

[puppetcla]

CLA signed by all contributors.