There is a typo in the above configuration. In [D-APRS], AX_PEERS should be MAX_PEERS. Other than that, your configuration looks good.

#hblink

Settings on hblink.cfg are: [D-APRS] MODE: MASTER ENABLED: True REPEAT: True AX_PEERS: 2 EXPORT_AMBE: False IP: PORT: 54070 PASSPHRASE: passw0rd GROUP_HANGTIME: 5 USE_ACL: True REG_ACL: DENY:1 SUB_ACL

#hblink

Hi All, I have recently deployed HBLink to provide a common point for my hotspots in my car and at the QTH to connect to instead of running DMRGateway on each unit. I felt that running DMRGateway woul

#talkeralias #hblink

Update: The problem may be caused by xlxd not using a unique stream id per transmission for transmissions sourced via YSF. I've opened an issue with the xlxd developers. https://github.com/LX3JL/xlxd/

I think you need to install an older version of one of the packages jinja2==2.11.3

#admin

Can't get HBmonitor to fly. When I try to start it: 2021-11-18 18:06:55,929 INFO monitor.py starting up 2021-11-18 18:06:55,931 INFO Copyright (c) 2016, 2017, 2018, 2019 The Regents of the K0USY Group

#admin

This is HbmBMonitor. Run it in the foreground! Go to HBMon directory run.. python3 monitor.py and screen shot your errors from the running log. Shane M0VUB

I get this error too, does anyone knows how to fix this? Thanks Eric hbmon.service - HBMonitor Loaded: loaded (/lib/systemd/system/hbmon.service; enabled; vendor preset: enabled) Active: failed (Resul

After implementing xlxd 2.5.0, I observe that HBlink no longer properly logs transmissions from an XLXPEER that originated via YSF. HBlink does still properly log those originating via DMR. Something

Hi, I have been playing around getting AES-256 to pass through HBlink --- I have a Maxon radio that it works fine on. I picked up a radiodity at10 which does aes256 I can talk radio to radio put not t

#hblink

Thanks old eyes missed it Bob KC2CWT Carmel NY 10512 (914) 497-5502

You make it wrong. Make to master section Master 1 connect pi-star hs1 Master 2 connect pi-star hs2 But you no need to masters you can connect booth Pi-Star on Master 1 and privat calls will work too

#mmdvm_bridge #hblink

Im trying, nothing I do seems to work my config--- Two Pi-star hotspots entered as router-1 and 2 [REPEATER-1] MODE: PEER #ENABLED: True ENABLED: True LOOSE: False EXPORT_AMBE: False IP: PORT: 54001 M

#mmdvm_bridge #hblink

Looks like False is spelled wrong

Hello all Looking for some help on the err below . this is on a Raspberry Pi :DMRlink$ sudo python IPSC_Bridge.py Traceback (most recent call last): File "IPSC_Bridge.py", line 252, in <module> CONFIG

No, put in the name(s) of they MASTER or PEER instances where you want private calls to be routed. You'll find these in hblink.cfg, where you define an instance for hotspots to connect to and what hbl

#mmdvm_bridge #hblink

Thanks for the help. What do I put in for UNIT one and two the hotspot IDs?

#mmdvm_bridge #hblink

First, be sure you have the latest commit from https://github.com/HBLink-org/hblink3. You shouldn't need to do a PCRewrite if your Pi-Star will only be connecting to your hblink server. In your hblink

#mmdvm_bridge #hblink

Hi, Im trying to make private calls through my HBlink server, I can't seem to figure it out. Do I need to add a PCRewrite=2,3179044,2,3179047 to my PI-Star? 4 Four radio ids and four hotspots --under

#mmdvm_bridge #hblink

Our primary use of HBlink is to bridge IPSC and HBP. We have 2 Motorola repeaters and a C-bridge connection. Also have a few hotspots and 2 open bridge connections. All of this is tied together with h

#hblink #support #dmrlink