ASL <-> D-Star <-> xlxd


va3dxv
 

Hello everyone. Is there much D-Star activity in the group? I've got a working xlxd reflector set up I use for a DStar group. Running on the same server, I have a working AllStar simplex radio node with Analog_Bridge and MMDVM_Bridge.

I'd like to bridge the ASL node into xlxd, in D-Star mode. So in theory, it goes like this: ASL <-> Analog_Bridge <-> (DStar, using hardware USB chip) <-> MMDVM_Bridge <-> xlxd

However I can only get MMDVM_Bridge to connect to xlxd if I use [DMR Network] in MMDVM_Bridge.ini. If I try using [D-Star Network], xlxd sees DPlus packets but it doesn't retransmit anything, and doesn't show the connection. Audio is messed up in DMR mode anyways, even though A_B says on start up it's using the hardware codec.

I could maybe insert ircDDBGateway between M_B and xlxd but it doesn't look like they can easily coexist on the same host.

Can MMDVM_Bridge connect to xlxd in DPlus or another DStar mode? I don't want to have to go analog->dmr->dstar, I'd rather just do analog->dstar. Wondering if anyone on here is doing this and how they went about it. Thank You


Steve N4IRS
 

It would be:
 ASL <-> Analog_Bridge <-> (DStar, using hardware USB chip) <-> MMDVM_Bridge <-> ircDDBGateway <-> xlxd

I don't know if ircDDBGateway and XLX can exist on the same machine. I assume it can.

Steve N4IRS

On 11/30/20 4:20 PM, va3dxv wrote:
Hello everyone. Is there much D-Star activity in the group? I've got a working xlxd reflector set up I use for a DStar group. Running on the same server, I have a working AllStar simplex radio node with Analog_Bridge and MMDVM_Bridge.

I'd like to bridge the ASL node into xlxd, in D-Star mode. So in theory, it goes like this: ASL <-> Analog_Bridge <-> (DStar, using hardware USB chip) <-> MMDVM_Bridge <-> xlxd

However I can only get MMDVM_Bridge to connect to xlxd if I use [DMR Network] in MMDVM_Bridge.ini. If I try using [D-Star Network], xlxd sees DPlus packets but it doesn't retransmit anything, and doesn't show the connection. Audio is messed up in DMR mode anyways, even though A_B says on start up it's using the hardware codec.

I could maybe insert ircDDBGateway between M_B and xlxd but it doesn't look like they can easily coexist on the same host.

Can MMDVM_Bridge connect to xlxd in DPlus or another DStar mode? I don't want to have to go analog->dmr->dstar, I'd rather just do analog->dstar. Wondering if anyone on here is doing this and how they went about it. Thank You


 

On 1/12/20 8:53 am, Steve N4IRS wrote:
It would be:
 ASL <-> Analog_Bridge <-> (DStar, using hardware USB chip) <->
MMDVM_Bridge <-> ircDDBGateway <-> xlxd

I don't know if ircDDBGateway and XLX can exist on the same machine. I
assume it can.
From memory, they both listen on the same ports.  I had to move
ircDDBGateway off the host I was running xlxd on in my setup.

--
73 de Tony VK3JED/VK3IRL
http://vkradio.com


Steve N4IRS
 

Should be able to move one of the ports.

On 11/30/20 7:42 PM, Tony Langdon wrote:
On 1/12/20 8:53 am, Steve N4IRS wrote:
It would be:
 ASL <-> Analog_Bridge <-> (DStar, using hardware USB chip) <->
MMDVM_Bridge <-> ircDDBGateway <-> xlxd

I don't know if ircDDBGateway and XLX can exist on the same machine. I
assume it can.
From memory, they both listen on the same ports.  I had to move
ircDDBGateway off the host I was running xlxd on in my setup.


 

I don't think so, because they are D-STAR protocol ports, which are
fixed (DPlus, DExtra, etc). 

