Date   

Followup on Network Watchdog timeout message FCS to DMR bridge

David Young
 

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
 

Post your MB.ini, dvswitch.ini and the 2 AB.ini

On 12/11/20 6:25 PM, Gary, KE8O wrote:

Stephen, 

Would I see an error if the gateway was getting confused over DMRID’s?


I posted some of my logs the other night. I’m not seeing anything obvious. I did try using my wife’s DMR ID  for one of the MMDVM instances but the outcome was unchanged. I also compared my bridge  AB log against my mobile server AB log and they look similar. I might change my setup and try using a YSF to P25 bridge. At least with that configuration I can see end to end. 



Re: Adding P25 to existing YSF and DMR bridge

Steve N4IRS
 

I don't see how the DMR ID would confuse the gateway. I'll look at your files in the morning.

On 12/11/20 6:25 PM, Gary, KE8O wrote:

Stephen, 

Would I see an error if the gateway was getting confused over DMRID’s?


I posted some of my logs the other night. I’m not seeing anything obvious. I did try using my wife’s DMR ID  for one of the MMDVM instances but the outcome was unchanged. I also compared my bridge  AB log against my mobile server AB log and they look similar. I might change my setup and try using a YSF to P25 bridge. At least with that configuration I can see end to end. 



Re: Adding P25 to existing YSF and DMR bridge

Gary, KE8O
 

Stephen, 

Would I see an error if the gateway was getting confused over DMRID’s?


I posted some of my logs the other night. I’m not seeing anything obvious. I did try using my wife’s DMR ID  for one of the MMDVM instances but the outcome was unchanged. I also compared my bridge  AB log against my mobile server AB log and they look similar. I might change my setup and try using a YSF to P25 bridge. At least with that configuration I can see end to end. 


Re: DVSwitch Server instructions refresh

Steve N4IRS
 

As I said, this is old. To get everything without going to github:

cd /tmp

wget http://dvswitch.org/buster

chmod +x buster

./buster

apt-get update -y

apt-get install dvswitch-server -y

See <https://github.com/DVSwitch/DVSwitch-System-Builder>


Re: DVSwitch Server instructions refresh

Steve N4IRS
 

