Date   

Re: Linking dmrlink and HBlink3 #dmrlink #hblink

Cort N0MJS <n0mjs@...>
 

You should only be defining one system on the dmrlink.cfg used with IPSC_Bridge.py. It’s intended to be a one-off. There is no call forwarding between systems. If you intend to use multiple IPSC Systems, you will need a pair of IPSC_Bridge.py and HB_Bridge.py for each. I explained this previously.

Address already in use is a SOCKET address, not an IP ADDRESS. Socket address is defined as the tuple of IP Address, Protocol, Port. You already have something listening on UDP port 62059. Only one process may bind to a specific socket address.


On Dec 1, 2019, at 10:52 AM, ai6bx via Groups.Io <ai6bx.keith@...> wrote:

Doh. Yep, I bridge.py now. I am starting small to get at least one bridge working and will replicate from there once success is achieved. I am building the Moto stanzas in dmrlink.cfg as follows and then launching IPSC_Bridge.py to look for errors. Regardless of the port number I use in IPSC_Bridge.cfg, I get an error indicating it is already in use which is pretty odd, at least to me. Logic would tell me to leave the default IP alone as both systems home on the same machine. Am I missing something?
 
Dmrlink.cfg
[RIFF_PEER]
ENABLED: True
RADIO_ID: 92374
IP:
PORT: 50001
ALIVE_TIMER: 5
MAX_MISSED: 20
PEER_OPER: True
IPSC_MODE: DIGITAL
TS1_LINK: True
TS2_LINK: True
CSBK_CALL: False
RCM: False
CON_APP: False
XNL_CALL: False
XNL_MASTER: False
DATA_CALL: True
VOICE_CALL: True
MASTER_PEER: False
AUTH_ENABLED: True
AUTH_KEY: AD07911
MASTER_IP: 47.180.30.199
MASTER_PORT: 7000
GROUP_HANGTIME: 5
 
[CARLSBAD]
ENABLED: True
RADIO_ID: 734566
IP:
PORT: 62042
ALIVE_TIMER: 5
MAX_MISSED: 20
PEER_OPER: True
IPSC_MODE: DIGITAL
TS1_LINK: True
TS2_LINK: True
CSBK_CALL: False
RCM: False
CON_APP: False
XNL_CALL: False
XNL_MASTER: False
DATA_CALL: True
VOICE_CALL: True
MASTER_PEER: True
AUTH_ENABLED: True
AUTH_KEY: AD07911
# Below not used for a Master
# MASTER_IP: 1.2.3.4
# MASTER_PORT: 50000
GROUP_HANGTIME: 5
 
[IBEX]
ENABLED: True
RADIO_ID: 734379
IP:
PORT: 62055
ALIVE_TIMER: 5
MAX_MISSED: 20
PEER_OPER: True
IPSC_MODE: DIGITAL
TS1_LINK: True
TS2_LINK: True
CSBK_CALL: False
RCM: False
CON_APP: False
XNL_CALL: False
XNL_MASTER: False
DATA_CALL: True
VOICE_CALL: True
MASTER_PEER: True
AUTH_ENABLED: True
AUTH_KEY: AD07911
# Below not used for a Master
# MASTER_IP: 1.2.3.4
# MASTER_PORT: 50000
GROUP_HANGTIME: 5
 
IPSC_Bridge.py output
 
root@AI6BX-DMR:/opt/DMRlink# python IPSC_Bridge.py
INFO 2019-12-01 16:51:32,087 DMRlink 'IPSC_Bridge.py' (c) 2015 N0MJS & the K0USY Group - SYSTEM STARTING...
INFO 2019-12-01 16:51:32,087 Version 20170620
INFO 2019-12-01 16:51:32,088 ID ALIAS MAPPER: 'peer_ids.json' is current, not downloaded
INFO 2019-12-01 16:51:32,088 ID ALIAS MAPPER: 'subscriber_ids.json' is current, not downloaded
INFO 2019-12-01 16:51:32,240 ID ALIAS MAPPER: peer_ids dictionary is available
INFO 2019-12-01 16:51:34,477 ID ALIAS MAPPER: subscriber_ids dictionary is available
INFO 2019-12-01 16:51:34,481 (RIFF_PEER) IPSC Instance Created: 92374, 0.0.0.0:50001
INFO 2019-12-01 16:51:34,482 section = RIFF_PEER
INFO 2019-12-01 16:51:34,482 Section RIFF_PEER was not found, using DEFAULTS
INFO 2019-12-01 16:51:34,482 gateway = 127.0.0.1
INFO 2019-12-01 16:51:34,483 toGatewayPort = 31003
INFO 2019-12-01 16:51:34,483 fromGatewayPort = 62059
INFO 2019-12-01 16:51:34,483 DMRLink IPSC Bridge
INFO 2019-12-01 16:51:34,487 (RIFF_PEER) Registering with the Master: 47.180.30.199:7000
INFO 2019-12-01 16:51:34,488 (IBEX) IPSC Instance Created: 734379, 0.0.0.0:62055
INFO 2019-12-01 16:51:34,488 section = IBEX
INFO 2019-12-01 16:51:34,489 Section IBEX was not found, using DEFAULTS
INFO 2019-12-01 16:51:34,489 gateway = 127.0.0.1
INFO 2019-12-01 16:51:34,489 toGatewayPort = 31003
INFO 2019-12-01 16:51:34,489 fromGatewayPort = 62059
INFO 2019-12-01 16:51:34,489 DMRLink IPSC Bridge
Traceback (most recent call last):
  File "IPSC_Bridge.py", line 308, in <module>
    systems[system] = ambeIPSC(system, CONFIG, logger, report_server)
  File "IPSC_Bridge.py", line 96, in __init__
    self.ipsc_ambe = AMBE_IPSC(self, _name, _config, _logger, self._ambeRxPort)
  File "/usr/local/lib/python2.7/dist-packages/dmr_utils/ambe_bridge.py", line 525, in __init__
    AMBE_BASE.__init__(self, _parent, _name, _config, _logger, _port)
  File "/usr/local/lib/python2.7/dist-packages/dmr_utils/ambe_bridge.py", line 187, in __init__
    self.udp_port = reactor.listenUDP(self._ambeRxPort, UDP_IMPORT(self.import_datagramReceived))
  File "/usr/lib/python2.7/dist-packages/twisted/internet/posixbase.py", line 369, in listenUDP
    p.startListening()
  File "/usr/lib/python2.7/dist-packages/twisted/internet/udp.py", line 178, in startListening
    self._bindSocket()
  File "/usr/lib/python2.7/dist-packages/twisted/internet/udp.py", line 198, in _bindSocket
    raise error.CannotListenError(self.interface, self.port, le)
twisted.internet.error.CannotListenError: Couldn't listen on any:62059: [Errno 98] Address already in use.
root@AI6BX-DMR:/opt/DMRlink#
 


Re: Linking dmrlink and HBlink3 #dmrlink #hblink

ai6bx
 

Doh. Yep, I bridge.py now. I am starting small to get at least one bridge working and will replicate from there once success is achieved. I am building the Moto stanzas in dmrlink.cfg as follows and then launching IPSC_Bridge.py to look for errors. Regardless of the port number I use in IPSC_Bridge.cfg, I get an error indicating it is already in use which is pretty odd, at least to me. Logic would tell me to leave the default IP alone as both systems home on the same machine. Am I missing something?

 

