Date   

Re: Linking dmrlink and HBlink3 #dmrlink #hblink

ai6bx
 

Steve,

 

Thank you for these links. Perhaps this is a stupid question however since I already have DMRlink installed via mk- should I just copy the IPSC files over or clone this entire directory and run mk- again? Also, should I remove HBlink3 and utilize this version or install this package in addition to HBlink3?

 

Thank you,

 

From: <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Organization: msgstor.com
Reply-To: <main@DVSwitch.groups.io>
Date: Saturday, November 30, 2019 at 4:10 PM
To: <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Linking dmrlink and HBlink3 #dmrlink #hblink

 

<https://github.com/n0mjs710/DMRlink/tree/IPSC_Bridge>
<https://github.com/n0mjs710/HBlink/tree/HB_Bridge>

On 11/30/19 6:59 PM, ai6bx via Groups.Io wrote:

Cort,

 

Note I do not see the IPSC_bridge.py in any of my current installed directories. Is this something installed independent of DMRlink?

 

Keith

 

From: <main@DVSwitch.groups.io> on behalf of "Cort N0MJS via Groups.Io" <n0mjs@...>
Reply-To: <main@DVSwitch.groups.io>
Date: Saturday, November 30, 2019 at 3:39 PM
To: "main@dvswitch.groups.io" <main@DVSwitch.groups.io>
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:

 

Cort,

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:
Confbridge.py
Bridge.py and have also tried bridge_all.py

Following are my files:
Rules:
Logs:

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

Sincerely,

Keith <dmrlink.cfg><hblink.cfg><confbridge_rules.py><rules.py><dmrlink.log><hblink.log><dmrlink.log>

 

--

Cort Buffington

H: +1-785-813-1501

M: +1-785-865-7206

 




 

 

 


Re: Linking dmrlink and HBlink3 #dmrlink #hblink

Cort N0MJS <n0mjs@...>
 

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 bridge.py 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 IPSC_Bridge.py and HB_Bridge.py 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”.

IPSC_Bridge.py and HB_Bridge.py 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 confbridge.py 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 confbridge.py or bridge.py 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 proxy.py 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:

Cort,
 
  • 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.
 
Keith
 
From: <main@DVSwitch.groups.io> on behalf of "Cort N0MJS via Groups.Io" <n0mjs@...>
Reply-To: <main@DVSwitch.groups.io>
Date: Saturday, November 30, 2019 at 3:39 PM
To: "main@dvswitch.groups.io" <main@DVSwitch.groups.io>
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:
 
Cort,

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:
Confbridge.py
Bridge.py and have also tried bridge_all.py

Following are my files:
Rules:
Logs:

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

Sincerely,

Keith <dmrlink.cfg><hblink.cfg><confbridge_rules.py><rules.py><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






Re: Linking dmrlink and HBlink3 #dmrlink #hblink

Steve N4IRS
 

On 11/30/19 6:59 PM, ai6bx via Groups.Io wrote:

Cort,

 

Note I do not see the IPSC_bridge.py in any of my current installed directories. Is this something installed independent of DMRlink?

 

Keith

 

From: <main@DVSwitch.groups.io> on behalf of "Cort N0MJS via Groups.Io" <n0mjs@...>
Reply-To: <main@DVSwitch.groups.io>
Date: Saturday, November 30, 2019 at 3:39 PM
To: "main@dvswitch.groups.io" <main@DVSwitch.groups.io>
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:

 

Cort,

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:
Confbridge.py
Bridge.py and have also tried bridge_all.py

Following are my files:
Rules:
Logs:

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

Sincerely,

Keith <dmrlink.cfg><hblink.cfg><confbridge_rules.py><rules.py><dmrlink.log><hblink.log><dmrlink.log>

 

--

Cort Buffington

H: +1-785-813-1501

M: +1-785-865-7206

 



 

 



Re: Linking dmrlink and HBlink3 #dmrlink #hblink

ai6bx
 

Cort,

 

Note I do not see the IPSC_bridge.py in any of my current installed directories. Is this something installed independent of DMRlink?

 

Keith

 

