Date   

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

Steve N4IRS
 

Dave,
I have uploaded a proposed for your FCS EOT issue. It is located in the testing branch on github at <https://github.com/DVSwitch/MMDVM_Bridge/blob/Testing/raw/MMDVM_Bridge.amd64>
To install:
cd /opt/MMDVM_Bridge
systemctl stop mmdvm_bridge
mv MMDVM_Bridge MMDVM_Bridge.old
wget https://github.com/DVSwitch/MMDVM_Bridge/raw/Testing/bin/MMDVM_Bridge.amd64
mv MMDVM_Bridge.amd64 MMDVM_Bridge
systemctl start mmdvm_bridge

retest and report.
For anyone else that wants to play, I also pushed a update to armhf.

Steve N4IRS

On 12/14/2020 12:12 PM, David Young wrote:
Steve,
Result of -v command:  MMDVM_Bridge version 20201105_V1.6.1 git #0a3bff0
We are running all bridging on cloud server running 'Debian 10 Buster x64' and using the DVSwitch module 'MMDVM_Bridge.amd64'
Didn't consider that HBlink3 might be causing the problem.  We have the HBlink3 configuration set to:  Repeat=true
I will attach with the simple bridge diagram additional config files including the hblink.cfg.  This is the first time I have used HBlink3 so you may see something wrong in my configuration causing this problem.  We are using the same TG number for both TGIF DMR and NXDN.

Thanks for your help,
Dave
--
Dave WB6DTB


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

David Young
 

Steve,
Result of -v command:  MMDVM_Bridge version 20201105_V1.6.1 git #0a3bff0
We are running all bridging on cloud server running 'Debian 10 Buster x64' and using the DVSwitch module 'MMDVM_Bridge.amd64'
Didn't consider that HBlink3 might be causing the problem.  We have the HBlink3 configuration set to:  Repeat=true
I will attach with the simple bridge diagram additional config files including the hblink.cfg.  This is the first time I have used HBlink3 so you may see something wrong in my configuration causing this problem.  We are using the same TG number for both TGIF DMR and NXDN.

Thanks for your help,
Dave
--
Dave WB6DTB


Re: Bridge

ibjosh1985@...
 

if it was a reference or something i kinda missed it sorry


Re: Bridge

Steve N4IRS
 

Never mind

On 12/14/2020 11:27 AM, ibjosh1985@... wrote:
?


Re: Bridge

ibjosh1985@...
 

?


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

Steve N4IRS
 

David,
What processor are you running your bridges on? uname -a

On 12/13/2020 11:59 PM, David Young wrote:
Steve,

Not sure about the command you are asking me to execute  /opt/MMDVM_Bridge -v
This results in command not found.  I think you are asking for the version of MMDVM_Bridge which is 1.6.1 for the NXDN bridge.

Attached are 2 log files, one from the NXDN bridge log and the second from the FCS bridge log.  These were copied from the MMDVM_Bridge log showing my transmissions from FCS00479 and resulting log entries seen from the NXDN MMDVM_Bridge.  As seen on the NXDN bridge log after each FCS transmission is received on NXDN at the end of those transmissions the log shows the Network Timeout error and no TX OFF log entry, causing NXDN to stay in receive mode.  The last transmission shown in the NXDN bridge log is from me transmitting from TGIF DMR showing a valid NXDN TX OFF log entry which then allows NXDN to pass new NXDN transmissions back through the bridge to HBlink3 master.

Dave
--
Dave WB6DTB


Re: Bridge

Steve N4IRS
 

If you run it on UDP port 31337, you can be leetx2 or confused for Back Orifice.

On 12/14/2020 10:55 AM, ibjosh1985@... wrote:
sweet 31337 is it then


Re: Bridge

ibjosh1985@...
 

sweet 31337 is it then


Re: Bridge

Steve N4IRS
 

Correct

On 12/14/2020 10:43 AM, ibjosh1985@... wrote:
yes i want to create my own TG. so basically you are saying to use a number that is not being used in that list.


Re: Bridge

ibjosh1985@...
 

yes i want to create my own TG. so basically you are saying to use a number that is not being used in that list.


Re: Bridge

Steve N4IRS
 

Are you going to create your own TG? If so You can find a list of TGs in use here /var/lib/mmdvm/P25Hosts.txt

On 12/14/2020 10:37 AM, ibjosh1985@... wrote:
i have both the p25 reflector and gateway installed how do i figure out its TG


Re: Bridge

ibjosh1985@...
 

