Date   

Pi image #dmrlink

ke2ems
 

Do anyone have a working imiage they could share or point me to one. KE2EMS@... 

Thanks


Re: LAN address as FQDN in P25Hosts.txt?

Ray Harden
 

Missed your earlier msg ... until now ...
The environment includes:

Two MMDVM/Rpi's, one with P25 & DMR enabled radio is MSF5000 VHF; Second RPi  running the MMDVM/DVSwitch recently downloaded - configured.

Radios: XTS3000 UHF P25 enabled, Astro Spectra VHF P25 enabled, both have the TGs 31900 31901 set.

XTS3000 UHF is used to access a remote MSF5000 similarly configured for further testing.

LAN is 192.168.3.xx, both RPi's locally attached. Software running well, and considerable time running the port chains, .ini settings to get things this far.

"PTT ON" shows in log, attempting to transmit to erroneous IP address.  It comes down network addressing I think.

Thanks for your valuable time


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: Thursday, February 28, 2019 1:52:27 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] LAN address as FQDN in P25Hosts.txt?
 
Ray,
Can you give me a better understanding of your configuration. hosts and LAN not .ini files.

On 2/28/2019 2:26 PM, Ray Harden wrote:
That was my first reaction too ... No way to know ... port 41000 is forwarded to 192. 168.3.130.  But no WAN access to modem.


Sent: Thursday, February 28, 2019 7:20:16 PM
Subject: Re: [DVSwitch] LAN address as FQDN in P25Hosts.txt?
 
This is what I see in your reflector log:
M: 2019-02-28 04:34:22.684 Currently linked repeaters:
M: 2019-02-28 04:34:22.684     W0RAY      (97.125.17.237:42010) 2/120
M: 2019-02-28 04:35:58.149 Removing W0RAY      (97.125.17.237:42010) unlinked
M: 2019-02-28 04:35:58.155 Data received from an unknown source - 97.125.17.237:42010
M: 2019-02-28 04:35:58.155 Data
M: 2019-02-28 04:35:58.155 0000:  F1 57 30 52 41 59 20 20 20 20 20                   *.W0RAY     *
M: 2019-02-28 04:35:58.155 Data received from an unknown source - 97.125.17.237:42010
M: 2019-02-28 04:35:58.155 Data
M: 2019-02-28 04:35:58.156 0000:  F1 57 30 52 41 59 20 20 20 20 20                   *.W0RAY     *
M: 2019-02-28 04:36:22.794 No repeaters linked
M

W0RAY connected to the reflector from 97.125.17.237
W0RAY unlinked from the reflector
W0RAY sent more data to the reflector after it unlinked.

Usually that means the gateway requested a unlink but did not change to another IP address. So the next data the gateway sent the reflector said huh? Who is this source?
Now the question is where is the reflector getting 97.125.17.237 from?

Steve

On 2/28/2019 2:13 PM, Ray Harden wrote:
Both hosts now @ "mytest" ... only two terminals active are Reflector & Gateway

This time no 31900 Link message after revert to mytest host name

Sent: Thursday, February 28, 2019 7:02:39 PM
Subject: Re: [DVSwitch] LAN address as FQDN in P25Hosts.txt?
 
No, don't revert anything yet. I'm asking that you try the same operation you did when you had 192.168.3.130 in the P25Host.ini

On 2/28/2019 2:00 PM, Ray Harden wrote:
Yes, from same P25 radio- select 31901 ... keyup & no response at Gateway, 39100 link disconnected

I think you wanted to revert from "mytest" back to 31900 host names - is that correct?

Sent: Thursday, February 28, 2019 12:49:21 PM
Subject: Re: [DVSwitch] LAN address as FQDN in P25Hosts.txt?
 
If I remember, the error was after a disconnect. I assume from the log that you keyed up on another TG. Please do the same.

On 2/28/2019 1:47 PM, Ray Harden wrote:
Gateway displays "Linked at startup"

Polling

Sent: Thursday, February 28, 2019 12:30:26 PM
Subject: Re: [DVSwitch] LAN address as FQDN in P25Hosts.txt?
 
OK good. Now test the gateway to reflector

On 2/28/2019 1:29 PM, Ray Harden wrote:
Ping sees 192.168.3.130

Sent: Thursday, February 28, 2019 6:13:15 PM
Subject: Re: [DVSwitch] LAN address as FQDN in P25Hosts.txt?
 
One other thing, after you change the /etc/hosts file try to ping mytest.

On 2/28/2019 1:04 PM, Ray Harden wrote:
Yes, from P25Reflector log ... I attempted to include this log with the original post.