From: <main@DVSwitch.groups.io> on behalf of "Cort N0MJS via Groups.Io" <n0mjs@...>
Reply-To: <main@DVSwitch.groups.io>
Date: Saturday, November 30, 2019 at 3:39 PM
To: "main@dvswitch.groups.io" <main@DVSwitch.groups.io>
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:

 

Cort,

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:
Confbridge.py
Bridge.py and have also tried bridge_all.py

Following are my files:
Rules:
Logs:

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

Sincerely,

Keith <dmrlink.cfg><hblink.cfg><confbridge_rules.py><rules.py><dmrlink.log><hblink.log><dmrlink.log>

 

--

Cort Buffington

H: +1-785-813-1501

M: +1-785-865-7206

 



 

 


Re: Linking dmrlink and HBlink3 #dmrlink #hblink

ai6bx
 

Cort,

 

  • 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.

 

Keith

 

From: <main@DVSwitch.groups.io> on behalf of "Cort N0MJS via Groups.Io" <n0mjs@...>
Reply-To: <main@DVSwitch.groups.io>
Date: Saturday, November 30, 2019 at 3:39 PM
To: "main@dvswitch.groups.io" <main@DVSwitch.groups.io>
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:

 

Cort,

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:
Confbridge.py
Bridge.py and have also tried bridge_all.py

Following are my files:
Rules:
Logs:

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

Sincerely,

Keith <dmrlink.cfg><hblink.cfg><confbridge_rules.py><rules.py><dmrlink.log><hblink.log><dmrlink.log>

 

--

Cort Buffington

H: +1-785-813-1501

M: +1-785-865-7206

 



 

 


Re: Linking dmrlink and HBlink3 #dmrlink #hblink

Cort N0MJS <n0mjs@...>
 

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:

Cort,

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:
Confbridge.py
Bridge.py and have also tried bridge_all.py

Following are my files:
Rules:
Logs:

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

Sincerely,

Keith <dmrlink.cfg><hblink.cfg><confbridge_rules.py><rules.py><dmrlink.log><hblink.log><dmrlink.log>

--
Cort Buffington
H: +1-785-813-1501
M: +1-785-865-7206






Re: Linking dmrlink and HBlink3 #dmrlink #hblink

ai6bx
 

Cort,

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:
Confbridge.py
Bridge.py and have also tried bridge_all.py

Following are my files:
Rules:
Logs:

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

Sincerely,

Keith


Re: Brandmeister to XLX

Steve N4IRS
 

You are going to do your cross connect in DVSwitch.ini

Sent by smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Saturday, November 30, 2019 5:21:54 PM
To: main@dvswitch.groups.io <main@dvswitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 
Oh yes, I forgot to mention that the MMDVM_Bridge is in its own directory with different rx and tx ports in DVSwitch.ini to avoid conflict with the existing bridge.


On Nov 30, 2019, at 16:49, Steve N4IRS <szingman@...> wrote:


See Ernie's reply AND since you are running 2 copies of MB, change the local post on one of them

Sent by smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Saturday, November 30, 2019 4:37:24 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

I downloaded the latest MMDVM_Bridge earlier today. My current issue is getting MMDVM-Bridge connected to XLXD on the same machine. I'm sure I've directly connected a hotspot to the reflector before, but that was a while ago.

The relevant part of MMDVM_Bridge.ini looks like this:


[DMR Network]
Enable=1
Address=127.0.0.1
Port=62030
Jitter=360
Local=62031
Password=passw0rd
Options=XLX:4002
Slot1=0
Slot2=1
Debug=0


Small part of the MMDVM_Bridge log:

E: 2019-11-30 21:34:28.884 DMR, Connection to the master has timed out, retrying connection

tcpdump shows active connections on UDP 62030, so XLXD should be accepting the connection from MMDVM_Bridge on that port.


On 11/30/2019 4:20 PM, Ernie Gm7kbk wrote:
latest version of MMDVM_bridge works with no problems. Use the options XLX:4005 this being the module you want to connect to. 4001 for A 4002 for B etc. latest version is here https://github.com/DVSwitch/MMDVM_Bridge


Re: Brandmeister to XLX

Steve N4IRS
 

The network address should point at the xlx reflector

