Date   

Re: Bridge

Steve N4IRS
 

This tells me otherwise.
Get:3 http://dvswitch.org/ASL_Repository stretch InRelease [4,806 B]
Err:3 http://dvswitch.org/ASL_Repository stretch InRelease

On 12/13/20 9:40 PM, ibjosh1985@... wrote:
yes


Re: Bridge

ibjosh1985@...
 

i got it did a restart on the box and ran the script again and did not give the error


Re: Bridge

Steve N4IRS
 

Show me the result of apt-get update.

On 12/13/20 9:11 PM, Steve Zingman wrote:
Did you?
rm /etc/apt/sources.list.d/allstarlink.list
rm /etc/apt/sources.list.d/dvswitch.list
apt-get update

On 12/13/20 9:09 PM, ibjosh1985@... wrote:
root@bridge:/home/kc5jmj# apt-get update
0% [Working]
Hit:1 http://deb.debian.org/debian buster InRelease
Hit:2 http://deb.debian.org/debian buster-updates InRelease
Get:3 http://dvswitch.org/ASL_Repository stretch InRelease [4,806 B]
Hit:4 http://security.debian.org/debian-security buster/updates InRelease
Hit:5 http://ftp.de.debian.org/debian buster-backports InRelease
Err:3 http://dvswitch.org/ASL_Repository stretch InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 72147EC1E788D4C3
Reading package lists... Done
W: GPG error: http://dvswitch.org/ASL_Repository stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 72147EC1E788D4C3
E: The repository 'http://dvswitch.org/ASL_Repository stretch InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
root@bridge:/home/kc5jmj#
root@bridge:/home/kc5jmj# cd /tmp
root@bridge:/tmp# wget http://dvswitch.org/buster
--2020-12-13 18:03:39--  http://dvswitch.org/buster
Resolving dvswitch.org (dvswitch.org)... 44.103.34.4
Connecting to dvswitch.org (dvswitch.org)|44.103.34.4|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1882 (1.8K)
Saving to: ‘buster’

buster                                                          100%[====================================================================================================================================================>]   1.84K  --.-KB/s    in 0s

2020-12-13 18:03:40 (27.9 MB/s) - ‘buster’ saved [1882/1882]

root@bridge:/tmp# chmod +x buster
root@bridge:/tmp# ./buster
The Repository file already exists, exiting
root@bridge:/tmp# apt-get update -y
Hit:1 http://security.debian.org/debian-security buster/updates InRelease
Hit:2 http://deb.debian.org/debian buster InRelease
Hit:3 http://deb.debian.org/debian buster-updates InRelease
Get:4 http://dvswitch.org/ASL_Repository stretch InRelease [4,806 B]
Hit:5 http://ftp.de.debian.org/debian buster-backports InRelease
Err:4 http://dvswitch.org/ASL_Repository stretch InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 72147EC1E788D4C3
Reading package lists... Done
W: GPG error: http://dvswitch.org/ASL_Repository stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 72147EC1E788D4C3
E: The repository 'http://dvswitch.org/ASL_Repository stretch InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
root@bridge:/tmp# ls
buster  systemd-private-ac6a4a5198324a4baf5d12819077641d-systemd-timesyncd.service-sraNEO
root@bridge:/tmp#




Re: Bridge

ibjosh1985@...
 

yes


Re: Bridge

Steve N4IRS
 

Did you?
rm /etc/apt/sources.list.d/allstarlink.list
rm /etc/apt/sources.list.d/dvswitch.list
apt-get update

On 12/13/20 9:09 PM, ibjosh1985@... wrote:
root@bridge:/home/kc5jmj# apt-get update
0% [Working]
Hit:1 http://deb.debian.org/debian buster InRelease
Hit:2 http://deb.debian.org/debian buster-updates InRelease
Get:3 http://dvswitch.org/ASL_Repository stretch InRelease [4,806 B]
Hit:4 http://security.debian.org/debian-security buster/updates InRelease
Hit:5 http://ftp.de.debian.org/debian buster-backports InRelease
Err:3 http://dvswitch.org/ASL_Repository stretch InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 72147EC1E788D4C3
Reading package lists... Done
W: GPG error: http://dvswitch.org/ASL_Repository stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 72147EC1E788D4C3
E: The repository 'http://dvswitch.org/ASL_Repository stretch InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
root@bridge:/home/kc5jmj#
root@bridge:/home/kc5jmj# cd /tmp
root@bridge:/tmp# wget http://dvswitch.org/buster
--2020-12-13 18:03:39--  http://dvswitch.org/buster
Resolving dvswitch.org (dvswitch.org)... 44.103.34.4
Connecting to dvswitch.org (dvswitch.org)|44.103.34.4|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1882 (1.8K)
Saving to: ‘buster’

