The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Feature #11439

proto[col] sets would be cool

Added by Daniel Black about 3 years ago. Updated about 2 years ago.

Status:ClosedStart date:12/16/2011
Priority:NormalDue date:
Assignee:Ken Barber% Done:

0%

Category:firewallSpent time:-
Target version:-
Keywords: Branch:

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com


Description

        firewall { '520 dns':
                chain => 'OUTPUT',
                dport => '53',
                proto => [ 'tcp','udp' ],
                action => 'accept',
        }

Currently generates only tcp

Chain OUTPUT (policy ACCEPT 133 packets, 14604 bytes)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 ACCEPT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0           multiport dports 53 /* 520 dns */ 

History

#1 Updated by Daniel Black about 3 years ago

actually given the only sensible set is [‘tcp’,‘udp’] perhaps a ‘tcp-udp’ quasi protocol.

#2 Updated by James Turnbull about 3 years ago

  • Status changed from Unreviewed to Needs Decision
  • Assignee set to Ken Barber

#3 Updated by Ken Barber about 2 years ago

  • Status changed from Needs Decision to Closed

Hiya … I’ve fall behind a bit on all this work, also the bug tracker is moving to here: https://github.com/puppetlabs/puppet-firewall/issues I’ve managed to move what I still think is relevant and merge up items that are related. Consider this a slight declaration of ‘ticket debt’. If you think you’re issue isn’t represented in the new tracker feel free to open a new one.

Apologies for any confusion :–).

Ken.

#4 Updated by Ken Barber about 2 years ago

Sorry – the new URL is actually: http://github.com/puppetlabs/puppetlabs-firewall/issues … thanks @Wolfspyre.

Also available in: Atom PDF