I edited /etc.hosts as you suggested, not sure of the format - added  192.168.3.130  31900. Not sure if this is the correct host name so please tell me if this what you suggested.

Sent: Thursday, February 28, 2019 10:33:35 AM
Subject: Re: [DVSwitch] LAN address as FQDN in P25Hosts.txt?
 
OK, just for the heck of it so I can wrap my head around the problem. Add a entry in the /etc/hosts file for 192.168.3.130 Put the fqdn in P25Hosts.ini and retest.
Are you getting this" ( 97.125.17.237:42010) from the reflector log or from something else?
I know of no reason that 192.168.3.130 should not work.

Steve
 

On 2/28/2019 10:17 AM, harden.ray@... wrote:
P25Reflector<->P25Gateway<->AnalogBridgeP25<->AnalogBridgeDMR<->MMSVMHost <-> Brandmeister

I am close to finishing testing of "This Beast", software is working.  The P25 <=> DMR equipment is physically located in my lab in the same local area net- MMDVM-P25 Moto MSF5000  --  RPi -- TYT 2017-DMR

Substituting in P25Hosts.txt the LAN address 192.168.3.130 for the FDQN results in an erroneous IP address at the time to PTT on the P25 radio  ===  ( 97.125.17.237:42010) instead of the intended 192.168.3.130 as coded in P25Hosts.txt (attached).  (see attached P25Reflector.log)

Is it possible to use a LAN address as the FQDN in P25Hosts.txt?

For example:  31900 (tab) 192.168.3.130 (tab) 41000

   instead of:   31900 (tab) dvsw.org (tab) 41000 

The DVSWITCH software is running at address 192.168.3.4 so it seems the LAN should support what I am tying to do.  Eventually I will provide the P25Hosts 31900 entry with a proper FQDN.

Thanks to all support this effort.
 








Re: looking at my options

Steve N4IRS
 

I believe you are correct. That is one for Jonathan or some enterprising person to modify the gateway to retry. Or, some enterprising person to write a script that scrapes the GW log and restarts the GW after a period of time.

On 2/28/2019 3:11 PM, Mike AE4ML wrote:
2 gateways down and 2 to go....

Not to add another concern. Re-connections..
I have noticed that if the Reflector goes down then that is it. There doesn't appear to be a mechanism in place to attempt a  reconnect to the client  or the gateway at a set period of time.  if there is an issue and I take down the reflector or drop the internet connection then the only fix is to restart the gateway service to bring it back. 

Any thoughts


Re: looking at my options

Steve N4IRS
 

OK

On 2/28/2019 3:13 PM, Mike AE4ML wrote:
I fat fingered it in note pad.
that list was supposed to be 10282  - 10285


Re: looking at my options

Mike AE4ML
 

I fat fingered it in note pad.
that list was supposed to be 10282  - 10285


Re: looking at my options

Mike AE4ML
 

2 gateways down and 2 to go....

Not to add another concern. Re-connections..
I have noticed that if the Reflector goes down then that is it. There doesn't appear to be a mechanism in place to attempt a  reconnect to the client  or the gateway at a set period of time.  if there is an issue and I take down the reflector or drop the internet connection then the only fix is to restart the gateway service to bring it back. 

Any thoughts


Re: looking at my options

Steve N4IRS
 

I just noticed this:

On 2/28/2019 1:44 PM, Mike AE4ML wrote:
#Spotsylvania 442.400
10282           ec2-34-221-180-45.us-west-2.compute.amazonaws.com       41000
# Madison 147.030
10282           ec2-34-221-180-45.us-west-2.compute.amazonaws.com       41010
# Madison 442.575
10283        ec2-34-221-180-45.us-west-2.compute.amazonaws.com       41020
# Fredericksburg 442.850
10284           ec2-34-221-180-45.us-west-2.compute.amazonaws.com       41030
#


Re: looking at my options

Steve N4IRS
 

Never dull. ;)
I'll try to connect to REF2

On 2/28/2019 3:04 PM, Mike AE4ML wrote:
I dont know whats up Steve,
I just did a systemctl restart on GW2  and tried to connect a pi-star mdvm and it has connected . GW 2 is working.

GW1 RF1
M: 2019-02-28 20:00:45.379 Removing AE4ML      (50.205.158.209:42010) disappeared
M: 2019-02-28 20:01:35.673 Currently linked repeaters:
M: 2019-02-28 20:01:35.673     AE4ML      (127.0.0.1:42000) 1/120
M: 2019-02-28 20:01:35.673     DVSWITCH   (208.35.139.12:52010) 2/120
M: 2019-02-28 20:01:35.673     AE4ML      (50.205.158.209:1255) 0/120

