Welcome to DVSwitch
Purpose
1) Allows “local” networking during an outage of the regional national/international network server.
2) Allows a local network operator to “blend” upstream feeds from different Networks (capital N on purpose). These Networks can’t get their act together and learn how to play nice with each other (everyone guilty as far as we are concerned). They may not like people doing this, but the solution is to grow up and work with each other, and not keep trying to force people to take sides.
3) Allows local segregation of localized traffic with more flexibility.
4) Allows experimentation with linking and how it’s done (part 97 specifies experimentation and advancement of the radio art are a core part of amateur radio).
Mission Statement/Position
WHEREAS the Networks continue to be largely islands and are not working together to create a unified network of Networks.
WHEREAS no firm reason has been given by any of the Networks why a *competent* local network operator cannot make this work effectively.
(US ONLY)
WHEREAS 47 CFR 97 (Amateur Radio Service) specifies that a core component of amateur radio is experimentation and advancement of the radio art [97.1(b)].
BE IT RESOLVED the core group of US amateur radio operators and experimenters organized around the DVSwitch project, and in the spirit of USA 47 CFR 97 and its intentions, support the *responsible* and *thoughtful* use of digital voice networking tools to create localized networks that will interconnect to the national/international Networks, and will support users of its tools in order to do this in the most effective and sustainable way possible.
|
Re: Confused hblink and MMDVM bridge.
G4WXN@...
OK I think I have this now. I have created MB ini files for each network, the scripts copy this over the MB ini file and then restarts the MB service. This works fine for BM and TGIF, however I still cannot get DMR+ to work. I tried using the one that is in the tune string 78.129.135.43 but again it fails. --
|
|
|
|
Re: Adding P25 to existing YSF and DMR bridge
Gary, KE8O
Steve,
I changed the YSF2DMR to a different DRM ID. I will arrange another test and provide feedback.
|
|
|
|
Re: Adding P25 to existing YSF and DMR bridge
That's what I expected. Both bridges are logging into TGIF with the
same DMR ID (139360) I can see where TGIF might be unhappy. Try 2
different IDs.
toggle quoted messageShow quoted text
Steve
On 12/20/20 5:16 PM, Gary, KE8O wrote:
Steve,
|
|
|
|
Re: Adding P25 to existing YSF and DMR bridge
Gary, KE8O
Steve,
Here's the two INI files.
|
|
|
|
Re: Adding P25 to existing YSF and DMR bridge
Gary,
toggle quoted messageShow quoted text
I see no port conflicts. Please send the two MMDVM_Bridge.ini files.
On 12/20/20 2:35 PM, Gary, KE8O wrote:
Hi Steve,
|
|
|
|
Re: Adding P25 to existing YSF and DMR bridge
Gary, KE8O
Hi Steve,
Sorry for the delay. My repeater decided to go belly up this weekend. But its working again. Attached are the two UDP captures with only one bridge running at a time.
|
|
|
|
Re: DVSwitch Dashboard Web Port
EA4GAX - Sergio
Ok, excelent.
Thank yor
|
|
|
|
Re: DVSwitch Dashboard Web Port
Sergio,
toggle quoted messageShow quoted text
The port number can be changed. edit /lib/systemd/system/webproxy.service See this line: ExecStart=/usr/bin/node /opt/Web_Proxy/proxy.js 8080 2222 edit to taste and reboot. 73, Steve N4IRS
On 12/20/20 6:38 AM, EA4GAX - Sergio
wrote:
Hi Steve and all, Is possible change port 8080? This port is to use for the other machine.
|
|
|
|
Re: DVSwitch Dashboard Web Port
EA4GAX - Sergio
Hi Steve and all, Is possible change port 8080? This port is to use for the other machine.
Thank you.
|
|
|
|
Re: ASL <-> D-Star <-> xlxd
On 20/12/20 4:23 am, Steve N4IRS wrote:
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
|
|
|
|
Re: ASL <-> D-Star <-> xlxd
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.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
|
|
|
|
Re: ASL <-> D-Star <-> xlxd
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.
toggle quoted messageShow quoted text
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:
|
|
|
|
Re: ASL <-> D-Star <-> xlxd
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
[Edited Message Follows] So,
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
|
|
|
|
Re: ASL <-> D-Star <-> xlxd
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:
--
Doug Gooden troytrojan@...
|
|
|
|
Re: ASL <-> D-Star <-> xlxd
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?
|
|
|
|
Re: ASL <-> D-Star <-> xlxd
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
|
|
|
|
Re: Adding P25 to existing YSF and DMR bridge
Complete bridge end to end. From what you told me, if only one
bridge is running it works fine (either one) I want you to capture
the UDP data for tach bridge running on its own.
toggle quoted messageShow quoted text
On 12/18/2020 3:35 PM, Gary, KE8O
wrote:
Ken
|
|
|
|
Re: Dmr Utils
root@dvswitch-server:/opt/dmr_utils3# ls
dmr_utils3 install.sh LICENSE README.rst setup.py
root@dvswitch-server:/opt/dmr_utils3# cd dmr_utils3
root@dvswitch-server:/opt/dmr_utils3/dmr_utils3# ls
ambe.py const.py encode.py hamming.py rs129.py
ambe_utils.py crc.py golay.py __init__.py utils.py
bptc.py decode.py golay_tables.py qr.py
root@dvswitch-server:/opt/dmr_utils3/dmr_utils3#
Something I did setup. I don't see HBlink3 directory. Lost and still looking 73 Don va7dgp/va7qu
|
|
|
|
Re: Adding P25 to existing YSF and DMR bridge
Gary, KE8O
Sorry meant to say Steve, was talking to K2KXK Ken when I was typing.
|
|
|
|
Re: Adding P25 to existing YSF and DMR bridge
Gary, KE8O
Ken
For clarification. When you say bridge are you referring to the MB instances only, or the complete bridge end to end..... i.e MB only for my YSF to DMR, then stop that MB, and for the P25 to DMR start its MB and both AB's ? Thanks
|
|
|