Date   

Re: MMDVM_Bridge segfaulting on RPi 1B with Debian Buster

Steve N4IRS
 

I have built Analog_Bridge on a Pi 1 (armv6l)
It is in the github repository at <https://github.com/DVSwitch/Analog_Bridge>

73, Steve N4IRS


Re: MMDVM_Bridge segfaulting on RPi 1B with Debian Buster

Steve N4IRS
 

Florian,
I have built MMDVM_Bridge on a Pi 1. (armv6l) Give it a try on your 1B
It is in the github repository at <https://github.com/DVSwitch/MMDVM_Bridge> in the bin directory.

We have no plans at this time to include support for the v6 in the apt repository, but I will update github with the binary.
Next I'll build Analog bridge for the v6.

73, Steve N4IRS

On 10/24/19 4:26 PM, Florian Wolters wrote:
Dear folks,

I am trying to rund MMDVM_Bridge on a RPi 1B with Debian Buster. The
binary exits with a Segementation Fault right after start. Nothing else
on the screen/console.
Is this binary not supposed to be run on that old hardware?

vy73 de Florian DF2ET





Re: Sgefault in MMDVM_Bridge

Steve N4IRS
 

Peter,
Please post or e-mail the MMDVM_Bridge.ini that connects to FCS. 

Thanks, Steve


Re: MMDVM_Bridge Timeout

Steve N4IRS
 

Philippe,
Great to hear. You are not the first, nor will you be the last to get caught by that.

73, Steve N4IRS

On 10/27/19 9:04 AM, ph.ttv@... via Groups.Io wrote:

I think I just understood my mistake (absurd)

1/ When I switch on my computer I run a first session in the backgroud with : systemctl stop mmdvm_bridge

2/ to see what's going on I opened a second session ... in the foreground : MMDVM_Bridge.ini
./MMDVM_Bridge MMDVM_Bridge.ini


I can login to the Master with the info you provided. Do you have a second copy of MMDVM_Bridge running?
So your first remark was very relevant !


everything looks ok now :-)
Thank you very much for taking the time to answer me, Steve !!!

Best 73

Philippe

ps : below the copy of what I visualize now