buster                                                          100%[====================================================================================================================================================>]   1.84K  --.-KB/s    in 0s

2020-12-13 18:03:40 (27.9 MB/s) - ‘buster’ saved [1882/1882]

root@bridge:/tmp# chmod +x buster
root@bridge:/tmp# ./buster
The Repository file already exists, exiting
root@bridge:/tmp# apt-get update -y
Hit:1 http://security.debian.org/debian-security buster/updates InRelease
Hit:2 http://deb.debian.org/debian buster InRelease
Hit:3 http://deb.debian.org/debian buster-updates InRelease
Get:4 http://dvswitch.org/ASL_Repository stretch InRelease [4,806 B]
Hit:5 http://ftp.de.debian.org/debian buster-backports InRelease
Err:4 http://dvswitch.org/ASL_Repository stretch InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 72147EC1E788D4C3
Reading package lists... Done
W: GPG error: http://dvswitch.org/ASL_Repository stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 72147EC1E788D4C3
E: The repository 'http://dvswitch.org/ASL_Repository stretch InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
root@bridge:/tmp# ls
buster  systemd-private-ac6a4a5198324a4baf5d12819077641d-systemd-timesyncd.service-sraNEO
root@bridge:/tmp#



Re: Bridge

ibjosh1985@...
 

root@bridge:/home/kc5jmj# apt-get update
0% [Working]
Hit:1 http://deb.debian.org/debian buster InRelease
Hit:2 http://deb.debian.org/debian buster-updates InRelease
Get:3 http://dvswitch.org/ASL_Repository stretch InRelease [4,806 B]
Hit:4 http://security.debian.org/debian-security buster/updates InRelease
Hit:5 http://ftp.de.debian.org/debian buster-backports InRelease
Err:3 http://dvswitch.org/ASL_Repository stretch InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 72147EC1E788D4C3
Reading package lists... Done
W: GPG error: http://dvswitch.org/ASL_Repository stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 72147EC1E788D4C3
E: The repository 'http://dvswitch.org/ASL_Repository stretch InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
root@bridge:/home/kc5jmj#
root@bridge:/home/kc5jmj# cd /tmp
root@bridge:/tmp# wget http://dvswitch.org/buster
--2020-12-13 18:03:39--  http://dvswitch.org/buster
Resolving dvswitch.org (dvswitch.org)... 44.103.34.4
Connecting to dvswitch.org (dvswitch.org)|44.103.34.4|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1882 (1.8K)
Saving to: ‘buster’

buster                                                          100%[====================================================================================================================================================>]   1.84K  --.-KB/s    in 0s

2020-12-13 18:03:40 (27.9 MB/s) - ‘buster’ saved [1882/1882]

root@bridge:/tmp# chmod +x buster
root@bridge:/tmp# ./buster
The Repository file already exists, exiting
root@bridge:/tmp# apt-get update -y
Hit:1 http://security.debian.org/debian-security buster/updates InRelease
Hit:2 http://deb.debian.org/debian buster InRelease
Hit:3 http://deb.debian.org/debian buster-updates InRelease
Get:4 http://dvswitch.org/ASL_Repository stretch InRelease [4,806 B]
Hit:5 http://ftp.de.debian.org/debian buster-backports InRelease
Err:4 http://dvswitch.org/ASL_Repository stretch InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 72147EC1E788D4C3
Reading package lists... Done
W: GPG error: http://dvswitch.org/ASL_Repository stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 72147EC1E788D4C3
E: The repository 'http://dvswitch.org/ASL_Repository stretch InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
root@bridge:/tmp# ls
buster  systemd-private-ac6a4a5198324a4baf5d12819077641d-systemd-timesyncd.service-sraNEO
root@bridge:/tmp#


Re: Followup on Network Watchdog timeout message FCS to DMR bridge

Steve N4IRS
 

Dave,
Please show me the result of:
/opt/MMDVM_Bridge -v

Also please show the log with some sample FCS transmissions.

