Date   

Re: Building up a network

beni@...
 

Yes, I edited the DMR_Hosts.txt file adding custom DMR Host, so basically using MMDVMHost without DMRGateway in the middle.

Well, HBLink is really toxic, lol. 2am in here and I cannot leave it for today.

Now will try to learn and use the routing/bridging options so I can use those too.


Re: Building up a network

beni@...
 

Steve, yes, definitely a DMRGateway problem!

Tried the method I said; the one involving directly editing the PiStar's DMR_Hosts.txt file and now it works and and I can see traffic passing through.


Re: Building up a network

Steve N4IRS
 

From my connected MMDVMHost:
M: 2018-06-03 23:31:32.213 DMR Slot 2, received network voice header from 9999300 to TG 222
M: 2018-06-03 23:31:33.833 DMR Slot 2, received network end of voice transmission, 1.6 seconds, 7% packet loss, BER: 0.3%


On 06/03/2018 07:21 PM, beni@... wrote:
I can see them RPTPINGing after run "python hb_bridge_all.py" but cannot see any traffic logging or traffic passing from one HS to another


Re: Building up a network

Steve N4IRS
 

You can change from DEBUG to INFO Debug does not really tell you much.

On 06/03/2018 07:21 PM, beni@... wrote:
I can see them RPTPINGing after run "python hb_bridge_all.py" but cannot see any traffic logging or traffic passing from one HS to another


Re: Building up a network

Steve N4IRS
 

INFO 2018-06-04 01:26:46,176 (MASTER-1) *CALL END*   STREAM ID: 2762760302 SUB: N4IRS (3112138) REPEATER: 311213801 (311213801) TGID 9 (9), TS 2, Duration: 94.2459661961


On 06/03/2018 07:21 PM, beni@... wrote:
I can see them RPTPINGing after run "python hb_bridge_all.py" but cannot see any traffic logging or traffic passing from one HS to another


Re: Building up a network

beni@...
 

I can see them RPTPINGing after run "python hb_bridge_all.py" but cannot see any traffic logging or traffic passing from one HS to another


Re: Building up a network

beni@...
 

Steve, thanks. In the meantime I would try another approach. As I don't really need the DMRGateway, I will try to directly edit PiStar's DMR_Hosts.txt file and then connect "normally" as I would connect to a DMR Master Server.


Re: Building up a network

Steve N4IRS
 

I do not see them logged in. One hint I can give you is that hblink by itself does not log traffic. The best way to do that is to run hb_bridge_all.

Steve

On 06/03/2018 07:12 PM, beni@... wrote:
You'll also find two HotSpots logged in there; ZALH01 and ZALH03


Re: Building up a network

beni@...
 

You'll also find two HotSpots logged in there; ZALH01 and ZALH03


Re: Building up a network

Steve N4IRS
 

Ben,
I have 2 hotspots logged into your VPS. I'm connecting directly from MMDVMHost to HBlink, no DMRGateway. I can see the traffic passing from one HS to the other. I think you need to look closely at your DMRGateway configuration. Someone on the dvswitch list may be able to help.

73, Steve N4IRS

On 06/03/2018 06:28 PM, beni@... wrote:
Nothing strange @ the log file (attached also).

I think I will need to make my own "/usr/local/etc/DMRIds.dat" if that's a hint, right?


Re: Building up a network

Steve N4IRS
 

I'm logged in to the VPS now.

On 06/03/2018 06:28 PM, beni@... wrote:
Nothing strange @ the log file (attached also).

I think I will need to make my own "/usr/local/etc/DMRIds.dat" if that's a hint, right?


Re: Building up a network

beni@...
 

Nothing strange @ the log file (attached also).

I think I will need to make my own "/usr/local/etc/DMRIds.dat" if that's a hint, right?


Re: Building up a network

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#


Re: Building up a network

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#


Re: Building up a network

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#


Re: Building up a network

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


Re: Building up a network

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


Re: Building up a network

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


Re: Building up a network

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


Re: Building up a network

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

9141 - 9160 of 10637