Date   

Re: Master maintenance loop started

Jürgen Clemenz
 

and that when we start hblink.py
appropriate


Re: Master maintenance loop started

Jürgen Clemenz
 


Portscan


Re: Master maintenance loop started

Jürgen Clemenz
 

On Thu, Aug 9, 2018 at 11:32 AM, Steve N4IRS wrote:
While hblink is running show us the result of netstat -unap
root@v293571:/home/dh9yap/HBlink# netstat -unap
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
udp    50688      0 0.0.0.0:33462           0.0.0.0:*                           162/svxlink
udp    18432      0 0.0.0.0:33569           0.0.0.0:*                           165/svxlink
udp    47616      0 0.0.0.0:34179           0.0.0.0:*                           165/svxlink
udp    17664      0 0.0.0.0:34313           0.0.0.0:*                           170/svxlink
udp    35328      0 0.0.0.0:39745           0.0.0.0:*                           168/svxlink
udp    35328      0 0.0.0.0:40734           0.0.0.0:*                           166/svxlink
udp    50688      0 0.0.0.0:41970           0.0.0.0:*                           166/svxlink
udp    35328      0 0.0.0.0:46506           0.0.0.0:*                           162/svxlink
udp    50688      0 0.0.0.0:56694           0.0.0.0:*                           168/svxlink
udp    36864      0 0.0.0.0:56829           0.0.0.0:*                           169/svxlink
udp    15360      0 0.0.0.0:57484           0.0.0.0:*                           169/svxlink
udp    51456      0 0.0.0.0:5300            0.0.0.0:*                           150/svxreflector
udp    19200      0 0.0.0.0:5310            0.0.0.0:*                           156/svxreflector
udp    40704      0 0.0.0.0:5320            0.0.0.0:*                           146/svxreflector
udp    19200      0 0.0.0.0:5330            0.0.0.0:*                           153/svxreflector
udp    40704      0 0.0.0.0:5340            0.0.0.0:*                           149/svxreflector
udp    13824      0 0.0.0.0:5350            0.0.0.0:*                           151/svxreflector
udp    36864      0 0.0.0.0:5360            0.0.0.0:*                           147/svxreflector
udp    36864      0 0.0.0.0:5370            0.0.0.0:*                           144/svxreflector
udp        0      0 0.0.0.0:5380            0.0.0.0:*                           145/svxreflector
udp        0      0 0.0.0.0:5400            0.0.0.0:*                           171/python
root@v293571:/home/dh9yap/HBlink#
 


Re: Master maintenance loop started

Steve N4IRS
 

While hblink is running show us the result of netstat -unap

On 8/9/2018 2:31 PM, Jürgen Clemenz wrote:
When starting hblink, the port 5400 is not opened.
Other applications such as Svxlink's Svxlink open doe ports.



Re: Master maintenance loop started

Jürgen Clemenz
 

When starting hblink, the port 5400 is not opened.
Other applications such as Svxlink's Svxlink open doe ports.


Re: Master maintenance loop started

Jürgen Clemenz
 

the /tmp/hblink.log
is empty.


Re: Master maintenance loop started

Jürgen Clemenz
 

here you have to doh then see the incoming connection !?
INFO 2018-08-09 19: 03: 11,401 Registration ACL file found, importing entries. This will take about 1.5 seconds per 1 million IDs
INFO 2018-08-09 19: 03: 11,402 Registration ACL loaded: action "DENY" for 2 registration IDs
INFO 2018-08-09 19: 03: 11,402 HBlink TCP reporting server configured
INFO 2018-08-09 19: 03: 11,403 HBlink 'HBlink.py' (c) 2016 N0MJS & the KOUSY Group - SYSTEM STARTING ...


Re: Master maintenance loop started

Jürgen Clemenz
 

Maybe you can try to connect my master.
Address: 213.202.228.66
Port 5400
Password: funknetz.nrw


Re: Master maintenance loop started

Jürgen Clemenz
 

Maybe I understand something wrong.
I have here 2 raspberry pi Zero with one MMDVM duplex board (hotspot).
Would like the two private networks.
Later, there are more hotspots to come and they should all be connected.
73 Jürgen