Dmrlink.cfg

[RIFF_PEER]

ENABLED: True

RADIO_ID: 92374

IP:

PORT: 50001

ALIVE_TIMER: 5

MAX_MISSED: 20

PEER_OPER: True

IPSC_MODE: DIGITAL

TS1_LINK: True

TS2_LINK: True

CSBK_CALL: False

RCM: False

CON_APP: False

XNL_CALL: False

XNL_MASTER: False

DATA_CALL: True

VOICE_CALL: True

MASTER_PEER: False

AUTH_ENABLED: True

AUTH_KEY: AD07911

MASTER_IP: 47.180.30.199

MASTER_PORT: 7000

GROUP_HANGTIME: 5

 

[CARLSBAD]

ENABLED: True

RADIO_ID: 734566

IP:

PORT: 62042

ALIVE_TIMER: 5

MAX_MISSED: 20

PEER_OPER: True

IPSC_MODE: DIGITAL

TS1_LINK: True

TS2_LINK: True

CSBK_CALL: False

RCM: False

CON_APP: False

XNL_CALL: False

XNL_MASTER: False

DATA_CALL: True

VOICE_CALL: True

MASTER_PEER: True

AUTH_ENABLED: True

AUTH_KEY: AD07911

# Below not used for a Master

# MASTER_IP: 1.2.3.4

# MASTER_PORT: 50000

GROUP_HANGTIME: 5

 

[IBEX]

ENABLED: True

RADIO_ID: 734379

IP:

PORT: 62055

ALIVE_TIMER: 5

MAX_MISSED: 20

PEER_OPER: True

IPSC_MODE: DIGITAL

TS1_LINK: True

TS2_LINK: True

CSBK_CALL: False

RCM: False

CON_APP: False

XNL_CALL: False

XNL_MASTER: False

DATA_CALL: True

VOICE_CALL: True

MASTER_PEER: True

AUTH_ENABLED: True

AUTH_KEY: AD07911

# Below not used for a Master

# MASTER_IP: 1.2.3.4

# MASTER_PORT: 50000

GROUP_HANGTIME: 5

 

IPSC_Bridge.py output

 

root@AI6BX-DMR:/opt/DMRlink# python IPSC_Bridge.py

INFO 2019-12-01 16:51:32,087 DMRlink 'IPSC_Bridge.py' (c) 2015 N0MJS & the K0USY Group - SYSTEM STARTING...

INFO 2019-12-01 16:51:32,087 Version 20170620

INFO 2019-12-01 16:51:32,088 ID ALIAS MAPPER: 'peer_ids.json' is current, not downloaded

INFO 2019-12-01 16:51:32,088 ID ALIAS MAPPER: 'subscriber_ids.json' is current, not downloaded

INFO 2019-12-01 16:51:32,240 ID ALIAS MAPPER: peer_ids dictionary is available

INFO 2019-12-01 16:51:34,477 ID ALIAS MAPPER: subscriber_ids dictionary is available

INFO 2019-12-01 16:51:34,481 (RIFF_PEER) IPSC Instance Created: 92374, 0.0.0.0:50001

INFO 2019-12-01 16:51:34,482 section = RIFF_PEER

INFO 2019-12-01 16:51:34,482 Section RIFF_PEER was not found, using DEFAULTS

INFO 2019-12-01 16:51:34,482 gateway = 127.0.0.1

INFO 2019-12-01 16:51:34,483 toGatewayPort = 31003

INFO 2019-12-01 16:51:34,483 fromGatewayPort = 62059

INFO 2019-12-01 16:51:34,483 DMRLink IPSC Bridge

INFO 2019-12-01 16:51:34,487 (RIFF_PEER) Registering with the Master: 47.180.30.199:7000

INFO 2019-12-01 16:51:34,488 (IBEX) IPSC Instance Created: 734379, 0.0.0.0:62055

INFO 2019-12-01 16:51:34,488 section = IBEX

INFO 2019-12-01 16:51:34,489 Section IBEX was not found, using DEFAULTS

INFO 2019-12-01 16:51:34,489 gateway = 127.0.0.1

INFO 2019-12-01 16:51:34,489 toGatewayPort = 31003

INFO 2019-12-01 16:51:34,489 fromGatewayPort = 62059

INFO 2019-12-01 16:51:34,489 DMRLink IPSC Bridge

Traceback (most recent call last):

  File "IPSC_Bridge.py", line 308, in <module>

    systems[system] = ambeIPSC(system, CONFIG, logger, report_server)

  File "IPSC_Bridge.py", line 96, in __init__

    self.ipsc_ambe = AMBE_IPSC(self, _name, _config, _logger, self._ambeRxPort)

  File "/usr/local/lib/python2.7/dist-packages/dmr_utils/ambe_bridge.py", line 525, in __init__

    AMBE_BASE.__init__(self, _parent, _name, _config, _logger, _port)

  File "/usr/local/lib/python2.7/dist-packages/dmr_utils/ambe_bridge.py", line 187, in __init__

    self.udp_port = reactor.listenUDP(self._ambeRxPort, UDP_IMPORT(self.import_datagramReceived))

  File "/usr/lib/python2.7/dist-packages/twisted/internet/posixbase.py", line 369, in listenUDP

    p.startListening()

  File "/usr/lib/python2.7/dist-packages/twisted/internet/udp.py", line 178, in startListening

    self._bindSocket()

  File "/usr/lib/python2.7/dist-packages/twisted/internet/udp.py", line 198, in _bindSocket

    raise error.CannotListenError(self.interface, self.port, le)

twisted.internet.error.CannotListenError: Couldn't listen on any:62059: [Errno 98] Address already in use.

root@AI6BX-DMR:/opt/DMRlink#

 

From: <main@DVSwitch.groups.io> on behalf of "Cort N0MJS via Groups.Io" <n0mjs@...>
Reply-To: <main@DVSwitch.groups.io>
Date: Sunday, December 1, 2019 at 6:54 AM
To: "main@dvswitch.groups.io" <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Linking dmrlink and HBlink3 #dmrlink #hblink

 

 



On Dec 1, 2019, at 2:46 AM, ai6bx via Groups.Io <ai6bx.keith@...> wrote:

 

Cort,

 

I am not seeing bridge.py in my installs. I do have hb_bridge.py and hb_bridge_all.py. Are these interchangeable?

 

bridge.py is part of hblink3 – the Python 3 version of HBlink.

 

HB_Bridge.py and hb_bridge_all.py are completely different programs with completely different uses.



With IPSC_Bridge.py I am getting the following errors at start up. 

 

twisted.internet.error.CannotListenError: Couldn't listen on any:31000: [Errno 98] Address already in use.

 

 

“Address already in use” Something else on your system is already listening on UDP port 31000.

 



 

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 6:31 PM
To: "main@dvswitch.groups.io" <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Linking dmrlink and HBlink3 #dmrlink #hblink

 

Keith,

 

You’re really going to have to think about your project goals and make a decision. I have run systems with confbridge.py running on one side and bridge.py on the other… There are a LOT of things that can get you in trouble. You’ll have to remember, you’re essentially running two separate multi-system “networks” that are cross-connected to each other.

 

