Date   

Re: MMDVM_Bridge segment fault issue

Steve N4IRS
 

I pushed the latest update to MMDVM_Bridge this morning for the AMD64 <https://github.com/DVSwitch/MMDVM_Bridge/raw/master/bin/MMDVM_Bridge.amd64>
Please replace your existing MB and retest.

Steve N4IRS

On 9/14/2020 2:28 PM, swinger72@... wrote:
Hi all. I have been riding for 2 mmdvm_bridge for 1 years already. 1 link my ysf reflector  and the other another ysf reflector . for 4 days an instance has stopped by itself and the only message is segmentation fault. I tried to rebuild without success. this instance is a copy of the original one and the original works fine. now i'm at heart i also notice that at the time of the crash which is never constant that a time lag appears.
; MMDVM_Bridge export / import configuration file.
;   This file should be placed along side of MMDVM_Bridge or it can be
;   supplied as a path on the MMDVM_BRIDGE environment variable.

; Configure the Quantar Repeater Partner
; Note that the TX and RX ports are already reversed for MMDVM_Bridge <--> Quantar_Bridge
;[QUANTAR]
;logFilePath = /var/log/Quantar_Bridge.log
;Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
;TXPort =                  ; Port to send AMBE TLV frames to (export)
;RXPort =                   ; Port to listen on (import)
;quantarPort = 1994              ; HDLC frames To/From the Quantar repeater
;logLevel = 2                    ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
;debug = 0                       ; Debug 0 = off, 1 = on (adds lots of additional messages)

; Configure the DMR Partner
; Audio format is AMBE 72 bit
;[DMR]
;Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
;TXPort =                   ; Port to send AMBE TLV frames to (export)
;RXPort =                  ; Port to listen on (import)
;Slot = 2                        ; Export slot

; Configure the D-Star Partner
; Audio format is AMBE 48 bit (DSAMBE)
;[DSTAR]
;Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
;TXPort =                   ; Port to send AMBE TLV frames to (export)
;RXPort =                   ; Port to listen on (import)
;FallbackID = 1234567            ; In case we can not find a valid DMR id in the database, export this one
;ExportTG = 9                    ; Which TG to export
;Slot = 2                        ; Export slot

; Configure the NXDN Partner
; Audio format is AMBE 72 bit
;[NXDN]
;Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
;TXPort =                  ; Port to send AMBE TLV frames to (export)
;RXPort =                   ; Port to listen on (import)
;FallbackID = 1234567            ; In case we can not find a valid DMR id in the database, export this one
;NXDNFallbackID  = 12345         ; Use this ID when the input DMR ID is not found in the database
;Translate = 1234=4321           ; Translate NXDN TG < -- > DMR TG (bidirectional)
;Slot = 2                        ; Export slot

; Configure the P25 Partner
; Audio format is IMBE 88 bit
;[P25]
;Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
;TXPort =                   ; Port to send AMBE TLV frames to (export)
;RXPort =                  ; Port to listen on (import)
;Slot = 2                        ; Export slot

; Configure the Yaesu Fusion Partner
; Audio format is AMBE 72 bit
; Audio format is IMBE 88 bit
[YSF]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 43500                  ; Port to send AMBE TLV frames to (export)
RXPort = 42500                  ; Port to listen on (import)
FallbackID = 1234567            ; In case we can not find a valid DMR id in the database, export this one
ExportTG =  1234                 ; Which TG to export
Slot = 2                        ; Export slot



[General]
Callsign=F1ZIT-L
Id=302252899
Timeout=180
Duplex=0

[Info]
RXFrequency=222340000
TXFrequency=224940000
Power=1
Latitude=41.7333
Longitude=-50.3999
Height=0
Location=Iceberg, North Atlantic
Description=MMDVM_Bridge2
URL=

[Log]
# Logging levels, 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
DisplayLevel=1
FileLevel=1
FilePath=/var/log/MMDVM_Bridge2
FileRoot=MMDVM_Bridge

[DMR Id Lookup]
File=/var/lib/mmdvm/DMRIds2.dat
Time=24

[NXDN Id Lookup]
File=/var/lib/mmdvm/NXDN.csv
Time=24

[Modem]
Port=/dev/null
RSSIMappingFile=RSSI.dat
Trace=0
Debug=0

[D-Star]
Enable=0
Module=C

[DMR]
Enable=0
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0

[System Fusion]
Enable=1

[P25]
Enable=0
NAC=293

[NXDN]
Enable=0
RAN=1
Id=12345

