Skip to content

HBlink3 part 2 Link to Brandmeister

If you haven’t seen my last post about making a private DMR server click this link to read that post. HBlink DMR Server. How to set it up for a private DMR server.

After doing some research I’ve found connecting to Brandmeister using this method is frowned upon by the Brandmeister team. A better option is to use OpenBridge. I’ve read in various forums Brandmeister has banned accounts using the method I’ve posted below. Use at your own risk.

My original thought was I would just set up HBlink3 as a private DMR server to have some friends use and to give us an as private as possible DMR experience. However I just couldn’t let well enough be enough and I went ahead and linked my HBlink server to BM as an experiment.

Here is my hblink config file. You’ll need to edit the fields under [REPEATER-1] to match your Brandmeister account details. I’ll add notes next to the fields I edited. You’ll also notice I changed the port numbers under the [PARROT] because BM needs to use port 62031, or at least I think it does. Mine didn’t work until I gave BM port 62031.

# PROGRAM-WIDE PARAMETERS GO HERE
# PATH - working path for files, leave it alone unless you NEED to change it
# PING_TIME - the interval that peers will ping the master, and re-try registraion
#           - how often the Master maintenance loop runs
# MAX_MISSED - how many pings are missed before we give up and re-register
#           - number of times the master maintenance loop runs before de-registering a peer
#
# ACLs:
#
# Access Control Lists are a very powerful tool for administering your system.
# But they consume packet processing time. Disable them if you are not using them.
# But be aware that, as of now, the configuration stanzas still need the ACL
# sections configured even if you're not using them.
#
# REGISTRATION ACLS ARE ALWAYS USED, ONLY SUBSCRIBER AND TGID MAY BE DISABLED!!!
#
# The 'action' May be PERMIT|DENY
# Each entry may be a single radio id, or a hypenated range (e.g. 1-2999)
# Format:
#       ACL = 'action:id|start-end|,id|start-end,....'
#               --for example--
#       SUB_ACL: DENY:1,1000-2000,4500-60000,17
#
# ACL Types:
#       REG_ACL: peer radio IDs for registration (only used on HBP master systems)
#       SUB_ACL: subscriber IDs for end-users
#       TGID_TS1_ACL: destination talkgroup IDs on Timeslot 1
#       TGID_TS2_ACL: destination talkgroup IDs on Timeslot 2
#
# ACLs may be repeated for individual systems if needed for granularity
# Global ACLs will be processed BEFORE the system level ACLs
# Packets will be matched against all ACLs, GLOBAL first. If a packet 'passes'
# All elements, processing continues. Packets are discarded at the first
# negative match, or 'reject' from an ACL element.
#
# If you do not wish to use ACLs, set them to 'PERMIT:ALL'
# TGID_TS1_ACL in the global stanza is used for OPENBRIDGE systems, since all
# traffic is passed as TS 1 between OpenBridges
[GLOBAL]
PATH: ./
PING_TIME: 5
MAX_MISSED: 3
USE_ACL: True
REG_ACL: PERMIT:ALL
SUB_ACL: DENY:1
TGID_TS1_ACL: PERMIT:ALL
TGID_TS2_ACL: PERMIT:ALL

# NOT YET WORKING: NETWORK REPORTING CONFIGURATION
#   Enabling "REPORT" will configure a socket-based reporting
#   system that will send the configuration and other items
#   to a another process (local or remote) that may process
#   the information for some useful purpose, like a web dashboard.
#
#   REPORT - True to enable, False to disable
#   REPORT_INTERVAL - Seconds between reports
#   REPORT_PORT - TCP port to listen on if "REPORT_NETWORKS" = NETWORK
#   REPORT_CLIENTS - comma separated list of IPs you will allow clients
#       to connect on. Entering a * will allow all.
#
# ****FOR NOW MUST BE TRUE - USE THE LOOPBACK IF YOU DON'T USE THIS!!!****
[REPORTS]
REPORT: True
REPORT_INTERVAL: 30
REPORT_PORT: 4321
REPORT_CLIENTS: *

# SYSTEM LOGGER CONFIGURAITON
#   This allows the logger to be configured without chaning the individual
#   python logger stuff. LOG_FILE should be a complete path/filename for *your*
#   system -- use /dev/null for non-file handlers.
#   LOG_HANDLERS may be any of the following, please, no spaces in the
#   list if you use several:
#       null
#       console
#       console-timed
#       file
#       file-timed
#       syslog
#   LOG_LEVEL may be any of the standard syslog logging levels, though
#   as of now, DEBUG, INFO, WARNING and CRITICAL are the only ones
#   used.
#
[LOGGER]
LOG_FILE: hblink.log
LOG_HANDLERS: file-timed,console-timed
LOG_LEVEL: INFO
LOG_NAME: HBlink

