Building up a network


beni@...
 

Hi there all and first of all thank you for the great tools; not only useful - but also interesting to learn.

Let me first give you some background information and next what I am trying to accomplish.

I live in a country - the "Black Sheep" of the HAM community in terms of digital - Albania. There are not too many HAMs in Albania, and even so mostly we operate in HF. In terms of Digital there is nothing - null - nil, and this is unacceptable to me, lol.

Now, I have some MMDVM hotspots (DVMega, Zumspot, Duplex MMDVM_HS), around 6 or 7 in total and I plan to distribute them (indeed for free) to HAMs around the country, so people can have at least a way to access DMR. Also some my own DMR HTs and some more I am trying to get form a good individual that is trying to help. Later on I was promised we would get two Mototrbo 1st gen repeaters (DR3000) from an organization, and in the meantime I am trying to build a home-brew MMDVD repeater with two GM300s that I have.

I would love to interconnect all those terminals in a network, and I want to do this without being part of the actual DMR Networks "political" games. My point is to incentivize HAMs in Albania and not making them part of the ongoing DMR Networks "war". I wont be around for long in Albania so the two months I got here I want to try to teach and incentivize HAMs - not lightning a fire. 

This is why I plan to use DVSwitch tools - first to learn and next interconnect to the whole worldwide DMR Network.

Tried to read most of the messages in here but I am still not very clear. Anyway I like experiments and I will start from HBLink right after I write this topic, and hope you understand when I ask questions from time to time if I don't find a solution.

In the meantime, if someone can help me with a rough - simple How to I would be very grateful.

Thanks in advance,

Ben


Steve N4IRS
 

Ben,
Welcome to the group. We understand not wanting to be part of the politics. I do not see any problem with waht you are trying to do and it certainly can be done with the programs of DVSwitch. I would star with HBlink on a computer that each HS can access (ping) That will get all the MMDVM based devices talking to each other. You can expand from there.

We are working on documentation and though it's slow going, we are getting there.

73, Steve N4IRS


On 06/03/2018 07:12 AM, beni@... wrote:
Hi there all and first of all thank you for the great tools; not only useful - but also interesting to learn.

Let me first give you some background information and next what I am trying to accomplish.

I live in a country - the "Black Sheep" of the HAM community in terms of digital - Albania. There are not too many HAMs in Albania, and even so mostly we operate in HF. In terms of Digital there is nothing - null - nil, and this is unacceptable to me, lol.

Now, I have some MMDVM hotspots (DVMega, Zumspot, Duplex MMDVM_HS), around 6 or 7 in total and I plan to distribute them (indeed for free) to HAMs around the country, so people can have at least a way to access DMR. Also some my own DMR HTs and some more I am trying to get form a good individual that is trying to help. Later on I was promised we would get two Mototrbo 1st gen repeaters (DR3000) from an organization, and in the meantime I am trying to build a home-brew MMDVD repeater with two GM300s that I have.

I would love to interconnect all those terminals in a network, and I want to do this without being part of the actual DMR Networks "political" games. My point is to incentivize HAMs in Albania and not making them part of the ongoing DMR Networks "war". I wont be around for long in Albania so the two months I got here I want to try to teach and incentivize HAMs - not lightning a fire. 

This is why I plan to use DVSwitch tools - first to learn and next interconnect to the whole worldwide DMR Network.

Tried to read most of the messages in here but I am still not very clear. Anyway I like experiments and I will start from HBLink right after I write this topic, and hope you understand when I ask questions from time to time if I don't find a solution.

In the meantime, if someone can help me with a rough - simple How to I would be very grateful.

Thanks in advance,

Ben


beni@...
 

Steve, thanks for the reply.

It is not that I do not want to connect to the "big" networks, but in my opinion (and I might be wrong, of course) it is best first they learn and adapt in a smaller scale, next they can connect to whatever network they want.

I am at the moment setting up a vps on Debian Stretch, then next HBLink.

Ben


beni@...
 

Setup HBLink on a vps, run it and it seems it runs ok.