[D-Star Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=20010
LocalPort=20011
Debug=0

[DMR Network]
Enable=0
Address=38.110.97.167
Port=62030
Jitter=500
Local=62032
Password=CANFR
# for DMR+ see https://github.com/DVSwitch/MMDVM_Bridge/blob/master/DOC/DMRplus_startup_options.md
# for XLX the syntax is: Options=XLX:4009
# Options=
Slot1=1
Slot2=1
Debug=0

[System Fusion Network]
Enable=1
LocalAddress=127.0.0.1
LocalPort=3299
GatewayAddress=127.0.0.1
GatewayPort=42000
Debug=0

[P25 Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=32010
LocalPort=42020
Debug=0

[NXDN Network]
Enable=0
#LocalAddress=127.0.0.1
Debug=0
LocalPort=14021
GatewayAddress=127.0.0.1
GatewayPort=14020






DMR to Analog ASL Bridge

Marshall Oldham
 

Okay, I know this has probably been asked many times before.

I did do a search, with lots of results that comes back, almost too much information. :)

I am wondering what the most current (easiest) way to go about building a DMR to Analog bridge is using ASL. 

I have a Raspberry Pi and a ThumbDV DV3000U.

My end goal is to be able to bridge DMR to an Analog system. 

Thanks 

Marshall - ke6pcv 


MMDVM_Bridge segment fault issue

swinger72@...
 
Edited

Hi all. I have been riding for 2 mmdvm_bridge for 1 years already. 1 link my ysf reflector  and the other another ysf reflector . for 4 days an instance has stopped by itself and the only message is segmentation fault. I tried to rebuild without success. this instance is a copy of the original one and the original works fine. now i'm at heart i also notice that at the time of the crash which is never constant that a time lag appears.
; MMDVM_Bridge export / import configuration file.
;   This file should be placed along side of MMDVM_Bridge or it can be
;   supplied as a path on the MMDVM_BRIDGE environment variable.

; Configure the Quantar Repeater Partner
; Note that the TX and RX ports are already reversed for MMDVM_Bridge <--> Quantar_Bridge
;[QUANTAR]
;logFilePath = /var/log/Quantar_Bridge.log
;Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
;TXPort =                  ; Port to send AMBE TLV frames to (export)
;RXPort =                   ; Port to listen on (import)
;quantarPort = 1994              ; HDLC frames To/From the Quantar repeater
;logLevel = 2                    ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
;debug = 0                       ; Debug 0 = off, 1 = on (adds lots of additional messages)

; Configure the DMR Partner
; Audio format is AMBE 72 bit
;[DMR]
;Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
;TXPort =                   ; Port to send AMBE TLV frames to (export)
;RXPort =                  ; Port to listen on (import)
;Slot = 2                        ; Export slot

; Configure the D-Star Partner
; Audio format is AMBE 48 bit (DSAMBE)
;[DSTAR]
;Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
;TXPort =                   ; Port to send AMBE TLV frames to (export)
;RXPort =                   ; Port to listen on (import)
;FallbackID = 1234567            ; In case we can not find a valid DMR id in the database, export this one
;ExportTG = 9                    ; Which TG to export
;Slot = 2                        ; Export slot

; Configure the NXDN Partner
; Audio format is AMBE 72 bit
;[NXDN]
;Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
;TXPort =                  ; Port to send AMBE TLV frames to (export)
;RXPort =                   ; Port to listen on (import)
;FallbackID = 1234567            ; In case we can not find a valid DMR id in the database, export this one
;NXDNFallbackID  = 12345         ; Use this ID when the input DMR ID is not found in the database
;Translate = 1234=4321           ; Translate NXDN TG < -- > DMR TG (bidirectional)
;Slot = 2                        ; Export slot

; Configure the P25 Partner
; Audio format is IMBE 88 bit
;[P25]
;Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
;TXPort =                   ; Port to send AMBE TLV frames to (export)
;RXPort =                  ; Port to listen on (import)
;Slot = 2                        ; Export slot

; Configure the Yaesu Fusion Partner
; Audio format is AMBE 72 bit
; Audio format is IMBE 88 bit
[YSF]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 43500                  ; Port to send AMBE TLV frames to (export)
RXPort = 42500                  ; Port to listen on (import)
FallbackID = 1234567            ; In case we can not find a valid DMR id in the database, export this one
ExportTG =  1234                 ; Which TG to export
Slot = 2                        ; Export slot



[General]
Callsign=F1ZIT-L
Id=302252899
Timeout=180
Duplex=0

[Info]
RXFrequency=222340000
TXFrequency=224940000
Power=1
Latitude=41.7333
Longitude=-50.3999
Height=0
Location=Iceberg, North Atlantic
Description=MMDVM_Bridge2
URL=

[Log]
# Logging levels, 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
DisplayLevel=1
FileLevel=1
FilePath=/var/log/MMDVM_Bridge2
FileRoot=MMDVM_Bridge

[DMR Id Lookup]
File=/var/lib/mmdvm/DMRIds2.dat
Time=24

[NXDN Id Lookup]
File=/var/lib/mmdvm/NXDN.csv
Time=24

[Modem]
Port=/dev/null
RSSIMappingFile=RSSI.dat
Trace=0
Debug=0

[D-Star]
Enable=0
Module=C

[DMR]
Enable=0
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0

[System Fusion]
Enable=1

[P25]
Enable=0
NAC=293

[NXDN]
Enable=0
RAN=1
Id=12345

[D-Star Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=20010
LocalPort=20011
Debug=0

[DMR Network]
Enable=0
Address=
Port=62030
Jitter=500
Local=62032
Password=
# for DMR+ see https://github.com/DVSwitch/MMDVM_Bridge/blob/master/DOC/DMRplus_startup_options.md
# for XLX the syntax is: Options=XLX:4009
# Options=
Slot1=1
Slot2=1
Debug=0

[System Fusion Network]
Enable=1
LocalAddress=127.0.0.1
LocalPort=3299
GatewayAddress=127.0.0.1
GatewayPort=42000
Debug=0

[P25 Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=32010
LocalPort=42020
Debug=0

[NXDN Network]
Enable=0
#LocalAddress=127.0.0.1
Debug=0
LocalPort=14021
GatewayAddress=127.0.0.1
GatewayPort=14020





Re: XLX Reflector to DMR talk group bridge on server cloud issue

Steve N4IRS
 

1: yes
2: yes, just in case, I built the most current amd64 binary this morning.
3: will try to look at logs later today.

Steve N4IRS

On 9/14/20 1:42 AM, David Young wrote:
Ok,  I read through the earlier posts on using DVSwitch to bridge XLX reflector to DMR talk group.  Per what I read there was an addition made to MMDVM_Bridge which when using DVSwitch would allow bridging without using DMRGateway.  It appears from the post thread that the changes were only made to the MMDVM_Bridge binary which is used for a Raspberry Pi.  I am trying to bridge XLX to TGIF DMR talk group from a cloud server using the MMDVM_Bridge binary updated to the latest version available for AMD_64 without using DMRGateway.  I have copied the new DVSwitch.ini file which includes the additional entry lines in the DMR standza and when I configure the bridge using separate copies of MMDVM_Bridge in different folders with two different DVSwitch.ini files, one for each MMDVM_Bridge it appears to work as I hoped.  Here's my problem, after some period of time and in the log files included in this post that time period is approximately 2.5 hours, MMDVM shuts down and I get an error message upon MMDVM restarting automatically stating "cannot bind the UDP address, err 98" and next line states "cannot open listener port 31103".  These same error messages also show up in the log for the XLX MMDVM_Bridge.  I have tried changing the DVSwitch ports 31100 and 31103 to 31600 and 31603, but get the same results after running for some time period.  So my questions are:
1.  Have the updates stated in earlier posts made for MMDVM_Bridge for Raspberry Pi systems been made also to MMDVM_Bridge for amd_64?
2.  If not, will the amd_64 MMDVM_Bridge binary be updated sometime soon?
3.  If they have already been updated, any suggestions on how to fix the above errors from occurring?

Dave

--
Dave WB6DTB


XLX Reflector to DMR talk group bridge on server cloud issue

David Young
 

Ok,  I read through the earlier posts on using DVSwitch to bridge XLX reflector to DMR talk group.  Per what I read there was an addition made to MMDVM_Bridge which when using DVSwitch would allow bridging without using DMRGateway.  It appears from the post thread that the changes were only made to the MMDVM_Bridge binary which is used for a Raspberry Pi.  I am trying to bridge XLX to TGIF DMR talk group from a cloud server using the MMDVM_Bridge binary updated to the latest version available for AMD_64 without using DMRGateway.  I have copied the new DVSwitch.ini file which includes the additional entry lines in the DMR standza and when I configure the bridge using separate copies of MMDVM_Bridge in different folders with two different DVSwitch.ini files, one for each MMDVM_Bridge it appears to work as I hoped.  Here's my problem, after some period of time and in the log files included in this post that time period is approximately 2.5 hours, MMDVM shuts down and I get an error message upon MMDVM restarting automatically stating "cannot bind the UDP address, err 98" and next line states "cannot open listener port 31103".  These same error messages also show up in the log for the XLX MMDVM_Bridge.  I have tried changing the DVSwitch ports 31100 and 31103 to 31600 and 31603, but get the same results after running for some time period.  So my questions are:
1.  Have the updates stated in earlier posts made for MMDVM_Bridge for Raspberry Pi systems been made also to MMDVM_Bridge for amd_64?
2.  If not, will the amd_64 MMDVM_Bridge binary be updated sometime soon?
3.  If they have already been updated, any suggestions on how to fix the above errors from occurring?

Dave

--
Dave WB6DTB


Re: Analog_Bridge not outputting to STDOUT or STDERR?

Matthew 2E0SIP
 

Thanks for that Steve, thats pretty conclusive. I'll try to figure out whats going on at my end.

Matthew


Re: Analog_Bridge not outputting to STDOUT or STDERR?

Steve N4IRS
 

root@dvswitch-server:/opt/Analog_Bridge# uname -a
Linux dvswitch-server 5.4.51-v7+ #1333 SMP Mon Aug 10 16:45:19 BST 2020 armv7l GNU/Linux

root@dvswitch-server:/opt/Analog_Bridge# wget https://github.com/DVSwitch/Analog_Bridge/raw/master/bin/Analog_Bridge.armhf
--2020-09-12 14:17:49--  https://github.com/DVSwitch/Analog_Bridge/raw/master/bin/Analog_Bridge.armhf
Resolving github.com (github.com)... 140.82.114.3
Connecting to github.com (github.com)|140.82.114.3|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://raw.githubusercontent.com/DVSwitch/Analog_Bridge/master/bin/Analog_Bridge.armhf [following]
--2020-09-12 14:17:50--  https://raw.githubusercontent.com/DVSwitch/Analog_Bridge/master/bin/Analog_Bridge.armhf
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 199.232.0.133
Connecting to raw.githubusercontent.com (raw.githubusercontent.comroot@dvswitch-server:/opt/Analog_Bridge# uname -a
Linux dvswitch-server 5.4.51-v7+ #1333 SMP Mon Aug 10 16:45:19 BST 2020 armv7l GNU/Linux
)|199.232.0.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 486128 (475K) [application/octet-stream]
Saving to: ‘Analog_Bridge.armhf’

Analog_Bridge.armhf                                         100%[=========================================================================================================================================>] 474.73K  --.-KB/s    in 0.1s   

2020-09-12 14:17:50 (4.39 MB/s) - ‘Analog_Bridge.armhf’ saved [486128/486128]

root@dvswitch-server:/opt/Analog_Bridge# mv Analog_Bridge.armhf Analog_Bridge
root@dvswitch-server:/opt/Analog_Bridge# chmod +x Analog_Bridge
root@dvswitch-server:/opt/Analog_Bridge# ./Analog_Bridge -v
Analog_Bridge version 1.5.9
root@dvswitch-server:/opt/Analog_Bridge# ./Analog_Bridge Analog_Bridge.ini >stdout.log 2>stderror.log
^C
root@dvswitch-server:/opt/Analog_Bridge# more stdout.log
I: 2020-09-12 18:18:57.053 Analog_Bridge Version 1.5.9 Fri  4 Sep 22:56:26 UTC 2020
I: 2020-09-12 18:18:57.054 Copyright (C) 2018, 2019, 2020 DVSwitch, INAD.
I: 2020-09-12 18:18:57.054 Created by Mike N4IRR and Steve N4IRSroot@dvswitch-server:/opt/Analog_Bridge# uname -a
Linux dvswitch-server 5.4.51-v7+ #1333 SMP Mon Aug 10 16:45:19 BST 2020 armv7l GNU/Linux

I: 2020-09-12 18:18:57.054 Analog_Bridge comes with ABSOLUTELY NO WARRANTY
I: 2020-09-12 18:18:57.054
I: 2020-09-12 18:18:57.054 This software is for use on amateur radio networks only,
I: 2020-09-12 18:18:57.054 it is to be used for educational purposes only. Its use on
I: 2020-09-12 18:18:57.054 commercial networks is strictly prohibited.
I: 2020-09-12 18:18:57.054
I: 2020-09-12 18:18:57.054 Analog_Bridge is starting
M: 2020-09-12 18:18:57.054 Setting [MACROS] DMR -> /opt/MMDVM_Bridge/dvswitch.sh mode DMR
M: 2020-09-12 18:18:57.054 Setting [MACROS] DSTAR -> /opt/MMDVM_Bridge/dvswitch.sh mode DSTAR
M: 2020-09-12 18:18:57.055 Setting [MACROS] NXDN -> /opt/MMDVM_Bridge/dvswitch.sh mode NXDN
M: 2020-09-12 18:18:57.055 Setting [MACROS] P25 -> /opt/MMDVM_Bridge/dvswitch.sh mode P25
M: 2020-09-12 18:18:57.055 Setting [MACROS] YSF -> /opt/MMDVM_Bridge/dvswitch.sh mode YSF
M: 2020-09-12 18:18:57.055 Setting [MACROS] dbupdate -> /opt/MMDVM_Bridge/dvswitch.sh collectProcessPushDataFiles
M: 2020-09-12 18:18:57.055 Setting [MACROS] 9876 -> /opt/Analog_Bridge/parrot.sh
M: 2020-09-12 18:18:57.055 Setting [] include -> dvsm.macro
M: 2020-09-12 18:18:57.055 Setting [GENERAL] logLevel -> 2
M: 2020-09-12 18:18:57.055 Setting [GENERAL] exportMetadata -> true
M: 2020-09-12 18:18:57.055 Setting [GENERAL] transferRootDir -> /tmp
M: 2020-09-12 18:18:57.055 Setting [GENERAL] subscriberFile -> /var/lib/dvswitch/subscriber_ids.csv
M: 2020-09-12 18:18:57.055 Setting [GENERAL] decoderFallBack -> true
M: 2020-09-12 18:18:57.055 Setting [GENERAL] useEmulator -> true
M: 2020-09-12 18:18:57.055 Setting [GENERAL] emulatorAddress -> 127.0.0.1:2470
M: 2020-09-12 18:18:57.055 Setting [AMBE_AUDIO] address -> 127.0.0.1
M: 2020-09-12 18:18:57.055 Setting [AMBE_AUDIO] txPort -> 31103
M: 2020-09-12 18:18:57.055 Setting [AMBE_AUDIO] rxPort -> 31100
M: 2020-09-12 18:18:57.055 Setting [AMBE_AUDIO] ambeMode -> DMR
M: 2020-09-12 18:18:57.055 Setting [AMBE_AUDIO] minTxTimeMS -> 2500
M: 2020-09-12 18:18:57.055 Setting [AMBE_AUDIO] gatewayDmrId -> 3112138
M: 2020-09-12 18:18:57.055 Setting [AMBE_AUDIO] repeaterID -> 311213811
M: 2020-09-12 18:18:57.055 Setting [AMBE_AUDIO] txTg -> 9
M: 2020-09-12 18:18:57.055 Setting [AMBE_AUDIO] txTs -> 2
M: 2020-09-12 18:18:57.055 Setting [AMBE_AUDIO] colorCode -> 1
M: 2020-09-12 18:18:57.056 Setting [USRP] address -> 127.0.0.1
M: 2020-09-12 18:18:57.056 Setting [USRP] txPort -> 54321
M: 2020-09-12 18:18:57.056 Setting [USRP] rxPort -> 54321
M: 2020-09-12 18:18:57.056 Setting [USRP] usrpAudio -> AUDIO_UNITY
M: 2020-09-12 18:18:57.056 Setting [USRP] usrpGain -> 1.10
M: 2020-09-12 18:18:57.056 Setting [USRP] usrpAGC -> -20,10,100
M: 2020-09-12 18:18:57.056 Setting [USRP] tlvAudio -> AUDIO_UNITY
M: 2020-09-12 18:18:57.056 Setting [USRP] tlvGain -> 0.35
I: 2020-09-12 18:18:57.056 Open UDP listener on 127.0.0.1:31100
I: 2020-09-12 18:18:57.056 Open USRP on 127.0.0.1:54321
M: 2020-09-12 18:18:57.056 Connecting to DV3000 hardware......
W: 2020-09-12 18:18:57.147 DV3000 did not reset at 127.0.0.1:2460
W: 2020-09-12 18:18:57.147 DV3000 not found at 127.0.0.1:2460 (Reset failed)
I: 2020-09-12 18:18:58.019 Subscriber IDs loaded: 172620
I: 2020-09-12 18:18:58.019 Default extended metadata <N4IRS>
I: 2020-09-12 18:18:58.019 Connecting to emulator on host 127.0.0.1:2470
W: 2020-09-12 18:18:58.019 Using software MBE decoder version 1.2.3
W: 2020-09-12 18:18:58.019 Using software OP25 IMBE/AMBE vocoder
W: 2020-09-12 18:18:58.020 WARNING, USRP can not have same ports (54321) defined for local network interface.  Using 169.254.42.42
I: 2020-09-12 18:18:58.020 Sending to USRP clients at 169.254.42.42 on port(s) 54321
I: 2020-09-12 18:18:58.020 Starting TLV --> Analog_Bridge (decoder) --> USRP thread
I: 2020-09-12 18:18:58.020 Starting USRP --> Analog_Bridge (encoder) -> TLV thread
root@dvswitch-server:/opt/Analog_Bridge# more stderror.log
Project 25 IMBE Encoder/Decoder Fixed-Point implementation
Developed by Pavel Yazev E-mail: pyazev@...
Version 1.0 (c) Copyright 2009
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; see the file ``LICENSE'' for details.

root@dvswitch-server:/opt/Analog_Bridge#



On 9/12/20 12:22 PM, Matthew 2E0SIP wrote:

Hi Steve, 

Thanks for checking. I think I'm still missing something. 

Do you get the same behaviour on the latest binary from the repo and supplied Analog_Bridge.ini?

If I do the following on a Pi running Raspbian (No docker) I still get an empty stdout.log, but if I run it without redirecting the output I see it in the console -

git clone https://github.com/DVSwitch/Analog_Bridge.git
cd Analog_Bridge/
./bin/Analog_Bridge.armhf Analog_Bridge.ini >stdout.log 2>stderr.log 

Thanks



Re: Analog_Bridge not outputting to STDOUT or STDERR?

Matthew 2E0SIP
 

Hi Steve, 

Thanks for checking. I think I'm still missing something. 

Do you get the same behaviour on the latest binary from the repo and supplied Analog_Bridge.ini?

If I do the following on a Pi running Raspbian (No docker) I still get an empty stdout.log, but if I run it without redirecting the output I see it in the console -

git clone https://github.com/DVSwitch/Analog_Bridge.git
cd Analog_Bridge/
./bin/Analog_Bridge.armhf Analog_Bridge.ini >stdout.log 2>stderr.log 

Thanks


Re: Analog_Bridge not outputting to STDOUT or STDERR?

Steve N4IRS
 

Matt,

I just ran a quick test on a RPi.

./Analog_Bridge Analog_Bridge.ini >stdout.log 2>stderror.log

root@dvswitch-server:/opt/Analog_Bridge# more stdout.log
I: 2020-09-11 22:52:09.963 Analog_Bridge Version 1.5.9 Fri  4 Sep 22:56:26 UTC 2020
I: 2020-09-11 22:52:09.964 Copyright (C) 2018, 2019, 2020 DVSwitch, INAD.
I: 2020-09-11 22:52:09.964 Created by Mike N4IRR and Steve N4IRS
I: 2020-09-11 22:52:09.964 Analog_Bridge comes with ABSOLUTELY NO WARRANTY
I: 2020-09-11 22:52:09.964
I: 2020-09-11 22:52:09.964 This software is for use on amateur radio networks only,
I: 2020-09-11 22:52:09.964 it is to be used for educational purposes only. Its use on
I: 2020-09-11 22:52:09.964 commercial networks is strictly prohibited.
I: 2020-09-11 22:52:09.964
I: 2020-09-11 22:52:09.964 Analog_Bridge is starting
M: 2020-09-11 22:52:09.965 Setting [MACROS] DMR -> /opt/MMDVM_Bridge/dvswitch.sh mode DMR
M: 2020-09-11 22:52:09.965 Setting [MACROS] DSTAR -> /opt/MMDVM_Bridge/dvswitch.sh mode DSTAR

root@dvswitch-server:/opt/Analog_Bridge# more stderr.log
more: stat of stderr.log failed: No such file or directory
root@dvswitch-server:/opt/Analog_Bridge# more stderror.log
Project 25 IMBE Encoder/Decoder Fixed-Point implementation
Developed by Pavel Yazev E-mail: pyazev@...
Version 1.0 (c) Copyright 2009
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; see the file ``LICENSE'' for details.

For stdout.log I did not include the complete output.

Steve N4IRS

On 9/11/20 6:40 PM, Matthew 2E0SIP wrote:
Hi All,

I am trying to run MMDVM_Bridge, Analog_Bridge etc in Docker to make my bridge a little more portable. If I actually get it working nicely I'll endeavour make it public.

By default docker writes the output to STDOUT and STDERR to the log, however with Analog_Bridge most of the output is missing. I've tried redirecting STD* to no avail. Please see the attached image - only the lines in red (STDERR) are included in the Docker logs.

I've done some googling and one theory is the process is writing directly to the TTY rather than STDOUT / STDERR

When someone gets a moment could they take a look at the code and confirm how these lines are being displayed?

Also whilst I'm here I was wondering if you could confirm if Analog_Bridge, MMDVM_Bridge etc support DNS? 

Thanks
Matthew
2E0SIP



Analog_Bridge not outputting to STDOUT or STDERR?

Matthew 2E0SIP
 

Hi All,

I am trying to run MMDVM_Bridge, Analog_Bridge etc in Docker to make my bridge a little more portable. If I actually get it working nicely I'll endeavour make it public.

By default docker writes the output to STDOUT and STDERR to the log, however with Analog_Bridge most of the output is missing. I've tried redirecting STD* to no avail. Please see the attached image - only the lines in red (STDERR) are included in the Docker logs.

I've done some googling and one theory is the process is writing directly to the TTY rather than STDOUT / STDERR

When someone gets a moment could they take a look at the code and confirm how these lines are being displayed?

Also whilst I'm here I was wondering if you could confirm if Analog_Bridge, MMDVM_Bridge etc support DNS? 

Thanks
Matthew
2E0SIP


Re: Cloud hosting

Steve N4IRS
 

For $10 a year, I did not really need a reason ;)

Steve

On 9/11/2020 3:04 PM, Jim - K6JM via groups.io wrote:
Russell,

Thanks for pointing out scrolling offers more options at virmach.com and yes, the server Steve documented is still available for the discounted price he paid:

At virmach.com, select VPS -> Affordable Linux VPS ->Scroll right to Micro+ ->Buy Now

A popup explains Micro+ is no longer available, but you can get a similar package SSD256. Click Continue and follow Steve's recommended selections. You end up with SSD256:

* 256MB memory
* 500GB bandwidth
* 10GB disk

at their Chicago datacenter for $12.50/year with a 1st year $2.50 discount.

For fun, I got the above configuration. I do not have any DVSwitch projects yet, so as an experiment I configured a LEMP (Linux, nginx, MySQL, PHP) server with WordPress. While DV servers work fine using the IP address, web servers are better with a domain name, so I got a free one from FreeNom. It all works for $10 for the 1st year:

https://www.k6jm.tk/wp/

Jim - K6JM


--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus



Re: Cloud hosting

Jim - K6JM
 

Russell,

Thanks for pointing out scrolling offers more options at virmach.com and yes, the server Steve documented is still available for the discounted price he paid:

At virmach.com, select VPS -> Affordable Linux VPS ->Scroll right to Micro+ ->Buy Now

A popup explains Micro+ is no longer available, but you can get a similar package SSD256. Click Continue and follow Steve's recommended selections. You end up with SSD256:

* 256MB memory
* 500GB bandwidth
* 10GB disk

at their Chicago datacenter for $12.50/year with a 1st year $2.50 discount.

For fun, I got the above configuration. I do not have any DVSwitch projects yet, so as an experiment I configured a LEMP (Linux, nginx, MySQL, PHP) server with WordPress. While DV servers work fine using the IP address, web servers are better with a domain name, so I got a free one from FreeNom. It all works for $10 for the 1st year:

https://www.k6jm.tk/wp/

Jim - K6JM


--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


Re: Update Binaries?

Steve N4IRS
 

dvswitch.sh has been getting update as we find the need to add features. I have been updating the binaries as we prepare for new features. Updating the binaries does just that, replace MB and AB mostly. In the future you won't use that procedure to upgrade.

Steve

On 9/10/20 9:10 PM, Tom Corcoran wrote:
Explanation please. What is the difference between doing a binaries update procedure versus updating the individual files as they are amended on github (ex. dvswitch.sh seems to get update more often than others lately).?
--
Tom VE3NY


Update Binaries?

Tom Corcoran
 

Explanation please. What is the difference between doing a binaries update procedure versus updating the individual files as they are amended on github (ex. dvswitch.sh seems to get update more often than others lately).?
--
Tom VE3NY


Re: Cloud hosting

 

Jim did you scroll to the right and see the Micro+ Plan?
$2.25 is the Value+ plan.

On Wed, Sep 9, 2020 at 7:08 PM Jim - K6JM via groups.io <jmm=k6jm.com@groups.io> wrote:
Sadly, the original US $12.50/year ($2.50 discount first year), does not appear to be available anymore.  I was able to get the one you got, but today, when choosing Billing Cycle, the options are now $2.25 USD Monthly, $6.25 USD Quarterly, $22.50 USD Annually.  It appears their promotion worked, since 6 of their 11 data centers are sold out of this product and the other 5 are listed as Low Stock.

    Jim – K6JM

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of Steve N4IRS
Sent: Tuesday, September 8, 2020 10:37 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Cloud hosting

This how I got to $10 per year.
Affordable Linux VPS / Value+ / chose Micro+ / chose continue on Micro+ to SSD256 popup / chose Billing Cycle 12.50 Annually / chose Chicago location and  Debian 9 64 bit  / add to cart /  checked Limited Support Agreement / agreed to Limited Support Package - Information

https://dvswitch.groups.io/g/main/message/6822
On 9/8/2020 1:23 PM, Jay wrote:

Cannot find any mention of on their site, just the starter $2.50 a month.


--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus





Re: Cloud hosting

 

I was under the impression the Micro plan is $12.50 a year. We got the discount so it was $10 for the first year then 12.50 a year after that.... I hope I read that right?
still a fantastic deal at $12.50 a year... :)


On Wed, Sep 9, 2020 at 7:11 PM Steve N4IRS <szingman@...> wrote:
So,
I guess the question is, what happens after our 12 months is up.

On 9/9/20 8:08 PM, Jim - K6JM via groups.io wrote:
> Sadly, the original US $12.50/year ($2.50 discount first year), does not appear to be available anymore.  I was able to get the one you got, but today, when choosing Billing Cycle, the options are now $2.25 USD Monthly, $6.25 USD Quarterly, $22.50 USD Annually.  It appears their promotion worked, since 6 of their 11 data centers are sold out of this product and the other 5 are listed as Low Stock.
>
>      Jim – K6JM
>
> From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of Steve N4IRS
> Sent: Tuesday, September 8, 2020 10:37 AM
> To: main@DVSwitch.groups.io
> Subject: Re: [DVSwitch] Cloud hosting
>
> This how I got to $10 per year.
> Affordable Linux VPS / Value+ / chose Micro+ / chose continue on Micro+ to SSD256 popup / chose Billing Cycle 12.50 Annually / chose Chicago location and  Debian 9 64 bit  / add to cart /  checked Limited Support Agreement / agreed to Limited Support Package - Information
>
> https://dvswitch.groups.io/g/main/message/6822
> On 9/8/2020 1:23 PM, Jay wrote:
>
> Cannot find any mention of on their site, just the starter $2.50 a month.
>
>
> --
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>
>
>
>





Re: Cloud hosting

Tito Lopez - YN1OB
 

I just bought the 12.50 /Year  this last weekend and you get the 2.50 discount upon checking out. 

W3DAW
YN1OB

On Wed, Sep 9, 2020, 5:08 PM Jim - K6JM via groups.io <jmm=k6jm.com@groups.io> wrote:
Sadly, the original US $12.50/year ($2.50 discount first year), does not appear to be available anymore.  I was able to get the one you got, but today, when choosing Billing Cycle, the options are now $2.25 USD Monthly, $6.25 USD Quarterly, $22.50 USD Annually.  It appears their promotion worked, since 6 of their 11 data centers are sold out of this product and the other 5 are listed as Low Stock.

    Jim – K6JM

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of Steve N4IRS
Sent: Tuesday, September 8, 2020 10:37 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Cloud hosting

This how I got to $10 per year.
Affordable Linux VPS / Value+ / chose Micro+ / chose continue on Micro+ to SSD256 popup / chose Billing Cycle 12.50 Annually / chose Chicago location and  Debian 9 64 bit  / add to cart /  checked Limited Support Agreement / agreed to Limited Support Package - Information

https://dvswitch.groups.io/g/main/message/6822
On 9/8/2020 1:23 PM, Jay wrote:

Cannot find any mention of on their site, just the starter $2.50 a month.


--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus





Re: Cloud hosting

Steve N4IRS
 

So,
I guess the question is, what happens after our 12 months is up.

On 9/9/20 8:08 PM, Jim - K6JM via groups.io wrote:
Sadly, the original US $12.50/year ($2.50 discount first year), does not appear to be available anymore. I was able to get the one you got, but today, when choosing Billing Cycle, the options are now $2.25 USD Monthly, $6.25 USD Quarterly, $22.50 USD Annually. It appears their promotion worked, since 6 of their 11 data centers are sold out of this product and the other 5 are listed as Low Stock.

Jim – K6JM

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of Steve N4IRS
Sent: Tuesday, September 8, 2020 10:37 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Cloud hosting

This how I got to $10 per year.
Affordable Linux VPS / Value+ / chose Micro+ / chose continue on Micro+ to SSD256 popup / chose Billing Cycle 12.50 Annually / chose Chicago location and Debian 9 64 bit / add to cart / checked Limited Support Agreement / agreed to Limited Support Package - Information

https://dvswitch.groups.io/g/main/message/6822
On 9/8/2020 1:23 PM, Jay wrote:

Cannot find any mention of on their site, just the starter $2.50 a month.


--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus



Re: Cloud hosting

Jim - K6JM
 

Sadly, the original US $12.50/year ($2.50 discount first year), does not appear to be available anymore. I was able to get the one you got, but today, when choosing Billing Cycle, the options are now $2.25 USD Monthly, $6.25 USD Quarterly, $22.50 USD Annually. It appears their promotion worked, since 6 of their 11 data centers are sold out of this product and the other 5 are listed as Low Stock.

Jim – K6JM

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of Steve N4IRS
Sent: Tuesday, September 8, 2020 10:37 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Cloud hosting

This how I got to $10 per year.
Affordable Linux VPS / Value+ / chose Micro+ / chose continue on Micro+ to SSD256 popup / chose Billing Cycle 12.50 Annually / chose Chicago location and Debian 9 64 bit / add to cart / checked Limited Support Agreement / agreed to Limited Support Package - Information

https://dvswitch.groups.io/g/main/message/6822
On 9/8/2020 1:23 PM, Jay wrote:

Cannot find any mention of on their site, just the starter $2.50 a month.


--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


FCS to DMR bridge Network watchdog has expired error message

David Young
 

Created a DVSwitch bridge between FCS room and DMR and am showing in the MMDVM log after each FCS fusion transmission Network Watchdog Timeout error message.  The bridge seems to work normally as audio transmissions between the FCS room and DMR talk group continue.  The problem this seems to cause is that I also have another DVSwitch bridge from an NXDN reflector to the same DMR talk group.  When I transmit from a fusion radio to the FCS room the bridge to DMR and then onto NXDN works, but because the NXDN bridge sees the network watchdog timeout for some reason it stops bridging back to DMR.  If I transmit to the DMR talk group with a DMR radio then this seems to clear the NXDN bridge from not bridging and it starts bridging again until it sees another network watchdog timeout from the FCS bridge. 
I have tried changing ports in both the YSFGateway.ini file and also the MMDVM_Bridge.ini file, but I cannot stop these network watchdog timeout errors which are stopping my NXDN to DMR bridging.  I am thinking this network watchdog timeout error is being generated by DVSwitch but cannot figure out how to prevent it.
Any help would be appreciated.  Attached are my working *.ini files.


--
Dave WB6DTB

2401 - 2420 of 9595