Date   

Re: LAN address as FQDN in P25Hosts.txt?

Steve N4IRS
 

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


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: Thursday, February 28, 2019 12:30:26 PM
To: main@DVSwitch.groups.io
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
 

You should see a connect from DVSwitch @ 208.35.139.12 on 10282

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: LAN address as FQDN in P25Hosts.txt?

Ray Harden
 

Gateway displays "Linked at startup"

Polling


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: Thursday, February 28, 2019 12:30:26 PM
To: main@DVSwitch.groups.io
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
 

OK, I just tested this on a single P25Gateway. It connects to 10200 fine. when I stop the Gateway, the reflector sees it go away after a period of time.
Is your REF1 exposed to the outside world? If so send IP and port direct and I'll try it from here.

[General]
Callsign=DVSwitch
RptAddress=127.0.0.1
RptPort=32010
LocalPort=42120
Announcements=1
Daemon=0

[Voice]
Enabled=1
Language=en_GB
Directory=./Audio

[Id Lookup]
Name=/var/lib/mmdvm/DMRIds.dat
Time=24

[Log]
FilePath=/var/log/mmdvm
FileRoot=P25Gateway

[Network]
Port=52010
HostsFile1=/var/lib/mmdvm/P25Hosts.txt
HostsFile2=/var/lib/mmdvm/Private_P25Hosts.txt
ReloadTime=60
ParrotAddress=127.0.0.1
ParrotPort=42011
Startup=10200
InactivityTimeout=0
Debug=0



On 2/28/2019 1:27 PM, Mike AE4ML wrote:
reflector
M: 2019-02-28 18:13:41.141 No repeaters linked
M: 2019-02-28 18:15:41.161 No repeaters linked
M: 2019-02-28 18:17:41.179 No repeaters linked
M: 2019-02-28 18:19:41.202 No repeaters linked
M: 2019-02-28 18:21:41.212 No repeaters linked
M: 2019-02-28 18:23:41.230 No repeaters linked

M: 2019-02-28 18:23:30.254 Starting P25Gateway-20180409
M: 2019-02-28 18:23:30.254 Linked at startup to reflector 10282
I: 2019-02-28 18:23:30.254 Started the DMR Id lookup reload thread
W: 2019-02-28 18:25:30.273 No response from 10282, unlinking
root@ip-172-31-19-69:/opt/310749/P25Gateway#


Re: LAN address as FQDN in P25Hosts.txt?

Steve N4IRS
 

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: LAN address as FQDN in P25Hosts.txt?

Ray Harden
 

Ping sees 192.168.3.130

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: Thursday, February 28, 2019 6:13:15 PM
To: main@DVSwitch.groups.io
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

Mike AE4ML
 

reflector
M: 2019-02-28 18:13:41.141 No repeaters linked
M: 2019-02-28 18:15:41.161 No repeaters linked
M: 2019-02-28 18:17:41.179 No repeaters linked
M: 2019-02-28 18:19:41.202 No repeaters linked
M: 2019-02-28 18:21:41.212 No repeaters linked
M: 2019-02-28 18:23:41.230 No repeaters linked

M: 2019-02-28 18:23:30.254 Starting P25Gateway-20180409
M: 2019-02-28 18:23:30.254 Linked at startup to reflector 10282
I: 2019-02-28 18:23:30.254 Started the DMR Id lookup reload thread
W: 2019-02-28 18:25:30.273 No response from 10282, unlinking
root@ip-172-31-19-69:/opt/310749/P25Gateway#


Re: LAN address as FQDN in P25Hosts.txt?

Steve N4IRS
 

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.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: Thursday, February 28, 2019 10:33:35 AM
To: main@DVSwitch.groups.io
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: LAN address as FQDN in P25Hosts.txt?

Steve N4IRS
 

Ray,
Here is a example entry from one of my /etc/hosts files:
208.35.139.12   stn2600.dvswitch.org    stn2600

So, add this to yours in place of the entry you added:
192.168.3.130 mytest

Then in your P25Host file:

31900    mytest

Now retest.

Steve


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.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: Thursday, February 28, 2019 10:33:35 AM
To: main@DVSwitch.groups.io
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
 

OK,
With everything else the same, change
LocalPort=42020

On 2/28/2019 1:05 PM, Mike AE4ML wrote:
I: 2019-02-28 18:00:36.254 Loaded 126028 Ids to the callsign lookup table
M: 2019-02-28 18:00:36.254 Starting P25Gateway-20180409
M: 2019-02-28 18:00:36.254 Linked at startup to reflector 10282
I: 2019-02-28 18:00:36.254 Started the DMR Id lookup reload thread
W: 2019-02-28 18:02:36.273 No response from 10282, unlinking


Re: looking at my options

Mike AE4ML
 

I: 2019-02-28 18:00:36.254 Loaded 126028 Ids to the callsign lookup table
M: 2019-02-28 18:00:36.254 Starting P25Gateway-20180409
M: 2019-02-28 18:00:36.254 Linked at startup to reflector 10282
I: 2019-02-28 18:00:36.254 Started the DMR Id lookup reload thread
W: 2019-02-28 18:02:36.273 No response from 10282, unlinking