root@raspberrypi:/opt/MMDVM_Bridge# ./MMDVM_Bridge MMDVM_Bridge.ini
I: 2019-10-27 12:40:13.224 MMDVM_Bridge:
I: 2019-10-27 12:40:13.224 Portions Copyright (C) 2018 DVSwitch, INAD.
I: 2019-10-27 12:40:13.224 Hacks by Mike N4IRR and Steve N4IRS
I: 2019-10-27 12:40:13.224 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I: 2019-10-27 12:40:13.225 This software is for use on amateur radio networks only,
I: 2019-10-27 12:40:13.225 it is to be used for educational purposes only. Its use on
I: 2019-10-27 12:40:13.225 commercial networks is strictly prohibited.
I: 2019-10-27 12:40:13.225 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2019-10-27 12:40:13.225 MMDVM_Bridge-20180423 is starting
M: 2019-10-27 12:40:13.225 Built 14:16:44 Jul  1 2019 (GitID #43be6b4)
I: 2019-10-27 12:40:13.225 General Parameters
I: 2019-10-27 12:40:13.225     Callsign: F5RVX
I: 2019-10-27 12:40:13.225     Id: 208801429
I: 2019-10-27 12:40:13.225     Duplex: no
I: 2019-10-27 12:40:13.226     Timeout: 180s
I: 2019-10-27 12:40:13.226     D-Star: disabled
I: 2019-10-27 12:40:13.226     DMR: enabled
I: 2019-10-27 12:40:13.226     YSF: disabled
I: 2019-10-27 12:40:13.226     P25: disabled
I: 2019-10-27 12:40:13.226     NXDN: disabled
I: 2019-10-27 12:40:13.226 Modem Parameters
I: 2019-10-27 12:40:13.226     Port: /dev/null
I: 2019-10-27 12:40:13.226     RX Invert: no
I: 2019-10-27 12:40:13.226     TX Invert: no
I: 2019-10-27 12:40:13.226     PTT Invert: no
I: 2019-10-27 12:40:13.227     TX Delay: 100ms
I: 2019-10-27 12:40:13.227     RX Offset: 0Hz
I: 2019-10-27 12:40:13.227     TX Offset: 0Hz
I: 2019-10-27 12:40:13.227     RX DC Offset: 0
I: 2019-10-27 12:40:13.227     TX DC Offset: 0
I: 2019-10-27 12:40:13.227     RF Level: 100.0%
I: 2019-10-27 12:40:13.227     DMR Delay: 0 (0.0ms)
I: 2019-10-27 12:40:13.227     RX Level: 50.0%
I: 2019-10-27 12:40:13.227     CW Id TX Level: 50.0%
I: 2019-10-27 12:40:13.227     D-Star TX Level: 50.0%
I: 2019-10-27 12:40:13.228     DMR TX Level: 50.0%
I: 2019-10-27 12:40:13.228     YSF TX Level: 50.0%
I: 2019-10-27 12:40:13.228     P25 TX Level: 50.0%
I: 2019-10-27 12:40:13.228     NXDN TX Level: 50.0%
I: 2019-10-27 12:40:13.228     RX Frequency: 0Hz (0Hz)
I: 2019-10-27 12:40:13.228     TX Frequency: 0Hz (0Hz)
M: 2019-10-27 12:40:13.228 Opening the MMDVM
I: 2019-10-27 12:40:13.228 Display Parameters
I: 2019-10-27 12:40:13.229     Type:
I: 2019-10-27 12:40:13.229 DMR Network Parameters
I: 2019-10-27 12:40:13.229     Address: 217.182.129.131
I: 2019-10-27 12:40:13.229     Port: 62031
I: 2019-10-27 12:40:13.229     Local: 62032
I: 2019-10-27 12:40:13.229     Jitter: 360ms
I: 2019-10-27 12:40:13.229     Slot 1: disabled
I: 2019-10-27 12:40:13.229     Slot 2: enabled
I: 2019-10-27 12:40:13.229     Mode Hang: 3s
I: 2019-10-27 12:40:13.230 Info Parameters
I: 2019-10-27 12:40:13.230     Callsign: F5RVX
I: 2019-10-27 12:40:13.230     RX Frequency: 0Hz
I: 2019-10-27 12:40:13.230     TX Frequency: 0Hz
I: 2019-10-27 12:40:13.230     Power: 0W
I: 2019-10-27 12:40:13.230     Latitude: 47.563599deg N
I: 2019-10-27 12:40:13.230     Longitude: -3.812300deg E
I: 2019-10-27 12:40:13.230     Height: 0m
I: 2019-10-27 12:40:13.230     Location: "Hotspot test dept 29 "
I: 2019-10-27 12:40:13.230     Description: "RX only for the moment"
I: 2019-10-27 12:40:13.231     URL: ""
M: 2019-10-27 12:40:13.231 DMR, Opening DMR Network
I: 2019-10-27 12:40:13.231 RSSI
I: 2019-10-27 12:40:13.231     Mapping File: RSSI.dat
W: 2019-10-27 12:40:13.231 Cannot open the RSSI data file - RSSI.dat
I: 2019-10-27 12:40:13.231 DMR Id Lookups
I: 2019-10-27 12:40:13.231     File: /var/lib/mmdvm/DMRIds.dat
I: 2019-10-27 12:40:13.231     Reload: 24 hours
I: 2019-10-27 12:40:14.020 Loaded 146882 Ids to the DMR callsign lookup table
I: 2019-10-27 12:40:14.020 DMR RF Parameters
I: 2019-10-27 12:40:14.020 Started the DMR Id lookup reload thread
I: 2019-10-27 12:40:14.020     Id: 208801429
I: 2019-10-27 12:40:14.020     Color Code: 1
I: 2019-10-27 12:40:14.020     Self Only: no
I: 2019-10-27 12:40:14.020     Embedded LC Only: yes
I: 2019-10-27 12:40:14.020     Dump Talker Alias Data: no
I: 2019-10-27 12:40:14.021     Prefixes: 0
I: 2019-10-27 12:40:14.021     Call Hang: 3s
I: 2019-10-27 12:40:14.021     TX Hang: 3s
I: 2019-10-27 12:40:14.021     Mode Hang: 10s
M: 2019-10-27 12:40:14.021 DMR, Opening INI file: DVSwitch.ini
M: 2019-10-27 12:40:14.021 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2019-10-27 12:40:14.021 DMR, Setting [DMR] TXPort -> 31100
M: 2019-10-27 12:40:14.021 DMR, Setting [DMR] RXPort -> 31103
M: 2019-10-27 12:40:14.021 DMR, Setting [DMR] Slot -> 2
M: 2019-10-27 12:40:14.021 DMR, Transmitting on 127.0.0.1:31100 and listening on port 31103.  Result = 1
M: 2019-10-27 12:40:14.021 MMDVM_Bridge-20180423 is running
D: 2019-10-27 12:40:24.045 DMR, Sending authorisation
D: 2019-10-27 12:40:24.071 DMR, Sending configuration
M: 2019-10-27 12:40:24.091 DMR, Logged into the master successfully
D: 2019-10-27 12:41:52.838 Network Received
D: 2019-10-27 12:41:52.838 0000:  44 4D 52 44 00 1F BD 3A 00 08 20 0C 72 0E 95 A1    *DMRD...:.. .r...*
D: 2019-10-27 12:41:52.838 0010:  00 00 00 00 0B E4 05 8E 0D E0 2A 20 28 10 C7 00    *..........* (...*
[...]

D: 2019-10-27 12:50:10.940 0030:  46 40 A7 81 5A 00 00                               *F@..Z..*
M: 2019-10-27 12:50:10.940 DMR Slot 2, received network end of voice transmission, 0.1 seconds, 0% packet loss, BER: 0.0%
[...]

(no further disconnections)




Re: MMDVM_Bridge Timeout

Philippe, f5rvx
 

I think I just understood my mistake (absurd)

1/ When I switch on my computer I run a first session in the backgroud with : systemctl stop mmdvm_bridge

2/ to see what's going on I opened a second session ... in the foreground : MMDVM_Bridge.ini
./MMDVM_Bridge MMDVM_Bridge.ini


I can login to the Master with the info you provided. Do you have a second copy of MMDVM_Bridge running?
So your first remark was very relevant !


everything looks ok now :-)
Thank you very much for taking the time to answer me, Steve !!!

Best 73

Philippe

ps : below the copy of what I visualize now

root@raspberrypi:/opt/MMDVM_Bridge# ./MMDVM_Bridge MMDVM_Bridge.ini
I: 2019-10-27 12:40:13.224 MMDVM_Bridge:
I: 2019-10-27 12:40:13.224 Portions Copyright (C) 2018 DVSwitch, INAD.
I: 2019-10-27 12:40:13.224 Hacks by Mike N4IRR and Steve N4IRS
I: 2019-10-27 12:40:13.224 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I: 2019-10-27 12:40:13.225 This software is for use on amateur radio networks only,
I: 2019-10-27 12:40:13.225 it is to be used for educational purposes only. Its use on
I: 2019-10-27 12:40:13.225 commercial networks is strictly prohibited.
I: 2019-10-27 12:40:13.225 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2019-10-27 12:40:13.225 MMDVM_Bridge-20180423 is starting
M: 2019-10-27 12:40:13.225 Built 14:16:44 Jul  1 2019 (GitID #43be6b4)
I: 2019-10-27 12:40:13.225 General Parameters
I: 2019-10-27 12:40:13.225     Callsign: F5RVX
I: 2019-10-27 12:40:13.225     Id: 208801429
I: 2019-10-27 12:40:13.225     Duplex: no
I: 2019-10-27 12:40:13.226     Timeout: 180s
I: 2019-10-27 12:40:13.226     D-Star: disabled
I: 2019-10-27 12:40:13.226     DMR: enabled
I: 2019-10-27 12:40:13.226     YSF: disabled
I: 2019-10-27 12:40:13.226     P25: disabled
I: 2019-10-27 12:40:13.226     NXDN: disabled
I: 2019-10-27 12:40:13.226 Modem Parameters
I: 2019-10-27 12:40:13.226     Port: /dev/null
I: 2019-10-27 12:40:13.226     RX Invert: no
I: 2019-10-27 12:40:13.226     TX Invert: no
I: 2019-10-27 12:40:13.226     PTT Invert: no
I: 2019-10-27 12:40:13.227     TX Delay: 100ms
I: 2019-10-27 12:40:13.227     RX Offset: 0Hz
I: 2019-10-27 12:40:13.227     TX Offset: 0Hz
I: 2019-10-27 12:40:13.227     RX DC Offset: 0
I: 2019-10-27 12:40:13.227     TX DC Offset: 0
I: 2019-10-27 12:40:13.227     RF Level: 100.0%
I: 2019-10-27 12:40:13.227     DMR Delay: 0 (0.0ms)
I: 2019-10-27 12:40:13.227     RX Level: 50.0%
I: 2019-10-27 12:40:13.227     CW Id TX Level: 50.0%
I: 2019-10-27 12:40:13.227     D-Star TX Level: 50.0%
I: 2019-10-27 12:40:13.228     DMR TX Level: 50.0%
I: 2019-10-27 12:40:13.228     YSF TX Level: 50.0%
I: 2019-10-27 12:40:13.228     P25 TX Level: 50.0%
I: 2019-10-27 12:40:13.228     NXDN TX Level: 50.0%
I: 2019-10-27 12:40:13.228     RX Frequency: 0Hz (0Hz)
I: 2019-10-27 12:40:13.228     TX Frequency: 0Hz (0Hz)
M: 2019-10-27 12:40:13.228 Opening the MMDVM
I: 2019-10-27 12:40:13.228 Display Parameters
I: 2019-10-27 12:40:13.229     Type:
I: 2019-10-27 12:40:13.229 DMR Network Parameters
I: 2019-10-27 12:40:13.229     Address: 217.182.129.131
I: 2019-10-27 12:40:13.229     Port: 62031
I: 2019-10-27 12:40:13.229     Local: 62032
I: 2019-10-27 12:40:13.229     Jitter: 360ms
I: 2019-10-27 12:40:13.229     Slot 1: disabled
I: 2019-10-27 12:40:13.229     Slot 2: enabled
I: 2019-10-27 12:40:13.229     Mode Hang: 3s
I: 2019-10-27 12:40:13.230 Info Parameters
I: 2019-10-27 12:40:13.230     Callsign: F5RVX
I: 2019-10-27 12:40:13.230     RX Frequency: 0Hz
I: 2019-10-27 12:40:13.230     TX Frequency: 0Hz
I: 2019-10-27 12:40:13.230     Power: 0W
I: 2019-10-27 12:40:13.230     Latitude: 47.563599deg N
I: 2019-10-27 12:40:13.230     Longitude: -3.812300deg E
I: 2019-10-27 12:40:13.230     Height: 0m
I: 2019-10-27 12:40:13.230     Location: "Hotspot test dept 29 "
I: 2019-10-27 12:40:13.230     Description: "RX only for the moment"
I: 2019-10-27 12:40:13.231     URL: ""
M: 2019-10-27 12:40:13.231 DMR, Opening DMR Network
I: 2019-10-27 12:40:13.231 RSSI
I: 2019-10-27 12:40:13.231     Mapping File: RSSI.dat
W: 2019-10-27 12:40:13.231 Cannot open the RSSI data file - RSSI.dat
I: 2019-10-27 12:40:13.231 DMR Id Lookups
I: 2019-10-27 12:40:13.231     File: /var/lib/mmdvm/DMRIds.dat
I: 2019-10-27 12:40:13.231     Reload: 24 hours
I: 2019-10-27 12:40:14.020 Loaded 146882 Ids to the DMR callsign lookup table
I: 2019-10-27 12:40:14.020 DMR RF Parameters
I: 2019-10-27 12:40:14.020 Started the DMR Id lookup reload thread
I: 2019-10-27 12:40:14.020     Id: 208801429
I: 2019-10-27 12:40:14.020     Color Code: 1
I: 2019-10-27 12:40:14.020     Self Only: no
I: 2019-10-27 12:40:14.020     Embedded LC Only: yes
I: 2019-10-27 12:40:14.020     Dump Talker Alias Data: no
I: 2019-10-27 12:40:14.021     Prefixes: 0
I: 2019-10-27 12:40:14.021     Call Hang: 3s
I: 2019-10-27 12:40:14.021     TX Hang: 3s
I: 2019-10-27 12:40:14.021     Mode Hang: 10s
M: 2019-10-27 12:40:14.021 DMR, Opening INI file: DVSwitch.ini
M: 2019-10-27 12:40:14.021 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2019-10-27 12:40:14.021 DMR, Setting [DMR] TXPort -> 31100
M: 2019-10-27 12:40:14.021 DMR, Setting [DMR] RXPort -> 31103
M: 2019-10-27 12:40:14.021 DMR, Setting [DMR] Slot -> 2
M: 2019-10-27 12:40:14.021 DMR, Transmitting on 127.0.0.1:31100 and listening on port 31103.  Result = 1
M: 2019-10-27 12:40:14.021 MMDVM_Bridge-20180423 is running
D: 2019-10-27 12:40:24.045 DMR, Sending authorisation
D: 2019-10-27 12:40:24.071 DMR, Sending configuration
M: 2019-10-27 12:40:24.091 DMR, Logged into the master successfully
D: 2019-10-27 12:41:52.838 Network Received
D: 2019-10-27 12:41:52.838 0000:  44 4D 52 44 00 1F BD 3A 00 08 20 0C 72 0E 95 A1    *DMRD...:.. .r...*
D: 2019-10-27 12:41:52.838 0010:  00 00 00 00 0B E4 05 8E 0D E0 2A 20 28 10 C7 00    *..........* (...*
[...]

D: 2019-10-27 12:50:10.940 0030:  46 40 A7 81 5A 00 00                               *F@..Z..*
M: 2019-10-27 12:50:10.940 DMR Slot 2, received network end of voice transmission, 0.1 seconds, 0% packet loss, BER: 0.0%
[...]

(no further disconnections)



Re: MMDVM_Bridge Timeout

Steve N4IRS
 

Philippe,
To run MMDVM_Bridge in the foreground:
systemctl stop mmdvm_bridge
cd to the directory with MMDVM_Bridge and MMDVM_Bridge.ini
./MMDVM_Bridge MMDVM_Bridge,ini
Wait a while and paste the output from MMDVM_Bridge.

Steve N4IRS

On 10/27/2019 8:24 AM, ph.ttv@... via Groups.Io wrote:


Le 27/10/2019 à 12:59, Steve N4IRS a écrit :
Stop MMDVM_Bridge.

root@raspberrypi:/opt/MMDVM_Bridge# systemctl stop mmdvm_bridge


Make sure it's stopped.
root@raspberrypi:/opt/MMDVM_Bridge# ps aux | grep mmdvm_bridge
root      2796  0.0  0.0   7364   524 pts/0    S+   13:15   0:00 grep mmdvm_bridge
root@raspberrypi:/opt/MMDVM_Bridge#


Run MMDVM_Bridge in the foreground .
systemctl start mmdvm_bridge    (background or foreground ? I'm not sure what I do here ... )


and paste the results
root@raspberrypi:/opt/MMDVM_Bridge# netstat -unap
Connexions Internet actives (serveurs et établies)
Proto Recv-Q Send-Q Adresse locale          Adresse distante        Etat        PID/Program name   
udp        0      0 0.0.0.0:31100           0.0.0.0:*                           1066/Analog_Bridge 
udp        0      0 0.0.0.0:31103           0.0.0.0:*                           2863/MMDVM_Bridge  
udp        0      0 0.0.0.0:2470            0.0.0.0:*                           1067/md380-emu     
udp        0      0 0.0.0.0:50111           0.0.0.0:*                           1066/Analog_Bridge 
udp        0      0 0.0.0.0:68              0.0.0.0:*                           413/dhcpcd         
udp        0      0 0.0.0.0:1194            0.0.0.0:*                           555/openvpn        
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           371/avahi-daemon: r
udp        0      0 0.0.0.0:40744           0.0.0.0:*                           1066/Analog_Bridge 
udp        0      0 0.0.0.0:36656           0.0.0.0:*                           371/avahi-daemon: r
udp        0      0 0.0.0.0:52564           0.0.0.0:*                           1066/Analog_Bridge 
udp6       0      0 :::53620                :::*                                371/avahi-daemon: r
udp6       0      0 :::64738                :::*                                1043/murmurd       
udp6       0      0 :::5353                 :::*                                371/avahi-daemon: r
root@raspberrypi:/opt/MMDVM_Bridge#

Philippe, f5rvx




Re: MMDVM_Bridge Timeout

Philippe, f5rvx
 


Le 27/10/2019 à 12:59, Steve N4IRS a écrit :
Stop MMDVM_Bridge.

root@raspberrypi:/opt/MMDVM_Bridge# systemctl stop mmdvm_bridge


Make sure it's stopped.
root@raspberrypi:/opt/MMDVM_Bridge# ps aux | grep mmdvm_bridge
root      2796  0.0  0.0   7364   524 pts/0    S+   13:15   0:00 grep mmdvm_bridge
root@raspberrypi:/opt/MMDVM_Bridge#


Run MMDVM_Bridge in the foreground .
systemctl start mmdvm_bridge    (background or foreground ? I'm not sure what I do here ... )


and paste the results
root@raspberrypi:/opt/MMDVM_Bridge# netstat -unap
Connexions Internet actives (serveurs et établies)
Proto Recv-Q Send-Q Adresse locale          Adresse distante        Etat        PID/Program name   
udp        0      0 0.0.0.0:31100           0.0.0.0:*                           1066/Analog_Bridge 
udp        0      0 0.0.0.0:31103           0.0.0.0:*                           2863/MMDVM_Bridge  
udp        0      0 0.0.0.0:2470            0.0.0.0:*                           1067/md380-emu     
udp        0      0 0.0.0.0:50111           0.0.0.0:*                           1066/Analog_Bridge 
udp        0      0 0.0.0.0:68              0.0.0.0:*                           413/dhcpcd         
udp        0      0 0.0.0.0:1194            0.0.0.0:*                           555/openvpn        
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           371/avahi-daemon: r
udp        0      0 0.0.0.0:40744           0.0.0.0:*                           1066/Analog_Bridge 
udp        0      0 0.0.0.0:36656           0.0.0.0:*                           371/avahi-daemon: r
udp        0      0 0.0.0.0:52564           0.0.0.0:*                           1066/Analog_Bridge 
udp6       0      0 :::53620                :::*                                371/avahi-daemon: r
udp6       0      0 :::64738                :::*                                1043/murmurd       
udp6       0      0 :::5353                 :::*                                371/avahi-daemon: r
root@raspberrypi:/opt/MMDVM_Bridge#

Philippe, f5rvx



Re: MMDVM_Bridge Timeout

Steve N4IRS
 

Philippe,
Stop MMDVM_Bridge. Make sure it's stopped.
Run MMDVM_Bridge in the foreground and paste the results.

Steve

On 10/27/2019 7:52 AM, ph.ttv@... via Groups.Io wrote:


Le 27/10/2019 à 12:27, Steve N4IRS a écrit :
Do you have a second copy of MMDVM_Bridge running?

No ... not to my knowledge ;)


Please show output of netstat -unap

Connexions Internet actives (serveurs et établies)
Proto Recv-Q Send-Q Adresse locale          Adresse distante        Etat        PID/Program name   
udp        0      0 0.0.0.0:31100           0.0.0.0:*                           1066/Analog_Bridge 
udp        0      0 0.0.0.0:31103           0.0.0.0:*                           1065/MMDVM_Bridge  
udp        0      0 0.0.0.0:44935           0.0.0.0:*                           1065/MMDVM_Bridge  
udp        0      0 0.0.0.0:2470            0.0.0.0:*                           1067/md380-emu     
udp        0      0 0.0.0.0:50111         0.0.0.0:*                           1066/Analog_Bridge 
udp        0      0 0.0.0.0:68                0.0.0.0:*                           413/dhcpcd         
udp        0      0 0.0.0.0:62032           0.0.0.0:*                           1065/MMDVM_Bridge  
udp        0      0 0.0.0.0:1194            0.0.0.0:*                           555/openvpn        
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           371/avahi-daemon: r
udp        0      0 0.0.0.0:40744           0.0.0.0:*                           1066/Analog_Bridge 
udp        0      0 0.0.0.0:36656           0.0.0.0:*                           371/avahi-daemon: r
udp        0      0 0.0.0.0:52564           0.0.0.0:*                           1066/Analog_Bridge 
udp6       0      0 :::53620                :::*                                371/avahi-daemon: r
udp6       0      0 :::64738                :::*                                1043/murmurd       
udp6       0      0 :::5353                 :::*                                371/avahi-daemon: r


Philippe, f5rvx




Re: MMDVM_Bridge Timeout

Philippe, f5rvx
 


Le 27/10/2019 à 12:27, Steve N4IRS a écrit :
Do you have a second copy of MMDVM_Bridge running?

No ... not to my knowledge ;)


Please show output of netstat -unap

Connexions Internet actives (serveurs et établies)
Proto Recv-Q Send-Q Adresse locale          Adresse distante        Etat        PID/Program name   
udp        0      0 0.0.0.0:31100           0.0.0.0:*                           1066/Analog_Bridge 
udp        0      0 0.0.0.0:31103           0.0.0.0:*                           1065/MMDVM_Bridge  
udp        0      0 0.0.0.0:44935           0.0.0.0:*                           1065/MMDVM_Bridge  
udp        0      0 0.0.0.0:2470            0.0.0.0:*                           1067/md380-emu     
udp        0      0 0.0.0.0:50111         0.0.0.0:*                           1066/Analog_Bridge 
udp        0      0 0.0.0.0:68                0.0.0.0:*                           413/dhcpcd         
udp        0      0 0.0.0.0:62032           0.0.0.0:*                           1065/MMDVM_Bridge  
udp        0      0 0.0.0.0:1194            0.0.0.0:*                           555/openvpn        
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           371/avahi-daemon: r
udp        0      0 0.0.0.0:40744           0.0.0.0:*                           1066/Analog_Bridge 
udp        0      0 0.0.0.0:36656           0.0.0.0:*                           371/avahi-daemon: r
udp        0      0 0.0.0.0:52564           0.0.0.0:*                           1066/Analog_Bridge 
udp6       0      0 :::53620                :::*                                371/avahi-daemon: r
udp6       0      0 :::64738                :::*                                1043/murmurd       
udp6       0      0 :::5353                 :::*                                371/avahi-daemon: r


Philippe, f5rvx



Re: MMDVM_Bridge Timeout

Steve N4IRS
 

I can login to the Master with the info you provided. Do you have a second copy of MMDVM_Bridge running?
Please show output of netstat -unap

On 10/27/2019 7:09 AM, ph.ttv@... via Groups.Io wrote:

Thanks for your return Steve,

but I'm sorry : I was thinking of bringing a bit of help  !!!


Please post your MMDVM_Bridge.ini so we can take a look.
[General]
Callsign=F5RVX
Id=208801429
Timeout=180
Duplex=0

[Info]
RXFrequency=000000000
TXFrequency=000000000
Power=0
Latitude=47.5636
Longitude=-3.8123
Height=0
Location=Hotspot test dept 29
Description=RX only for the moment
URL=

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

[DMR Id Lookup]
File=/var/lib/mmdvm/DMRIds.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=1
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0

[System Fusion]
Enable=0

[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=1

[DMR Network]
Enable=1
#Address=hblink.dvswitch.org
Address=217.182.129.131
# (
I tried different addresses in Europe but
everywhere the same thing : connect/disconnect )
Port=62031
Jitter=360
#Jitter=450
Local=62032
#Password=passw0rd
Password=xxxxxxxxxx
Slot1=0
#Slot1=1 
is it possible to have slot1=1 AND slot2=1? if not why ?
Slot2=1
Debug=1

[System Fusion Network]
Enable=0
LocalAddress=0
LocalPort=3200
GatewayAddress=ysfreflector.dvswitch.org
GatewayPort=42166
Debug=1

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

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


Best 73'

Philippe, f5rvx


Le 27/10/2019 à 11:20, Steve N4IRS a écrit :
Philippe,
Your issue is a little different unless you do get logged in for a while then loose connection.Please post your MMDVM_Bridge.ini so we can take a look.

73, Steve N4IRS

On 10/27/19 5:44 AM, ph.ttv@... via Groups.Io wrote:

Hi Dvswitchers,

I discovered for a few days this world of digital (I hope I have a few years left to understand ... the basics;)
First tests so with DvSwitch + DvSwitch Mobile on Rx and if I tell you my little life here, it is because I encounter the same problem as
Dexter.

D: 2019-10-27 09:25:05.897 DMR, Sending authorisation
D: 2019-10-27 09:25:05.923 DMR, Sending configuration
M: 2019-10-27 09:25:05.949 DMR, Logged into the master successfully
W: 2019-10-27 09:26:05.990 DMR, Login to the master has failed, retrying login ...
E: 2019-10-27 09:27:05.994 DMR, Connection to the master has timed out, retrying connection
M: 2019-10-27 09:27:05.994 DMR, Closing DMR Network
M: 2019-10-27 09:27:05.994 DMR, Opening DMR Network
D: 2019-10-27 09:27:16.020 DMR, Sending authorisation
D: 2019-10-27 09:27:16.046 DMR, Sending configuration
M: 2019-10-27 09:27:16.071 DMR, Logged into the master successfully
W: 2019-10-27 09:28:16.105 DMR, Login to the master has failed, retrying login ...


Or the common denominator, Raspbian?
I do not think poor Raspbian is to blame, but maybe a father, a mother, or some grandparent, because I found exactly the same thing by first installing DvSwitch on my computer. .. that works under ... Ubuntu (18.04).


That's all I can add, well not quite:
Thank you very much for this forum and sharing all this work around DvSwitch!

Philippe, f5rvx





D: 2019-10-27 09:25:05.897 DMR, Sending authorisation
D: 2019-10-27 09:25:05.923 DMR, Sending configuration
M: 2019-10-27 09:25:05.949 DMR, Logged into the master successfully
W: 2019-10-27 09:26:05.990 DMR, Login to the master has failed, retrying login ...
E: 2019-10-27 09:27:05.994 DMR, Connection to the master has timed out, retrying connection
M: 2019-10-27 09:27:05.994 DMR, Closing DMR Network
M: 2019-10-27 09:27:05.994 DMR, Opening DMR Network
D: 2019-10-27 09:27:16.020 DMR, Sending authorisation
D: 2019-10-27 09:27:16.046 DMR, Sending configuration
M: 2019-10-27 09:27:16.071 DMR, Logged into the master successfully
W: 2019-10-27 09:28:16.105 DMR, Login to the master has failed, retrying login ...


Le 27/10/2019 à 00:37, Steve N4IRS a écrit :
Or the common denominator, Raspbian?

On 10/26/2019 6:35 PM, David Ranch wrote:

I had a very similar issue with my Rpi 3+ running HamVoIP the current version of HamVoIP + DVSwitch software.  In my case, I was loosing connection to the BM Master every 70 seconds and I even created Brandmeister support ticket BMUSA-1193 .  The fix?  I rebooted my Raspberry Pi.  I can't explain why this would be but after I did that, everything was fine.  Give the reboot a try and let us know if it helps.  If it does, maybe this is indicating some sort of a long run issue with DV Switch, HamVoIP's Asterisk, etc.

--David
KI6ZHD


On 10/26/2019 01:07 PM, Dexter Harroo wrote:
Hi Guys,
I have MMDVM_Bridge setup to link a DMR Talkgroup to a ysf reflector, it has been working flawlessly for quite some time, recently i started having issues with the connection where it times out.
closing DMR network
opening DMR network
Login to the master has failed, retrying network connection
closing DMR network
opening DMR network
sending autorization 
sending configuration
logged into the master successfully
Login to the master has failed, retrying network connection.


and it keeps doing that over and over again, has any one else experienced this, can someone shed some light as to what may be the issue, so far i checked my ports on the router to make sure they're opened
9Y4C
Dexter





Re: MMDVM_Bridge Timeout

Philippe, f5rvx
 

Thanks for your return Steve,

but I'm sorry : I was thinking of bringing a bit of help  !!!


Please post your MMDVM_Bridge.ini so we can take a look.
[General]
Callsign=F5RVX
Id=208801429
Timeout=180
Duplex=0

[Info]
RXFrequency=000000000
TXFrequency=000000000
Power=0
Latitude=47.5636
Longitude=-3.8123
Height=0
Location=Hotspot test dept 29
Description=RX only for the moment
URL=

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

[DMR Id Lookup]
File=/var/lib/mmdvm/DMRIds.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=1
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0

[System Fusion]
Enable=0

[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=1

[DMR Network]
Enable=1
#Address=hblink.dvswitch.org
Address=217.182.129.131
# (
I tried different addresses in Europe but
everywhere the same thing : connect/disconnect )
Port=62031
Jitter=360
#Jitter=450
Local=62032
#Password=passw0rd
Password=xxxxxxxxxx
Slot1=0
#Slot1=1 
is it possible to have slot1=1 AND slot2=1? if not why ?
Slot2=1
Debug=1

[System Fusion Network]
Enable=0
LocalAddress=0
LocalPort=3200
GatewayAddress=ysfreflector.dvswitch.org
GatewayPort=42166
Debug=1

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

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


Best 73'

Philippe, f5rvx


Le 27/10/2019 à 11:20, Steve N4IRS a écrit :
Philippe,
Your issue is a little different unless you do get logged in for a while then loose connection.Please post your MMDVM_Bridge.ini so we can take a look.

73, Steve N4IRS

On 10/27/19 5:44 AM, ph.ttv@... via Groups.Io wrote:

Hi Dvswitchers,

I discovered for a few days this world of digital (I hope I have a few years left to understand ... the basics;)
First tests so with DvSwitch + DvSwitch Mobile on Rx and if I tell you my little life here, it is because I encounter the same problem as
Dexter.

D: 2019-10-27 09:25:05.897 DMR, Sending authorisation
D: 2019-10-27 09:25:05.923 DMR, Sending configuration
M: 2019-10-27 09:25:05.949 DMR, Logged into the master successfully
W: 2019-10-27 09:26:05.990 DMR, Login to the master has failed, retrying login ...
E: 2019-10-27 09:27:05.994 DMR, Connection to the master has timed out, retrying connection
M: 2019-10-27 09:27:05.994 DMR, Closing DMR Network
M: 2019-10-27 09:27:05.994 DMR, Opening DMR Network
D: 2019-10-27 09:27:16.020 DMR, Sending authorisation
D: 2019-10-27 09:27:16.046 DMR, Sending configuration
M: 2019-10-27 09:27:16.071 DMR, Logged into the master successfully
W: 2019-10-27 09:28:16.105 DMR, Login to the master has failed, retrying login ...


Or the common denominator, Raspbian?
I do not think poor Raspbian is to blame, but maybe a father, a mother, or some grandparent, because I found exactly the same thing by first installing DvSwitch on my computer. .. that works under ... Ubuntu (18.04).


That's all I can add, well not quite:
Thank you very much for this forum and sharing all this work around DvSwitch!

Philippe, f5rvx





D: 2019-10-27 09:25:05.897 DMR, Sending authorisation
D: 2019-10-27 09:25:05.923 DMR, Sending configuration
M: 2019-10-27 09:25:05.949 DMR, Logged into the master successfully
W: 2019-10-27 09:26:05.990 DMR, Login to the master has failed, retrying login ...
E: 2019-10-27 09:27:05.994 DMR, Connection to the master has timed out, retrying connection
M: 2019-10-27 09:27:05.994 DMR, Closing DMR Network
M: 2019-10-27 09:27:05.994 DMR, Opening DMR Network
D: 2019-10-27 09:27:16.020 DMR, Sending authorisation
D: 2019-10-27 09:27:16.046 DMR, Sending configuration
M: 2019-10-27 09:27:16.071 DMR, Logged into the master successfully
W: 2019-10-27 09:28:16.105 DMR, Login to the master has failed, retrying login ...


Le 27/10/2019 à 00:37, Steve N4IRS a écrit :
Or the common denominator, Raspbian?

On 10/26/2019 6:35 PM, David Ranch wrote:

I had a very similar issue with my Rpi 3+ running HamVoIP the current version of HamVoIP + DVSwitch software.  In my case, I was loosing connection to the BM Master every 70 seconds and I even created Brandmeister support ticket BMUSA-1193 .  The fix?  I rebooted my Raspberry Pi.  I can't explain why this would be but after I did that, everything was fine.  Give the reboot a try and let us know if it helps.  If it does, maybe this is indicating some sort of a long run issue with DV Switch, HamVoIP's Asterisk, etc.

--David
KI6ZHD


On 10/26/2019 01:07 PM, Dexter Harroo wrote:
Hi Guys,
I have MMDVM_Bridge setup to link a DMR Talkgroup to a ysf reflector, it has been working flawlessly for quite some time, recently i started having issues with the connection where it times out.
closing DMR network
opening DMR network
Login to the master has failed, retrying network connection
closing DMR network
opening DMR network
sending autorization 
sending configuration
logged into the master successfully
Login to the master has failed, retrying network connection.


and it keeps doing that over and over again, has any one else experienced this, can someone shed some light as to what may be the issue, so far i checked my ports on the router to make sure they're opened
9Y4C
Dexter




Re: MMDVM_Bridge Timeout

Steve N4IRS
 

Philippe,
Your issue is a little different unless you do get logged in for a while then loose connection.Please post your MMDVM_Bridge.ini so we can take a look.

73, Steve N4IRS

On 10/27/19 5:44 AM, ph.ttv@... via Groups.Io wrote:

Hi Dvswitchers,

I discovered for a few days this world of digital (I hope I have a few years left to understand ... the basics;)
First tests so with DvSwitch + DvSwitch Mobile on Rx and if I tell you my little life here, it is because I encounter the same problem as
Dexter.

D: 2019-10-27 09:25:05.897 DMR, Sending authorisation
D: 2019-10-27 09:25:05.923 DMR, Sending configuration
M: 2019-10-27 09:25:05.949 DMR, Logged into the master successfully
W: 2019-10-27 09:26:05.990 DMR, Login to the master has failed, retrying login ...
E: 2019-10-27 09:27:05.994 DMR, Connection to the master has timed out, retrying connection
M: 2019-10-27 09:27:05.994 DMR, Closing DMR Network
M: 2019-10-27 09:27:05.994 DMR, Opening DMR Network
D: 2019-10-27 09:27:16.020 DMR, Sending authorisation
D: 2019-10-27 09:27:16.046 DMR, Sending configuration
M: 2019-10-27 09:27:16.071 DMR, Logged into the master successfully
W: 2019-10-27 09:28:16.105 DMR, Login to the master has failed, retrying login ...


Or the common denominator, Raspbian?
I do not think poor Raspbian is to blame, but maybe a father, a mother, or some grandparent, because I found exactly the same thing by first installing DvSwitch on my computer. .. that works under ... Ubuntu (18.04).


That's all I can add, well not quite:
Thank you very much for this forum and sharing all this work around DvSwitch!

Philippe, f5rvx





D: 2019-10-27 09:25:05.897 DMR, Sending authorisation
D: 2019-10-27 09:25:05.923 DMR, Sending configuration
M: 2019-10-27 09:25:05.949 DMR, Logged into the master successfully
W: 2019-10-27 09:26:05.990 DMR, Login to the master has failed, retrying login ...
E: 2019-10-27 09:27:05.994 DMR, Connection to the master has timed out, retrying connection
M: 2019-10-27 09:27:05.994 DMR, Closing DMR Network
M: 2019-10-27 09:27:05.994 DMR, Opening DMR Network
D: 2019-10-27 09:27:16.020 DMR, Sending authorisation
D: 2019-10-27 09:27:16.046 DMR, Sending configuration
M: 2019-10-27 09:27:16.071 DMR, Logged into the master successfully
W: 2019-10-27 09:28:16.105 DMR, Login to the master has failed, retrying login ...


Le 27/10/2019 à 00:37, Steve N4IRS a écrit :
Or the common denominator, Raspbian?

On 10/26/2019 6:35 PM, David Ranch wrote:

I had a very similar issue with my Rpi 3+ running HamVoIP the current version of HamVoIP + DVSwitch software.  In my case, I was loosing connection to the BM Master every 70 seconds and I even created Brandmeister support ticket BMUSA-1193 .  The fix?  I rebooted my Raspberry Pi.  I can't explain why this would be but after I did that, everything was fine.  Give the reboot a try and let us know if it helps.  If it does, maybe this is indicating some sort of a long run issue with DV Switch, HamVoIP's Asterisk, etc.

--David
KI6ZHD


On 10/26/2019 01:07 PM, Dexter Harroo wrote:
Hi Guys,
I have MMDVM_Bridge setup to link a DMR Talkgroup to a ysf reflector, it has been working flawlessly for quite some time, recently i started having issues with the connection where it times out.
closing DMR network
opening DMR network
Login to the master has failed, retrying network connection
closing DMR network
opening DMR network
sending autorization 
sending configuration
logged into the master successfully
Login to the master has failed, retrying network connection.


and it keeps doing that over and over again, has any one else experienced this, can someone shed some light as to what may be the issue, so far i checked my ports on the router to make sure they're opened
9Y4C
Dexter




Re: MMDVM_Bridge Timeout

Philippe, f5rvx
 

Hi Dvswitchers,

I discovered for a few days this world of digital (I hope I have a few years left to understand ... the basics;)
First tests so with DvSwitch + DvSwitch Mobile on Rx and if I tell you my little life here, it is because I encounter the same problem as
Dexter.

D: 2019-10-27 09:25:05.897 DMR, Sending authorisation
D: 2019-10-27 09:25:05.923 DMR, Sending configuration
M: 2019-10-27 09:25:05.949 DMR, Logged into the master successfully
W: 2019-10-27 09:26:05.990 DMR, Login to the master has failed, retrying login ...
E: 2019-10-27 09:27:05.994 DMR, Connection to the master has timed out, retrying connection
M: 2019-10-27 09:27:05.994 DMR, Closing DMR Network
M: 2019-10-27 09:27:05.994 DMR, Opening DMR Network
D: 2019-10-27 09:27:16.020 DMR, Sending authorisation
D: 2019-10-27 09:27:16.046 DMR, Sending configuration
M: 2019-10-27 09:27:16.071 DMR, Logged into the master successfully
W: 2019-10-27 09:28:16.105 DMR, Login to the master has failed, retrying login ...


Or the common denominator, Raspbian?
I do not think poor Raspbian is to blame, but maybe a father, a mother, or some grandparent, because I found exactly the same thing by first installing DvSwitch on my computer. .. that works under ... Ubuntu (18.04).


That's all I can add, well not quite:
Thank you very much for this forum and sharing all this work around DvSwitch!

Philippe, f5rvx





D: 2019-10-27 09:25:05.897 DMR, Sending authorisation
D: 2019-10-27 09:25:05.923 DMR, Sending configuration
M: 2019-10-27 09:25:05.949 DMR, Logged into the master successfully
W: 2019-10-27 09:26:05.990 DMR, Login to the master has failed, retrying login ...
E: 2019-10-27 09:27:05.994 DMR, Connection to the master has timed out, retrying connection
M: 2019-10-27 09:27:05.994 DMR, Closing DMR Network
M: 2019-10-27 09:27:05.994 DMR, Opening DMR Network
D: 2019-10-27 09:27:16.020 DMR, Sending authorisation
D: 2019-10-27 09:27:16.046 DMR, Sending configuration
M: 2019-10-27 09:27:16.071 DMR, Logged into the master successfully
W: 2019-10-27 09:28:16.105 DMR, Login to the master has failed, retrying login ...


Le 27/10/2019 à 00:37, Steve N4IRS a écrit :
Or the common denominator, Raspbian?

On 10/26/2019 6:35 PM, David Ranch wrote:

I had a very similar issue with my Rpi 3+ running HamVoIP the current version of HamVoIP + DVSwitch software.  In my case, I was loosing connection to the BM Master every 70 seconds and I even created Brandmeister support ticket BMUSA-1193 .  The fix?  I rebooted my Raspberry Pi.  I can't explain why this would be but after I did that, everything was fine.  Give the reboot a try and let us know if it helps.  If it does, maybe this is indicating some sort of a long run issue with DV Switch, HamVoIP's Asterisk, etc.

--David
KI6ZHD


On 10/26/2019 01:07 PM, Dexter Harroo wrote:
Hi Guys,
I have MMDVM_Bridge setup to link a DMR Talkgroup to a ysf reflector, it has been working flawlessly for quite some time, recently i started having issues with the connection where it times out.
closing DMR network
opening DMR network
Login to the master has failed, retrying network connection
closing DMR network
opening DMR network
sending autorization 
sending configuration
logged into the master successfully
Login to the master has failed, retrying network connection.


and it keeps doing that over and over again, has any one else experienced this, can someone shed some light as to what may be the issue, so far i checked my ports on the router to make sure they're opened
9Y4C
Dexter



Re: HBlink Help

wqtt240@...
 

found it
[XLX-1]
MODE: XLXPEER
ENABLED: True
LOOSE: True
EXPORT_AMBE: False


Re: HBlink Help

Kevin Halton
 

Let’s see your HBlink.cfg and rules.py


On Oct 26, 2019, at 10:03 PM, wqtt240@... wrote:

set up a dmr server as per Chris Hood it seems to be working but after connecting to master and peer I keep getting this in the log
INFO DATE AND TIME STAMP (XLX-1) Sending login request master 172.16.1.1:62030 can anyone why and how to fix


HBlink Help

wqtt240@...
 

set up a dmr server as per Chris Hood it seems to be working but after connecting to master and peer I keep getting this in the log
INFO DATE AND TIME STAMP (XLX-1) Sending login request master 172.16.1.1:62030 can anyone why and how to fix


Re: MMDVM_Bridge Timeout

Steve N4IRS
 

Or the common denominator, Raspbian?

On 10/26/2019 6:35 PM, David Ranch wrote:

I had a very similar issue with my Rpi 3+ running HamVoIP the current version of HamVoIP + DVSwitch software.  In my case, I was loosing connection to the BM Master every 70 seconds and I even created Brandmeister support ticket BMUSA-1193 .  The fix?  I rebooted my Raspberry Pi.  I can't explain why this would be but after I did that, everything was fine.  Give the reboot a try and let us know if it helps.  If it does, maybe this is indicating some sort of a long run issue with DV Switch, HamVoIP's Asterisk, etc.

--David
KI6ZHD


On 10/26/2019 01:07 PM, Dexter Harroo wrote:
Hi Guys,
I have MMDVM_Bridge setup to link a DMR Talkgroup to a ysf reflector, it has been working flawlessly for quite some time, recently i started having issues with the connection where it times out.
closing DMR network
opening DMR network
Login to the master has failed, retrying network connection
closing DMR network
opening DMR network
sending autorization 
sending configuration
logged into the master successfully
Login to the master has failed, retrying network connection.


and it keeps doing that over and over again, has any one else experienced this, can someone shed some light as to what may be the issue, so far i checked my ports on the router to make sure they're opened
9Y4C
Dexter



Re: MMDVM_Bridge Timeout

David Ranch
 


I had a very similar issue with my Rpi 3+ running HamVoIP the current version of HamVoIP + DVSwitch software.  In my case, I was loosing connection to the BM Master every 70 seconds and I even created Brandmeister support ticket BMUSA-1193 .  The fix?  I rebooted my Raspberry Pi.  I can't explain why this would be but after I did that, everything was fine.  Give the reboot a try and let us know if it helps.  If it does, maybe this is indicating some sort of a long run issue with DV Switch, HamVoIP's Asterisk, etc.

--David
KI6ZHD


On 10/26/2019 01:07 PM, Dexter Harroo wrote:
Hi Guys,
I have MMDVM_Bridge setup to link a DMR Talkgroup to a ysf reflector, it has been working flawlessly for quite some time, recently i started having issues with the connection where it times out.
closing DMR network
opening DMR network
Login to the master has failed, retrying network connection
closing DMR network
opening DMR network
sending autorization 
sending configuration
logged into the master successfully
Login to the master has failed, retrying network connection.


and it keeps doing that over and over again, has any one else experienced this, can someone shed some light as to what may be the issue, so far i checked my ports on the router to make sure they're opened
9Y4C
Dexter


Re: MMDVM_Bridge Timeout

Steve N4IRS
 

What network are you using now?
Please show the [DMR Network] stanza from MMDVM_Bridge.ini

On 10/26/19 5:34 PM, Dexter Harroo wrote:
OK, Lemme look for some info on connecting to BM


Re: MMDVM_Bridge Timeout

Dexter Harroo
 

OK, Lemme look for some info on connecting to BM

4781 - 4800 of 9820