Re: Linking dmrlink and HBlink3 #dmrlink #hblink






From: <> on behalf of Corey Dean N3FE <n3fe@...>
Reply-To: <>
Date: Saturday, November 30, 2019 at 6:22 PM
To: <>
Subject: Re: [DVSwitch] Linking dmrlink and HBlink3 #dmrlink #hblink


They can coexist just fine.  Just do got clone in a different directory and away you go!


Corey n3fe


On Sat, Nov 30, 2019 at 8:30 PM ai6bx via Groups.Io <> wrote:



Thank you for your timely and detailed response. With the links Steve sent, I think I am ready to have a go at it again. That said, I note in your response below that use of TGID and some repeater grouping would be desireable which is the other benefit that has drawn me to your work. Would I still use the or after setting up IPSC? Would best practice be to remove my current installs of DMRlink and HBlink3 before installing the suggested branch versions?


Thank you,




From: <> on behalf of "Cort N0MJS via Groups.Io" <>
Reply-To: <>
Date: Saturday, November 30, 2019 at 4:15 PM
To: "" <>
Subject: Re: [DVSwitch] Linking dmrlink and HBlink3 #dmrlink #hblink


Why not just connect the XPR8300s to the IPSC system with the SLR5700s? By the way, the “master” is inconsequential. The only purpose it serves is bootstrapping a new peer in the IPSC mesh – it doesn’t really matter who plays that role. When systems are meshed, they all operate as “peers” for the purpose of passing traffic. Master is only unique for link establishment. As for the hotspots, there’s no need to use either.


My recommendation is to connect all Motorola repeaters in the same IPSC mesh (system, network – whatever you want to call it), and then use and to connect a single Homebrew server (master) over to the Motorolas. BTW: On the home-brew side, “master” does have significant meaning since the repeaters to not form a mesh like IPSC. All traffic has to traverse a central server, which just happens to be (unfortunately, because it really clouds the issue) a “master”. and are found in the specific branches of DMRlink and HBlink (the original Python2 version) named for those programs. You’ll have to clone and switch the branch, or just clone the branch you want directly. Please don’t be temped to just use the versions of etc. with the “Bridge” branches. They’re based on quite old versions that are missing a lot of updates to other programs, but they are EXTREMELY stable and do the job they need to for protocol bridging quite well.


If you are struggling with how branches and stuff work with GitHub, the Internet us FULL of how-tos and tutorials on the topic.


I’m advising this setup because it appears you’re heavily invested in Motorola IPSC networking already, and the solution I’ve offered provides the most continuity for what you’re used to and already doing with the SLR5700s. There’s no need to run or unless unless you’re wanting to segregated traffic between parts of your system – that is to say, have a TGID available on a group of repeaters not available on another group, etc.


If you reach the point where you have too many machines in a single IPSC mesh and you’re using too much bandwidth (n-1 stream count and all) you could look into in DMRlink, which will transparently break up your IPSC mesh into smaller sub-groups.


0x49 DE N0MJS


On Nov 30, 2019, at 5:57 PM, ai6bx via Groups.Io <ai6bx.keith@...> wrote:




  • Currently I have an SLR5700 functioning as a master hosting six Motorola DMR repeaters. These all live on a public Internet address.
  • I have two Moto XPR8300’s that I want to peer to DMRlink and bridge to the current SLR5700 Master. Ultimately, I wish to transition the six repeaters from the 5700 so they are all on DMR link.
  • I am currently working with one MMDVM hotspot on the HBlink3 side of things with the goal of bridging the two sides together, something I can’t do with the SLR5700. Once working, hotspots will likely grow to about 15 or 20 devices.
  • Down the road the total number of Moto repeaters will grow to about 15.
  • This will be operated on a private network supported by ARDEN mesh networking operating in the 10.x.x.x domain and will have a gateway to the broader Internet via an AMPR.or 44.x.x.x address for hotspot connections when members travel.
  • The system will be migrated to a Debian 9 Blade server once ready for production deployment. I am currently building on a Vultr Debian VM for test and learning purposes.


I hope this helps.




From: <> on behalf of "Cort N0MJS via Groups.Io" <n0mjs@...>
Reply-To: <>
Date: Saturday, November 30, 2019 at 3:39 PM
To: "" <>
Subject: Re: [DVSwitch] Linking dmrlink and HBlink3 #dmrlink #hblink


I need to understand what you’re attempting to do. Please fill in the gaps for me?


You have a number of Motorola repeaters and MMDVM devices. You’re trying to make them all talk together on a private network. You do not have any “upstream” connections to the “big networks” or laterals to other independent networks?


Is that right? The use case changes best practice. Also, which “side” has more devices – the Motorola repeaters or the MMDVM devices? Today? Expected in the future?

On Nov 30, 2019, at 5:13 PM, ai6bx via Groups.Io <ai6bx.keith@...> wrote:



First, my apology as I am still new to the groups here and finding my way through these tools. DVSwitch is clearly a powerful set of programs and bridges that I am certain will do exactly what I am trying to accomplish Once I better understand the relationships between them and some of the pieces that make those links work. I am currently running: and have also tried

Following are my files:

Again, I sincerely appreciate any guidance possible and suspect I am missing something that will be blatantly obvious once pointed out.


Keith <dmrlink.cfg><hblink.cfg><><><dmrlink.log><hblink.log><dmrlink.log>



Cort Buffington

H: +1-785-813-1501

M: +1-785-865-7206






Cort Buffington

H: +1-785-813-1501

M: +1-785-865-7206





Join to automatically receive all group messages.