[
https://issues.apache.org/jira/browse/VCL-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15991031#comment-15991031
]
ASF subversion and git services commented on VCL-1031:
------------------------------------------------------
Commit 1793370 from [email protected] in branch 'vcl/trunk'
[ https://svn.apache.org/r1793370 ]
VCL-1031
Updated Linux.pm::firewall to return a generic VCL::Module::OS::Linux::firewall
object if none of the specific (iptables, firewalld, ufw) modules could be
initialized. This allows you to call '$self->os->firewall->can(...)' without
having to check if $self->os->firewall is defined and valid first. Without
this, many warnings were generated from Lab.pm.
> Update iptables.pm to be used for all iptables configuration
> ------------------------------------------------------------
>
> Key: VCL-1031
> URL: https://issues.apache.org/jira/browse/VCL-1031
> Project: VCL
> Issue Type: Improvement
> Components: vcld (backend)
> Reporter: Andy Kurth
> Assignee: Andy Kurth
> Fix For: 2.5
>
>
> The iptables.pm module was created when the NAT functionality was added. Up
> to this point, it is only being used to configure the firewall on the NAT
> host. The Linux OS modules are still used to configure iptables. With the
> addition of firewalld (VCL-972) and ufw (VCL-971), all of the Linux firewall
> code should be pulled out of the main OS module and into the dedicated file.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