On 12/13/20 12:09 PM, David Young wrote:
Steve,

Tx on FCS00379
The log message is on the NXDN MMDVM_Bridge:  "M: 2020-12-12 14:37:26.510 DMR Slot 2, received network voice header from WB6DTB to TG 30639"
"M: 2020-12-12 14:37:26.510 DMR Slot 2, network watchdog has expired, 2.4 seconds, 12% packet loss, BER: 0.0%"

So we are sending both NXDN and various FCS rooms to HBlink3 master using DVSwitch MMDVM_Bridge modules.  FCS uses YSFGateway and I guess because we are then going from FCS through YSFGateway through MMDVM_Bridge to HBlink3 that is why the log shows DMR instead of YSF for the two log entries as above.  This is all running on cloud servers.
--
Dave WB6DTB


Re: Bridge

Steve N4IRS
 

On 12/13/20 6:55 PM, ibjosh1985@... wrote:
do you have some links i may be able to follow on this journey


Re: Bridge

ibjosh1985@...
 

do you have some links i may be able to follow on this journey


Re: Bridge

Steve N4IRS
 

That document is outdated. If you want to continue to use it, I suggest you contact the author.

For your error:
rm /etc/apt/sources.list.d/allstarlink.list
rm /etc/apt/sources.list.d/dvswitch.list

Note: Both files may not exist.

apt-get update

cd /tmp
wget http://dvswitch.org/buster
chmod +x buster
./buster
apt-get update -y

Steve N4IRS


On 12/13/20 6:36 PM, ibjosh1985@... wrote:
i've been following this site https://www.lucifernet.com/2020/01/08/build-a-p25-dmr-cross-mode-bridge/
as a starting ground but started coming up with errors

ERROR 1