GW2 RF2
M: 2019-02-28 19:58:25.663 Adding AE4ML      (127.0.0.1:42110)
M: 2019-02-28 19:58:55.453 Adding AE4ML      (50.205.158.209:42010)


Re: looking at my options

Steve N4IRS
 

REF1 is listening on 41000 it will reply to the connecting GW on the localport defined in the GW .ini file (42010)
REF2 is listening on 41010 it will reply to the connecting GW on the localport defined in the GW .ini file (42110)

The repeater ports do not matter except where 2 gateways are running on the same machine.


On 2/28/2019 2:54 PM, Mike AE4ML wrote:
Please correct me if I'm wrong here.
Each reflector talks to P25gateway via 2 UDP ports . If I have one reflector (REF 1)  listening 41000 and talking to the gateway 31020, 42010 then we have Reflector  2  (REF2)  listening 41010   and talking  to the gateway 31120 and 42110 .

If I shutdown GW 1 and tell gateway 2 to connect to REF 2 dont we have to adjust the  ports that they are using to allow communications ?


Re: looking at my options

Mike AE4ML
 

Please correct me if I'm wrong here.
Each reflector talks to P25gateway via 2 UDP ports . If I have one reflector (REF 1)  listening 41000 and talking to the gateway 31020, 42010 then we have Reflector  2  (REF2)  listening 41010   and talking  to the gateway 31120 and 42110 .

If I shutdown GW 1 and tell gateway 2 to connect to REF 2 dont we have to adjust the  ports that they are using to allow communications ?


Re: LAN address as FQDN in P25Hosts.txt?

Steve N4IRS
 

Ray,
Can you give me a better understanding of your configuration. hosts and LAN not .ini files.

On 2/28/2019 2:26 PM, Ray Harden wrote:
That was my first reaction too ... No way to know ... port 41000 is forwarded to 192. 168.3.130.  But no WAN access to modem.


Sent: Thursday, February 28, 2019 7:20:16 PM
Subject: Re: [DVSwitch] LAN address as FQDN in P25Hosts.txt?
 
This is what I see in your reflector log:
M: 2019-02-28 04:34:22.684 Currently linked repeaters:
M: 2019-02-28 04:34:22.684     W0RAY      (97.125.17.237:42010) 2/120
M: 2019-02-28 04:35:58.149 Removing W0RAY      (97.125.17.237:42010) unlinked
M: 2019-02-28 04:35:58.155 Data received from an unknown source - 97.125.17.237:42010
M: 2019-02-28 04:35:58.155 Data
M: 2019-02-28 04:35:58.155 0000:  F1 57 30 52 41 59 20 20 20 20 20                   *.W0RAY     *
M: 2019-02-28 04:35:58.155 Data received from an unknown source - 97.125.17.237:42010
M: 2019-02-28 04:35:58.155 Data
M: 2019-02-28 04:35:58.156 0000:  F1 57 30 52 41 59 20 20 20 20 20                   *.W0RAY     *
M: 2019-02-28 04:36:22.794 No repeaters linked
M

W0RAY connected to the reflector from 97.125.17.237
W0RAY unlinked from the reflector
W0RAY sent more data to the reflector after it unlinked.

Usually that means the gateway requested a unlink but did not change to another IP address. So the next data the gateway sent the reflector said huh? Who is this source?
Now the question is where is the reflector getting 97.125.17.237 from?

Steve

On 2/28/2019 2:13 PM, Ray Harden wrote:
Both hosts now @ "mytest" ... only two terminals active are Reflector & Gateway

This time no 31900 Link message after revert to mytest host name

Sent: Thursday, February 28, 2019 7:02:39 PM
Subject: Re: [DVSwitch] LAN address as FQDN in P25Hosts.txt?
 
No, don't revert anything yet. I'm asking that you try the same operation you did when you had 192.168.3.130 in the P25Host.ini

On 2/28/2019 2:00 PM, Ray Harden wrote:
Yes, from same P25 radio- select 31901 ... keyup & no response at Gateway, 39100 link disconnected

I think you wanted to revert from "mytest" back to 31900 host names - is that correct?

Sent: Thursday, February 28, 2019 12:49:21 PM
Subject: Re: [DVSwitch] LAN address as FQDN in P25Hosts.txt?
 
If I remember, the error was after a disconnect. I assume from the log that you keyed up on another TG. Please do the same.