xlxd:
udp        0      0 103.4.234.160:8880     
0.0.0.0:*                           4607/xlxd
udp        0      0 103.4.234.160:10001    
0.0.0.0:*                           4607/xlxd
udp        0      0 103.4.234.160:10002    
0.0.0.0:*                           4607/xlxd
udp        0      0 103.4.234.160:30001    
0.0.0.0:*                           4607/xlxd
udp        0      0 103.4.234.160:30051    
0.0.0.0:*                           4607/xlxd
udp        0      0 103.4.234.160:10100    
0.0.0.0:*                           4607/xlxd
udp        0      0 103.4.234.160:42000    
0.0.0.0:*                           4607/xlxd
udp        0      0 103.4.234.160:20001    
0.0.0.0:*                           4607/xlxd
udp        0      0 103.4.234.160:12345    
0.0.0.0:*                           4607/xlxd
udp        0      0 103.4.234.160:12346    
0.0.0.0:*                           4607/xlxd
udp        0      0 103.4.234.160:40000    
0.0.0.0:*                           4607/xlxd
udp        0      0 103.4.234.160:62030    
0.0.0.0:*                           4607/xlxd

ircDDBgateway
udp        0      0 127.0.0.1:20001        
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 127.0.0.1:20002        
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 127.0.0.1:20003        
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 127.0.0.1:20004        
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 127.0.0.1:20005        
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 127.0.0.1:20006        
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 127.0.0.1:20007        
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 10.43.21.136:20010     
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:40000          
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:30001          
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:30002          
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:30003          
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:30004          
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:30005          
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:30006          
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:30007          
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:30051          
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:30052          
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:30053          
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:30054          
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:30055          
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:30056          
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:30057          
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:30062          
0.0.0.0:*                           3484/ircddbgatewayd

On 1/12/20 11:44 am, Steve N4IRS wrote:
Should be able to move one of the ports.

On 11/30/20 7:42 PM, Tony Langdon wrote:
On 1/12/20 8:53 am, Steve N4IRS wrote:
It would be:
  ASL <-> Analog_Bridge <-> (DStar, using hardware USB chip) <->
MMDVM_Bridge <-> ircDDBGateway <-> xlxd

I don't know if ircDDBGateway and XLX can exist on the same machine. I
assume it can.
 From memory, they both listen on the same ports.  I had to move
ircDDBGateway off the host I was running xlxd on in my setup.




--
73 de Tony VK3JED/VK3IRL
http://vkradio.com


va3dxv
 

Yeah I thought I'd be clever and change the ircddbgateway ports (./Common/DStarDefines.h) and recompile but that just confused it, now seems to try to make the outgoing connections on those ports.


Steve N4IRS
 

Ircddbgateway is installed by the image or by the system builder script.

Sent by smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Ken KE2N via groups.io <ke2n@...>
Sent: Friday, December 18, 2020 11:23:13 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] ASL <-> D-Star <-> xlxd
 
NXDN, P25 and YSF gateways are included with DVSM.  But ircddbgateway is not..
Where should I pull ircddbgateway from (to be assured it will work with MMDVM_Bridge)?

Is it this one?     

https://github.com/g4klx/ircddbgateway



Tnx
Ken
KE2N


Steve N4IRS
 
Edited

So,
I was playing around this morning. I'll preface this as I can't even spell xlxd.
I find xlxd listens on a number of UDP ports, some of which conflict with ircDDBGateway.
This is a systemctl status after starting xlxd on a DVSwitch Server

Dec 19 12:07:27 new xlxd[1337]: Read 162240 DMR ids from xlxapi.rlx.lu database
Dec 19 12:07:28 new xlxd[1337]: Read 6004 YSF nodes from xlxapi.rlx.lu database
Dec 19 12:07:28 new xlxd[1337]: Error opening socket on port UDP30001 on ip 44.103.34.85
Dec 19 12:07:28 new xlxd[1337]: Error opening socket on port UDP30051 on ip 44.103.34.85
Dec 19 12:07:28 new xlxd[1337]: Error opening socket on port UDP42000 on ip 44.103.34.85
Dec 19 12:07:28 new xlxd[1337]: Error opening socket on port UDP40000 on ip 44.103.34.85
Dec 19 12:07:28 new xlxd[1337]: Error opening socket on port UDP12346 on ip 44.103.34.85
Dec 19 12:07:28 new xlxd[1337]: Error opening socket on port UDP12345 on ip 44.103.34.85
Dec 19 12:07:28 new xlxd[1337]: Error opening raw socket for ICMP
Dec 19 12:07:28 new xlxd[1337]: Error starting reflector
 