If at all possible, I’d recommend handling all of your call routing in bridge.py and translating the Motorolas into home-brew. Why this way and not the other? I’ve sunset development on DMRlink – mostly because I don’t even have a Motorola repeater anymore and I need at least 2 to really do any development work with it. Time is another reason. But I also see home-brew protocol and MMDVM as the future of digital ham radio… for me at least, and since I’m not getting paid for this, I’ll be following the beat of my own drum :)

 

Because you’re so Motorola heavy, you should consider running the call routing in confbridge.py on the IPSC side and bring your MMDVMs in as the afterthought. Just remember that there will be no new development on DMRlink unless someone else does it. It is what it is.

 

For the KS-DMR network, when someone shows up with a Motorola repeater, we deploy an IPSC_Bridge.py and HB_bridge.py combo for each one. The idea is simply convert the Motorola to speak home-brew as fast and as close to the source as possible. Often times this is a small single board computer – usually with “Pi” in the name somewhere – right with the repeater itself. Other times, for folks who want to be a part of it it just can’t handle (or just don’t want to) running those services we provide them on our infrastructure.

 

0x49 DE N0MJS




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

 

Cort,

 

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 confbridge.py or bridge.py 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,

 

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 4:15 PM
To: "main@dvswitch.groups.io" <main@DVSwitch.groups.io>
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 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

 





 

 

 

--

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: Brandmeister to XLX

Adrian Fewster <vk4tux@...>
 

Yes I am still there on D-Star & DMR, and tested both ways fine re transcoder. However when the MB traffic from BM TG commences,

the transcoder fails and the BM traffic is just heard on the DMR connection until ambed is restarted.

So that's where we were, Patrick should setup ;

root@XLX389:/# cat /ambed/run
#!/bin/bash                                                                                                                                 
# start ambed server

sudo rmmod ftdi_sio
sudo rmmod usbserial
sudo /ambed/ambed 127.0.0.1 >/var/log/ambed.log &

,so we can check the log for the ambed crash.


Adrian ... vk4tux



On 2/12/19 1:59 am, Ernie Gm7kbk wrote:
Logged on via MB and my DMR repeater all seams ok. Passing traffic. Cannot test Dstar.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Adrian Fewster <vk4tux@...>
Sent: Sunday, December 1, 2019 3:16:23 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>; patrick@... >> Patrick Perdue <patrick@...>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

Ernie, they may be symptoms associated at the time, but the red thumb, is just a failure of the database sync with the authenticated hash file that the server then verifies the Ip, and

set the thumb status ;

if ($CallingHome['Active']) {


$CallHomeNow = false;

$LastSync = 0;

$Hash = "";


if (!file_exists($CallingHome['HashFile'])) {

$Ressource = fopen($CallingHome['HashFile'], "w+");

if ($Ressource) {

$Hash = CreateCode(16);

@fwrite($Ressource, "<?php\n");

@fwrite($Ressource, "\n".'$Hash = "'.$Hash.'";');

@fwrite($Ressource, "\n\n".'?>');

@fflush($Ressource);

@fclose($Ressource);

@chmod($HashFile, 0777);

}

}

else {

require_once($CallingHome['HashFile']);

}


if (@file_exists($CallingHome['LastCallHomefile'])) {

if (@is_readable($CallingHome['LastCallHomefile'])) {

$tmp = @file($CallingHome['LastCallHomefile']);

if (isset($tmp[0])) {

$LastSync = $tmp[0];

}

unset($tmp);

}

}


if ($LastSync < (time() - $CallingHome['PushDelay'])) {

$CallHomeNow = true;

$Ressource = @fopen($CallingHome['LastCallHomefile'], "w+");

if ($Ressource) {

@fwrite($Ressource, time());

@fflush($Ressource);

@fclose($Ressource);

@chmod($HashFile, 0777);

}

}


if ($CallHomeNow || isset($_GET['callhome'])) {

$Reflector->SetCallingHome($CallingHome, $Hash);

$Reflector->ReadInterlinkFile();

$Reflector->PrepareInterlinkXML();

$Reflector->PrepareReflectorXML();

$Reflector->CallHome();

}


}

else {

$Hash = "";

}


Red thumb consequences are that hams can no longer connect, due to invalid or no hostfile information. There is no code
to detect the issue's below you name to trigger a red thumb. If the system is not running, then of course sync will not occur either.

Certainly it needs fixing asap.

In this case we suspect there is more than one dashboard installed, as the dashboard displayed error path does not match config.inc.php.

Adrian ... vk4tux

On 2/12/19 12:36 am, Ernie Gm7kbk wrote:
If I see a red thumb on my server it means there is something  wrong. Failed to start ambeserver. Ports not set. XLX not started properly. Taking a hard drive from another machine. XLX looks for the old IP address.
Looking for faults in xlx is for another forum.
Happy to help with MB as I've had most of problems that everyone has. I make sure both sides are working then fill in the puzzel.




Re: Brandmeister to XLX

 

Logged on via MB and my DMR repeater all seams ok. Passing traffic. Cannot test Dstar.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Adrian Fewster <vk4tux@...>
Sent: Sunday, December 1, 2019 3:16:23 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>; patrick@... >> Patrick Perdue <patrick@...>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

Ernie, they may be symptoms associated at the time, but the red thumb, is just a failure of the database sync with the authenticated hash file that the server then verifies the Ip, and

set the thumb status ;

if ($CallingHome['Active']) {


$CallHomeNow = false;

$LastSync = 0;

$Hash = "";


if (!file_exists($CallingHome['HashFile'])) {

$Ressource = fopen($CallingHome['HashFile'], "w+");

if ($Ressource) {

$Hash = CreateCode(16);

@fwrite($Ressource, "<?php\n");

@fwrite($Ressource, "\n".'$Hash = "'.$Hash.'";');

@fwrite($Ressource, "\n\n".'?>');

@fflush($Ressource);

@fclose($Ressource);

@chmod($HashFile, 0777);

}

}

else {

require_once($CallingHome['HashFile']);

}


if (@file_exists($CallingHome['LastCallHomefile'])) {

if (@is_readable($CallingHome['LastCallHomefile'])) {

$tmp = @file($CallingHome['LastCallHomefile']);

if (isset($tmp[0])) {

$LastSync = $tmp[0];

}

unset($tmp);

}

}


if ($LastSync < (time() - $CallingHome['PushDelay'])) {

$CallHomeNow = true;

$Ressource = @fopen($CallingHome['LastCallHomefile'], "w+");

if ($Ressource) {

@fwrite($Ressource, time());

@fflush($Ressource);

@fclose($Ressource);

@chmod($HashFile, 0777);

}

}


if ($CallHomeNow || isset($_GET['callhome'])) {

$Reflector->SetCallingHome($CallingHome, $Hash);

$Reflector->ReadInterlinkFile();

$Reflector->PrepareInterlinkXML();

$Reflector->PrepareReflectorXML();

$Reflector->CallHome();

}


}

else {

$Hash = "";

}


Red thumb consequences are that hams can no longer connect, due to invalid or no hostfile information. There is no code
to detect the issue's below you name to trigger a red thumb. If the system is not running, then of course sync will not occur either.

Certainly it needs fixing asap.

In this case we suspect there is more than one dashboard installed, as the dashboard displayed error path does not match config.inc.php.

Adrian ... vk4tux