Re: Master maintenance loop started

Jürgen Clemenz
 

Pi star could not get in touch before. I thought it was due to debug message.
I have now taken another port that is open on my Ubuntu server.
It does not work !

73 de Jürgen :-)


Re: Master maintenance loop started

Steve N4IRS
 

Are you saying that after the log change, Pi-Star can no longer connect?

Sent via smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Jürgen Clemenz <j.clemenz@...>
Sent: Thursday, August 9, 2018 10:48:18 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Master maintenance loop started
 
On Mon, Aug 6, 2018 at 09:17 AM, Steve N4IRS wrote:
LOG_LEVEL: INFO
Thank you for your prompt reply.
After the change the master is running.

I get with Pi-Star but no connection!
Log from Pi Star:

: 2018-08-09 14:36:21.598 MMDVMHost-20180802_Pi-Star exited on receipt of SIGTERM
I: 2018-08-09 14:36:28.061 This software is for use on amateur radio networks only,
I: 2018-08-09 14:36:28.061 it is to be used for educational purposes only. Its use on
I: 2018-08-09 14:36:28.061 commercial networks is strictly prohibited.
I: 2018-08-09 14:36:28.062 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2018-08-09 14:36:28.062 MMDVMHost-20180802_Pi-Star is starting
M: 2018-08-09 14:36:28.062 Built 22:50:25 Aug  2 2018 (GitID #69f1a21)
I: 2018-08-09 14:36:28.062 General Parameters
I: 2018-08-09 14:36:28.062     Callsign: DH9YAP
I: 2018-08-09 14:36:28.062     Id: 263441224
I: 2018-08-09 14:36:28.062     Duplex: no
I: 2018-08-09 14:36:28.062     Timeout: 240s
I: 2018-08-09 14:36:28.062     D-Star: disabled
I: 2018-08-09 14:36:28.062     DMR: enabled
I: 2018-08-09 14:36:28.062     YSF: disabled
I: 2018-08-09 14:36:28.063     P25: disabled
I: 2018-08-09 14:36:28.063     NXDN: disabled
I: 2018-08-09 14:36:28.063     POCSAG: disabled
I: 2018-08-09 14:36:28.063 Modem Parameters
I: 2018-08-09 14:36:28.063     Port: /dev/ttyAMA0
I: 2018-08-09 14:36:28.063     Protocol: uart
I: 2018-08-09 14:36:28.063     RX Invert: no
I: 2018-08-09 14:36:28.063     TX Invert: yes
I: 2018-08-09 14:36:28.063     PTT Invert: no
I: 2018-08-09 14:36:28.063     TX Delay: 100ms
I: 2018-08-09 14:36:28.063     RX Offset: 0Hz
I: 2018-08-09 14:36:28.063     TX Offset: 0Hz
I: 2018-08-09 14:36:28.063     RX DC Offset: 0
I: 2018-08-09 14:36:28.063     TX DC Offset: 0
I: 2018-08-09 14:36:28.063     RF Level: 100.0%
I: 2018-08-09 14:36:28.063     DMR Delay: 0 (0.0ms)
I: 2018-08-09 14:36:28.063     RX Level: 50.0%
I: 2018-08-09 14:36:28.063     CW Id TX Level: 50.0%
I: 2018-08-09 14:36:28.063     D-Star TX Level: 50.0%
I: 2018-08-09 14:36:28.064     DMR TX Level: 50.0%
I: 2018-08-09 14:36:28.064     YSF TX Level: 50.0%
I: 2018-08-09 14:36:28.064     P25 TX Level: 50.0%
I: 2018-08-09 14:36:28.064     NXDN TX Level: 50.0%
I: 2018-08-09 14:36:28.064     POCSAG TX Level: 50.0%
I: 2018-08-09 14:36:28.064     RX Frequency: 433612500Hz (433612500Hz)
I: 2018-08-09 14:36:28.064     TX Frequency: 433612500Hz (433612500Hz)
M: 2018-08-09 14:36:28.065 Opening the MMDVM
I: 2018-08-09 14:36:30.080 MMDVM protocol version: 1, description: MMDVM_HS_Dual_Hat-v1.4.6 20180720 14.7456MHz dual ADF7021 FW by CA6JAU GitID #10c725c
I: 2018-08-09 14:36:30.103 Display Parameters
I: 2018-08-09 14:36:30.103     Type: None
W: 2018-08-09 14:36:30.103 No valid display found, disabling
I: 2018-08-09 14:36:30.103 DMR Network Parameters
I: 2018-08-09 14:36:30.104     Address: 213.202.228.66
I: 2018-08-09 14:36:30.104     Port: 54000
I: 2018-08-09 14:36:30.104     Local: random
I: 2018-08-09 14:36:30.104     Jitter: 360ms
I: 2018-08-09 14:36:30.104     Slot 1: enabled
I: 2018-08-09 14:36:30.104     Slot 2: enabled
I: 2018-08-09 14:36:30.104     Mode Hang: 20s
I: 2018-08-09 14:36:30.104 Info Parameters
I: 2018-08-09 14:36:30.104     Callsign: DH9YAP
I: 2018-08-09 14:36:30.104     RX Frequency: 433612500Hz
I: 2018-08-09 14:36:30.104     TX Frequency: 433612500Hz
I: 2018-08-09 14:36:30.104     Power: 1W
I: 2018-08-09 14:36:30.104     Latitude: 51.588268deg N
I: 2018-08-09 14:36:30.104     Longitude: 7.145595deg E
I: 2018-08-09 14:36:30.104     Height: 0m
I: 2018-08-09 14:36:30.104     Location: "Herten, JO31NO"
I: 2018-08-09 14:36:30.104     Description: "Germany"
I: 2018-08-09 14:36:30.104     URL: "http://www.funknetz.nrw"
M: 2018-08-09 14:36:30.104 DMR, Opening DMR Network
I: 2018-08-09 14:36:30.105 RSSI
I: 2018-08-09 14:36:30.105     Mapping File: /usr/local/etc/RSSI.dat
I: 2018-08-09 14:36:30.107 Loaded 14 RSSI data mapping points from /usr/local/etc/RSSI.dat
I: 2018-08-09 14:36:30.107 DMR Id Lookups
I: 2018-08-09 14:36:30.107     File: /usr/local/etc/DMRIds.dat
I: 2018-08-09 14:36:30.107     Reload: 24 hours
I: 2018-08-09 14:36:32.132 Loaded 104513 Ids to the DMR callsign lookup table
I: 2018-08-09 14:36:32.132 DMR RF Parameters
I: 2018-08-09 14:36:32.132     Id: 263441224
I: 2018-08-09 14:36:32.132     Color Code: 1
I: 2018-08-09 14:36:32.132     Self Only: yes
I: 2018-08-09 14:36:32.132     Embedded LC Only: no
I: 2018-08-09 14:36:32.132     Dump Talker Alias Data: yes
I: 2018-08-09 14:36:32.132     Prefixes: 0
I: 2018-08-09 14:36:32.132     Call Hang: 3s
I: 2018-08-09 14:36:32.132     TX Hang: 4s
I: 2018-08-09 14:36:32.132     Mode Hang: 20s
M: 2018-08-09 14:36:32.133 MMDVMHost-20180802_Pi-Star is running
I: 2018-08-09 14:36:32.138 Started the DMR Id lookup reload thread
E: 2018-08-09 14:36:42.149 Error returned from sendto, err: 1
E: 2018-08-09 14:36:42.149 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:36:42.150 DMR, Opening DMR Network
E: 2018-08-09 14:36:52.176 Error returned from sendto, err: 1
E: 2018-08-09 14:36:52.177 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:36:52.177 DMR, Opening DMR Network
E: 2018-08-09 14:37:02.210 Error returned from sendto, err: 1
E: 2018-08-09 14:37:02.211 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:37:02.211 DMR, Opening DMR Network
E: 2018-08-09 14:37:12.229 Error returned from sendto, err: 1
E: 2018-08-09 14:37:12.229 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:37:12.229 DMR, Opening DMR Network
M: 2018-08-09 14:37:15.639 DMR Slot 2, received RF voice header from DH9YAP to TG ALL
M: 2018-08-09 14:37:17.677 DMR Slot 2, RF voice transmission lost, 0.7 seconds, BER: 13.2%, RSSI: -47/-47/-47 dBm
E: 2018-08-09 14:37:22.258 Error returned from sendto, err: 1
E: 2018-08-09 14:37:22.258 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:37:22.258 DMR, Opening DMR Network
M: 2018-08-09 14:37:32.175 DMR Slot 2, received RF voice header from DH9YAP to TG ALL
E: 2018-08-09 14:37:32.277 Error returned from sendto, err: 1
E: 2018-08-09 14:37:32.277 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:37:32.277 DMR, Opening DMR Network
M: 2018-08-09 14:37:37.811 DMR Slot 2, RF voice transmission lost, 5.5 seconds, BER: 5.9%, RSSI: -47/-47/-47 dBm
E: 2018-08-09 14:37:42.294 Error returned from sendto, err: 1
E: 2018-08-09 14:37:42.294 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:37:42.295 DMR, Opening DMR Network
E: 2018-08-09 14:37:52.319 Error returned from sendto, err: 1
E: 2018-08-09 14:37:52.320 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:37:52.320 DMR, Opening DMR Network
E: 2018-08-09 14:38:02.349 Error returned from sendto, err: 1
E: 2018-08-09 14:38:02.349 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:38:02.349 DMR, Opening DMR Network
E: 2018-08-09 14:38:12.366 Error returned from sendto, err: 1
E: 2018-08-09 14:38:12.366 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:38:12.367 DMR, Opening DMR Network
E: 2018-08-09 14:38:22.397 Error returned from sendto, err: 1
E: 2018-08-09 14:38:22.397 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:38:22.397 DMR, Opening DMR Network


Re: Master maintenance loop started

Jürgen Clemenz
 

On Mon, Aug 6, 2018 at 09:17 AM, Steve N4IRS wrote:
LOG_LEVEL: INFO
Thank you for your prompt reply.
After the change the master is running.

I get with Pi-Star but no connection!
Log from Pi Star:

: 2018-08-09 14:36:21.598 MMDVMHost-20180802_Pi-Star exited on receipt of SIGTERM
I: 2018-08-09 14:36:28.061 This software is for use on amateur radio networks only,
I: 2018-08-09 14:36:28.061 it is to be used for educational purposes only. Its use on
I: 2018-08-09 14:36:28.061 commercial networks is strictly prohibited.
I: 2018-08-09 14:36:28.062 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2018-08-09 14:36:28.062 MMDVMHost-20180802_Pi-Star is starting
M: 2018-08-09 14:36:28.062 Built 22:50:25 Aug  2 2018 (GitID #69f1a21)
I: 2018-08-09 14:36:28.062 General Parameters
I: 2018-08-09 14:36:28.062     Callsign: DH9YAP
I: 2018-08-09 14:36:28.062     Id: 263441224
I: 2018-08-09 14:36:28.062     Duplex: no
I: 2018-08-09 14:36:28.062     Timeout: 240s
I: 2018-08-09 14:36:28.062     D-Star: disabled
I: 2018-08-09 14:36:28.062     DMR: enabled
I: 2018-08-09 14:36:28.062     YSF: disabled
I: 2018-08-09 14:36:28.063     P25: disabled
I: 2018-08-09 14:36:28.063     NXDN: disabled
I: 2018-08-09 14:36:28.063     POCSAG: disabled
I: 2018-08-09 14:36:28.063 Modem Parameters
I: 2018-08-09 14:36:28.063     Port: /dev/ttyAMA0
I: 2018-08-09 14:36:28.063     Protocol: uart
I: 2018-08-09 14:36:28.063     RX Invert: no
I: 2018-08-09 14:36:28.063     TX Invert: yes
I: 2018-08-09 14:36:28.063     PTT Invert: no
I: 2018-08-09 14:36:28.063     TX Delay: 100ms
I: 2018-08-09 14:36:28.063     RX Offset: 0Hz
I: 2018-08-09 14:36:28.063     TX Offset: 0Hz
I: 2018-08-09 14:36:28.063     RX DC Offset: 0
I: 2018-08-09 14:36:28.063     TX DC Offset: 0
I: 2018-08-09 14:36:28.063     RF Level: 100.0%
I: 2018-08-09 14:36:28.063     DMR Delay: 0 (0.0ms)
I: 2018-08-09 14:36:28.063     RX Level: 50.0%
I: 2018-08-09 14:36:28.063     CW Id TX Level: 50.0%
I: 2018-08-09 14:36:28.063     D-Star TX Level: 50.0%
I: 2018-08-09 14:36:28.064     DMR TX Level: 50.0%
I: 2018-08-09 14:36:28.064     YSF TX Level: 50.0%
I: 2018-08-09 14:36:28.064     P25 TX Level: 50.0%
I: 2018-08-09 14:36:28.064     NXDN TX Level: 50.0%
I: 2018-08-09 14:36:28.064     POCSAG TX Level: 50.0%
I: 2018-08-09 14:36:28.064     RX Frequency: 433612500Hz (433612500Hz)
I: 2018-08-09 14:36:28.064     TX Frequency: 433612500Hz (433612500Hz)
M: 2018-08-09 14:36:28.065 Opening the MMDVM
I: 2018-08-09 14:36:30.080 MMDVM protocol version: 1, description: MMDVM_HS_Dual_Hat-v1.4.6 20180720 14.7456MHz dual ADF7021 FW by CA6JAU GitID #10c725c
I: 2018-08-09 14:36:30.103 Display Parameters
I: 2018-08-09 14:36:30.103     Type: None
W: 2018-08-09 14:36:30.103 No valid display found, disabling
I: 2018-08-09 14:36:30.103 DMR Network Parameters
I: 2018-08-09 14:36:30.104     Address: 213.202.228.66
I: 2018-08-09 14:36:30.104     Port: 54000
I: 2018-08-09 14:36:30.104     Local: random
I: 2018-08-09 14:36:30.104     Jitter: 360ms
I: 2018-08-09 14:36:30.104     Slot 1: enabled
I: 2018-08-09 14:36:30.104     Slot 2: enabled
I: 2018-08-09 14:36:30.104     Mode Hang: 20s
I: 2018-08-09 14:36:30.104 Info Parameters
I: 2018-08-09 14:36:30.104     Callsign: DH9YAP
I: 2018-08-09 14:36:30.104     RX Frequency: 433612500Hz
I: 2018-08-09 14:36:30.104     TX Frequency: 433612500Hz
I: 2018-08-09 14:36:30.104     Power: 1W
I: 2018-08-09 14:36:30.104     Latitude: 51.588268deg N
I: 2018-08-09 14:36:30.104     Longitude: 7.145595deg E
I: 2018-08-09 14:36:30.104     Height: 0m
I: 2018-08-09 14:36:30.104     Location: "Herten, JO31NO"
I: 2018-08-09 14:36:30.104     Description: "Germany"
I: 2018-08-09 14:36:30.104     URL: "http://www.funknetz.nrw"
M: 2018-08-09 14:36:30.104 DMR, Opening DMR Network
I: 2018-08-09 14:36:30.105 RSSI
I: 2018-08-09 14:36:30.105     Mapping File: /usr/local/etc/RSSI.dat
I: 2018-08-09 14:36:30.107 Loaded 14 RSSI data mapping points from /usr/local/etc/RSSI.dat
I: 2018-08-09 14:36:30.107 DMR Id Lookups
I: 2018-08-09 14:36:30.107     File: /usr/local/etc/DMRIds.dat
I: 2018-08-09 14:36:30.107     Reload: 24 hours
I: 2018-08-09 14:36:32.132 Loaded 104513 Ids to the DMR callsign lookup table
I: 2018-08-09 14:36:32.132 DMR RF Parameters
I: 2018-08-09 14:36:32.132     Id: 263441224
I: 2018-08-09 14:36:32.132     Color Code: 1
I: 2018-08-09 14:36:32.132     Self Only: yes
I: 2018-08-09 14:36:32.132     Embedded LC Only: no
I: 2018-08-09 14:36:32.132     Dump Talker Alias Data: yes
I: 2018-08-09 14:36:32.132     Prefixes: 0
I: 2018-08-09 14:36:32.132     Call Hang: 3s
I: 2018-08-09 14:36:32.132     TX Hang: 4s
I: 2018-08-09 14:36:32.132     Mode Hang: 20s
M: 2018-08-09 14:36:32.133 MMDVMHost-20180802_Pi-Star is running
I: 2018-08-09 14:36:32.138 Started the DMR Id lookup reload thread
E: 2018-08-09 14:36:42.149 Error returned from sendto, err: 1
E: 2018-08-09 14:36:42.149 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:36:42.150 DMR, Opening DMR Network
E: 2018-08-09 14:36:52.176 Error returned from sendto, err: 1
E: 2018-08-09 14:36:52.177 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:36:52.177 DMR, Opening DMR Network
E: 2018-08-09 14:37:02.210 Error returned from sendto, err: 1
E: 2018-08-09 14:37:02.211 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:37:02.211 DMR, Opening DMR Network
E: 2018-08-09 14:37:12.229 Error returned from sendto, err: 1
E: 2018-08-09 14:37:12.229 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:37:12.229 DMR, Opening DMR Network
M: 2018-08-09 14:37:15.639 DMR Slot 2, received RF voice header from DH9YAP to TG ALL
M: 2018-08-09 14:37:17.677 DMR Slot 2, RF voice transmission lost, 0.7 seconds, BER: 13.2%, RSSI: -47/-47/-47 dBm
E: 2018-08-09 14:37:22.258 Error returned from sendto, err: 1
E: 2018-08-09 14:37:22.258 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:37:22.258 DMR, Opening DMR Network
M: 2018-08-09 14:37:32.175 DMR Slot 2, received RF voice header from DH9YAP to TG ALL
E: 2018-08-09 14:37:32.277 Error returned from sendto, err: 1
E: 2018-08-09 14:37:32.277 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:37:32.277 DMR, Opening DMR Network
M: 2018-08-09 14:37:37.811 DMR Slot 2, RF voice transmission lost, 5.5 seconds, BER: 5.9%, RSSI: -47/-47/-47 dBm
E: 2018-08-09 14:37:42.294 Error returned from sendto, err: 1
E: 2018-08-09 14:37:42.294 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:37:42.295 DMR, Opening DMR Network
E: 2018-08-09 14:37:52.319 Error returned from sendto, err: 1
E: 2018-08-09 14:37:52.320 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:37:52.320 DMR, Opening DMR Network
E: 2018-08-09 14:38:02.349 Error returned from sendto, err: 1
E: 2018-08-09 14:38:02.349 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:38:02.349 DMR, Opening DMR Network
E: 2018-08-09 14:38:12.366 Error returned from sendto, err: 1
E: 2018-08-09 14:38:12.366 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:38:12.367 DMR, Opening DMR Network
E: 2018-08-09 14:38:22.397 Error returned from sendto, err: 1
E: 2018-08-09 14:38:22.397 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:38:22.397 DMR, Opening DMR Network


Re: HBlink "socket_address" Branch

Cort N0MJS <n0mjs@...>
 

merge #15 on July 29, 2018.

I always fork from the current master branch.

On Aug 8, 2018, at 7:07 PM, JJ Cummings <cummingsj@...> wrote:

Court as long as it supports the different config files that I sent the pull for a while back I’ll test it.

Sent from the iRoad

On Aug 8, 2018, at 18:12, Cort N0MJS via Groups.Io <n0mjs@...> wrote:

both sides were intended to, so if there are errors, I need the full traceback output and configuration files. I’ve been able to let them  register both ways, keep state, but extremely limited traffic through the apps above HBlink.py itself – which is where the VAST majority fo the updates were.

On Aug 8, 2018, at 5:24 PM, Joe <ea5sw@...> wrote:

The Client part don't work at this time, only the master right ??

Cort Buffington
785-865-7206


Cort Buffington
785-865-7206


Re: HBlink "socket_address" Branch

JJ Cummings
 

Court as long as it supports the different config files that I sent the pull for a while back I’ll test it.

Sent from the iRoad

On Aug 8, 2018, at 18:12, Cort N0MJS via Groups.Io <n0mjs@...> wrote:

both sides were intended to, so if there are errors, I need the full traceback output and configuration files. I’ve been able to let them  register both ways, keep state, but extremely limited traffic through the apps above HBlink.py itself – which is where the VAST majority fo the updates were.

On Aug 8, 2018, at 5:24 PM, Joe <ea5sw@...> wrote:

The Client part don't work at this time, only the master right ??

Cort Buffington
785-865-7206


Re: HBlink "socket_address" Branch

Cort N0MJS <n0mjs@...>
 

both sides were intended to, so if there are errors, I need the full traceback output and configuration files. I’ve been able to let them  register both ways, keep state, but extremely limited traffic through the apps above HBlink.py itself – which is where the VAST majority fo the updates were.

On Aug 8, 2018, at 5:24 PM, Joe <ea5sw@...> wrote:

The Client part don't work at this time, only the master right ??

Cort Buffington
785-865-7206


Re: HBlink "socket_address" Branch

Jose - EA5SW
 

The Client part don't work at this time, only the master right ??


Re: HBlink "socket_address" Branch

Cort N0MJS <n0mjs@...>
 

GitHub, “socket_address” branch.

On Aug 8, 2018, at 3:36 AM, Peter M0NWI <peter-martin@...> wrote:

Hi Cort,

I've a non mission critical HBLink instance connected to a few hotspots and a repeater, which I bridge into my DMRLink confbridge over IPSCBridge, I'm sure I could give the new version a try?

Where do I grab the files from?

73,
Peter



From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Cort N0MJS via Groups.Io <n0mjs@...>
Sent: 07 August 2018 23:18
To: DVSwitch@groups.io; HBlink@DVSwitch.groups.io
Subject: [DVSwitch] HBlink "socket_address" Branch
 
I NEED TESTERS FOR THE “socket_address” BRANCH OF HBLINK

This is only applicable to those using hblink.py by itself, hb_confbridge.py and hb_bridge_all.py. I also ask that testers be folks who can successfully set up these programs on their own without help – that is to say, those of you who have UNIX cli, can generally read python error messages, and understand what I need to diagnose an errors.

I would like this branch to merge to the master BEFORE the next steps, because up to this point, I’ve mad a number of changes that make HBlink better, but does not yet change peer validation to use socket address instead of DMR ID.

I probably pushed way too many changes before more testing. The fact of the matter is, I now have way too much going on here to maintain a comprehensive test environment. I will need your help to run this as DevOps in order to catch issues. If you find a bug and can offer a fix, but are not comfortable using GitHub, please just send me before/after snippets with line numbers.

Please let me know if you’re going to test so I have some idea who’s brave enough to ride along. Also, this message is cross-posted to both the main and hblink sub-groups in DVSWitch. Let’s keep the discussion related to this on the HBlink sub-group to keep the noise down here.


FROM THE COMMIT MESSAGE:

0) CONFIGURATION FILES WILL NEED UPDATED TO CHANGE NAMING
CONFIGURATIONS!

1) Updated use of socket address instead of discrete IP/port. This will
be needed for socket address based validation and is faster… duh…
should have done this in the beginning.