install-dvswitch-repo                                           100%[========================================================================================

2020-12-13 17:34:53 (13.7 MB/s) - ‘install-dvswitch-repo’ saved [782/782]

root@bridge:/tmp# chmod +x install-dvswitch-repo
root@bridge:/tmp# ./install-dvswitch-repo
The Repository file already exists, exiting
root@bridge:/tmp#  apt-get update
Get:1 http://dvswitch.org/ASL_Repository stretch InRelease [4,806 B]
Err:1 http://dvswitch.org/ASL_Repository stretch InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 72147EC1E788D4C3
Hit:2 http://deb.debian.org/debian buster InRelease
Hit:3 http://security.debian.org/debian-security buster/updates InRelease
Hit:4 http://deb.debian.org/debian buster-updates InRelease
Hit:5 http://ftp.de.debian.org/debian buster-backports InRelease
M: 2020-12-13 23:35:01.060 No repeaters linked
Reading package lists... Done
W: GPG error: http://dvswitch.org/ASL_Repository stretch InRelease: The followin                                                                             g signatures couldn't be verified because the public key is not available: NO_PU                                                                             BKEY 72147EC1E788D4C3
E: The repository 'http://dvswitch.org/ASL_Repository stretch InRelease' is not                                                                              signed.
N: Updating from such a repository can't be done securely, and is therefore disa                                                                             bled by default.
N: See apt-secure(8) manpage for repository creation and user configuration deta                                                                             ils.
root@bridge:/tmp#



Bridge

ibjosh1985@...
 

i've been following this site https://www.lucifernet.com/2020/01/08/build-a-p25-dmr-cross-mode-bridge/
as a starting ground but started coming up with errors

ERROR 1

install-dvswitch-repo                                           100%[========================================================================================

2020-12-13 17:34:53 (13.7 MB/s) - ‘install-dvswitch-repo’ saved [782/782]

root@bridge:/tmp# chmod +x install-dvswitch-repo
root@bridge:/tmp# ./install-dvswitch-repo
The Repository file already exists, exiting
root@bridge:/tmp#  apt-get update
Get:1 http://dvswitch.org/ASL_Repository stretch InRelease [4,806 B]
Err:1 http://dvswitch.org/ASL_Repository stretch InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 72147EC1E788D4C3
Hit:2 http://deb.debian.org/debian buster InRelease
Hit:3 http://security.debian.org/debian-security buster/updates InRelease
Hit:4 http://deb.debian.org/debian buster-updates InRelease
Hit:5 http://ftp.de.debian.org/debian buster-backports InRelease
M: 2020-12-13 23:35:01.060 No repeaters linked
Reading package lists... Done
W: GPG error: http://dvswitch.org/ASL_Repository stretch InRelease: The followin                                                                             g signatures couldn't be verified because the public key is not available: NO_PU                                                                             BKEY 72147EC1E788D4C3
E: The repository 'http://dvswitch.org/ASL_Repository stretch InRelease' is not                                                                              signed.
N: Updating from such a repository can't be done securely, and is therefore disa                                                                             bled by default.
N: See apt-secure(8) manpage for repository creation and user configuration deta                                                                             ils.
root@bridge:/tmp#


Re: Followup on Network Watchdog timeout message FCS to DMR bridge

k7wby@...
 

On Sun, Dec 13, 2020 at 09:09 AM, David Young wrote:
network watchdog has expired, 2.4 seconds, 12% packet loss, BER: 0.0%
That is an AMBE error. It's important to remember that when you bridge from YSF to DMR the transition is done by stripping the unique data from YSF leaving only what is common to both modes and then reapplying (when possible) the data to destination mode. The process of vocoding is important and both modes should use the same process. If one is using the md380 and the other OP25 you may experience these errors. 


Re: Followup on Network Watchdog timeout message FCS to DMR bridge

David Young
 

Steve,

Tx on FCS00379
The log message is on the NXDN MMDVM_Bridge:  "M: 2020-12-12 14:37:26.510 DMR Slot 2, received network voice header from WB6DTB to TG 30639"
"M: 2020-12-12 14:37:26.510 DMR Slot 2, network watchdog has expired, 2.4 seconds, 12% packet loss, BER: 0.0%"

So we are sending both NXDN and various FCS rooms to HBlink3 master using DVSwitch MMDVM_Bridge modules.  FCS uses YSFGateway and I guess because we are then going from FCS through YSFGateway through MMDVM_Bridge to HBlink3 that is why the log shows DMR instead of YSF for the two log entries as above.  This is all running on cloud servers.
--
Dave WB6DTB


Re: Followup on Network Watchdog timeout message FCS to DMR bridge

k7wby@...
 

I thought network watchdog errors were XLX/AMBED related?


Re: Your gatewayDmrId nnnnnnn is NOT in the subscriber f .net ile.

G4WXN@...
 

This problem continues to occur randomly.

Just had to run the update again.

Any help appreciated.


--
Derek

G4WXN


Re: Adding P25 to existing YSF and DMR bridge

Gary, KE8O
 

Hi Steve,

I changed txTG from 9 to 27715 and I'm seeing transmissions from P25 showing up on DMR last heard. I'm also seeing when I transmit on DMR it's making it to my P25reflector log.

I also verified that my YSF outbound to DMR  works. However, my inbound from DMR to YSF no longer works based on reviewing MB logs. When coming inbound from DMR I'm only seeing a log activity in the DMR/P25 MB log, nothing in the YSF/DMR MB log for the same period. 

I don't have enough devices to be able to test all modes at the same time. Tomorrow I'll be able to setup a sked with some others to test further.

Thanks again for your time!




Re: Followup on Network Watchdog timeout message FCS to DMR bridge

Steve N4IRS
 

Dave,
One question. You reference "Network Watchdog Timeout" Are you seeing those words in the log?
You should be seeing this:
M: 2020-12-12 14:37:26.510 YSF, received network end of transmission (expired), 1.5 seconds, 0% packet loss, BER: 1.3%


 

On 12/11/20 7:45 PM, David Young wrote:
I posted an issue several months ago concerning getting the error message 'Network Watchdog Timeout' after any FCS transmission using an MMDVM_Bridge between FCS and DMR.  Specifically this caused another bridge which I am running 'NXDN to DMR', same DMR TG, to stop working.  What happens is that the NXDN MMDVM_Bridge log file sees the Network Watchdog Timeout error message and does not see any subsequent Tx Stop message so NXDN thinks that the FCS bridge is still talking and stays in listen mode.  So the Tx Stop message does not get passed to the NXDN Bridge after the Network Watchdog Timeout message.  I had a suggestion that possibly to prevent the Network Watchdog Timeout error message from occurring that in G4KLX's MMDVM.ini configuration file there is a software switch in the "System Fusion" stanza labeled "RemoteGateway=".  Setting this switch to a numeric 1 might prevent the Network Watchdog Timeout error and resulting error message in the FCS MMDVM_Bridge.  Looking at the DVSwitch MMDVM_Bridge configuration 'ini' file, there is no software switch suggested in the "System Fusion" stanza.  Is it possible to add this switch or would this be of any help to my problem with the NXDN bridge?
--
Dave WB6DTB


Re: Followup on Network Watchdog timeout message FCS to DMR bridge

Steve N4IRS
 

Dave,
We thought this was resolved. I am going to setup a test FCS <-> NXDN bridge. I will report my findings. I expect I'll do it first thing tomorrow morning.

Steve

On 12/11/20 7:45 PM, David Young wrote:
I posted an issue several months ago concerning getting the error message 'Network Watchdog Timeout' after any FCS transmission using an MMDVM_Bridge between FCS and DMR.  Specifically this caused another bridge which I am running 'NXDN to DMR', same DMR TG, to stop working.  What happens is that the NXDN MMDVM_Bridge log file sees the Network Watchdog Timeout error message and does not see any subsequent Tx Stop message so NXDN thinks that the FCS bridge is still talking and stays in listen mode.  So the Tx Stop message does not get passed to the NXDN Bridge after the Network Watchdog Timeout message.  I had a suggestion that possibly to prevent the Network Watchdog Timeout error message from occurring that in G4KLX's MMDVM.ini configuration file there is a software switch in the "System Fusion" stanza labeled "RemoteGateway=".  Setting this switch to a numeric 1 might prevent the Network Watchdog Timeout error and resulting error message in the FCS MMDVM_Bridge.  Looking at the DVSwitch MMDVM_Bridge configuration 'ini' file, there is no software switch suggested in the "System Fusion" stanza.  Is it possible to add this switch or would this be of any help to my problem with the NXDN bridge?
--
Dave WB6DTB


Re: Adding P25 to existing YSF and DMR bridge

Steve N4IRS
 

Gary,
Below is the [AMBE_AUDIO] stanza of you 2 AB instances. Notice you have the txTG set to 9. This tells AB to send traffic it receives on the the USRP port (from the other AB) to TG9
Set your txtg to 27715 and retest.



DMR AB.ini

[AMBE_AUDIO]
address = 127.0.0.1                     ; IP address of xx_Bridge
txPort = 31113                          ; Transmit TLV frames to partner on this port
rxPort = 31110                          ; Listen for TLV frames from partner on this port
ambeMode = DMR                          ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (encode PCM to this format)
minTxTimeMS = 2500                      ; Analog -> Digital Minimum time in MS for hang delay (0-10000)

; The metadata below is used when ASL is the source since it does not have any concept of digital modes
gatewayDmrId = 1139360                ; ID to use when transmitting from Analog_Bridge 7 digit ID
repeaterID = 113936022                  ; ID of source repeater 7 digit ID plus 2 digit SSID
txTg = 9                                ; TG to use for all frames sent from Analog_Bridge -> xx_Bridge
txTs = 2                                ; Slot to use for frames sent from Analog_Bridge -> xx_Bridge
colorCode = 1                           ; Color Code to assign DMR frames


P25 AB.ini

[AMBE_AUDIO]
address = 127.0.0.1                     ; IP address of xx_Bridge
txPort = 34103                          ; Transmit TLV frames to partner on this port
rxPort = 34100                          ; Listen for TLV frames from partner on this port
ambeMode = P25                        ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (encode PCM to this format)
minTxTimeMS = 2500                      ; Analog -> Digital Minimum time in MS for hang delay (0-10000)

; The metadata below is used when ASL is the source since it does not have any concept of digital modes
gatewayDmrId = 1139360                 ; ID to use when transmitting from Analog_Bridge 7 digit ID
repeaterID = 113936033                  ; ID of source repeater 7 digit ID plus 2 digit SSID
txTg = 9                                ; TG to use for all frames sent from Analog_Bridge -> xx_Bridge
txTs = 2                                ; Slot to use for frames sent from Analog_Bridge -> xx_Bridge
colorCode = 1                           ; Color Code to assign DMR frames




On 12/12/20 10:11 AM, Gary, KE8O wrote:
TG 27715. I’m trying to set things up so 27715 is the YSF, DMR, and P25 reflector/TG number. 


Re: Adding P25 to existing YSF and DMR bridge

Gary, KE8O
 

TG 27715. I’m trying to set things up so 27715 is the YSF, DMR, and P25 reflector/TG number. 

1841 - 1860 of 9579