# DOWNLOAD AND IMPORT SUBSCRIBER, PEER and TGID ALIASES
# Ok, not the TGID, there's no master list I know of to download
# This is intended as a facility for other applcations built on top of
# HBlink to use, and will NOT be used in HBlink directly.
# STALE_DAYS is the number of days since the last download before we
# download again. Don't be an ass and change this to less than a few days.
[ALIASES]
TRY_DOWNLOAD: True
PATH: ./json/
PEER_FILE: peer_ids.json
SUBSCRIBER_FILE: subscriber_ids.json
TGID_FILE: talkgroup_ids.json
PEER_URL: https://radioid.net/static/rptrs.json
SUBSCRIBER_URL: https://radioid.net/static/users.json
STALE_DAYS: 28

# OPENBRIDGE INSTANCES - DUPLICATE SECTION FOR MULTIPLE CONNECTIONS
# OpenBridge is a protocol originally created by DMR+ for connection between an
# IPSC2 server and Brandmeister. It has been implemented here at the suggestion
# of the Brandmeister team as a way to legitimately connect HBlink to the
# Brandemiester network.
# It is recommended to name the system the ID of the Brandmeister server that
# it connects to, but is not necessary. TARGET_IP and TARGET_PORT are of the
# Brandmeister or IPSC2 server you are connecting to. PASSPHRASE is the password
# that must be agreed upon between you and the operator of the server you are
# connecting to. NETWORK_ID is a number in the format of a DMR Radio ID that
# will be sent to the other server to identify this connection.
# other parameters follow the other system types.
#
# ACLs:
# OpenBridge does not 'register', so registration ACL is meaningless.
# Proper OpenBridge passes all traffic on TS1.
# HBlink can extend OPB to use both slots for unit calls only.
# Setting "BOTH_SLOTS" True ONLY affects unit traffic!
# Otherwise ACLs work as described in the global stanza
[OBP-1]
MODE: OPENBRIDGE
ENABLED: False
IP:
PORT: 62035
NETWORK_ID: 3129100
PASSPHRASE: password
TARGET_IP: 1.2.3.4
TARGET_PORT: 62035
BOTH_SLOTS: True
USE_ACL: True
SUB_ACL: DENY:1
TGID_ACL: PERMIT:ALL

# MASTER INSTANCES - DUPLICATE SECTION FOR MULTIPLE MASTERS
# HomeBrew Protocol Master instances go here.
# IP may be left blank if there's one interface on your system.
# Port should be the port you want this master to listen on. It must be unique
# and unused by anything else.
# Repeat - if True, the master repeats traffic to peers, False, it does nothing.
#
# MAX_PEERS -- maximun number of peers that may be connect to this master
# at any given time. This is very handy if you're allowing hotspots to
# connect, or using a limited computer like a Raspberry Pi.
#
# ACLs:
# See comments in the GLOBAL stanza
[MASTER-1]
MODE: MASTER
ENABLED: True
REPEAT: True
MAX_PEERS: 10
EXPORT_AMBE: False
IP:
PORT: 62030
PASSPHRASE: passw0rd
GROUP_HANGTIME: 5
USE_ACL: True
REG_ACL: DENY:1
SUB_ACL: DENY:1
TGID_TS1_ACL: PERMIT:ALL
TGID_TS2_ACL: PERMIT:ALL

# PEER INSTANCES - DUPLICATE SECTION FOR MULTIPLE PEERS
# There are a LOT of errors in the HB Protocol specifications on this one!
# MOST of these items are just strings and will be properly dealt with by the program
# The TX & RX Frequencies are 9-digit numbers, and are the frequency in Hz.
# Latitude is an 8-digit unsigned floating point number.
# Longitude is a 9-digit signed floating point number.
# Height is in meters
# Setting Loose to True relaxes the validation on packets received from the master.
# This will allow HBlink to connect to a non-compliant system such as XLXD, DMR+ etc.
#
# ACLs:
# See comments in the GLOBAL stanza
[PARROT]
MODE: PEER
ENABLED: True 
LOOSE: True
EXPORT_AMBE: False
IP: 127.0.0.1
PORT: 62032 <------ CHANGE THIS FROM 62031 TO 62032
MASTER_IP: 127.0.0.1
MASTER_PORT: 54100
PASSPHRASE: passw0rd
CALLSIGN: ECHO
RADIO_ID: 9999
RX_FREQ: 434000000
TX_FREQ: 434000000
TX_POWER: 10
COLORCODE: 1
SLOTS: 2
LATITUDE: 33.0000
LONGITUDE: -84.0000
HEIGHT: 75
LOCATION:
DESCRIPTION:
URL:
SOFTWARE_ID: 20230806
PACKAGE_ID: MMDVM_HBlink3
GROUP_HANGTIME: 5
OPTIONS:
USE_ACL: False
SUB_ACL: DENY:1
TGID_TS1_ACL: PERMIT:ALL
TGID_TS2_ACL: PERMIT:ALL