Sent by smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Saturday, November 30, 2019 5:18:50 PM
To: main@dvswitch.groups.io <main@dvswitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 
That was actually the first configuration I tried. Same result either with the Interface IP address, or local loopback. I’ll mess with it some more later. The MMDVM_Bridge part looks easy enough once I can get it talking to XLXD.


On Nov 30, 2019, at 16:39, Ernie Gm7kbk <erniepratt@...> wrote:


Use the ip address  of the machine not 127.0.0.1


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Saturday, November 30, 2019 9:37:24 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

I downloaded the latest MMDVM_Bridge earlier today. My current issue is getting MMDVM-Bridge connected to XLXD on the same machine. I'm sure I've directly connected a hotspot to the reflector before, but that was a while ago.

The relevant part of MMDVM_Bridge.ini looks like this:


[DMR Network]
Enable=1
Address=127.0.0.1
Port=62030
Jitter=360
Local=62031
Password=passw0rd
Options=XLX:4002
Slot1=0
Slot2=1
Debug=0


Small part of the MMDVM_Bridge log:

E: 2019-11-30 21:34:28.884 DMR, Connection to the master has timed out, retrying connection

tcpdump shows active connections on UDP 62030, so XLXD should be accepting the connection from MMDVM_Bridge on that port.


On 11/30/2019 4:20 PM, Ernie Gm7kbk wrote:
latest version of MMDVM_bridge works with no problems. Use the options XLX:4005 this being the module you want to connect to. 4001 for A 4002 for B etc. latest version is here https://github.com/DVSwitch/MMDVM_Bridge


Re: Brandmeister to XLX

Patrick Perdue
 

Oh yes, I forgot to mention that the MMDVM_Bridge is in its own directory with different rx and tx ports in DVSwitch.ini to avoid conflict with the existing bridge.


On Nov 30, 2019, at 16:49, Steve N4IRS <szingman@...> wrote:


See Ernie's reply AND since you are running 2 copies of MB, change the local post on one of them

Sent by smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Saturday, November 30, 2019 4:37:24 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

I downloaded the latest MMDVM_Bridge earlier today. My current issue is getting MMDVM-Bridge connected to XLXD on the same machine. I'm sure I've directly connected a hotspot to the reflector before, but that was a while ago.

The relevant part of MMDVM_Bridge.ini looks like this:


[DMR Network]
Enable=1
Address=127.0.0.1
Port=62030
Jitter=360
Local=62031
Password=passw0rd
Options=XLX:4002
Slot1=0
Slot2=1
Debug=0


Small part of the MMDVM_Bridge log:

E: 2019-11-30 21:34:28.884 DMR, Connection to the master has timed out, retrying connection

tcpdump shows active connections on UDP 62030, so XLXD should be accepting the connection from MMDVM_Bridge on that port.


On 11/30/2019 4:20 PM, Ernie Gm7kbk wrote:
latest version of MMDVM_bridge works with no problems. Use the options XLX:4005 this being the module you want to connect to. 4001 for A 4002 for B etc. latest version is here https://github.com/DVSwitch/MMDVM_Bridge


Re: Brandmeister to XLX

Patrick Perdue
 

That was actually the first configuration I tried. Same result either with the Interface IP address, or local loopback. I’ll mess with it some more later. The MMDVM_Bridge part looks easy enough once I can get it talking to XLXD.


On Nov 30, 2019, at 16:39, Ernie Gm7kbk <erniepratt@...> wrote:


Use the ip address  of the machine not 127.0.0.1


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Saturday, November 30, 2019 9:37:24 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

I downloaded the latest MMDVM_Bridge earlier today. My current issue is getting MMDVM-Bridge connected to XLXD on the same machine. I'm sure I've directly connected a hotspot to the reflector before, but that was a while ago.

The relevant part of MMDVM_Bridge.ini looks like this:


[DMR Network]
Enable=1
Address=127.0.0.1
Port=62030
Jitter=360
Local=62031
Password=passw0rd
Options=XLX:4002
Slot1=0
Slot2=1
Debug=0


Small part of the MMDVM_Bridge log:

E: 2019-11-30 21:34:28.884 DMR, Connection to the master has timed out, retrying connection