also, configured two of the hotspots (Pi-Star) enabling DMRGateway, disabling BM and DMR+, enabling HBLink and configuring HBLink with the IP, port and password I setup on hblink configuration file.

But, the hotspots seems do not connect, when I run "hblink.py" I get the following:

root@vps523689:~# cd /home/debian/Downloads/HBlink ; python hblink.py
DEBUG 2018-06-03 17:22:15,858 Logging system started, anything from here on gets logged
INFO 2018-06-03 17:22:15,858 HBlink 'HBlink.py' (c) 2016 N0MJS & the K0USY Group - SYSTEM STARTING...
DEBUG 2018-06-03 17:22:15,859 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:22:15,860 MASTER instance created: MASTER-1, <__main__.HBSYSTEM instance at 0x7faa2581f8c0>
DEBUG 2018-06-03 17:22:20,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:22:25,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:22:30,865 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:22:35,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:22:40,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:22:45,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:22:50,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:22:55,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:23:00,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:23:05,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:23:10,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:23:15,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:23:20,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:23:25,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:23:30,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:23:35,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:23:40,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:23:45,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:23:50,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:23:55,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:24:00,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:24:05,865 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:24:10,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:24:15,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:24:20,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:24:25,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:24:30,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:24:35,860 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:24:40,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:24:45,860 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:24:50,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:24:55,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:25:00,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:25:05,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:25:10,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:25:15,864 (MASTER-1) Master maintenance loop started


and I do not see any connection messages from the hotspots trying to connect.

Anything you think I did wrong?


Steve N4IRS
 

Ben,
Can you post your MASTER-1 stanza and the section of DMRGateway that is suppoed to be connecting to hblink?
Anything in the logs of dmrgateay or MMDVM?

Steve

On 06/03/2018 11:35 AM, beni@... wrote:
Setup HBLink on a vps, run it and it seems it runs ok.

also, configured two of the hotspots (Pi-Star) enabling DMRGateway, disabling BM and DMR+, enabling HBLink and configuring HBLink with the IP, port and password I setup on hblink configuration file.

But, the hotspots seems do not connect, when I run "hblink.py" I get the following:

root@vps523689:~# cd /home/debian/Downloads/HBlink ; python hblink.py
DEBUG 2018-06-03 17:22:15,858 Logging system started, anything from here on gets logged
INFO 2018-06-03 17:22:15,858 HBlink 'HBlink.py' (c) 2016 N0MJS & the K0USY Group - SYSTEM STARTING...
DEBUG 2018-06-03 17:22:15,859 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:22:15,860 MASTER instance created: MASTER-1, <__main__.HBSYSTEM instance at 0x7faa2581f8c0>
DEBUG 2018-06-03 17:22:20,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:22:25,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:22:30,865 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:22:35,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:22:40,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:22:45,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:22:50,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:22:55,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:23:00,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:23:05,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:23:10,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:23:15,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:23:20,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:23:25,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:23:30,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:23:35,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:23:40,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:23:45,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:23:50,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:23:55,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:24:00,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:24:05,865 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:24:10,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:24:15,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:24:20,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:24:25,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:24:30,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:24:35,860 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:24:40,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:24:45,860 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:24:50,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:24:55,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:25:00,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:25:05,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:25:10,864 (MASTER-1) Master maintenance loop started
DEBUG 2018-06-03 17:25:15,864 (MASTER-1) Master maintenance loop started


and I do not see any connection messages from the hotspots trying to connect.

Anything you think I did wrong?


beni@...
 

Steve, thanks.

Attached herein hblink.cfg, and the Pi-Star's DMRGateway config section that connects to hblink is:


[DMR Network 3]
Enabled=1
Name=HBLink
Address=164.132.42.221
Port=8413
TGRewrite=2,11,2,11,1
Password=passiword
Location=0
Debug=0

PS. It is Pi-Star's own option, not added by me. The only thing I changed there are the IP, port and password.


Steve N4IRS
 

Anything in the DMRGateway log?

On 06/03/2018 11:58 AM, beni@... wrote:
Steve, thanks.