2) Changed all references to “clients” as HBP systems to “peers”. This
sets the stage for having a peer_id and an originator_id for DMRD
packets.

3) Found and squashed a number of other random bugs, including the
registration ACL not working in confbridge or bridge_all.

4) router is now retired. confbridge is the future.

0x49 DE N0MJS

Cort Buffington
785-865-7206





Cort Buffington
785-865-7206


Re: HBlink "socket_address" Branch

Peter M0NWI
 

Hi Cort,


I've a non mission critical HBLink instance connected to a few hotspots and a repeater, which I bridge into my DMRLink confbridge over IPSCBridge, I'm sure I could give the new version a try?


Where do I grab the files from?


73,

Peter




From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Cort N0MJS via Groups.Io <n0mjs@...>
Sent: 07 August 2018 23:18
To: DVSwitch@groups.io; HBlink@DVSwitch.groups.io
Subject: [DVSwitch] HBlink "socket_address" Branch
 
I NEED TESTERS FOR THE “socket_address” BRANCH OF HBLINK

This is only applicable to those using hblink.py by itself, hb_confbridge.py and hb_bridge_all.py. I also ask that testers be folks who can successfully set up these programs on their own without help – that is to say, those of you who have UNIX cli, can generally read python error messages, and understand what I need to diagnose an errors.