On 2/12/19 12:36 am, Ernie Gm7kbk wrote:
If I see a red thumb on my server it means there is something  wrong. Failed to start ambeserver. Ports not set. XLX not started properly. Taking a hard drive from another machine. XLX looks for the old IP address.
Looking for faults in xlx is for another forum.
Happy to help with MB as I've had most of problems that everyone has. I make sure both sides are working then fill in the puzzel.




Re: Brandmeister to XLX

Adrian Fewster <vk4tux@...>
 

Ernie, they may be symptoms associated at the time, but the red thumb, is just a failure of the database sync with the authenticated hash file that the server then verifies the Ip, and

set the thumb status ;

if ($CallingHome['Active']) {


$CallHomeNow = false;

$LastSync = 0;

$Hash = "";


if (!file_exists($CallingHome['HashFile'])) {

$Ressource = fopen($CallingHome['HashFile'], "w+");

if ($Ressource) {

$Hash = CreateCode(16);

@fwrite($Ressource, "<?php\n");

@fwrite($Ressource, "\n".'$Hash = "'.$Hash.'";');

@fwrite($Ressource, "\n\n".'?>');

@fflush($Ressource);

@fclose($Ressource);

@chmod($HashFile, 0777);

}

}

else {

require_once($CallingHome['HashFile']);

}


if (@file_exists($CallingHome['LastCallHomefile'])) {

if (@is_readable($CallingHome['LastCallHomefile'])) {

$tmp = @file($CallingHome['LastCallHomefile']);

if (isset($tmp[0])) {

$LastSync = $tmp[0];

}

unset($tmp);

}

}


if ($LastSync < (time() - $CallingHome['PushDelay'])) {

$CallHomeNow = true;

$Ressource = @fopen($CallingHome['LastCallHomefile'], "w+");

if ($Ressource) {

@fwrite($Ressource, time());

@fflush($Ressource);

@fclose($Ressource);

@chmod($HashFile, 0777);

}

}


if ($CallHomeNow || isset($_GET['callhome'])) {

$Reflector->SetCallingHome($CallingHome, $Hash);

$Reflector->ReadInterlinkFile();

$Reflector->PrepareInterlinkXML();

$Reflector->PrepareReflectorXML();

$Reflector->CallHome();

}


}

else {

$Hash = "";

}


Red thumb consequences are that hams can no longer connect, due to invalid or no hostfile information. There is no code
to detect the issue's below you name to trigger a red thumb. If the system is not running, then of course sync will not occur either.

Certainly it needs fixing asap.

In this case we suspect there is more than one dashboard installed, as the dashboard displayed error path does not match config.inc.php.

Adrian ... vk4tux

On 2/12/19 12:36 am, Ernie Gm7kbk wrote:
If I see a red thumb on my server it means there is something  wrong. Failed to start ambeserver. Ports not set. XLX not started properly. Taking a hard drive from another machine. XLX looks for the old IP address.
Looking for faults in xlx is for another forum.
Happy to help with MB as I've had most of problems that everyone has. I make sure both sides are working then fill in the puzzel.




Re: Linking dmrlink and HBlink3 #dmrlink #hblink

Cort N0MJS <n0mjs@...>
 



On Dec 1, 2019, at 2:46 AM, ai6bx via Groups.Io <ai6bx.keith@...> wrote:

Cort,
 
I am not seeing bridge.py in my installs. I do have hb_bridge.py and hb_bridge_all.py. Are these interchangeable?

bridge.py is part of hblink3 – the Python 3 version of HBlink.

HB_Bridge.py and hb_bridge_all.py are completely different programs with completely different uses.

With IPSC_Bridge.py I am getting the following errors at start up. 
 
twisted.internet.error.CannotListenError: Couldn't listen on any:31000: [Errno 98] Address already in use.


“Address already in use” Something else on your system is already listening on UDP port 31000.


 
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 6:31 PM
To: "main@dvswitch.groups.io" <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Linking dmrlink and HBlink3 #dmrlink #hblink
 
Keith,
 
You’re really going to have to think about your project goals and make a decision. I have run systems with confbridge.py running on one side and bridge.py on the other… There are a LOT of things that can get you in trouble. You’ll have to remember, you’re essentially running two separate multi-system “networks” that are cross-connected to each other.
 
If at all possible, I’d recommend handling all of your call routing in bridge.py and translating the Motorolas into home-brew. Why this way and not the other? I’ve sunset development on DMRlink – mostly because I don’t even have a Motorola repeater anymore and I need at least 2 to really do any development work with it. Time is another reason. But I also see home-brew protocol and MMDVM as the future of digital ham radio… for me at least, and since I’m not getting paid for this, I’ll be following the beat of my own drum :)
 
Because you’re so Motorola heavy, you should consider running the call routing in confbridge.py on the IPSC side and bring your MMDVMs in as the afterthought. Just remember that there will be no new development on DMRlink unless someone else does it. It is what it is.
 
For the KS-DMR network, when someone shows up with a Motorola repeater, we deploy an IPSC_Bridge.py and HB_bridge.py combo for each one. The idea is simply convert the Motorola to speak home-brew as fast and as close to the source as possible. Often times this is a small single board computer – usually with “Pi” in the name somewhere – right with the repeater itself. Other times, for folks who want to be a part of it it just can’t handle (or just don’t want to) running those services we provide them on our infrastructure.
 
0x49 DE N0MJS


On Nov 30, 2019, at 7:30 PM, ai6bx via Groups.Io <ai6bx.keith@...> wrote:
 
Cort,
 
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 confbridge.py or bridge.py 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,
 
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 4:15 PM
To: "main@dvswitch.groups.io" <main@DVSwitch.groups.io>
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 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
 



 

 
 
--
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: Brandmeister to XLX

 

If I see a red thumb on my server it means there is something  wrong. Failed to start ambeserver. Ports not set. XLX not started properly. Taking a hard drive from another machine. XLX looks for the old IP address.
Looking for faults in xlx is for another forum.
Happy to help with MB as I've had most of problems that everyone has. I make sure both sides are working then fill in the puzzel.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Adrian Fewster <vk4tux@...>
Sent: Sunday, December 1, 2019 1:23:24 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>; patrick@... >> Patrick Perdue <patrick@...>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

The red thumb just indicates that the system is not reporting it's Ip to the XLX database server, and hence will be dropped out of the host files.

It is not an indication of any dstar traffic issue. The dstar side looks ok, and I test connected.

It is the DMR side that has the issue., 62030 UDP port block tested here, and really the

reflector needs setting up properly, regarding port forwarding and configuration. It doesn't look finished re xlxd setup.

See  .webroot > ...pgs/config.inc.php to configure correct ;

$CallingHome['Active']                               = true;                                                   // xlx phone home, true or false  << check true ?
$CallingHome['MyDashBoardURL']                       = 'http://xlxdmr.duckdns.org/db/';                        // dashboard url  << check
$CallingHome['ServerURL']                            = 'http://xlxapi.rlx.lu/api.php';         // database server, do not change !!!!
$CallingHome['PushDelay']                            = 600;                                    // push delay in seconds
$CallingHome['Country']                              = "Australia";                         // Country
$CallingHome['Comment']                              = "";                                         // Comment. Max 100 character
$CallingHome['HashFile']                             = "/var/www/db/callinghome.php";                 // Make sure the apache user has read and write permissions in this folder. << best in folder with web user/group permission's ownership re eg www-data etc, and/or make it so.
$CallingHome['LastCallHomefile']                     = "/tmp/lastcallhome.php";                 // lastcallhome.php can remain in the tmp folder
$CallingHome['OverrideIPAddress']                    = "";                                      // Insert your IP address here. Leave blank for autodetection. No need to enter a fake address.
$CallingHome['InterlinkFile']                        = "/xlxd/xlxd.interlink";                  // Path to interlink file

