Randy and all, I have started to get the following errors in my hblink.log. It showed up I bewleive after doing apt updates and upgrades. I have not changed anything in the server since installation.

I'm trying to connect the latest HBLink3 via a PEER connection to HBLink (HB_Bridge). When the PEER logs into HBLink, I get the following error and the login sequence repeats. It appears when HBLink3

It’s most likely BM have changed something there end. Normally password error or if they have reconfigured. If you haven’t touched it in years it’s probably a good idea to do an update/upgrade and may

By itself, we can't help, unless you can offer up your config file to look through. Is this OBP connection with BrandMeister? If so, a ticket with them to confirm that nothing has changed on their sid

I have had HBlink3 running for years now with now difficulty. I just noticed that the log file is blowing up and when I review I see strings of (3103-OB) OpenBridge HMAC failed, packet discarded - OPC

This is the way I have done ours. HBLink is DMR so you could use YSF2DMR to link YSFReflector to HBLink. XLX uses DMR natively as well so add it as a peer in HBLink (add rules for TG9 for your XLX pee

Folks, A year ago I had played around with setting up a YSF reflector, before I knew the advantages of the multi-mode xlx reflector, so consequently I have YSF reflector 75749 that does appear to work

Hi i install hblink3 on my local server and working good same in link https://github.com/lz5pn/HBlink3 just change Master port to 62030 and password to passw0rd . but my problem is when i want to add

#web

Yes. That’s exactly what you do. On my HBLink each user has a master. Their hotspot connects to their master. I route Talkgroups that each User wants via the rules.py file. That’s how you do it. It’s

#hblink #support

The original poster wanted to run an hblink master with TG1 and TG2 but have them not talk to each other. As best as I can figure that is an impossibility as all master traffic goes to all radios no m

#hblink #support

I think we are saying the same thing. I get so many emails. What is someone trying to do? :)

#hblink #support

Ok so in repeater terms there is a repeater with a frequency of 441.5 and a ctcss of 67 ENC and DEC radio one has both enc and dec set to 67 so it can talk and hear radio two has dec set but not enc s

#hblink #support

Think of HBLINK Masters as a “virtual repeater” as with any local repeater if someone is on it someone else on it “shares” the same traffic. Hope that helps someone. Doug W4DBG

#hblink #support

Also i have found for some reason 2 radios connected to the same hotspot hear each others traffic no matter the TG but only the one using the correct TG can speak..

#hblink #support

Ok Im not sure if this will help anyone but as far as I can tell I got mine to work like I wanted. on hblink config create a main with a different name, and port for each desired channel eg below this

#hblink #support

I'm going to augment the link to the current xlxd version info with lines 50 to 52 of the main program here: https://github.com/LX3JL/xlxd/blob/master/src/main.h #define VERSION_MAJOR 2 #define VERSIO

XLX094 seems to be running a non-released version of the XLX server - XLX v2.4.31, latest version is 2.4.1 per line 20 of the source code in this link to the xlxd source on GitHub: https://github.com/

So if I’m understanding you right, I should only need the two DVstick 30s, and configure them to work with the xlx reflector, and the vocoders will make it so that d-star will talk to the other modes?

For XLX575, rather than a big cloud provider, I went with a local ISP company that provides RF internet service in semi-rural areas of New Mexico. They were already running the reflector for the local

Hi Justin, Wow, there's a lot going on there. I don't suppose you've gone through the trouble to diagram this in order to see where the voice traffic flows? Something like this perhaps. You might cons