tcpdump shows active connections on UDP 62030, so XLXD should be accepting the connection from MMDVM_Bridge on that port.


On 11/30/2019 4:20 PM, Ernie Gm7kbk wrote:
latest version of MMDVM_bridge works with no problems. Use the options XLX:4005 this being the module you want to connect to. 4001 for A 4002 for B etc. latest version is here https://github.com/DVSwitch/MMDVM_Bridge


Re: Brandmeister to XLX

Steve N4IRS
 

See Ernie's reply AND since you are running 2 copies of MB, change the local post on one of them

Sent by smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Saturday, November 30, 2019 4:37:24 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

I downloaded the latest MMDVM_Bridge earlier today. My current issue is getting MMDVM-Bridge connected to XLXD on the same machine. I'm sure I've directly connected a hotspot to the reflector before, but that was a while ago.

The relevant part of MMDVM_Bridge.ini looks like this:


[DMR Network]
Enable=1
Address=127.0.0.1
Port=62030
Jitter=360
Local=62031
Password=passw0rd
Options=XLX:4002
Slot1=0
Slot2=1
Debug=0


Small part of the MMDVM_Bridge log:

E: 2019-11-30 21:34:28.884 DMR, Connection to the master has timed out, retrying connection

tcpdump shows active connections on UDP 62030, so XLXD should be accepting the connection from MMDVM_Bridge on that port.


On 11/30/2019 4:20 PM, Ernie Gm7kbk wrote:
latest version of MMDVM_bridge works with no problems. Use the options XLX:4005 this being the module you want to connect to. 4001 for A 4002 for B etc. latest version is here https://github.com/DVSwitch/MMDVM_Bridge


Re: Brandmeister to XLX

 

Use the ip address  of the machine not 127.0.0.1


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Saturday, November 30, 2019 9:37:24 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

I downloaded the latest MMDVM_Bridge earlier today. My current issue is getting MMDVM-Bridge connected to XLXD on the same machine. I'm sure I've directly connected a hotspot to the reflector before, but that was a while ago.

The relevant part of MMDVM_Bridge.ini looks like this:


[DMR Network]
Enable=1
Address=127.0.0.1
Port=62030
Jitter=360
Local=62031
Password=passw0rd
Options=XLX:4002
Slot1=0
Slot2=1
Debug=0


Small part of the MMDVM_Bridge log:

E: 2019-11-30 21:34:28.884 DMR, Connection to the master has timed out, retrying connection

tcpdump shows active connections on UDP 62030, so XLXD should be accepting the connection from MMDVM_Bridge on that port.


On 11/30/2019 4:20 PM, Ernie Gm7kbk wrote:
latest version of MMDVM_bridge works with no problems. Use the options XLX:4005 this being the module you want to connect to. 4001 for A 4002 for B etc. latest version is here https://github.com/DVSwitch/MMDVM_Bridge


Re: Brandmeister to XLX

Patrick Perdue
 

I downloaded the latest MMDVM_Bridge earlier today. My current issue is getting MMDVM-Bridge connected to XLXD on the same machine. I'm sure I've directly connected a hotspot to the reflector before, but that was a while ago.

The relevant part of MMDVM_Bridge.ini looks like this:


[DMR Network]
Enable=1
Address=127.0.0.1
Port=62030
Jitter=360
Local=62031
Password=passw0rd
Options=XLX:4002
Slot1=0
Slot2=1
Debug=0


Small part of the MMDVM_Bridge log:

E: 2019-11-30 21:34:28.884 DMR, Connection to the master has timed out, retrying connection

tcpdump shows active connections on UDP 62030, so XLXD should be accepting the connection from MMDVM_Bridge on that port.


On 11/30/2019 4:20 PM, Ernie Gm7kbk wrote:
latest version of MMDVM_bridge works with no problems. Use the options XLX:4005 this being the module you want to connect to. 4001 for A 4002 for B etc. latest version is here https://github.com/DVSwitch/MMDVM_Bridge


Re: Brandmeister to XLX

 

latest version of MMDVM_bridge works with no problems. Use the options XLX:4005 this being the module you want to connect to. 4001 for A 4002 for B etc. latest version is here https://github.com/DVSwitch/MMDVM_Bridge