On 12/11/2020 1:04 PM, ruediger.h@... wrote:
Under 5.
the Entry
wget https://github.com/DVSwitch/Analog_Bridge/raw/master/dvswitch.sh
wont work, 404 :(


Re: DVSwitch Server instructions refresh

R. H.
 


Re: Replicated DMR Voice Packets

g8ptn@...
 

Hi Pierre,

Yes, I agree the situation is not desirable in the network. The actual issue was that packets were being duplicated; I don’t think it was a loop in this case.

Interestingly, I was the only person to spot the issue on DVSwitch and an old Openspot 1. Many stations are using Pi-Star MMDVM hotspots and there were no issues detected since the duplicated frames were being silently dropped.

Dave


Re: Replicated DMR Voice Packets

Pierre Martel
 

I think it is a good idea to have a problem when there is packet duplication, cause the only reason I can think of for the cause of packet duplication is a loop into the network. Now if there is a loop, and the packets keep on being replicated and no one notices, and other loops come and now we would have 3,4,5 time the packet replicated the end result would be network congestion. Bandwidth is not of infinite supply. And looping does degrade network performance. So the best thing is to make sure there is no looping and the 'bug' won't happen. It is not because you can link multiple systems together that it is a good thing to actually link them.





Le ven. 11 déc. 2020 à 08:42, <g8ptn@...> a écrit :

For general information, on a recent switch to a new DMR server, an observation was made that DVSwitch does not seem to cope with replicated voice packets.

The effect of the replicated packets is that the outgoing audio stream to DVSM sounds slow.


Whilst it is not desirable to have this situation in the network, my understanding is that the G4KLX software does deal with this by looking at a sequence number in the packets and drops replicated packets and replaces them with silence.


The cause of the replication has been fixed on the network in question, but it highlighted that it is also desirable to drop the replicated packets at the client side if possible.


I am not sure if the feature to drop can only be provided for the homebrew DMR protocol.


Dave (G8PTN)


Replicated DMR Voice Packets

g8ptn@...
 

For general information, on a recent switch to a new DMR server, an observation was made that DVSwitch does not seem to cope with replicated voice packets.

The effect of the replicated packets is that the outgoing audio stream to DVSM sounds slow.


Whilst it is not desirable to have this situation in the network, my understanding is that the G4KLX software does deal with this by looking at a sequence number in the packets and drops replicated packets and replaces them with silence.


The cause of the replication has been fixed on the network in question, but it highlighted that it is also desirable to drop the replicated packets at the client side if possible.


I am not sure if the feature to drop can only be provided for the homebrew DMR protocol.


Dave (G8PTN)


Re: DVSwitch Dashboard - DMR Master Information

g8ptn@...
 

Hi Waldek,

Next time I see the missing information I will check the log files with the grep command you have provided and add the workaround.

Thank you very much for the prompt and detailed response.


Dave


Re: DVSwitch Dashboard - DMR Master Information

SP2ONG Waldek
 

My dvswitch server is working 24H and I use a simple method to recovery info about status connected servers / links

I put in /etc/cron.d/ file with contain:

MAILTO=""
#
0 2 * * * root systemctl restart mmdvm_bridge
0 2 * * * root systemctl restart ysfgateway
0 2 * * * root systemctl restart nxdngateway
0 2 * * * root systemctl restart p25gateway
#

after creating the file you must restart crontab

/etc/init.d/cron restart

which restart services during the night for example 2:00
In MMDV_Bridge.ini in [DMR Network] I put my base DMR server (IP address, port , password) and
in NXDNGateway.ini and P25gateway.ini YSFgateway.ini  I have defined in Startup=  
reflectors which I want always connected after a restart of services


Re: DVSwitch Dashboard - DMR Master Information

SP2ONG Waldek
 

Dave,

The dashboard is searching in MMDVM_Bridge log file with current data

grep -a 'DMR, Logged\|DMR, Closing DMR\|DMR, Opening DMR\|DMR, Connection' /var/log/mmdvm/MMDVM_Bridge-2020-12-11.log

and if the result is empty the dashboard looking to MMDVM_Bridge log file with yesterday

grep -a 'DMR, Logged\|DMR, Closing DMR\|DMR, Opening DMR\|DMR, Connection' /var/log/mmdvm/MMDVM_Bridge-2020-12-10.log

As so result this command is used to create the status of DMR Server.

If your system works 24H and you have connected to DMR Serve for more than 2 days without changing DMR server at current the dashboard can not has the possibility get info about the connected DMR server

if see that info about the status DMR Server is empty try to check log file with the above command where file name MMDVM_Bridge log file must be with yesterday

Waldek



Re: DVSwitch Dashboard - DMR Master Information

g8ptn@...
 

Hi Steve,

Unfortunately, when I opened the browser today 11th Dec, the “DMR Master” information had disappeared again. I wonder if it is happening on a 24-hour basis.


Changing the Default DMR Server in the “dvs” control panel restores the information as before.


Dave 


Re: DVSwitch Dashboard - DMR Master Information

Steve N4IRS
 

Did you edit /etc/lighttpd/lighttpd.conf?
show me the result of: systemctl status webproxy
show me the result of: ls /lib/systemd/system/web*

Steve N4IRS


On 12/10/2020 3:53 PM, Chris K6CV wrote:
Hi Steve, I'm a newbie here, and seem to have a issue with lighttpd, below is what I see, and of course no dashboard web page found.
Not sure what all this means, but it looks like my webproxy service is in a damaged and not running state.
:
root@raspberrypi:/var# ps ax | grep lighttpd
17717 pts/0    S+     0:00 grep lighttpd
root@raspberrypi:/var#

root@raspberrypi:/var/log/mmdvm# systemctl restart webproxy
Failed to restart webproxy.service: Unit webproxy.service not found.
root@raspberrypi:/var/log/mmdvm# ps ax | grep lighttpd
11431 pts/0    S+     0:00 grep lighttpd

root@raspberrypi:/var/log/mmdvm# systemctl status lighttpd
● lighttpd.service - Lighttpd Daemon
   Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2020-12-10 11:06:31 PST; 1h 8min ago
  Process: 773 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf (code=exited, status=0/SUCCESS)
  Process: 778 ExecStart=/usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf (code=exited, status=255/EXCEPTION)
 Main PID: 778 (code=exited, status=255/EXCEPTION)
 
Dec 10 11:06:31 raspberrypi systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
Dec 10 11:06:31 raspberrypi systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 5.
Dec 10 11:06:31 raspberrypi systemd[1]: Stopped Lighttpd Daemon.
Dec 10 11:06:31 raspberrypi systemd[1]: lighttpd.service: Start request repeated too quickly.
Dec 10 11:06:31 raspberrypi systemd[1]: lighttpd.service: Failed with result 'exit-code'.
Dec 10 11:06:31 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.
root@raspberrypi:/var/log/mmdvm#

73's
DE K6CV Chris.


Re: DVSwitch Dashboard - DMR Master Information

Chris K6CV
 

Hi Steve, I'm a newbie here, and seem to have a issue with lighttpd, below is what I see, and of course no dashboard web page found.
Not sure what all this means, but it looks like my webproxy service is in a damaged and not running state.
:
root@raspberrypi:/var# ps ax | grep lighttpd
17717 pts/0    S+     0:00 grep lighttpd
root@raspberrypi:/var#

root@raspberrypi:/var/log/mmdvm# systemctl restart webproxy
Failed to restart webproxy.service: Unit webproxy.service not found.
root@raspberrypi:/var/log/mmdvm# ps ax | grep lighttpd
11431 pts/0    S+     0:00 grep lighttpd

root@raspberrypi:/var/log/mmdvm# systemctl status lighttpd
● lighttpd.service - Lighttpd Daemon
   Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2020-12-10 11:06:31 PST; 1h 8min ago
  Process: 773 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf (code=exited, status=0/SUCCESS)
  Process: 778 ExecStart=/usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf (code=exited, status=255/EXCEPTION)
 Main PID: 778 (code=exited, status=255/EXCEPTION)
 
Dec 10 11:06:31 raspberrypi systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
Dec 10 11:06:31 raspberrypi systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 5.
Dec 10 11:06:31 raspberrypi systemd[1]: Stopped Lighttpd Daemon.
Dec 10 11:06:31 raspberrypi systemd[1]: lighttpd.service: Start request repeated too quickly.
Dec 10 11:06:31 raspberrypi systemd[1]: lighttpd.service: Failed with result 'exit-code'.
Dec 10 11:06:31 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.
root@raspberrypi:/var/log/mmdvm#

73's
DE K6CV Chris.


Re: DVSwitch Dashboard - DMR Master Information

g8ptn@...
 

Hi Steve,

I have done the update/upgrade and it seems fine now.

Many thanks.

Dave


Re: Using DVSwitch to access DMR+/Phoenix

G4WXN@...
 

Thanks, I'll give it a whirl.

--
Derek

G4WXN


Re: MMDVM to MMDVM connections ?

Gerry Filby
 

Figures ... was curious if the underlying protocol could support peer to peer connections ...

Cheers !
Gerry.


Re: Using DVSwitch to access DMR+/Phoenix

Steve N4IRS
 

sudo /opt/Analog_Bridge/dvswitch.sh tune PASSWORD@...:55555:StartRef=4440;RelinkTime=180;UserLink=1!9

On 12/10/2020 11:16 AM, G4WXN@... wrote:
sudo /opt/Analog_Bridge/dvswitch.sh tune PASSWORD@...:55555:StartRef=4440;RelinkTime=180;UserLink=1
--
Derek

G4WXN

2081 - 2100 of 9795