$VNStat['Interfaces']                                = array();
$VNStat['Interfaces'][0]['Name']                     = 'eth0';
$VNStat['Interfaces'][0]['Address']                  = 'eth0';
$VNStat['Binary']                                    = '/usr/bin/vnstat';



On 1/12/19 10:34 pm, Ernie Gm7kbk wrote:
Xlx679 has got a red thumb. That's your problem. It's not working. No traffic will pass from the dstar side




Re: Brandmeister to XLX

Adrian Fewster <vk4tux@...>
 

It's looking now like a bad packet knocking out the transcoder. Need to setup logging to test further.

DMR & D-Star connections seem solid, and ports ok.

On 1/12/19 11:28 pm, Patrick Perdue wrote:

I had this reflector working for about five months until yesterday, accessible in host lists. However, I had a partial system failure yesterday, and callinghome.php didn't seem to make the backup for some reason. The switch is still set to true, but the file isn't showing up after XLXD is restarted. Maybe a permissions problem.


On 12/1/2019 8:23 AM, Adrian wrote:

The red thumb just indicates that the system is not reporting it's Ip to the XLX database server, and hence will be dropped out of the host files.

It is not an indication of any dstar traffic issue. The dstar side looks ok, and I test connected.

It is the DMR side that has the issue., 62030 UDP port block tested here, and really the

reflector needs setting up properly, regarding port forwarding and configuration. It doesn't look finished re xlxd setup.

See  .webroot > ...pgs/config.inc.php to configure correct ;

$CallingHome['Active']                               = true;                                                   // xlx phone home, true or false  << check true ?
$CallingHome['MyDashBoardURL']                       = 'http://xlxdmr.duckdns.org/db/';                        // dashboard url  << check
$CallingHome['ServerURL']                            = 'http://xlxapi.rlx.lu/api.php';         // database server, do not change !!!!
$CallingHome['PushDelay']                            = 600;                                    // push delay in seconds
$CallingHome['Country']                              = "Australia";                         // Country
$CallingHome['Comment']                              = "";                                         // Comment. Max 100 character
$CallingHome['HashFile']                             = "/var/www/db/callinghome.php";                 // Make sure the apache user has read and write permissions in this folder. << best in folder with web user/group permission's ownership re eg www-data etc, and/or make it so.
$CallingHome['LastCallHomefile']                     = "/tmp/lastcallhome.php";                 // lastcallhome.php can remain in the tmp folder
$CallingHome['OverrideIPAddress']                    = "";                                      // Insert your IP address here. Leave blank for autodetection. No need to enter a fake address.
$CallingHome['InterlinkFile']                        = "/xlxd/xlxd.interlink";                  // Path to interlink file

$VNStat['Interfaces']                                = array();
$VNStat['Interfaces'][0]['Name']                     = 'eth0';
$VNStat['Interfaces'][0]['Address']                  = 'eth0';
$VNStat['Binary']                                    = '/usr/bin/vnstat';



On 1/12/19 10:34 pm, Ernie Gm7kbk wrote:
Xlx679 has got a red thumb. That's your problem. It's not working. No traffic will pass from the dstar side




Re: Brandmeister to XLX

Adrian Fewster <vk4tux@...>
 

Check

http://64.94.238.196/status/places/BlockedUsers.htm

for any blocks once you test again and it fails.

On 1/12/19 11:28 pm, Patrick Perdue wrote:

I had this reflector working for about five months until yesterday, accessible in host lists. However, I had a partial system failure yesterday, and callinghome.php didn't seem to make the backup for some reason. The switch is still set to true, but the file isn't showing up after XLXD is restarted. Maybe a permissions problem.




Re: Brandmeister to XLX

Adrian Fewster <vk4tux@...>
 

Further testing now has the DMR connecting, and I am in contact with Patrick on XLX679 to help troubleshoot.

On 1/12/19 11:23 pm, Adrian Fewster via Groups.Io wrote:

The red thumb just indicates that the system is not reporting it's Ip to the XLX database server, and hence will be dropped out of the host files.

It is not an indication of any dstar traffic issue. The dstar side looks ok, and I test connected.

It is the DMR side that has the issue., 62030 UDP port block tested here, and really the

reflector needs setting up properly, regarding port forwarding and configuration. It doesn't look finished re xlxd setup.

See  .webroot > ...pgs/config.inc.php to configure correct ;

$CallingHome['Active']                               = true;                                                   // xlx phone home, true or false  << check true ?
$CallingHome['MyDashBoardURL']                       = 'http://xlxdmr.duckdns.org/db/';                        // dashboard url  << check
$CallingHome['ServerURL']                            = 'http://xlxapi.rlx.lu/api.php';         // database server, do not change !!!!
$CallingHome['PushDelay']                            = 600;                                    // push delay in seconds
$CallingHome['Country']                              = "Australia";                         // Country
$CallingHome['Comment']                              = "";                                         // Comment. Max 100 character
$CallingHome['HashFile']                             = "/var/www/db/callinghome.php";                 // Make sure the apache user has read and write permissions in this folder. << best in folder with web user/group permission's ownership re eg www-data etc, and/or make it so.
$CallingHome['LastCallHomefile']                     = "/tmp/lastcallhome.php";                 // lastcallhome.php can remain in the tmp folder
$CallingHome['OverrideIPAddress']                    = "";                                      // Insert your IP address here. Leave blank for autodetection. No need to enter a fake address.
$CallingHome['InterlinkFile']                        = "/xlxd/xlxd.interlink";                  // Path to interlink file

$VNStat['Interfaces']                                = array();
$VNStat['Interfaces'][0]['Name']                     = 'eth0';
$VNStat['Interfaces'][0]['Address']                  = 'eth0';
$VNStat['Binary']                                    = '/usr/bin/vnstat';



On 1/12/19 10:34 pm, Ernie Gm7kbk wrote:
Xlx679 has got a red thumb. That's your problem. It's not working. No traffic will pass from the dstar side




Re: Brandmeister to XLX

Adrian Fewster <vk4tux@...>
 


I tested again just now and now it is linking, nothing changed my end, before it wouldn't, strange, perhaps a dns/nameserver issue with that address.

Anyhow we can test further for a good result.


Adrian




On 1/12/19 11:17 pm, Patrick Perdue wrote:

Hmm...

I can connect my hotspot directly to the reflector on port 62030, and hear myself on D-STAR. The reflector and my hotspot are not on the same network. Hotspot is at my house behind a router, reflector is on a VPS facing the public internet. So, the transcoders are working, and the port doesn't seem to actually be blocked. Otherwise, I wouldn't be able to get to it from here. I just had a QSO with someone from D-STAR via DMR directly connected to the reflector, and that worked well

I just realized when I did a new install of XLXD yesterday that I broke my callinghome.php, so I'll fix that in a bit.




On 12/1/2019 7:36 AM, Adrian wrote:

Your port 62030 UDP is blocked ;