I would like this branch to merge to the master BEFORE the next steps, because up to this point, I’ve mad a number of changes that make HBlink better, but does not yet change peer validation to use socket address instead of DMR ID.

I probably pushed way too many changes before more testing. The fact of the matter is, I now have way too much going on here to maintain a comprehensive test environment. I will need your help to run this as DevOps in order to catch issues. If you find a bug and can offer a fix, but are not comfortable using GitHub, please just send me before/after snippets with line numbers.

Please let me know if you’re going to test so I have some idea who’s brave enough to ride along. Also, this message is cross-posted to both the main and hblink sub-groups in DVSWitch. Let’s keep the discussion related to this on the HBlink sub-group to keep the noise down here.


FROM THE COMMIT MESSAGE:

0) CONFIGURATION FILES WILL NEED UPDATED TO CHANGE NAMING
CONFIGURATIONS!

1) Updated use of socket address instead of discrete IP/port. This will
be needed for socket address based validation and is faster… duh…
should have done this in the beginning.

2) Changed all references to “clients” as HBP systems to “peers”. This
sets the stage for having a peer_id and an originator_id for DMRD
packets.

3) Found and squashed a number of other random bugs, including the
registration ACL not working in confbridge or bridge_all.

4) router is now retired. confbridge is the future.

0x49 DE N0MJS