It seems the default startup for xlxd is: xlxd XLX999 192.168.178.212 127.0.0.1
Question, what is xlxd listening to 127.0.0.1 for?
If I start xlxd without the 127.0.0.1 address, the daemon starts with no error.

AH! if I start xlxd without 127.0.0.1 it starts, but is not listening to any UDP ports...

Comments?


Doug - W4DBG
 

I believe it is looking for AMBE transcoding. 

I am no expert though. 

Just trying to help :)




On Sat, Dec 19, 2020 at 11:25 AM Steve N4IRS <szingman@...> wrote:

[Edited Message Follows]

So,
I was playing around this morning. I'll preface this as I can't even spell xlxd.
I find xlxd listens on a number of UDP ports, some of which conflict with ircDDBGateway.
This is a systemctl status after starting xlxd on a DVSwitch Server

Dec 19 12:07:27 new xlxd[1337]: Read 162240 DMR ids from xlxapi.rlx.lu database
Dec 19 12:07:28 new xlxd[1337]: Read 6004 YSF nodes from xlxapi.rlx.lu database
Dec 19 12:07:28 new xlxd[1337]: Error opening socket on port UDP30001 on ip 44.103.34.85
Dec 19 12:07:28 new xlxd[1337]: Error opening socket on port UDP30051 on ip 44.103.34.85
Dec 19 12:07:28 new xlxd[1337]: Error opening socket on port UDP42000 on ip 44.103.34.85
Dec 19 12:07:28 new xlxd[1337]: Error opening socket on port UDP40000 on ip 44.103.34.85
Dec 19 12:07:28 new xlxd[1337]: Error opening socket on port UDP12346 on ip 44.103.34.85
Dec 19 12:07:28 new xlxd[1337]: Error opening socket on port UDP12345 on ip 44.103.34.85
Dec 19 12:07:28 new xlxd[1337]: Error opening raw socket for ICMP
Dec 19 12:07:28 new xlxd[1337]: Error starting reflector
 
It seems the default startup for xlxd is: xlxd XLX999 192.168.178.212 127.0.0.1
Question, what is xlxd listening to 127.0.0.1 for?
If I start xlxd without the 127.0.0.1 address, the daemon starts with no error.

AH! if I start xlxd without 127.0.0.1 it starts, but is not listening to any UDP ports...

Comments?

--
Doug Gooden
troytrojan@...


Charles Wiant
 

If I am not mistaken the 127.0.0.1 is supposed to be ambed.

 

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of Steve N4IRS
Sent: Saturday, December 19, 2020 11:23 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] ASL <-> D-Star <-> xlxd

 

[Edited Message Follows]

So,
I was playing around this morning. I'll preface this as I can't even spell xlxd.
I find xlxd listens on a number of UDP ports, some of which conflict with ircDDBGateway.
This is a systemctl status after starting xlxd on a DVSwitch Server


Dec 19 12:07:27 new xlxd[1337]: Read 162240 DMR ids from xlxapi.rlx.lu database

Dec 19 12:07:28 new xlxd[1337]: Read 6004 YSF nodes from xlxapi.rlx.lu database

Dec 19 12:07:28 new xlxd[1337]: Error opening socket on port UDP30001 on ip 44.103.34.85

Dec 19 12:07:28 new xlxd[1337]: Error opening socket on port UDP30051 on ip 44.103.34.85

Dec 19 12:07:28 new xlxd[1337]: Error opening socket on port UDP42000 on ip 44.103.34.85

Dec 19 12:07:28 new xlxd[1337]: Error opening socket on port UDP40000 on ip 44.103.34.85

Dec 19 12:07:28 new xlxd[1337]: Error opening socket on port UDP12346 on ip 44.103.34.85

Dec 19 12:07:28 new xlxd[1337]: Error opening socket on port UDP12345 on ip 44.103.34.85

Dec 19 12:07:28 new xlxd[1337]: Error opening raw socket for ICMP

Dec 19 12:07:28 new xlxd[1337]: Error starting reflector

 
It seems the default startup for xlxd is: xlxd XLX999 192.168.178.212 127.0.0.1
Question, what is xlxd listening to 127.0.0.1 for?
If I start xlxd without the 127.0.0.1 address, the daemon starts with no error.

AH! if I start xlxd without 127.0.0.1 it starts, but is not listening to any UDP ports...

