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

Join main@DVSwitch.groups.io to automatically receive all group messages.