Cort Buffington
785-865-7206





HBlink "socket_address" Branch

Cort N0MJS <n0mjs@...>
 

I NEED TESTERS FOR THE “socket_address” BRANCH OF HBLINK

This is only applicable to those using hblink.py by itself, hb_confbridge.py and hb_bridge_all.py. I also ask that testers be folks who can successfully set up these programs on their own without help – that is to say, those of you who have UNIX cli, can generally read python error messages, and understand what I need to diagnose an errors.

I would like this branch to merge to the master BEFORE the next steps, because up to this point, I’ve mad a number of changes that make HBlink better, but does not yet change peer validation to use socket address instead of DMR ID.

I probably pushed way too many changes before more testing. The fact of the matter is, I now have way too much going on here to maintain a comprehensive test environment. I will need your help to run this as DevOps in order to catch issues. If you find a bug and can offer a fix, but are not comfortable using GitHub, please just send me before/after snippets with line numbers.

Please let me know if you’re going to test so I have some idea who’s brave enough to ride along. Also, this message is cross-posted to both the main and hblink sub-groups in DVSWitch. Let’s keep the discussion related to this on the HBlink sub-group to keep the noise down here.


FROM THE COMMIT MESSAGE:

0) CONFIGURATION FILES WILL NEED UPDATED TO CHANGE NAMING
CONFIGURATIONS!

1) Updated use of socket address instead of discrete IP/port. This will
be needed for socket address based validation and is faster… duh…
should have done this in the beginning.

2) Changed all references to “clients” as HBP systems to “peers”. This
sets the stage for having a peer_id and an originator_id for DMRD
packets.

3) Found and squashed a number of other random bugs, including the
registration ACL not working in confbridge or bridge_all.

4) router is now retired. confbridge is the future.

0x49 DE N0MJS

Cort Buffington
785-865-7206


Hbmonitor full work. Perfectly

EA5GVK Joaquin
 

Many thx Steven and all friends groups.io for your help me. 
HBmonitor magnífic. 
Http://ea5gvk.duckdns.org:8088.

7781 - 7800 of 9820