[MODULES-443] firewall proto should default to all, not tcp Created: 2014/01/31  Updated: 2019/09/04

Status: Accepted
Project: Modules
Component/s: firewall, supported
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: Hunter (Hunner) Haugen Assignee: Hunter (Hunner) Haugen
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Epic Link: Firewall Next
Team: Modules

 Description   

See https://github.com/puppetlabs/puppetlabs-firewall/issues/290 for context.

A deprecation warning in the mean time should work.



 Comments   
Comment by Rob Nelson [ 2014/06/02 ]

Some decisions need to be made on how to proceed as the PR https://github.com/puppetlabs/puppetlabs-firewall/pull/295 was closed without merging.

Comment by Morgan Rhodes [ 2015/01/22 ]

FYI, this is still something we'd like to do, possibly for the next major release of firewall.

Comment by Chris Butler [ 2019/09/04 ]

Is this still on the roadmap? We've recently discovered a number of issues in our config caused by the mistaken assumption that not specifying proto meant "all" instead of "tcp".

Generated at Wed Apr 01 15:14:52 PDT 2020 using Jira 8.5.2#805002-sha1:a66f9354b9e12ac788984e5d84669c903a370049.