Comments?


Steve N4IRS
 

As I found, without 127.0.0.1 xlxd is not listening on any UDP ports. I did not think xlxd HAD to be used with a vocoder if all it was to do is be a D-Star reflector.
Not high on my list of things to care about, I was just playing and or bringing up a test D-Star or DMR or YSF reflector.

Steve

On 12/19/20 9:52 PM, Charles Wiant via groups.io wrote:

If I am not mistaken the 127.0.0.1 is supposed to be ambed.

 

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of Steve N4IRS
Sent: Saturday, December 19, 2020 11:23 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] ASL <-> D-Star <-> xlxd

 

[Edited Message Follows]

So,
I was playing around this morning. I'll preface this as I can't even spell xlxd.
I find xlxd listens on a number of UDP ports, some of which conflict with ircDDBGateway.
This is a systemctl status after starting xlxd on a DVSwitch Server


Dec 19 12:07:27 new xlxd[1337]: Read 162240 DMR ids from xlxapi.rlx.lu database

Dec 19 12:07:28 new xlxd[1337]: Read 6004 YSF nodes from xlxapi.rlx.lu database

Dec 19 12:07:28 new xlxd[1337]: Error opening socket on port UDP30001 on ip 44.103.34.85

Dec 19 12:07:28 new xlxd[1337]: Error opening socket on port UDP30051 on ip 44.103.34.85

Dec 19 12:07:28 new xlxd[1337]: Error opening socket on port UDP42000 on ip 44.103.34.85

Dec 19 12:07:28 new xlxd[1337]: Error opening socket on port UDP40000 on ip 44.103.34.85

Dec 19 12:07:28 new xlxd[1337]: Error opening socket on port UDP12346 on ip 44.103.34.85

Dec 19 12:07:28 new xlxd[1337]: Error opening socket on port UDP12345 on ip 44.103.34.85

Dec 19 12:07:28 new xlxd[1337]: Error opening raw socket for ICMP

Dec 19 12:07:28 new xlxd[1337]: Error starting reflector

 
It seems the default startup for xlxd is: xlxd XLX999 192.168.178.212 127.0.0.1
Question, what is xlxd listening to 127.0.0.1 for?
If I start xlxd without the 127.0.0.1 address, the daemon starts with no error.

AH! if I start xlxd without 127.0.0.1 it starts, but is not listening to any UDP ports...

Comments?



 

On 20/12/20 1:56 pm, Steve N4IRS wrote:
As I found, without 127.0.0.1 xlxd is not listening on any UDP ports.
I did not think xlxd HAD to be used with a vocoder if all it was to do
is be a D-Star reflector.
Not high on my list of things to care about, I was just playing and or
bringing up a test D-Star or DMR or YSF reflector.
You are correct, xlxd doesn't need the AMBE chip or server, unless you
actually want to transcode.  I'm running an xlxd reflector without the
AMBE transcoder.  I am using primarily two modules.  One is for D-STAR
on my multimode gateway (XLX432 D) and another is a YSF reflector.  
Other than the YSF channel, the rest are available for D-STAR use.

--
73 de Tony VK3JED/VK3IRL
http://vkradio.com


 

On 20/12/20 4:23 am, Steve N4IRS wrote:

[Edited Message Follows]

So,
I was playing around this morning. I'll preface this as I can't even
spell xlxd.
I find xlxd listens on a number of UDP ports, some of which conflict
with ircDDBGateway.
This is a systemctl status after starting xlxd on a DVSwitch Server
Yes, that's correct, because both ircDDBGateway and xlxd are able to
listen for incoming traffic on the same protocols.  You need to bind
them to separate IPs, or run them on separate servers.  I now do the
latter, where I run xlxd alongside AllStar, YSFReflector and
P25Reflector on one server, while DVSwitch itself runs on another
server.  I was able to have all of the reflectors, except for xlxd on
the same server (using different ports for YSFReflector and xlxd's YSF
support), plus AllStar on the one server, but separated out DVSwitch
when the new version came out for ease of maintenance, and not wanting
to conflict with old code.

And yes, 127.0.0.1 would be for ambed, which I'm not running here, as my
xlxd currently does no transcoding. 

--
73 de Tony VK3JED/VK3IRL
http://vkradio.com