[REPEATER-1]
MODE: PEER
ENABLED: True <----- SET THIS TO True
LOOSE: False
EXPORT_AMBE: False
IP:
PORT: 54001
MASTER_IP: 74.91.114.19 <------- ENTER THE BM SERVER IP THAT YOU WANT TO USE
MASTER_PORT: 62031 <------ ENTER THIS PORT NUMBER FOR BM
PASSPHRASE: passw0rd <------ ENTER YOUR BRANDMIESTER PASSWORD
CALLSIGN: N3EMC <=------- ENTER YOUR CALLSIGN
RADIO_ID: 99999999 <------ YOUR DMR ID PLUS A 2 DIGIT SUFFIX I.E 31245601 
RX_FREQ: 449000000 <------ OPTIONAL
TX_FREQ: 444000000 <------ OPTIONAL
TX_POWER: 25 <------ OPTIONAL
COLORCODE: 1 <------ OPTIONAL / MATCH RADIO
SLOTS: 2 <------- ENTER THE SLOT YOU WANT TO USE 1,2 OR 3 FOR 1 AND 2 OR 4 FOR?
LATITUDE: 38.0000 <------ OPTIONAL / MUST BE THE SAME NUMBER OF DIGITS AS THIS EXAMPLE
LONGITUDE: -095.0000 <------ OPTIONAL / MUST BE THE SAME NUMBER OF DIGITS AS THIS EXAMPLE
HEIGHT: 75 <------ OPTIONAL
LOCATION: United States <------ OPTIONAL
DESCRIPTION: This is a very cool repeater <------ OPTIONAL
URL: www.freestar.network <------ OPTIONAL
SOFTWARE_ID: 20230103 <----LEAVE EVERYTHING HERE AND BELOW ALONE
PACKAGE_ID: MMDVM_HBlink3
GROUP_HANGTIME: 5
OPTIONS:
USE_ACL: True
SUB_ACL: DENY:1
TGID_TS1_ACL: PERMIT:ALL
TGID_TS2_ACL: PERMIT:ALL

[XLX-1]
MODE: XLXPEER
ENABLED: False
LOOSE: True
EXPORT_AMBE: False
IP:
PORT: 54002
MASTER_IP: 172.16.1.1
MASTER_PORT: 62030
PASSPHRASE: passw0rd
CALLSIGN: M1ABC
RADIO_ID: 2350000
RX_FREQ: 449000000
TX_FREQ: 444000000
TX_POWER: 25
COLORCODE: 1
SLOTS: 1
LATITUDE: 38.0000
LONGITUDE: -095.0000
HEIGHT: 75
LOCATION: United Kingdom
DESCRIPTION: This is a very cool repeater
URL: www.w1abc.org
SOFTWARE_ID: 20230103
PACKAGE_ID: MMDVM_HBlink3
GROUP_HANGTIME: 5
XLXMODULE: 4004
USE_ACL: True
SUB_ACL: DENY:1
TGID_TS1_ACL: PERMIT:ALL
TGID_TS2_ACL: PERMIT:ALL

iF YOU COPY / PASTE THE ABOVE CONFIG FILE REMOVE THE <—- PARTS AS YOU EDIT IT.

Edit your rules.py file to look like this and add any TG’s you want to it following the same scheme as this file.

BRIDGES = {
    'PRIVATE_TG': [
        {'SYSTEM': 'MASTER-1', 'TS': 2, 'TGID': 9, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [9], 'OFF': []}
    ],
    'PARROT': [
        {'SYSTEM': 'MASTER-1', 'TS': 2, 'TGID': 9999, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [9999], 'OFF': []},
        {'SYSTEM': 'PARROT', 'TS': 2, 'TGID': 9999, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [9999], 'OFF': []}
    ],
    'PRIVATE_TG': [
        {'SYSTEM': 'MASTER-1', 'TS': 2, 'TGID': 8, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [8], 'OFF': []}
    ],
    'BRANDMEISTER': [
        {'SYSTEM': 'MASTER-1', 'TS': 2, 'TGID': 91, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [9,10], 'OFF': []},
        {'SYSTEM': 'REPEATER-1', 'TS': 2, 'TGID': 91, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [9,10], 'OFF': []},
    ]
}

As you can see I added TG 91 Worldwide to my file for testing. Make sure when you copy paste that each line isn’t justified like my website shows it. It should be each TG is on a single line in your rules.py. My website makes it look like it’s 2 lines but when you copy paste it should be correct, at least from my testing.

Restart HBlink via the GUI and you shouldn’t see any error messages at start up. That’s it! You should be able to key up on TG 91 from your radio 60091 (if you followed my pi star setup) and check the BM hose line to see if you’re getting though. You can also check the BM Devices page and you should see HBlink there as a bridge with your DMR + the two digit suffix you added to the hblink.cfg file.

You may want to play around with the Timeout timers in rules.py to match your needs.

en_USEnglish