Re: looking at my options

Mike AE4ML
 

I did that and this is the result

M: 2019-02-28 18:01:41.033 Currently linked repeaters:
M: 2019-02-28 18:01:41.033     AE4ML      (127.0.0.1:42110) 69/120
M: 2019-02-28 18:02:31.349 Removing AE4ML      (127.0.0.1:42110) disappeared


Re: LAN address as FQDN in P25Hosts.txt?

Ray Harden
 

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.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: Thursday, February 28, 2019 10:33:35 AM
To: main@DVSwitch.groups.io
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
 

Can you just add a entry in the host file for GW2 pointing at ref1 to test?

On 2/28/2019 12:47 PM, Mike AE4ML wrote:
Steve, I'm sorry am I making this more complex that it needs to be ?
How can I use REF 1 with GW2 without changing port numbers ?

REF 1 (10282)           P25GW 1
41000                    41000 32010
42010                    42010 42020

REF 2 (10283)        P25GW 2
41010                  41010  32110
42110                  42110  42120


Re: looking at my options

Mike AE4ML
 

Steve, I'm sorry am I making this more complex that it needs to be ?
How can I use REF 1 with GW2 without changing port numbers ?

REF 1 (10282)           P25GW 1
41000                    41000 32010
42010                    42010 42020

REF 2 (10283)        P25GW 2
41010                  41010  32110
42110                  42110  42120


Re: looking at my options

Steve N4IRS
 

Why would you have to change any of the values below. Add a entry for REF1 to the host file for GW2.

On 2/28/2019 12:25 PM, Mike AE4ML wrote:
Yes,
GW2 to REF 1 works if I change these values in the p25gateway.ini file for GW2

RptPort=32110  to 32010
LocalPort=42120 to 42020
startup=10283 to  10282


Re: looking at my options

Mike AE4ML
 

Yes,
GW2 to REF 1 works if I change these values in the p25gateway.ini file for GW2

RptPort=32110  to 32010
LocalPort=42120 to 42020
startup=10283 to  10282


Do we need more subgroups. #poll

Steve N4IRS
 

With over 600 users and quite a few subgroups already I'm not sure is we need more segregation of the topics. The initial list of subgroups works until we get into bridging something other than AllStarLink. Where do I ask about bridging DMR to P25? where do I ask about bridging from YSF to NXDN? My first thought is we need a subgroup for each mode. A lot of questions / answers are ending up in the main area. That may be OK. I think if we had a subgroup for each mode someone could ask a question in the subgroup that deals with the mode the problem is in. Have another idea? Post your idea. So here is a poll.   

Results

See Who Responded


Re: looking at my options

Steve N4IRS
 

Why 2 variables? GW2 REF1 works?

On 2/28/2019 12:03 PM, Mike AE4ML wrote:
running GW 1 / REF 1 ONLY no problem 127.0.01 shows and  repeaters can connect

Running GW 2 / REF 2 ONLY  127.0.0.1 shows in the reflector and no one can connect to the reflector

no crossed port numbers and with both GW and REF up I can see these ports
root@ip-172-31-19-69:/opt/310749/P25Gateway# netstat -unap | grep -e "P25Gateway" -e "P25Reflector"
udp        0      0 0.0.0.0:42010           0.0.0.0:*                           7522/P25Gateway
udp        0      0 0.0.0.0:42020           0.0.0.0:*                           7522/P25Gateway
udp        0      0 0.0.0.0:41000           0.0.0.0:*                           1564/P25Reflector
udp        0      0 0.0.0.0:41010           0.0.0.0:*                           23972/P25Reflector
udp        0      0 0.0.0.0:42110           0.0.0.0:*                           11638/P25Gateway
udp        0      0 0.0.0.0:42120           0.0.0.0:*                           11638/P25Gateway


Re: looking at my options

Mike AE4ML
 

running GW 1 / REF 1 ONLY no problem 127.0.01 shows and  repeaters can connect

Running GW 2 / REF 2 ONLY  127.0.0.1 shows in the reflector and no one can connect to the reflector

no crossed port numbers and with both GW and REF up I can see these ports
root@ip-172-31-19-69:/opt/310749/P25Gateway# netstat -unap | grep -e "P25Gateway" -e "P25Reflector"
udp        0      0 0.0.0.0:42010           0.0.0.0:*                           7522/P25Gateway
udp        0      0 0.0.0.0:42020           0.0.0.0:*                           7522/P25Gateway
udp        0      0 0.0.0.0:41000           0.0.0.0:*                           1564/P25Reflector
udp        0      0 0.0.0.0:41010           0.0.0.0:*                           23972/P25Reflector
udp        0      0 0.0.0.0:42110           0.0.0.0:*                           11638/P25Gateway
udp        0      0 0.0.0.0:42120           0.0.0.0:*                           11638/P25Gateway

6541 - 6560 of 9882