Attached herein hblink.cfg, and the Pi-Star's DMRGateway config section that connects to hblink is:


[DMR Network 3]
Enabled=1
Name=HBLink
Address=164.132.42.221
Port=8413
TGRewrite=2,11,2,11,1
Password=passiword
Location=0
Debug=0

PS. It is Pi-Star's own option, not added by me. The only thing I changed there are the IP, port and password.


beni@...
 

Yep, sorry. forgot to attach:

I: 2018-06-03 15:23:10.101 This software is for use on amateur radio networks only,
I: 2018-06-03 15:23:10.102 it is to be used for educational purposes only. Its use on
I: 2018-06-03 15:23:10.102 commercial networks is strictly prohibited.
I: 2018-06-03 15:23:10.102 Copyright(C) 2017 by Jonathan Naylor, G4KLX and others
M: 2018-06-03 15:23:10.102 DMRGateway-20180528_Pi-Star is starting
M: 2018-06-03 15:23:10.102 Built 19:11:37 May 28 2018 (GitID #aa4c906)
I: 2018-06-03 15:23:10.102 MMDVM Network Parameters
I: 2018-06-03 15:23:10.102     Rpt Address: 127.0.0.1
I: 2018-06-03 15:23:10.102     Rpt Port: 62032
I: 2018-06-03 15:23:10.102     Local Address: 127.0.0.1
I: 2018-06-03 15:23:10.102     Local Port: 62031
M: 2018-06-03 15:23:10.102 MMDVM Network, Opening
M: 2018-06-03 15:23:10.103 Waiting for MMDVM to connect.....
M: 2018-06-03 15:23:43.714 MMDVM has connected
I: 2018-06-03 15:23:43.714 Rule trace: no
I: 2018-06-03 15:23:43.714 DMR Network 3 Parameters
I: 2018-06-03 15:23:43.714     Name:
I: 2018-06-03 15:23:43.714     Id: 222624702
I: 2018-06-03 15:23:43.714     Address: 164.132.42.221
I: 2018-06-03 15:23:43.714     Port: 8413
I: 2018-06-03 15:23:43.714     Local: random
I: 2018-06-03 15:23:43.714     Location Data: no
I: 2018-06-03 15:23:43.715 HBLink: Original configuration message: ZA1AVK  235500000235500000010135.09999-17.00000000TR,   TR, AL        4http://www.qrz.com/db/ZA1AVK                                                                                                20180522_Pi-Star                        MMDVM_MMDVM_HS_Hat                     
I: 2018-06-03 15:23:43.715 HBLink: New configuration message: ZA1AVK  235500000235500000010135.09999-17.00000000TR,   TR, AL            4http://www.qrz.com/db/ZA1AVK                                                                                                20180522_Pi-Star                        MMDVM_MMDVM_HS_Hat                     
M: 2018-06-03 15:23:43.715 HBLink, Opening DMR Network
I: 2018-06-03 15:23:43.715     Rewrite RF: 2:TG11 -> 2:TG11
I: 2018-06-03 15:23:43.715     Rewrite Net: 2:TG11 -> 2:TG11
M: 2018-06-03 15:23:43.715 DMRGateway-20180528_Pi-Star is running
E: 2018-06-03 15:23:53.724 Error returned from sendto, err: 1
E: 2018-06-03 15:23:53.724 HBLink, Socket has failed when writing data to the master, retrying connection
M: 2018-06-03 15:23:53.724 HBLink, Opening DMR Network
E: 2018-06-03 15:24:03.737 Error returned from sendto, err: 1
E: 2018-06-03 15:24:03.737 HBLink, Socket has failed when writing data to the master, retrying connection
M: 2018-06-03 15:24:03.737 HBLink, Opening DMR Network
E: 2018-06-03 15:24:13.744 Error returned from sendto, err: 1
E: 2018-06-03 15:24:13.744 HBLink, Socket has failed when writing data to the master, retrying connection
M: 2018-06-03 15:24:13.744 HBLink, Opening DMR Network
E: 2018-06-03 15:24:23.749 Error returned from sendto, err: 1
E: 2018-06-03 15:24:23.749 HBLink, Socket has failed when writing data to the master, retrying connection
.
.
.
.
M: 2018-06-03 16:09:05.973 HBLink, Opening DMR Network
E: 2018-06-03 16:09:15.981 Error returned from sendto, err: 1
E: 2018-06-03 16:09:15.981 HBLink, Socket has failed when writing data to the master, retrying connection
M: 2018-06-03 16:09:15.982 HBLink, Opening DMR Network
E: 2018-06-03 16:09:25.995 Error returned from sendto, err: 1
E: 2018-06-03 16:09:25.995 HBLink, Socket has failed when writing data to the master, retrying connection
M: 2018-06-03 16:09:25.995 HBLink, Opening DMR Network


Steve N4IRS
 

Ben,
From what you show below, DMRGateway is unable to login. The port numbers look good. Are you sure of the IP address of the machine running HBlink?
netstat -unap should show you python listening on port 8413. Is it possible the port is getting blocked?

Steve

On 06/03/2018 12:16 PM, beni@... wrote:
Yep, sorry. forgot to attach:

I: 2018-06-03 15:23:10.101 This software is for use on amateur radio networks only,
I: 2018-06-03 15:23:10.102 it is to be used for educational purposes only. Its use on
I: 2018-06-03 15:23:10.102 commercial networks is strictly prohibited.
I: 2018-06-03 15:23:10.102 Copyright(C) 2017 by Jonathan Naylor, G4KLX and others
M: 2018-06-03 15:23:10.102 DMRGateway-20180528_Pi-Star is starting
M: 2018-06-03 15:23:10.102 Built 19:11:37 May 28 2018 (GitID #aa4c906)
I: 2018-06-03 15:23:10.102 MMDVM Network Parameters
I: 2018-06-03 15:23:10.102     Rpt Address: 127.0.0.1
I: 2018-06-03 15:23:10.102     Rpt Port: 62032
I: 2018-06-03 15:23:10.102     Local Address: 127.0.0.1
I: 2018-06-03 15:23:10.102     Local Port: 62031
M: 2018-06-03 15:23:10.102 MMDVM Network, Opening
M: 2018-06-03 15:23:10.103 Waiting for MMDVM to connect.....
M: 2018-06-03 15:23:43.714 MMDVM has connected
I: 2018-06-03 15:23:43.714 Rule trace: no
I: 2018-06-03 15:23:43.714 DMR Network 3 Parameters
I: 2018-06-03 15:23:43.714     Name:
I: 2018-06-03 15:23:43.714     Id: 222624702
I: 2018-06-03 15:23:43.714     Address: 164.132.42.221
I: 2018-06-03 15:23:43.714     Port: 8413
I: 2018-06-03 15:23:43.714     Local: random
I: 2018-06-03 15:23:43.714     Location Data: no
I: 2018-06-03 15:23:43.715 HBLink: Original configuration message: ZA1AVK  235500000235500000010135.09999-17.00000000TR,   TR, AL        4http://www.qrz.com/db/ZA1AVK                                                                                                20180522_Pi-Star                        MMDVM_MMDVM_HS_Hat                     
I: 2018-06-03 15:23:43.715 HBLink: New configuration message: ZA1AVK  235500000235500000010135.09999-17.00000000TR,   TR, AL            4http://www.qrz.com/db/ZA1AVK                                                                                                20180522_Pi-Star                        MMDVM_MMDVM_HS_Hat                     
M: 2018-06-03 15:23:43.715 HBLink, Opening DMR Network
I: 2018-06-03 15:23:43.715     Rewrite RF: 2:TG11 -> 2:TG11
I: 2018-06-03 15:23:43.715     Rewrite Net: 2:TG11 -> 2:TG11
M: 2018-06-03 15:23:43.715 DMRGateway-20180528_Pi-Star is running
E: 2018-06-03 15:23:53.724 Error returned from sendto, err: 1
E: 2018-06-03 15:23:53.724 HBLink, Socket has failed when writing data to the master, retrying connection
M: 2018-06-03 15:23:53.724 HBLink, Opening DMR Network
E: 2018-06-03 15:24:03.737 Error returned from sendto, err: 1
E: 2018-06-03 15:24:03.737 HBLink, Socket has failed when writing data to the master, retrying connection
M: 2018-06-03 15:24:03.737 HBLink, Opening DMR Network
E: 2018-06-03 15:24:13.744 Error returned from sendto, err: 1
E: 2018-06-03 15:24:13.744 HBLink, Socket has failed when writing data to the master, retrying connection
M: 2018-06-03 15:24:13.744 HBLink, Opening DMR Network
E: 2018-06-03 15:24:23.749 Error returned from sendto, err: 1
E: 2018-06-03 15:24:23.749 HBLink, Socket has failed when writing data to the master, retrying connection
.
.
.
.
M: 2018-06-03 16:09:05.973 HBLink, Opening DMR Network
E: 2018-06-03 16:09:15.981 Error returned from sendto, err: 1
E: 2018-06-03 16:09:15.981 HBLink, Socket has failed when writing data to the master, retrying connection
M: 2018-06-03 16:09:15.982 HBLink, Opening DMR Network
E: 2018-06-03 16:09:25.995 Error returned from sendto, err: 1
E: 2018-06-03 16:09:25.995 HBLink, Socket has failed when writing data to the master, retrying connection
M: 2018-06-03 16:09:25.995 HBLink, Opening DMR Network


beni@...
 

netstat show this:

root@vps523689:~# netstat -unap
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State                                                                                                                                                                    PID/Program name
udp        0      0 0.0.0.0:68              0.0.0.0:*                                                                                                                                                                                        649/dhclient
udp        0      0 0.0.0.0:8413            0.0.0.0:*                                                                                                                                                                                        1168/python
root@vps523689:~#

I don't think ISP is blocking anything, but, who knows. Let me try with another port and let you know.


Steve N4IRS
 

That looks good. I can try connecting from here if you would like.

On 06/03/2018 12:30 PM, beni@... wrote:
netstat show this:

root@vps523689:~# netstat -unap
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State                                                                                                                                                                    PID/Program name
udp        0      0 0.0.0.0:68              0.0.0.0:*                                                                                                                                                                                        649/dhclient
udp        0      0 0.0.0.0:8413            0.0.0.0:*                                                                                                                                                                                        1168/python
root@vps523689:~#

I don't think ISP is blocking anything, but, who knows. Let me try with another port and let you know.


beni@...
 

sure, be my guest if you like. Port changed to 62113 by the way and still no connection


Steve N4IRS
 
Edited

So,
Ben and i have been working via e-mail direct to resolve his issue. To be complete and have a post for the next guy that runs into this I'm posting the results.
Ben is trying to connect to a clean install of HBlink on a VPS host. He can not connect with a Pi-Star DMRGateway on ports 62113 and 8413. When I tried from my non Pi-Star MMDVMHost, I was able to connect.
Well, I tried on my Pi-Star install. I could not connect on port numbers 62113 and 8413. When I changed Ben's hblink.cfg to the default HB port of 62031, I could connect with DMRGateway on my Pi-Star install.


I checked the Pi-Star GUI, I could find no editor for the firewall on the Pi-Star  install. I think you could edit the file used to setup the firewall, but I'm going to stop here. Can you guess what the problem is?

Pi-Star is blocking the outbound UDP traffic on ports 62113 and 8413. I just set fire to my Pi-Star install so I could not test further. (not really)
In looking at /usr/local/sbin/pistar-firewall I see that outbound UDP ports 62031 and 55555 are allowed. If you are using Pi-Star I suggest you use you use port 55555 since editing the firewall script will be overwritten by a update from Pi-Star.

73, Steve N4IRS

On 06/03/2018 12:36 PM, beni@... wrote:
sure, be my guest if you like. Port changed to 62113 by the way and still no connection


Matthew 2E0SIP
 

Good Work Steve, it would have taken me a while to remember Pi-Star drops outbound connections.

For the Pi-Star firewall rules, you can edit it them using the CLI - http://wiki.pistar.uk/Adding_custom_firewall_rules_to_Pi-Star


Peter M0NWI
 

Steve,

These is a custom ports firewall file in /root you can alter to allow custom ports, you need to edit the file, do an update (which incorporates the customs), and a restart.

If you just mod it directly then it stops PiStar doing any further updates, which is a bit annoying, but I understand where Andy is coming from with regards to being secure and easier to support.

73,
Peter

Sent from Outlook
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: 03 June 2018 19:47:24
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Building up a network
 
So,
Ben and i have been working via e-mail direct to resolve his issue. To be complete and have a post for the next guy that runs into this I'm posting the results.
Ben is trying to connect to a clean install of HBlink on a VPS host. He can not connect with a Pi-Star DMRGateway on ports 62113 and 8413. When I tried from my non Pi-Star MMDVMHost, I was able to connect.
Well, I tried on my Pi-Star install. I could not connect on port numbers 62113 and 8413. When I changed Ben's hblink.cfg to the default HB port of 62031, I could connect with DMRGateway on my Pi-Star install.


I checked the Pi-Star GUI, I could find no editor for the firewall on the Pi-Star  install. I think you could edit the file used to setup the firewall, but I'm going to stop here. Can you guess what the problem is?

Pi-Star is blocking the outbound UDP traffic on ports 62113 and 8413. I just set fire to my Pi-Star install so I could not test further. (not really)

73, Steve N4IRS

On 06/03/2018 12:36 PM, beni@... wrote:
sure, be my guest if you like. Port changed to 62113 by the way and still no connection


beni@...
 

Well, I don't know what to say except many many many thanks to all and especially - to Steve for the help!

I am sure I would never found a solution if it were for me!


Ben


Corey Dean N3FE <n3fe@...>
 

Disable the firewall on the pi-star


On Jun 3, 2018, at 2:47 PM, Steve N4IRS <szingman@...> wrote:

So,
Ben and i have been working via e-mail direct to resolve his issue. To be complete and have a post for the next guy that runs into this I'm posting the results.
Ben is trying to connect to a clean install of HBlink on a VPS host. He can not connect with a Pi-Star DMRGateway on ports 62113 and 8413. When I tried from my non Pi-Star MMDVMHost, I was able to connect.
Well, I tried on my Pi-Star install. I could not connect on port numbers 62113 and 8413. When I changed Ben's hblink.cfg to the default HB port of 62031, I could connect with DMRGateway on my Pi-Star install.


I checked the Pi-Star GUI, I could find no editor for the firewall on the Pi-Star  install. I think you could edit the file used to setup the firewall, but I'm going to stop here. Can you guess what the problem is?

Pi-Star is blocking the outbound UDP traffic on ports 62113 and 8413. I just set fire to my Pi-Star install so I could not test further. (not really)

73, Steve N4IRS

On 06/03/2018 12:36 PM, beni@... wrote:
sure, be my guest if you like. Port changed to 62113 by the way and still no connection


beni@...
 

That did the trick. Hotspots connecting to HBLink instance successfully, but not communicating with eachother. I mean, I TX into HotSpot A - HotSpot A recieves the TX but HotSpot B remains silent.

Also when running "python hb_confbridge.py" i get

root@vps550841:/home/debian/Downloads/HBlink# python hb_confbridge.py
DEBUG 2018-06-04 00:05:28,816 Logging system started, anything from here on gets logged
INFO 2018-06-04 00:05:28,817 ID ALIAS MAPPER: 'peer_ids.csv' is current, not downloaded
INFO 2018-06-04 00:05:28,817 ID ALIAS MAPPER: 'subscriber_ids.csv' is current, not downloaded
INFO 2018-06-04 00:05:28,829 ID ALIAS MAPPER: peer_ids dictionary is available
INFO 2018-06-04 00:05:28,910 ID ALIAS MAPPER: subscriber_ids dictionary is available
INFO 2018-06-04 00:05:28,911 ID ALIAS MAPPER: talkgroup_ids dictionary is available
Traceback (most recent call last):
  File "hb_confbridge.py", line 468, in <module>
    BRIDGES = make_bridges('hb_confbridge_rules')
  File "hb_confbridge.py", line 72, in make_bridges
    bridge_file = import_module(_hb_confbridge_bridges)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
  File "/home/debian/Downloads/HBlink/hb_confbridge_rules.py", line 44
    'TIRANA': [
           ^
SyntaxError: invalid syntax
root@vps550841:/home/debian/Downloads/HBlink#


Steve N4IRS
 

Just running hblink with repeat=true all connected MMDVMs should hear each other. You should also be able to run bridge_all.py

On 06/03/2018 06:08 PM, beni@... wrote:
That did the trick. Hotspots connecting to HBLink instance successfully, but not communicating with eachother. I mean, I TX into HotSpot A - HotSpot A recieves the TX but HotSpot B remains silent.

Also when running "python hb_confbridge.py" i get

root@vps550841:/home/debian/Downloads/HBlink# python hb_confbridge.py
DEBUG 2018-06-04 00:05:28,816 Logging system started, anything from here on gets logged
INFO 2018-06-04 00:05:28,817 ID ALIAS MAPPER: 'peer_ids.csv' is current, not downloaded
INFO 2018-06-04 00:05:28,817 ID ALIAS MAPPER: 'subscriber_ids.csv' is current, not downloaded
INFO 2018-06-04 00:05:28,829 ID ALIAS MAPPER: peer_ids dictionary is available
INFO 2018-06-04 00:05:28,910 ID ALIAS MAPPER: subscriber_ids dictionary is available
INFO 2018-06-04 00:05:28,911 ID ALIAS MAPPER: talkgroup_ids dictionary is available
Traceback (most recent call last):
  File "hb_confbridge.py", line 468, in <module>
    BRIDGES = make_bridges('hb_confbridge_rules')
  File "hb_confbridge.py", line 72, in make_bridges
    bridge_file = import_module(_hb_confbridge_bridges)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
  File "/home/debian/Downloads/HBlink/hb_confbridge_rules.py", line 44
    'TIRANA': [
           ^
SyntaxError: invalid syntax
root@vps550841:/home/debian/Downloads/HBlink#


Steve N4IRS
 

Check the MMDVMHost log on all connected nodes for hints.

On 06/03/2018 06:08 PM, beni@... wrote:
That did the trick. Hotspots connecting to HBLink instance successfully, but not communicating with eachother. I mean, I TX into HotSpot A - HotSpot A recieves the TX but HotSpot B remains silent.

Also when running "python hb_confbridge.py" i get

root@vps550841:/home/debian/Downloads/HBlink# python hb_confbridge.py
DEBUG 2018-06-04 00:05:28,816 Logging system started, anything from here on gets logged
INFO 2018-06-04 00:05:28,817 ID ALIAS MAPPER: 'peer_ids.csv' is current, not downloaded
INFO 2018-06-04 00:05:28,817 ID ALIAS MAPPER: 'subscriber_ids.csv' is current, not downloaded
INFO 2018-06-04 00:05:28,829 ID ALIAS MAPPER: peer_ids dictionary is available
INFO 2018-06-04 00:05:28,910 ID ALIAS MAPPER: subscriber_ids dictionary is available
INFO 2018-06-04 00:05:28,911 ID ALIAS MAPPER: talkgroup_ids dictionary is available
Traceback (most recent call last):
  File "hb_confbridge.py", line 468, in <module>
    BRIDGES = make_bridges('hb_confbridge_rules')
  File "hb_confbridge.py", line 72, in make_bridges
    bridge_file = import_module(_hb_confbridge_bridges)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
  File "/home/debian/Downloads/HBlink/hb_confbridge_rules.py", line 44
    'TIRANA': [
           ^
SyntaxError: invalid syntax
root@vps550841:/home/debian/Downloads/HBlink#