On 2/28/2019 1:47 PM, Ray Harden wrote:
Gateway displays "Linked at startup"

Polling

Sent: Thursday, February 28, 2019 12:30:26 PM
Subject: Re: [DVSwitch] LAN address as FQDN in P25Hosts.txt?
 
OK good. Now test the gateway to reflector

On 2/28/2019 1:29 PM, Ray Harden wrote:
Ping sees 192.168.3.130

Sent: Thursday, February 28, 2019 6:13:15 PM
Subject: Re: [DVSwitch] LAN address as FQDN in P25Hosts.txt?
 
One other thing, after you change the /etc/hosts file try to ping mytest.

On 2/28/2019 1:04 PM, Ray Harden wrote:
Yes, from P25Reflector log ... I attempted to include this log with the original post.

I edited /etc.hosts as you suggested, not sure of the format - added  192.168.3.130  31900. Not sure if this is the correct host name so please tell me if this what you suggested.

Sent: Thursday, February 28, 2019 10:33:35 AM
Subject: Re: [DVSwitch] LAN address as FQDN in P25Hosts.txt?
 
OK, just for the heck of it so I can wrap my head around the problem. Add a entry in the /etc/hosts file for 192.168.3.130 Put the fqdn in P25Hosts.ini and retest.
Are you getting this" ( 97.125.17.237:42010) from the reflector log or from something else?
I know of no reason that 192.168.3.130 should not work.

Steve
 

On 2/28/2019 10:17 AM, harden.ray@... wrote:
P25Reflector<->P25Gateway<->AnalogBridgeP25<->AnalogBridgeDMR<->MMSVMHost <-> Brandmeister

I am close to finishing testing of "This Beast", software is working.  The P25 <=> DMR equipment is physically located in my lab in the same local area net- MMDVM-P25 Moto MSF5000  --  RPi -- TYT 2017-DMR

Substituting in P25Hosts.txt the LAN address 192.168.3.130 for the FDQN results in an erroneous IP address at the time to PTT on the P25 radio  ===  ( 97.125.17.237:42010) instead of the intended 192.168.3.130 as coded in P25Hosts.txt (attached).  (see attached P25Reflector.log)

Is it possible to use a LAN address as the FQDN in P25Hosts.txt?

For example:  31900 (tab) 192.168.3.130 (tab) 41000

   instead of:   31900 (tab) dvsw.org (tab) 41000 

The DVSWITCH software is running at address 192.168.3.4 so it seems the LAN should support what I am tying to do.  Eventually I will provide the P25Hosts 31900 entry with a proper FQDN.

Thanks to all support this effort.
 








Re: looking at my options

Steve N4IRS
 

What I have yet to understand is how a gateway will stop a reflector from operating unless there is a port conflict.

On 2/28/2019 2:44 PM, Mike AE4ML wrote:
gateway 2 stopped
systemctl stop p25gateway-310749

I dont expect any problems with gateway 1 ,. Its been rock solid


Re: looking at my options

Mike AE4ML
 

gateway 2 stopped
systemctl stop p25gateway-310749

I dont expect any problems with gateway 1 ,. Its been rock solid


Re: looking at my options

Steve N4IRS
 

OK, JUST stop GW2.

On 2/28/2019 2:39 PM, Mike AE4ML wrote:
that is correct


Re: looking at my options

Mike AE4ML
 

that is correct


Re: looking at my options

Steve N4IRS
 

OK, that is with GW1 and GW2 running?

On 2/28/2019 2:33 PM, Mike AE4ML wrote:
M: 2019-02-28 19:32:34.887 Adding DVSWITCH   (208.35.139.12:52010)


Re: looking at my options

Mike AE4ML
 

M: 2019-02-28 19:32:34.887 Adding DVSWITCH   (208.35.139.12:52010)


Re: looking at my options

Steve N4IRS
 

I fat fingered the port scan. Retesting

On 2/28/2019 2:29 PM, Mike AE4ML wrote:
interesting yes there are limited ports open and not all of them are showing to you with NMAP.
41000 , 41010 , 41020, 41030 and a handful of others.
no ICMP isn't allowed.


Re: looking at my options

Mike AE4ML
 

I have a handful of connections on GW1 / REF 1 41000 now.
only one 127.0.0.1 on GW2 / REF 2 41010


Re: looking at my options

Mike AE4ML
 

interesting yes there are limited ports open and not all of them are showing to you with NMAP.
41000 , 41010 , 41020, 41030 and a handful of others.
no ICMP isn't allowed.

7261 - 7280 of 10634