Helix Core is now P4. Product user interfaces will be updated soon. Learn more >>

P4 Server Administration Documentation | 2025.1

# 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 P4 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/TLS, 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
--- | ---
`<not set>` | If the `net.rfc3484` configurable is set, allow the OS to determine which transport is used. This is applicable only if a host name (either FQDN or unqualified) is used. If an IPv4 literal address (for example, `127.0.0.1`) is used, the transport is always `tcp4`, and if an IPv6 literal address (for example, `::1`) is used, then the transport is always `tcp6`.
`tcp:` | Use `tcp4:` behavior, but if the address is numeric and contains two or more colons, assume `tcp6:`. If the `net.rfc3484` configurable is set, allow the OS to determine which transport is used.
`tcp4:` | Listen on/connect to an IPv4 address/port only.
`tcp6:` | Listen on/connect to an IPv6 address/port only.
`tcp46:` | Attempt to listen on/connect to an IPv4 address/port. If this fails, try IPv6.
`tcp64:` | Attempt to listen on/connect to an IPv6 address/port. If this fails, try IPv4.
`ssl:` | Use `ssl4:` behavior, but if the address is numeric and contains two or more colons, assume `ssl6:`. If the `net.rfc3484` configurable is set, allow the OS to determine which transport is used.
`ssl4:` | Listen on/connect to an IPv4 address/port only, using SSL/TLS encryption.
`ssl6:` | Listen on/connect to an IPv6 address/port only, using SSL/TLS encryption.
`ssl46:` | Attempt to listen on/connect to an IPv4 address/port. If this fails, try IPv6. After connecting, require SSL/TLS encryption.
`ssl64:` | Attempt to listen on/connect to an IPv6 address/port. If this fails, try IPv4. After connecting, require SSL/TLS 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.

## Next step

Global settings

Your search for returned results