This information is gleaned from the GitHub repository for HBlink.
[GLOBAL] - Systemwide Parameters
This section defines program-wide parameters and settings. Some of the keys in this section are reused elsewhere and may supersede these values in that circumstance.
This is the working path for files, you should leave it alone unless you NEED to change it
Depending on whether you're configuring masters or peers, the behavior of this value is slightly different. The value is in seconds.
Master: determines how often (in seconds) the Master maintenance loop runs
Peer: the interval (in seconds) that peers will ping the master, and re-try registraion
As with PING_TIME, this parameter specifies behavior for both masters and peers.
Master: number of times the master maintenance loop runs before de-registering a peer
Peer: how many pings are missed before we give up and re-register
Access Control Lists
Access Control Lists (ACLs) are used throughout the configuration file. You should be careful not to overuse them, as they can impact packet throughput. That said, they are a critical and flexible way to make sure you only get the traffic you want to see on your network.
[REPORTS] - Network Reporting Parameters
[LOGGER] - System Logger Parameters
[ALIASES] - ID lists from external sources
Instance Common Parameters
Should be relevant to what the role is. If it's a Master, it might do well to include "Master" in the identifier. For OpenBridge instances, we suggest that the master that the bridge is connecting with be included in the identifier. For peers, perhaps the callsign of the peer should be included in the identifier, such that when troubleshooting or examining logs, you can get a sense as to what is happening and which components are involved.
ACL Usage for OpenBridge Instances
Be aware that OpenBridge doesn't support peers per se, as it's a bridge between HBlink and a network like BrandMeister. It doesn't behave like a peer connection, so the concept of REG_ACL is not relevant in this section and any value set with that key will be ignored.
See the usage for this parameter above under [GLOBAL]. Since OpenBridge only deals with TS1, there is only one ACL for talk group ID's, hence the parameter name is different. Still, the ACL behaves the same as TGID_TS1_ACL as mentioned above.
ACL Usage for Master Instances
ACL Usage for Peer Instances
It's a bit redundant to consider whether rpeers should be deciding whether another peer can connect to it. If a peer is connecting to a master, the assumption is that it is appropriate that all peers connect with each other. Hence, the concept of REG_ACL is not relevant in this section and any value set with that key will be ignored.