M: 2019-12-01 12:26:21.679 XLX, Opening DMR Network
M: 2019-12-01 12:26:21.679 XLX, Connecting to XLX679
D: 2019-12-01 12:26:21.679 TGIF_Network, Sending configuration
M: 2019-12-01 12:26:21.919 TGIF_Network, Logged into the master successfully
D: 2019-12-01 12:26:31.906 XLX, Sending authorisation
D: 2019-12-01 12:26:32.151 XLX, Sending configuration
M: 2019-12-01 12:26:32.395 XLX, Logged into the master successfully
M: 2019-12-01 12:26:32.395 XLX, Linking to reflector XLX679 U
M: 2019-12-01 12:27:52.211 XLX, Linking to reflector XLX679 A

No connection achieved, i manually added to XLXHosts.txt  679;xlx.borris.me;4001 , as your system is not in the database, as callinghome.php is not functioning,

and dashboard link is faulty. ;


> your private hash in /xlxd/callinghome.php could not be created, please check your config file and the permissions for the defined folder.


D-Star is fine of course, I connected VK4RBX to A, and wanted to test your transcoders. However if my DMR connection will not connect,

I doubt your MB connects will. Time to check port forwarding and iptables  ?

Firewall settings

XLX Server requires the following ports to be open and forwarded properly for in- and outgoing network traffic:

  • TCP port 80 (http) optional TCP port 443 (https)
  • TCP port 8080 (RepNet) optional
  • UDP port 10001 (json interface XLX Core)
  • UDP port 10002 (XLX interlink)
  • TCP port 22 (ssh) optional TCP port 10022
  • UDP port 42000 (YSF protocol)
  • UDP port 30001 (DExtra protocol)
  • UPD port 20001 (DPlus protocol)
  • UDP port 30051 (DCS protocol)
  • UDP port 8880 (DMR+ DMO mode)
  • UDP port 62030 (MMDVM protocol)  <<<<<<<<<<<<
  • UDP port 10100 (AMBE controller port)
  • UDP port 10101 - 10199 (AMBE transcoding port)


Adrian ... vk4tux





On 1/12/19 10:10 pm, Patrick Perdue wrote:

The local ports are already different -- BM instance local port is 62032, XLX is 62034.

I have them both running in console.

Traffic passes fine from BM to XLX, but as soon as anyone transmits from D-STAR to the reflector, everything breaks, and traffic doesn't pass in either direction.

I don't see any log entries from either MMDVM_Bridge instance after that, until at least one of the bridges is restarted.


On 12/1/2019 5:18 AM, Ernie Gm7kbk wrote:
No
If you have two instances running you have to change one of the local ports. Change 62032 to 62033. To test I always run In a terminal. Not as a service. Switch debug=1 then start up one get it going . Stop the working one then start the other and get it working. Fire up both once you have inverted the ports in the DVSwitch.ini.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Sunday, December 1, 2019 9:57:10 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

This is XLX679 module A.

FWIW: I copied the exact configuration over to a machine on my LAN, and it works there. Don't know what the difference is.

I have two instances of MMDVM_Bridge running -- one connected to Brandmeister, the other to my XLX reflector. Ports are inverted on the second instance of DVSwitch.ini.

Transmissions from Brandmeister make it to the reflector, but outbound from the module doesn't go back to the Brandmeister talkgroup. Do I need to use DMRGateway for talkgroup rewriting in this case?


On 12/1/2019 4:20 AM, Ernie Gm7kbk wrote:
What xlx are you trying to get into. As I set my odroid n2 to do the very same the other day. Just to check if the ports are open.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Sunday, December 1, 2019 9:14:29 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

Right. I wasn't referring directly to the INI file at the time.

My machine is on a VPS, so the IP of ETH0 is a public IP address.

So, it looks like this.

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

I've tried moving the local port as well.


In DVSwitch.ini, I have differentiated the RXPort and TXPort from my existing DMR to Allstar setup.

[DMR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31200                  ; Port to send AMBE TLV frames to (export)
RXPort = 31203                  ; Port to listen on (import)
Slot = 2                        ; Export slot


On 12/1/2019 3:56 AM, Ernie Gm7kbk wrote:
No that's the port
My address looks like 192.168.1.66 this is the private network ipv4.

Xlx looks at the port of 62030 and the ipv4 address of the device. Or you can put in the external ipv4 address or web address. 


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Sunday, December 1, 2019 8:41:57 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

Currently, I have the address in the DMR Network stanza pointed to the XLX reflector <IP_ADDRESS:62030). I assume this is the network address you're referring to?

If so, then the reflector isn't doing much with that, and this is probably not a DVSwitch issue.



On 11/30/2019 5:22 PM, Steve N4IRS wrote:
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

Adrian Fewster <vk4tux@...>
 

The red thumb just indicates that the system is not reporting it's Ip to the XLX database server, and hence will be dropped out of the host files.

It is not an indication of any dstar traffic issue. The dstar side looks ok, and I test connected.

It is the DMR side that has the issue., 62030 UDP port block tested here, and really the

reflector needs setting up properly, regarding port forwarding and configuration. It doesn't look finished re xlxd setup.

See  .webroot > ...pgs/config.inc.php to configure correct ;

$CallingHome['Active']                               = true;                                                   // xlx phone home, true or false  << check true ?
$CallingHome['MyDashBoardURL']                       = 'http://xlxdmr.duckdns.org/db/';                        // dashboard url  << check
$CallingHome['ServerURL']                            = 'http://xlxapi.rlx.lu/api.php';         // database server, do not change !!!!
$CallingHome['PushDelay']                            = 600;                                    // push delay in seconds
$CallingHome['Country']                              = "Australia";                         // Country
$CallingHome['Comment']                              = "";                                         // Comment. Max 100 character
$CallingHome['HashFile']                             = "/var/www/db/callinghome.php";                 // Make sure the apache user has read and write permissions in this folder. << best in folder with web user/group permission's ownership re eg www-data etc, and/or make it so.
$CallingHome['LastCallHomefile']                     = "/tmp/lastcallhome.php";                 // lastcallhome.php can remain in the tmp folder
$CallingHome['OverrideIPAddress']                    = "";                                      // Insert your IP address here. Leave blank for autodetection. No need to enter a fake address.
$CallingHome['InterlinkFile']                        = "/xlxd/xlxd.interlink";                  // Path to interlink file

$VNStat['Interfaces']                                = array();
$VNStat['Interfaces'][0]['Name']                     = 'eth0';
$VNStat['Interfaces'][0]['Address']                  = 'eth0';
$VNStat['Binary']                                    = '/usr/bin/vnstat';



On 1/12/19 10:34 pm, Ernie Gm7kbk wrote:
Xlx679 has got a red thumb. That's your problem. It's not working. No traffic will pass from the dstar side




Re: Brandmeister to XLX

 

Xlx679 has got a red thumb. That's your problem. It's not working. No traffic will pass from the dstar side


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Ernie Gm7kbk <erniepratt@...>
Sent: Sunday, December 1, 2019 12:27:56 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 
Your running on a vps. Where is the ambeserver? Don't think the problem is with MB. Only have the one instance of MB the one connected to xlx. In debug mode you should see traffic . I have seen me spending hours trying to find a fault finding it's just a typo


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Sunday, December 1, 2019 12:10:22 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

The local ports are already different -- BM instance local port is 62032, XLX is 62034.

I have them both running in console.

