Note: You cannot activate the HTTP configuration (part of Proxy Administration) from the Enterprise Firewall Manager. The HTTP daemon must be stopped and started via either local or remote administration.
Note: There can be more than one instance of the same rule added to this list. This is because it is possible that an administrator would want to use the same rule template twice, and assign a different value for the "Flow" field. Use caution when selecting rule templates so that you do not select the same instance of a template more times than what you intended.
![]() | Left to Right indicates that the Source and Destination of the Connection will get written directly to the rule as it is written into the Rule Base File. |
![]() | Right to Left indicates that the Source and Destination of the Connection will be reversed when it is written to the Rule Base File. |
The default Security Agreement is "Host Only" which will not permit the Enterprise Firewall Manager to update any of the configuration files for this Managed Firewall.
Note that the Recipient firewall must have "Host Only" selected for its Security Agreement. When the recipient firewall is cloned, the source's assigned Security Agreement will be assigned to the recipient.
Note: You cannot activate the HTTP configuration (part of Proxy Administration) from the Enterprise Firewall Manager. The HTTP daemon must be stopped and started via either local or remote administration.