Bug #10951
closed
Firewall Rule Defaults Should be Any Instead of TCP
0%
Description
In any new firewall rule creation, the protocol defaults to TCP rather than "Any" (or at the very least TCP/UDP). All other fields in the firewall rule creation default to "Any" when no options are changed on the rule, except the Protocol field. This creates inconsistency in the expected operation of the new rule creation screen.
There have been multiple instances where customers create firewall rules and run into problems with things like DNS and DHCP not working because they didn't allow UDP protocols accidentally. I personally have spent an hour or more troubleshooting connectivity only to miss that the rule was set to IPv4 TCP accidentally.
This would be a minor change and save a lot of headache for new users and seasoned ones alike.
Updated by Jim Pingle over 3 years ago
- Status changed from New to Rejected
We've debated this before and the current default is acceptable. You'd be trading one set of support questions for another (e.g. "Why are there no port options on firewall rules?" and other similar questions) and it's also slightly less insecure to default to TCP rather than any.