This directory contains sample service files for the firewalld firewall service to 'poke a hole' in the firewall enabling access to Perforce. If the firewalld service is used, these sample files may prove useful.
These instructions apply only after the <CODE>mkdirs.sh</CODE> script has been run for a given instance, as discussed in the SDP Guide.
To use these files:
For each instance, create your own p4d_N.xml file, copying from p4d_1.xml. Here N is the instance name, e.g. '2' or 'acme'. If your instance has a broker, proxy, or other component that is to run on the current machine, create additional files as needed. See the p4broker_1.xml file as an example.
Modify your XML files, changing the port number, short name, and description fields as desired. Keep the short name the same as the file (less the .xml extension). For example, p4d_1.xml might look like this: <PRE> <?xml version="1.0" encoding="utf-8"?> <service> <short>p4d_1</short> <description>Enable access to Helix Server on port 1666.</description> <port protocol="tcp" port="1666"/> </service> </PRE>
As root, copy your modified <CODE>p4*.xml</CODE> files to the <CODE>/etc/firewalld/services</CODE> directory.
<PRE> firewall-cmd --reload firewall-cmd --permanent --zone=public --add-service p4d_1 firewall-cmd --permanent --zone=public --add-service p4broker_1 firewall-cmd --reload iptables-save </PRE>
In these samples, the default public security zone is used. Further reading of the firewalld and firewall-cmd man pages is recommended for a more detailed understanding of security zones and other firewalld configuration details.
This example exposes ports for both p4d and p4broker processes. For replication, the P4TARGET values configured for replicas should bypass the broker and go direct to p4d. Ports for both p4d and p4broker must be open. Having them both open in the same public zone would allow regular users to potentially bypass the broker and access p4d directly (unless prevented by other means). This may well be intended behavior.
A more sophisticated firewall configuration could be configured such that the broker port is exposed in the public zone, while the direct p4d port is exposed in a separate zone accessible only by other server machines. This could allow replicas but not regular users to bypass the broker.
|#1||15797||tom_tyler||Routine Merge Down to dev from main for SDP.|
Added sample systemd init scripts for the SDP for RHEL/CentOS 7
and other Linux distros that use systemd.
Also updated README.md for firewalld.
Added sample firewalld configuration files illustrating how to 'poke a hole'
thru the firewall for p4broker, p4d, etc. Also added a README file
describing how to use them.