|
BNBT Tracker Links Documentation
Configuration
bnbt_tlink_bind - The IP address that tracker link communication is handled on.
Only use this when you KNOW you need to, since incorrect bindings will prevent the link from working.
bnbt_tlink_connect - The IP address or domain name of the tracker network hub you want your tracker to connect to.
This is not to be used by the tracker network hub. Because this can be a domain name, the tracker hub CAN be on a dynamic domain name.
bnbt_tlink_password - The password to be used by the tracker network. This must match across ALL trackers on the network.
bnbt_tlink_port - The TCP port used by the tracker network. This must match across ALL trackers on the network. The tracker hub must be configured to allow inbound communication on this port.
Running firwewalls that allow you to restrict access may help improve network stability. Allow only communication from IP addresses that you know are going to be hosting trackers for you.
- Valid range: 0-65535, recommended range: 1024-65535. One port from the range.
bnbt_tlink_server - Is this tracker the hub of the network? (0 - no/1 - yes)
Example configuration for a tracker hub (address: tracker-hub.testsite.com):
bnbt_tlink_bind =
bnbt_tlink_connect =
bnbt_tlink_password = bnbtLinkTest
bnbt_tlink_port = 59100
bnbt_tlink_server = 1
Example configuration for tracker leaves to tracker-hub.testsite.com
(addresses: tracker-x.testsite.com where X is a tracker number):
bnbt_tlink_bind =
bnbt_tlink_connect = tracker-hub.testsite.com
bnbt_tlink_password = bnbtLinkTest
bnbt_tlink_port = 59100
bnbt_tlink_server = 0
Notice that the bind values are blank for both example configurations. This is
because we don't need to bind to a specific IP address at all unless we have
computers with multiple network adapters and we want the link to operate on only
one of them (example, running a link over a 100mbit backbone while not accepting
link requests from the internet).
| 