Traffic passes fine from BM to XLX, but as soon as anyone transmits from D-STAR to the reflector, everything breaks, and traffic doesn't pass in either direction.

I don't see any log entries from either MMDVM_Bridge instance after that, until at least one of the bridges is restarted.


On 12/1/2019 5:18 AM, Ernie Gm7kbk wrote:
No
If you have two instances running you have to change one of the local ports. Change 62032 to 62033. To test I always run In a terminal. Not as a service. Switch debug=1 then start up one get it going . Stop the working one then start the other and get it working. Fire up both once you have inverted the ports in the DVSwitch.ini.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Sunday, December 1, 2019 9:57:10 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

This is XLX679 module A.

FWIW: I copied the exact configuration over to a machine on my LAN, and it works there. Don't know what the difference is.

I have two instances of MMDVM_Bridge running -- one connected to Brandmeister, the other to my XLX reflector. Ports are inverted on the second instance of DVSwitch.ini.

Transmissions from Brandmeister make it to the reflector, but outbound from the module doesn't go back to the Brandmeister talkgroup. Do I need to use DMRGateway for talkgroup rewriting in this case?


On 12/1/2019 4:20 AM, Ernie Gm7kbk wrote:
What xlx are you trying to get into. As I set my odroid n2 to do the very same the other day. Just to check if the ports are open.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Sunday, December 1, 2019 9:14:29 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

Right. I wasn't referring directly to the INI file at the time.

My machine is on a VPS, so the IP of ETH0 is a public IP address.

So, it looks like this.

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

I've tried moving the local port as well.


In DVSwitch.ini, I have differentiated the RXPort and TXPort from my existing DMR to Allstar setup.

[DMR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31200                  ; Port to send AMBE TLV frames to (export)
RXPort = 31203                  ; Port to listen on (import)
Slot = 2                        ; Export slot


On 12/1/2019 3:56 AM, Ernie Gm7kbk wrote:
No that's the port
My address looks like 192.168.1.66 this is the private network ipv4.

Xlx looks at the port of 62030 and the ipv4 address of the device. Or you can put in the external ipv4 address or web address. 


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Sunday, December 1, 2019 8:41:57 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

Currently, I have the address in the DMR Network stanza pointed to the XLX reflector <IP_ADDRESS:62030). I assume this is the network address you're referring to?

If so, then the reflector isn't doing much with that, and this is probably not a DVSwitch issue.



On 11/30/2019 5:22 PM, Steve N4IRS wrote:
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

 

Your running on a vps. Where is the ambeserver? Don't think the problem is with MB. Only have the one instance of MB the one connected to xlx. In debug mode you should see traffic . I have seen me spending hours trying to find a fault finding it's just a typo


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Sunday, December 1, 2019 12:10:22 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

The local ports are already different -- BM instance local port is 62032, XLX is 62034.

I have them both running in console.

Traffic passes fine from BM to XLX, but as soon as anyone transmits from D-STAR to the reflector, everything breaks, and traffic doesn't pass in either direction.

I don't see any log entries from either MMDVM_Bridge instance after that, until at least one of the bridges is restarted.


On 12/1/2019 5:18 AM, Ernie Gm7kbk wrote:
No
If you have two instances running you have to change one of the local ports. Change 62032 to 62033. To test I always run In a terminal. Not as a service. Switch debug=1 then start up one get it going . Stop the working one then start the other and get it working. Fire up both once you have inverted the ports in the DVSwitch.ini.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Sunday, December 1, 2019 9:57:10 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

This is XLX679 module A.

FWIW: I copied the exact configuration over to a machine on my LAN, and it works there. Don't know what the difference is.

I have two instances of MMDVM_Bridge running -- one connected to Brandmeister, the other to my XLX reflector. Ports are inverted on the second instance of DVSwitch.ini.

Transmissions from Brandmeister make it to the reflector, but outbound from the module doesn't go back to the Brandmeister talkgroup. Do I need to use DMRGateway for talkgroup rewriting in this case?


On 12/1/2019 4:20 AM, Ernie Gm7kbk wrote:
What xlx are you trying to get into. As I set my odroid n2 to do the very same the other day. Just to check if the ports are open.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Sunday, December 1, 2019 9:14:29 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

Right. I wasn't referring directly to the INI file at the time.

My machine is on a VPS, so the IP of ETH0 is a public IP address.

So, it looks like this.

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

I've tried moving the local port as well.


In DVSwitch.ini, I have differentiated the RXPort and TXPort from my existing DMR to Allstar setup.

[DMR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31200                  ; Port to send AMBE TLV frames to (export)
RXPort = 31203                  ; Port to listen on (import)
Slot = 2                        ; Export slot


On 12/1/2019 3:56 AM, Ernie Gm7kbk wrote:
No that's the port
My address looks like 192.168.1.66 this is the private network ipv4.

Xlx looks at the port of 62030 and the ipv4 address of the device. Or you can put in the external ipv4 address or web address. 


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Sunday, December 1, 2019 8:41:57 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

Currently, I have the address in the DMR Network stanza pointed to the XLX reflector <IP_ADDRESS:62030). I assume this is the network address you're referring to?

If so, then the reflector isn't doing much with that, and this is probably not a DVSwitch issue.



On 11/30/2019 5:22 PM, Steve N4IRS wrote:
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
 

The local ports are already different -- BM instance local port is 62032, XLX is 62034.

I have them both running in console.

Traffic passes fine from BM to XLX, but as soon as anyone transmits from D-STAR to the reflector, everything breaks, and traffic doesn't pass in either direction.

I don't see any log entries from either MMDVM_Bridge instance after that, until at least one of the bridges is restarted.


On 12/1/2019 5:18 AM, Ernie Gm7kbk wrote:
No
If you have two instances running you have to change one of the local ports. Change 62032 to 62033. To test I always run In a terminal. Not as a service. Switch debug=1 then start up one get it going . Stop the working one then start the other and get it working. Fire up both once you have inverted the ports in the DVSwitch.ini.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Sunday, December 1, 2019 9:57:10 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

This is XLX679 module A.

FWIW: I copied the exact configuration over to a machine on my LAN, and it works there. Don't know what the difference is.

I have two instances of MMDVM_Bridge running -- one connected to Brandmeister, the other to my XLX reflector. Ports are inverted on the second instance of DVSwitch.ini.

Transmissions from Brandmeister make it to the reflector, but outbound from the module doesn't go back to the Brandmeister talkgroup. Do I need to use DMRGateway for talkgroup rewriting in this case?


On 12/1/2019 4:20 AM, Ernie Gm7kbk wrote:
What xlx are you trying to get into. As I set my odroid n2 to do the very same the other day. Just to check if the ports are open.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Sunday, December 1, 2019 9:14:29 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

Right. I wasn't referring directly to the INI file at the time.

My machine is on a VPS, so the IP of ETH0 is a public IP address.

So, it looks like this.

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

I've tried moving the local port as well.


In DVSwitch.ini, I have differentiated the RXPort and TXPort from my existing DMR to Allstar setup.

[DMR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31200                  ; Port to send AMBE TLV frames to (export)
RXPort = 31203                  ; Port to listen on (import)
Slot = 2                        ; Export slot


On 12/1/2019 3:56 AM, Ernie Gm7kbk wrote:
No that's the port
My address looks like 192.168.1.66 this is the private network ipv4.

Xlx looks at the port of 62030 and the ipv4 address of the device. Or you can put in the external ipv4 address or web address. 


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Sunday, December 1, 2019 8:41:57 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

Currently, I have the address in the DMR Network stanza pointed to the XLX reflector <IP_ADDRESS:62030). I assume this is the network address you're referring to?