i have both the p25 reflector and gateway installed how do i figure out its TG


Re: Bridge

Steve N4IRS
 

Yes you can. I have not built a .deb for it yet, so you will need to install from source.

On 12/14/2020 8:40 AM, ibjosh1985@... wrote:
Ok and to verify I can install it on the same system


Re: Bridge

ibjosh1985@...
 

Ok and to verify I can install it on the same system


Re: Bridge

Steve N4IRS
 

You will need to install that. It is not part of DVSwitch Server.

On 12/13/2020 11:13 PM, ibjosh1985@... wrote:
question when i had setup the dv switch did that install the p25 reflector to or do i still need to install that


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

Steve N4IRS
 

Dave,
Mike and I tested FCS bridging this weekend. Here is what we ran:

Mike:
FCS00290 to NXDN 3166

Steve
FCS00290 to DMR 3112138

In each case, audio is clean and EOT is being received by a station monitoring to bridge output. Admittedly, we were listening to the output on DVSwitch based nodes.
We did not test with HBlink3 in the mix. Can you give me a simple diagram of what your are doing to bridge the 3 modes?

Steve

On 12/13/2020 11:59 PM, David Young wrote:
Steve,

Not sure about the command you are asking me to execute  /opt/MMDVM_Bridge -v
This results in command not found.  I think you are asking for the version of MMDVM_Bridge which is 1.6.1 for the NXDN bridge.

Attached are 2 log files, one from the NXDN bridge log and the second from the FCS bridge log.  These were copied from the MMDVM_Bridge log showing my transmissions from FCS00479 and resulting log entries seen from the NXDN MMDVM_Bridge.  As seen on the NXDN bridge log after each FCS transmission is received on NXDN at the end of those transmissions the log shows the Network Timeout error and no TX OFF log entry, causing NXDN to stay in receive mode.  The last transmission shown in the NXDN bridge log is from me transmitting from TGIF DMR showing a valid NXDN TX OFF log entry which then allows NXDN to pass new NXDN transmissions back through the bridge to HBlink3 master.

Dave
--
Dave WB6DTB


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

Steve N4IRS
 

Sorry.
Show the output of:
/opt/MMDVM_Bridge/MMDVM_Bridge -v

Sent by smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of David Young <dly2@...>
Sent: Sunday, December 13, 2020 11:59:05 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Followup on Network Watchdog timeout message FCS to DMR bridge
 
Steve,

Not sure about the command you are asking me to execute  /opt/MMDVM_Bridge -v
This results in command not found.  I think you are asking for the version of MMDVM_Bridge which is 1.6.1 for the NXDN bridge.

Attached are 2 log files, one from the NXDN bridge log and the second from the FCS bridge log.  These were copied from the MMDVM_Bridge log showing my transmissions from FCS00479 and resulting log entries seen from the NXDN MMDVM_Bridge.  As seen on the NXDN bridge log after each FCS transmission is received on NXDN at the end of those transmissions the log shows the Network Timeout error and no TX OFF log entry, causing NXDN to stay in receive mode.  The last transmission shown in the NXDN bridge log is from me transmitting from TGIF DMR showing a valid NXDN TX OFF log entry which then allows NXDN to pass new NXDN transmissions back through the bridge to HBlink3 master.

Dave
--
Dave WB6DTB


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

David Young
 

Steve,

Not sure about the command you are asking me to execute  /opt/MMDVM_Bridge -v
This results in command not found.  I think you are asking for the version of MMDVM_Bridge which is 1.6.1 for the NXDN bridge.

Attached are 2 log files, one from the NXDN bridge log and the second from the FCS bridge log.  These were copied from the MMDVM_Bridge log showing my transmissions from FCS00479 and resulting log entries seen from the NXDN MMDVM_Bridge.  As seen on the NXDN bridge log after each FCS transmission is received on NXDN at the end of those transmissions the log shows the Network Timeout error and no TX OFF log entry, causing NXDN to stay in receive mode.  The last transmission shown in the NXDN bridge log is from me transmitting from TGIF DMR showing a valid NXDN TX OFF log entry which then allows NXDN to pass new NXDN transmissions back through the bridge to HBlink3 master.

Dave
--
Dave WB6DTB


Re: Bridge

ibjosh1985@...
 

question when i had setup the dv switch did that install the p25 reflector to or do i still need to install that


Re: Bridge

ibjosh1985@...
 

that installed with no error's is there more steps that i need to do

1581 - 1600 of 9344