Specify hosts
The broker configuration requires specification of the
target
setting, which identifies the
Perforce
service to which commands are to be sent, the listen
address, which identifies the address where the broker listens for
commands from
Helix Core Server
client applications, and the optional altserver
alternate
server address, which identifies a replica, proxy, or other broker
connected to the
Perforce
service.
The host specification uses the format
protocol:host:port
, where
protocol
is the communications protocol (beginning
with ssl:
for SSL, or tcp:
for plaintext),
host
is the name or IP address of the machine to
connect to, and port
is the number of the port on the
host.
Protocol | Behavior |
---|---|
|
If the If an IPv4 literal address (for example, |
|
Use |
|
Listen on/connect to an IPv4 address/port only. |
|
Listen on/connect to an IPv6 address/port only. |
|
Attempt to listen on/connect to an IPv4 address/port. If this fails, try IPv6. |
|
Attempt to listen on/connect to an IPv6 address/port. If this fails, try IPv4. |
|
Use |
|
Listen on/connect to an IPv4 address/port only, using SSL encryption. |
|
Listen on/connect to an IPv6 address/port only, using SSL encryption. |
|
Attempt to listen on/connect to an IPv4 address/port. If this fails, try IPv6. After connecting, require SSL encryption. |
|
Attempt to listen on/connect to an IPv6 address/port. If this fails, try IPv4. After connecting, require SSL encryption. |
The host
field can be the hosts' hostname or its IP
address. Both IPv4 and IPv6 addresses are supported. For the
listen
setting, you can use the *
wildcard to
refer to all IP addresses, but only when you are not using CIDR
notation.
If you use the *
wildcard with an IPv6 address, you must
enclose the entire IPv6 address in square brackets. For example,
[2001:db8:1:2:*]
is equivalent to
[2001:db8:1:2::]/64
. Best practice is to use CIDR notation,
surround IPv6 addresses with square brackets, and to avoid the
*
wildcard.