If so, then the reflector isn't doing much with that, and this is probably not a DVSwitch issue.



On 11/30/2019 5:22 PM, Steve N4IRS wrote:
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

 

No
If you have two instances running you have to change one of the local ports. Change 62032 to 62033. To test I always run In a terminal. Not as a service. Switch debug=1 then start up one get it going . Stop the working one then start the other and get it working. Fire up both once you have inverted the ports in the DVSwitch.ini.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Sunday, December 1, 2019 9:57:10 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

This is XLX679 module A.

FWIW: I copied the exact configuration over to a machine on my LAN, and it works there. Don't know what the difference is.

I have two instances of MMDVM_Bridge running -- one connected to Brandmeister, the other to my XLX reflector. Ports are inverted on the second instance of DVSwitch.ini.

Transmissions from Brandmeister make it to the reflector, but outbound from the module doesn't go back to the Brandmeister talkgroup. Do I need to use DMRGateway for talkgroup rewriting in this case?


On 12/1/2019 4:20 AM, Ernie Gm7kbk wrote:
What xlx are you trying to get into. As I set my odroid n2 to do the very same the other day. Just to check if the ports are open.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Sunday, December 1, 2019 9:14:29 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

Right. I wasn't referring directly to the INI file at the time.

My machine is on a VPS, so the IP of ETH0 is a public IP address.

So, it looks like this.

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

I've tried moving the local port as well.


In DVSwitch.ini, I have differentiated the RXPort and TXPort from my existing DMR to Allstar setup.

[DMR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31200                  ; Port to send AMBE TLV frames to (export)
RXPort = 31203                  ; Port to listen on (import)
Slot = 2                        ; Export slot


On 12/1/2019 3:56 AM, Ernie Gm7kbk wrote:
No that's the port
My address looks like 192.168.1.66 this is the private network ipv4.

Xlx looks at the port of 62030 and the ipv4 address of the device. Or you can put in the external ipv4 address or web address. 


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Sunday, December 1, 2019 8:41:57 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

Currently, I have the address in the DMR Network stanza pointed to the XLX reflector <IP_ADDRESS:62030). I assume this is the network address you're referring to?

If so, then the reflector isn't doing much with that, and this is probably not a DVSwitch issue.



On 11/30/2019 5:22 PM, Steve N4IRS wrote:
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
 

This is XLX679 module A.

FWIW: I copied the exact configuration over to a machine on my LAN, and it works there. Don't know what the difference is.

I have two instances of MMDVM_Bridge running -- one connected to Brandmeister, the other to my XLX reflector. Ports are inverted on the second instance of DVSwitch.ini.

Transmissions from Brandmeister make it to the reflector, but outbound from the module doesn't go back to the Brandmeister talkgroup. Do I need to use DMRGateway for talkgroup rewriting in this case?


On 12/1/2019 4:20 AM, Ernie Gm7kbk wrote:
What xlx are you trying to get into. As I set my odroid n2 to do the very same the other day. Just to check if the ports are open.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Sunday, December 1, 2019 9:14:29 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

Right. I wasn't referring directly to the INI file at the time.

My machine is on a VPS, so the IP of ETH0 is a public IP address.

So, it looks like this.

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

I've tried moving the local port as well.


In DVSwitch.ini, I have differentiated the RXPort and TXPort from my existing DMR to Allstar setup.

[DMR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31200                  ; Port to send AMBE TLV frames to (export)
RXPort = 31203                  ; Port to listen on (import)
Slot = 2                        ; Export slot


On 12/1/2019 3:56 AM, Ernie Gm7kbk wrote:
No that's the port
My address looks like 192.168.1.66 this is the private network ipv4.

Xlx looks at the port of 62030 and the ipv4 address of the device. Or you can put in the external ipv4 address or web address. 


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Sunday, December 1, 2019 8:41:57 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

Currently, I have the address in the DMR Network stanza pointed to the XLX reflector <IP_ADDRESS:62030). I assume this is the network address you're referring to?

If so, then the reflector isn't doing much with that, and this is probably not a DVSwitch issue.



On 11/30/2019 5:22 PM, Steve N4IRS wrote:
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

 

What xlx are you trying to get into. As I set my odroid n2 to do the very same the other day. Just to check if the ports are open.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Sunday, December 1, 2019 9:14:29 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

Right. I wasn't referring directly to the INI file at the time.

My machine is on a VPS, so the IP of ETH0 is a public IP address.

So, it looks like this.

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

I've tried moving the local port as well.


In DVSwitch.ini, I have differentiated the RXPort and TXPort from my existing DMR to Allstar setup.

[DMR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31200                  ; Port to send AMBE TLV frames to (export)
RXPort = 31203                  ; Port to listen on (import)
Slot = 2                        ; Export slot


On 12/1/2019 3:56 AM, Ernie Gm7kbk wrote:
No that's the port
My address looks like 192.168.1.66 this is the private network ipv4.

Xlx looks at the port of 62030 and the ipv4 address of the device. Or you can put in the external ipv4 address or web address. 


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Sunday, December 1, 2019 8:41:57 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

Currently, I have the address in the DMR Network stanza pointed to the XLX reflector <IP_ADDRESS:62030). I assume this is the network address you're referring to?

If so, then the reflector isn't doing much with that, and this is probably not a DVSwitch issue.



On 11/30/2019 5:22 PM, Steve N4IRS wrote:
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
 

Right. I wasn't referring directly to the INI file at the time.

My machine is on a VPS, so the IP of ETH0 is a public IP address.

So, it looks like this.

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

I've tried moving the local port as well.


In DVSwitch.ini, I have differentiated the RXPort and TXPort from my existing DMR to Allstar setup.

[DMR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31200                  ; Port to send AMBE TLV frames to (export)
RXPort = 31203                  ; Port to listen on (import)
Slot = 2                        ; Export slot


On 12/1/2019 3:56 AM, Ernie Gm7kbk wrote:
No that's the port
My address looks like 192.168.1.66 this is the private network ipv4.

Xlx looks at the port of 62030 and the ipv4 address of the device. Or you can put in the external ipv4 address or web address. 


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Sunday, December 1, 2019 8:41:57 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

Currently, I have the address in the DMR Network stanza pointed to the XLX reflector <IP_ADDRESS:62030). I assume this is the network address you're referring to?

If so, then the reflector isn't doing much with that, and this is probably not a DVSwitch issue.



On 11/30/2019 5:22 PM, Steve N4IRS wrote:
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

 

No that's the port
My address looks like 192.168.1.66 this is the private network ipv4.

Xlx looks at the port of 62030 and the ipv4 address of the device. Or you can put in the external ipv4 address or web address. 


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Sunday, December 1, 2019 8:41:57 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
 

Currently, I have the address in the DMR Network stanza pointed to the XLX reflector <IP_ADDRESS:62030). I assume this is the network address you're referring to?

If so, then the reflector isn't doing much with that, and this is probably not a DVSwitch issue.



On 11/30/2019 5:22 PM, Steve N4IRS wrote:
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

4501 - 4520 of 9891