Re: Brandmeister to XLX

Patrick Perdue
 

OK.

I just tried setting up an instance of MMDVM_Bridge to point to 127.0.0.1 on port 62030 (MMDVM) using the DMRNetwork. I thought XLXD responded to that, but apparently it doesn't, as the connection timed out.


On 11/30/2019 2:57 PM, Steve KC1AWV wrote:
DMRGateway is not required. I have made a note in my old doc that reflects this. I will be creating a new doc that should be available after the holidays.

Steve KC1AWV 

On Sat, Nov 30, 2019, 2:55 PM Patrick Perdue <patrick@...> wrote:
Hello:

I found an old docc referring to using two instances of MMDVM_Bridge and
DMRGateway to bridge DMR to XLX. Is this necessary anymore, or can we
now just use two instances of MMDVM_Bridge, since it seems you can now
specifically address XLX modules? I want to use XLX and ambed for
transcoding DMR to D-STAR (DCS via XLXD) since this is already in place,
and bridge between that and Brandmeister.





Re: Linking dmrlink and HBlink3 #dmrlink #hblink

Cort N0MJS <n0mjs@...>
 

PLEASE TAKE NOTICE:

We have asked this many time. If you intend to ask for help, the following are absolutely mandatory. The people who write the software will not supply help if you do not:

* Include the explicit names of the programs you’re running and how they’re connected. This isn’t “HBlink3” it’s probably bridge.py, probably not DMRlink, but IPSC_Bridge.py
* Include copied of configuration files, rule files, etc. The files, or the text NO SCREENSHOTS
* Include any pertinent, tracebacks (errors) and/or log files
* NO SCREENSHOTS

From this moment on, I will not offer or even respond to requests for help if these things are not included. Period.

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

I have DMRlink configured and running with a bridge to a Motorola master as well as two peer moto DMR machines linked to a master instance I have built within DMRlink. I also have HBlink3 installed with a master for my hotspot. This seems to be running as well with no errors. As I have no interest at this point in linking to Brandmeister, I have not built an OpenBridge or built out the Repeater-1 profile so both are set to false. I can see my hotspot keying and can also see activity in the logfiles for DMRlink. What I am not seeing is traffic passing between the two. It feels like I am missing a stanza in the .cfg files or a bridge activating somewhere. 

Any pointers would be appreciated.

--
Cort Buffington
H: +1-785-813-1501
M: +1-785-865-7206






Linking dmrlink and HBlink3 #dmrlink #hblink

ai6bx
 

I have DMRlink configured and running with a bridge to a Motorola master as well as two peer moto DMR machines linked to a master instance I have built within DMRlink. I also have HBlink3 installed with a master for my hotspot. This seems to be running as well with no errors. As I have no interest at this point in linking to Brandmeister, I have not built an OpenBridge or built out the Repeater-1 profile so both are set to false. I can see my hotspot keying and can also see activity in the logfiles for DMRlink. What I am not seeing is traffic passing between the two. It feels like I am missing a stanza in the .cfg files or a bridge activating somewhere. 

Any pointers would be appreciated.


Re: mmdvmb.service in amd64?

Tom Corcoran
 

Dropped full path and now all is working as intended. Cloud instance of DVS supporting YSF, P25 and DMR (BM, TGIF and QRM).

tnx for help .-- Tom VE3NY


Re: Brandmeister to XLX

Steve KC1AWV
 

DMRGateway is not required. I have made a note in my old doc that reflects this. I will be creating a new doc that should be available after the holidays.

Steve KC1AWV 

On Sat, Nov 30, 2019, 2:55 PM Patrick Perdue <patrick@...> wrote:
Hello:

I found an old docc referring to using two instances of MMDVM_Bridge and
DMRGateway to bridge DMR to XLX. Is this necessary anymore, or can we
now just use two instances of MMDVM_Bridge, since it seems you can now
specifically address XLX modules? I want to use XLX and ambed for
transcoding DMR to D-STAR (DCS via XLXD) since this is already in place,
and bridge between that and Brandmeister.




4161 - 4180 of 9520