Date   

Re: Bridging a P25Reflector and a YSFReflector?

Jake Litwin
 

Thanks Steve for all of the guidance through this! Thank you too Adrian for the feedback and pointing me back towards my ini configs. Yeah was my own dumb fault for trying to change up ports and then losing track in the process.

On Fri, Oct 11, 2019 at 1:12 PM Steve N4IRS <szingman@...> wrote:
No,
The gateway logging leaves a lot to be desired. Just look for startup connect and possible disconnect.

On 10/11/19 2:07 PM, Jake Litwin wrote:
So this is my own dumb &$& fault.. I started changing ports because I originally thought 41000 was being used by the YSF reflector I have installed. It's not. I put both the P25Reflector.ini and P25Gateway.ini files back to their original states. Yes 41000 is the port Reflector should be using.

Reflector Log:

M: 2019-10-11 18:01:42.055 Adding N9KRG      (174.253.82.128:42722)
M: 2019-10-11 18:01:46.066 Currently linked repeaters:
M: 2019-10-11 18:01:46.066     N9KRG      (127.0.0.1:42010) 4/120
M: 2019-10-11 18:01:46.066     N9KRG      (174.253.82.128:42722) 3/120
M: 2019-10-11 18:01:57.349 Transmission started from N9KRG      (174.253.82.128:42722)
M: 2019-10-11 18:01:57.374 Transmission from N9KRG at N9KRG      to TG 420
M: 2019-10-11 18:01:59.484 Received end of transmission
M: 2019-10-11 18:02:10.898 Transmission started from N9KRG      (174.253.82.128:42722)
M: 2019-10-11 18:02:10.908 Transmission from N9KRG at N9KRG      to TG 420
M: 2019-10-11 18:02:12.826 Received end of transmission

Gateway Log:
M: 2019-10-11 17:14:04.641 Linked at startup to reflector 420
W: 2019-10-11 17:16:04.647 No response from 420, unlinking
I: 2019-10-11 17:19:50.623 Opening P25 network connection
I: 2019-10-11 17:19:50.623 Opening P25 network connection
I: 2019-10-11 17:19:50.893 Loaded 13 P25 reflectors
I: 2019-10-11 17:19:50.893 Loaded P25 parrot (TG10)
I: 2019-10-11 17:19:50.934 Loaded 145704 Ids to the callsign lookup table
M: 2019-10-11 17:19:50.934 Starting P25Gateway-20180409
I: 2019-10-11 17:19:50.934 Started the DMR Id lookup reload thread
M: 2019-10-11 17:19:50.934 Linked at startup to reflector 420

I think I'm all set right? Or should I be seeing some activity on the Gateway log for traffic?


On Fri, Oct 11, 2019 at 11:56 AM Adrian Fewster <vk4tux@...> wrote:

42020 UDP has nothing to do with the P25Reflector, it is the gateway comms port along with 32010 between P25Gateway and MMDVM_Bridge.


Check the P25 Network gateway port matches the local port between P25Gateway.ini and MMDVM_Bridge.ini and vice versa.


Adrian ... vk4tux


On 12/10/19 2:31 am, Jake Litwin wrote:
Changing the P25Hosts file to 42020 would not connect to the reflector. Keeping it on 41000 gateway connects to the reflector but that's where I get

Data received from an unknown source - 127.0.0.1:42020
M: 2019-10-11 01:28:23.400 Data
M: 2019-10-11 01:28:23.400 0000:  62 02 02 0C 0B 12 64 00 00 80 18 72 8A 2A 19 40    *b.....d....r.*.@*
M: 2019-10-11 01:28:23.400 0010:  00 D4 0C 80 62 00                                  *....b.*
 

I did a port check and Reflector is listening on 41000

root@SuperFreq:/var/log/mmdvm# sudo lsof -i:41000
COMMAND     PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
P25Reflec 20357 root    4u  IPv4 1373306      0t0  UDP *:41000
root@SuperFreq:/var/log/mmdvm# sudo lsof -i:42020
COMMAND     PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
P25Gatewa 21266 root    4u  IPv4 1378574      0t0  UDP *:42020


On Fri, Oct 11, 2019 at 7:31 AM Steve N4IRS <szingman@...> wrote:
So,
The reflector startup looks normal but I expect the gateway will timeout since it is trying to connect to reflector 420 on port UDP 41000 as reflected in p25hosts. The P25Reflector is listening on UDP port 42020. So, the Gateway never connects or logs into the reflector. The error you get:

Data received from an unknown source - 127.0.0.1:42020
M: 2019-10-11 01:28:23.400 Data
M: 2019-10-11 01:28:23.400 0000:  62 02 02 0C 0B 12 64 00 00 80 18 72 8A 2A 19 40    *b.....d....r.*.@*
M: 2019-10-11 01:28:23.400 0010:  00 D4 0C 80 62 00                                  *....b.*


Is caused by the gateway sending data but not logged into the the reflector. Change p25hosts to reflect the port the reflector is actually listening on. Since you can connect to the reflector from your MMDVMHost:

M: 2019-10-11 01:27:49.733 Adding N9KRG      (141.126.148.63:24186)
M: 2019-10-11 01:28:23.375 Transmission started from N9KRG      (141.126.148.63:24186)
M: 2019-10-11 01:28:23.385 Transmission from N9KRG at N9KRG      to TG 420


I would expect the published UDP port of 42020 is correct.

Steve N4IRS

On 10/10/19 10:45 PM, Jake Litwin wrote:
hmmm. This is all I"m seeing on the live output for gateway

root@SuperFreq:/opt/P25Gateway# ./P25Gateway
I: 2019-10-11 02:44:53.322 Opening P25 network connection
I: 2019-10-11 02:44:53.322 Opening P25 network connection
I: 2019-10-11 02:44:53.324 Loaded 13 P25 reflectors
I: 2019-10-11 02:44:53.324 Loaded P25 parrot (TG10)
I: 2019-10-11 02:44:53.359 Loaded 145619 Ids to the callsign lookup table
M: 2019-10-11 02:44:53.359 Starting P25Gateway-20180409
M: 2019-10-11 02:44:53.359 Linked at startup to reflector 420
I: 2019-10-11 02:44:53.359 Started the DMR Id lookup reload thread



Re: Bridging a P25Reflector and a YSFReflector?

Steve N4IRS
 

No,
The gateway logging leaves a lot to be desired. Just look for startup connect and possible disconnect.

On 10/11/19 2:07 PM, Jake Litwin wrote:
So this is my own dumb &$& fault.. I started changing ports because I originally thought 41000 was being used by the YSF reflector I have installed. It's not. I put both the P25Reflector.ini and P25Gateway.ini files back to their original states. Yes 41000 is the port Reflector should be using.

Reflector Log:

M: 2019-10-11 18:01:42.055 Adding N9KRG      (174.253.82.128:42722)
M: 2019-10-11 18:01:46.066 Currently linked repeaters:
M: 2019-10-11 18:01:46.066     N9KRG      (127.0.0.1:42010) 4/120
M: 2019-10-11 18:01:46.066     N9KRG      (174.253.82.128:42722) 3/120
M: 2019-10-11 18:01:57.349 Transmission started from N9KRG      (174.253.82.128:42722)
M: 2019-10-11 18:01:57.374 Transmission from N9KRG at N9KRG      to TG 420
M: 2019-10-11 18:01:59.484 Received end of transmission
M: 2019-10-11 18:02:10.898 Transmission started from N9KRG      (174.253.82.128:42722)
M: 2019-10-11 18:02:10.908 Transmission from N9KRG at N9KRG      to TG 420
M: 2019-10-11 18:02:12.826 Received end of transmission

Gateway Log:
M: 2019-10-11 17:14:04.641 Linked at startup to reflector 420
W: 2019-10-11 17:16:04.647 No response from 420, unlinking
I: 2019-10-11 17:19:50.623 Opening P25 network connection
I: 2019-10-11 17:19:50.623 Opening P25 network connection
I: 2019-10-11 17:19:50.893 Loaded 13 P25 reflectors
I: 2019-10-11 17:19:50.893 Loaded P25 parrot (TG10)
I: 2019-10-11 17:19:50.934 Loaded 145704 Ids to the callsign lookup table
M: 2019-10-11 17:19:50.934 Starting P25Gateway-20180409
I: 2019-10-11 17:19:50.934 Started the DMR Id lookup reload thread
M: 2019-10-11 17:19:50.934 Linked at startup to reflector 420

I think I'm all set right? Or should I be seeing some activity on the Gateway log for traffic?


On Fri, Oct 11, 2019 at 11:56 AM Adrian Fewster <vk4tux@...> wrote:

42020 UDP has nothing to do with the P25Reflector, it is the gateway comms port along with 32010 between P25Gateway and MMDVM_Bridge.


Check the P25 Network gateway port matches the local port between P25Gateway.ini and MMDVM_Bridge.ini and vice versa.


Adrian ... vk4tux


On 12/10/19 2:31 am, Jake Litwin wrote:
Changing the P25Hosts file to 42020 would not connect to the reflector. Keeping it on 41000 gateway connects to the reflector but that's where I get

Data received from an unknown source - 127.0.0.1:42020
M: 2019-10-11 01:28:23.400 Data
M: 2019-10-11 01:28:23.400 0000:  62 02 02 0C 0B 12 64 00 00 80 18 72 8A 2A 19 40    *b.....d....r.*.@*
M: 2019-10-11 01:28:23.400 0010:  00 D4 0C 80 62 00                                  *....b.*
 

I did a port check and Reflector is listening on 41000

root@SuperFreq:/var/log/mmdvm# sudo lsof -i:41000
COMMAND     PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
P25Reflec 20357 root    4u  IPv4 1373306      0t0  UDP *:41000
root@SuperFreq:/var/log/mmdvm# sudo lsof -i:42020
COMMAND     PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
P25Gatewa 21266 root    4u  IPv4 1378574      0t0  UDP *:42020


On Fri, Oct 11, 2019 at 7:31 AM Steve N4IRS <szingman@...> wrote:
So,
The reflector startup looks normal but I expect the gateway will timeout since it is trying to connect to reflector 420 on port UDP 41000 as reflected in p25hosts. The P25Reflector is listening on UDP port 42020. So, the Gateway never connects or logs into the reflector. The error you get:

Data received from an unknown source - 127.0.0.1:42020
M: 2019-10-11 01:28:23.400 Data
M: 2019-10-11 01:28:23.400 0000:  62 02 02 0C 0B 12 64 00 00 80 18 72 8A 2A 19 40    *b.....d....r.*.@*
M: 2019-10-11 01:28:23.400 0010:  00 D4 0C 80 62 00                                  *....b.*


Is caused by the gateway sending data but not logged into the the reflector. Change p25hosts to reflect the port the reflector is actually listening on. Since you can connect to the reflector from your MMDVMHost:

M: 2019-10-11 01:27:49.733 Adding N9KRG      (141.126.148.63:24186)
M: 2019-10-11 01:28:23.375 Transmission started from N9KRG      (141.126.148.63:24186)
M: 2019-10-11 01:28:23.385 Transmission from N9KRG at N9KRG      to TG 420


I would expect the published UDP port of 42020 is correct.

Steve N4IRS

On 10/10/19 10:45 PM, Jake Litwin wrote:
hmmm. This is all I"m seeing on the live output for gateway

root@SuperFreq:/opt/P25Gateway# ./P25Gateway
I: 2019-10-11 02:44:53.322 Opening P25 network connection
I: 2019-10-11 02:44:53.322 Opening P25 network connection
I: 2019-10-11 02:44:53.324 Loaded 13 P25 reflectors
I: 2019-10-11 02:44:53.324 Loaded P25 parrot (TG10)
I: 2019-10-11 02:44:53.359 Loaded 145619 Ids to the callsign lookup table
M: 2019-10-11 02:44:53.359 Starting P25Gateway-20180409
M: 2019-10-11 02:44:53.359 Linked at startup to reflector 420
I: 2019-10-11 02:44:53.359 Started the DMR Id lookup reload thread



Re: Bridging a P25Reflector and a YSFReflector?

Jake Litwin
 

So this is my own dumb &$& fault.. I started changing ports because I originally thought 41000 was being used by the YSF reflector I have installed. It's not. I put both the P25Reflector.ini and P25Gateway.ini files back to their original states. Yes 41000 is the port Reflector should be using.

Reflector Log:

M: 2019-10-11 18:01:42.055 Adding N9KRG      (174.253.82.128:42722)
M: 2019-10-11 18:01:46.066 Currently linked repeaters:
M: 2019-10-11 18:01:46.066     N9KRG      (127.0.0.1:42010) 4/120
M: 2019-10-11 18:01:46.066     N9KRG      (174.253.82.128:42722) 3/120
M: 2019-10-11 18:01:57.349 Transmission started from N9KRG      (174.253.82.128:42722)
M: 2019-10-11 18:01:57.374 Transmission from N9KRG at N9KRG      to TG 420
M: 2019-10-11 18:01:59.484 Received end of transmission
M: 2019-10-11 18:02:10.898 Transmission started from N9KRG      (174.253.82.128:42722)
M: 2019-10-11 18:02:10.908 Transmission from N9KRG at N9KRG      to TG 420
M: 2019-10-11 18:02:12.826 Received end of transmission

Gateway Log:
M: 2019-10-11 17:14:04.641 Linked at startup to reflector 420
W: 2019-10-11 17:16:04.647 No response from 420, unlinking
I: 2019-10-11 17:19:50.623 Opening P25 network connection
I: 2019-10-11 17:19:50.623 Opening P25 network connection
I: 2019-10-11 17:19:50.893 Loaded 13 P25 reflectors
I: 2019-10-11 17:19:50.893 Loaded P25 parrot (TG10)
I: 2019-10-11 17:19:50.934 Loaded 145704 Ids to the callsign lookup table
M: 2019-10-11 17:19:50.934 Starting P25Gateway-20180409
I: 2019-10-11 17:19:50.934 Started the DMR Id lookup reload thread
M: 2019-10-11 17:19:50.934 Linked at startup to reflector 420

I think I'm all set right? Or should I be seeing some activity on the Gateway log for traffic?


On Fri, Oct 11, 2019 at 11:56 AM Adrian Fewster <vk4tux@...> wrote:

42020 UDP has nothing to do with the P25Reflector, it is the gateway comms port along with 32010 between P25Gateway and MMDVM_Bridge.


Check the P25 Network gateway port matches the local port between P25Gateway.ini and MMDVM_Bridge.ini and vice versa.


Adrian ... vk4tux


On 12/10/19 2:31 am, Jake Litwin wrote:
Changing the P25Hosts file to 42020 would not connect to the reflector. Keeping it on 41000 gateway connects to the reflector but that's where I get

Data received from an unknown source - 127.0.0.1:42020
M: 2019-10-11 01:28:23.400 Data
M: 2019-10-11 01:28:23.400 0000:  62 02 02 0C 0B 12 64 00 00 80 18 72 8A 2A 19 40    *b.....d....r.*.@*
M: 2019-10-11 01:28:23.400 0010:  00 D4 0C 80 62 00                                  *....b.*
 

I did a port check and Reflector is listening on 41000

root@SuperFreq:/var/log/mmdvm# sudo lsof -i:41000
COMMAND     PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
P25Reflec 20357 root    4u  IPv4 1373306      0t0  UDP *:41000
root@SuperFreq:/var/log/mmdvm# sudo lsof -i:42020
COMMAND     PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
P25Gatewa 21266 root    4u  IPv4 1378574      0t0  UDP *:42020


On Fri, Oct 11, 2019 at 7:31 AM Steve N4IRS <szingman@...> wrote:
So,
The reflector startup looks normal but I expect the gateway will timeout since it is trying to connect to reflector 420 on port UDP 41000 as reflected in p25hosts. The P25Reflector is listening on UDP port 42020. So, the Gateway never connects or logs into the reflector. The error you get:

Data received from an unknown source - 127.0.0.1:42020
M: 2019-10-11 01:28:23.400 Data
M: 2019-10-11 01:28:23.400 0000:  62 02 02 0C 0B 12 64 00 00 80 18 72 8A 2A 19 40    *b.....d....r.*.@*
M: 2019-10-11 01:28:23.400 0010:  00 D4 0C 80 62 00                                  *....b.*


Is caused by the gateway sending data but not logged into the the reflector. Change p25hosts to reflect the port the reflector is actually listening on. Since you can connect to the reflector from your MMDVMHost:

M: 2019-10-11 01:27:49.733 Adding N9KRG      (141.126.148.63:24186)
M: 2019-10-11 01:28:23.375 Transmission started from N9KRG      (141.126.148.63:24186)
M: 2019-10-11 01:28:23.385 Transmission from N9KRG at N9KRG      to TG 420


I would expect the published UDP port of 42020 is correct.

Steve N4IRS

On 10/10/19 10:45 PM, Jake Litwin wrote:
hmmm. This is all I"m seeing on the live output for gateway

root@SuperFreq:/opt/P25Gateway# ./P25Gateway
I: 2019-10-11 02:44:53.322 Opening P25 network connection
I: 2019-10-11 02:44:53.322 Opening P25 network connection
I: 2019-10-11 02:44:53.324 Loaded 13 P25 reflectors
I: 2019-10-11 02:44:53.324 Loaded P25 parrot (TG10)
I: 2019-10-11 02:44:53.359 Loaded 145619 Ids to the callsign lookup table
M: 2019-10-11 02:44:53.359 Starting P25Gateway-20180409
M: 2019-10-11 02:44:53.359 Linked at startup to reflector 420
I: 2019-10-11 02:44:53.359 Started the DMR Id lookup reload thread


Re: Bridging a P25Reflector and a YSFReflector?

Adrian Fewster <vk4tux@...>
 

42020 UDP has nothing to do with the P25Reflector, it is the gateway comms port along with 32010 between P25Gateway and MMDVM_Bridge.


Check the P25 Network gateway port matches the local port between P25Gateway.ini and MMDVM_Bridge.ini and vice versa.


Adrian ... vk4tux


On 12/10/19 2:31 am, Jake Litwin wrote:
Changing the P25Hosts file to 42020 would not connect to the reflector. Keeping it on 41000 gateway connects to the reflector but that's where I get

Data received from an unknown source - 127.0.0.1:42020
M: 2019-10-11 01:28:23.400 Data
M: 2019-10-11 01:28:23.400 0000:  62 02 02 0C 0B 12 64 00 00 80 18 72 8A 2A 19 40    *b.....d....r.*.@*
M: 2019-10-11 01:28:23.400 0010:  00 D4 0C 80 62 00                                  *....b.*
 

I did a port check and Reflector is listening on 41000

root@SuperFreq:/var/log/mmdvm# sudo lsof -i:41000
COMMAND     PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
P25Reflec 20357 root    4u  IPv4 1373306      0t0  UDP *:41000
root@SuperFreq:/var/log/mmdvm# sudo lsof -i:42020
COMMAND     PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
P25Gatewa 21266 root    4u  IPv4 1378574      0t0  UDP *:42020


On Fri, Oct 11, 2019 at 7:31 AM Steve N4IRS <szingman@...> wrote:
So,
The reflector startup looks normal but I expect the gateway will timeout since it is trying to connect to reflector 420 on port UDP 41000 as reflected in p25hosts. The P25Reflector is listening on UDP port 42020. So, the Gateway never connects or logs into the reflector. The error you get:

Data received from an unknown source - 127.0.0.1:42020
M: 2019-10-11 01:28:23.400 Data
M: 2019-10-11 01:28:23.400 0000:  62 02 02 0C 0B 12 64 00 00 80 18 72 8A 2A 19 40    *b.....d....r.*.@*
M: 2019-10-11 01:28:23.400 0010:  00 D4 0C 80 62 00                                  *....b.*


Is caused by the gateway sending data but not logged into the the reflector. Change p25hosts to reflect the port the reflector is actually listening on. Since you can connect to the reflector from your MMDVMHost:

M: 2019-10-11 01:27:49.733 Adding N9KRG      (141.126.148.63:24186)
M: 2019-10-11 01:28:23.375 Transmission started from N9KRG      (141.126.148.63:24186)
M: 2019-10-11 01:28:23.385 Transmission from N9KRG at N9KRG      to TG 420


I would expect the published UDP port of 42020 is correct.

Steve N4IRS

On 10/10/19 10:45 PM, Jake Litwin wrote:
hmmm. This is all I"m seeing on the live output for gateway

root@SuperFreq:/opt/P25Gateway# ./P25Gateway
I: 2019-10-11 02:44:53.322 Opening P25 network connection
I: 2019-10-11 02:44:53.322 Opening P25 network connection
I: 2019-10-11 02:44:53.324 Loaded 13 P25 reflectors
I: 2019-10-11 02:44:53.324 Loaded P25 parrot (TG10)
I: 2019-10-11 02:44:53.359 Loaded 145619 Ids to the callsign lookup table
M: 2019-10-11 02:44:53.359 Starting P25Gateway-20180409
M: 2019-10-11 02:44:53.359 Linked at startup to reflector 420
I: 2019-10-11 02:44:53.359 Started the DMR Id lookup reload thread


Re: Bridging a P25Reflector and a YSFReflector?

Steve N4IRS
 

Well,
I see the results of lsof. But this is what you posted as p25reflector.txt

[General]
Daemon=0

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

[Log]
# Logging levels, 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
DisplayLevel=1
FileLevel=2
FilePath=/var/log/mmdvm
FileRoot=P25Reflector

[Network]
Port=42020
Debug=0

On 10/11/19 12:31 PM, Jake Litwin wrote:
Changing the P25Hosts file to 42020 would not connect to the reflector. Keeping it on 41000 gateway connects to the reflector but that's where I get

Data received from an unknown source - 127.0.0.1:42020
M: 2019-10-11 01:28:23.400 Data
M: 2019-10-11 01:28:23.400 0000:  62 02 02 0C 0B 12 64 00 00 80 18 72 8A 2A 19 40    *b.....d....r.*.@*
M: 2019-10-11 01:28:23.400 0010:  00 D4 0C 80 62 00                                  *....b.*
 

I did a port check and Reflector is listening on 41000

root@SuperFreq:/var/log/mmdvm# sudo lsof -i:41000
COMMAND     PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
P25Reflec 20357 root    4u  IPv4 1373306      0t0  UDP *:41000
root@SuperFreq:/var/log/mmdvm# sudo lsof -i:42020
COMMAND     PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
P25Gatewa 21266 root    4u  IPv4 1378574      0t0  UDP *:42020


On Fri, Oct 11, 2019 at 7:31 AM Steve N4IRS <szingman@...> wrote:
So,
The reflector startup looks normal but I expect the gateway will timeout since it is trying to connect to reflector 420 on port UDP 41000 as reflected in p25hosts. The P25Reflector is listening on UDP port 42020. So, the Gateway never connects or logs into the reflector. The error you get:

Data received from an unknown source - 127.0.0.1:42020
M: 2019-10-11 01:28:23.400 Data
M: 2019-10-11 01:28:23.400 0000:  62 02 02 0C 0B 12 64 00 00 80 18 72 8A 2A 19 40    *b.....d....r.*.@*
M: 2019-10-11 01:28:23.400 0010:  00 D4 0C 80 62 00                                  *....b.*


Is caused by the gateway sending data but not logged into the the reflector. Change p25hosts to reflect the port the reflector is actually listening on. Since you can connect to the reflector from your MMDVMHost:

M: 2019-10-11 01:27:49.733 Adding N9KRG      (141.126.148.63:24186)
M: 2019-10-11 01:28:23.375 Transmission started from N9KRG      (141.126.148.63:24186)
M: 2019-10-11 01:28:23.385 Transmission from N9KRG at N9KRG      to TG 420


I would expect the published UDP port of 42020 is correct.

Steve N4IRS

On 10/10/19 10:45 PM, Jake Litwin wrote:
hmmm. This is all I"m seeing on the live output for gateway

root@SuperFreq:/opt/P25Gateway# ./P25Gateway
I: 2019-10-11 02:44:53.322 Opening P25 network connection
I: 2019-10-11 02:44:53.322 Opening P25 network connection
I: 2019-10-11 02:44:53.324 Loaded 13 P25 reflectors
I: 2019-10-11 02:44:53.324 Loaded P25 parrot (TG10)
I: 2019-10-11 02:44:53.359 Loaded 145619 Ids to the callsign lookup table
M: 2019-10-11 02:44:53.359 Starting P25Gateway-20180409
M: 2019-10-11 02:44:53.359 Linked at startup to reflector 420
I: 2019-10-11 02:44:53.359 Started the DMR Id lookup reload thread



Re: Bridging a P25Reflector and a YSFReflector?

Jake Litwin
 

Changing the P25Hosts file to 42020 would not connect to the reflector. Keeping it on 41000 gateway connects to the reflector but that's where I get

Data received from an unknown source - 127.0.0.1:42020
M: 2019-10-11 01:28:23.400 Data
M: 2019-10-11 01:28:23.400 0000:  62 02 02 0C 0B 12 64 00 00 80 18 72 8A 2A 19 40    *b.....d....r.*.@*
M: 2019-10-11 01:28:23.400 0010:  00 D4 0C 80 62 00                                  *....b.*
 

I did a port check and Reflector is listening on 41000

root@SuperFreq:/var/log/mmdvm# sudo lsof -i:41000
COMMAND     PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
P25Reflec 20357 root    4u  IPv4 1373306      0t0  UDP *:41000
root@SuperFreq:/var/log/mmdvm# sudo lsof -i:42020
COMMAND     PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
P25Gatewa 21266 root    4u  IPv4 1378574      0t0  UDP *:42020


On Fri, Oct 11, 2019 at 7:31 AM Steve N4IRS <szingman@...> wrote:
So,
The reflector startup looks normal but I expect the gateway will timeout since it is trying to connect to reflector 420 on port UDP 41000 as reflected in p25hosts. The P25Reflector is listening on UDP port 42020. So, the Gateway never connects or logs into the reflector. The error you get:

Data received from an unknown source - 127.0.0.1:42020
M: 2019-10-11 01:28:23.400 Data
M: 2019-10-11 01:28:23.400 0000:  62 02 02 0C 0B 12 64 00 00 80 18 72 8A 2A 19 40    *b.....d....r.*.@*
M: 2019-10-11 01:28:23.400 0010:  00 D4 0C 80 62 00                                  *....b.*


Is caused by the gateway sending data but not logged into the the reflector. Change p25hosts to reflect the port the reflector is actually listening on. Since you can connect to the reflector from your MMDVMHost:

M: 2019-10-11 01:27:49.733 Adding N9KRG      (141.126.148.63:24186)
M: 2019-10-11 01:28:23.375 Transmission started from N9KRG      (141.126.148.63:24186)
M: 2019-10-11 01:28:23.385 Transmission from N9KRG at N9KRG      to TG 420


I would expect the published UDP port of 42020 is correct.

Steve N4IRS

On 10/10/19 10:45 PM, Jake Litwin wrote:
hmmm. This is all I"m seeing on the live output for gateway

root@SuperFreq:/opt/P25Gateway# ./P25Gateway
I: 2019-10-11 02:44:53.322 Opening P25 network connection
I: 2019-10-11 02:44:53.322 Opening P25 network connection
I: 2019-10-11 02:44:53.324 Loaded 13 P25 reflectors
I: 2019-10-11 02:44:53.324 Loaded P25 parrot (TG10)
I: 2019-10-11 02:44:53.359 Loaded 145619 Ids to the callsign lookup table
M: 2019-10-11 02:44:53.359 Starting P25Gateway-20180409
M: 2019-10-11 02:44:53.359 Linked at startup to reflector 420
I: 2019-10-11 02:44:53.359 Started the DMR Id lookup reload thread


Re: Bridging a P25Reflector and a YSFReflector?

Steve N4IRS
 

So,
The reflector startup looks normal but I expect the gateway will timeout since it is trying to connect to reflector 420 on port UDP 41000 as reflected in p25hosts. The P25Reflector is listening on UDP port 42020. So, the Gateway never connects or logs into the reflector. The error you get:

Data received from an unknown source - 127.0.0.1:42020
M: 2019-10-11 01:28:23.400 Data
M: 2019-10-11 01:28:23.400 0000:  62 02 02 0C 0B 12 64 00 00 80 18 72 8A 2A 19 40    *b.....d....r.*.@*
M: 2019-10-11 01:28:23.400 0010:  00 D4 0C 80 62 00                                  *....b.*


Is caused by the gateway sending data but not logged into the the reflector. Change p25hosts to reflect the port the reflector is actually listening on. Since you can connect to the reflector from your MMDVMHost:

M: 2019-10-11 01:27:49.733 Adding N9KRG      (141.126.148.63:24186)
M: 2019-10-11 01:28:23.375 Transmission started from N9KRG      (141.126.148.63:24186)
M: 2019-10-11 01:28:23.385 Transmission from N9KRG at N9KRG      to TG 420


I would expect the published UDP port of 42020 is correct.

Steve N4IRS

On 10/10/19 10:45 PM, Jake Litwin wrote:
hmmm. This is all I"m seeing on the live output for gateway

root@SuperFreq:/opt/P25Gateway# ./P25Gateway
I: 2019-10-11 02:44:53.322 Opening P25 network connection
I: 2019-10-11 02:44:53.322 Opening P25 network connection
I: 2019-10-11 02:44:53.324 Loaded 13 P25 reflectors
I: 2019-10-11 02:44:53.324 Loaded P25 parrot (TG10)
I: 2019-10-11 02:44:53.359 Loaded 145619 Ids to the callsign lookup table
M: 2019-10-11 02:44:53.359 Starting P25Gateway-20180409
M: 2019-10-11 02:44:53.359 Linked at startup to reflector 420
I: 2019-10-11 02:44:53.359 Started the DMR Id lookup reload thread


Re: Bridging a P25Reflector and a YSFReflector?

Jake Litwin
 

hmmm. This is all I"m seeing on the live output for gateway

root@SuperFreq:/opt/P25Gateway# ./P25Gateway
I: 2019-10-11 02:44:53.322 Opening P25 network connection
I: 2019-10-11 02:44:53.322 Opening P25 network connection
I: 2019-10-11 02:44:53.324 Loaded 13 P25 reflectors
I: 2019-10-11 02:44:53.324 Loaded P25 parrot (TG10)
I: 2019-10-11 02:44:53.359 Loaded 145619 Ids to the callsign lookup table
M: 2019-10-11 02:44:53.359 Starting P25Gateway-20180409
M: 2019-10-11 02:44:53.359 Linked at startup to reflector 420
I: 2019-10-11 02:44:53.359 Started the DMR Id lookup reload thread


Re: Bridging a P25Reflector and a YSFReflector?

Steve N4IRS
 

Is there a reason you can't just capture the text output from P25Gateway?

On 10/10/19 9:51 PM, Jake Litwin wrote:
Here’s a short video of what’s happening. 

On Thu, Oct 10, 2019 at 8:29 PM litwinjwi via Groups.Io <litwinjwi=gmail.com@groups.io> wrote:
The Reflector logs though say this

M: 2019-10-11 01:27:49.733 Adding N9KRG      (141.126.148.63:24186)
M: 2019-10-11 01:28:23.375 Transmission started from N9KRG      (141.126.148.63:24186)
M: 2019-10-11 01:28:23.385 Transmission from N9KRG at N9KRG      to TG 420
M: 2019-10-11 01:28:23.400 Data received from an unknown source - 127.0.0.1:42020
M: 2019-10-11 01:28:23.400 Data
M: 2019-10-11 01:28:23.400 0000:  62 02 02 0C 0B 12 64 00 00 80 18 72 8A 2A 19 40    *b.....d....r.*.@*
M: 2019-10-11 01:28:23.400 0010:  00 D4 0C 80 62 00                                  *....b.*
M: 2019-10-11 01:28:23.400 Data received from an unknown source - 127.0.0.1:42020
M: 2019-10-11 01:28:23.400 Data
M: 2019-10-11 01:28:23.400 0000:  63 18 72 8A 2A 19 40 00 D4 0C 80 62 00 02          *c.r.*.@....b..*
M: 2019-10-11 01:28:23.406 Data received from an unknown source - 127.0.0.1:42020
M: 2019-10-11 01:28:23.406 Data
M: 2019-10-11 01:28:23.406 0000:  64 00 00 00 00 18 72 8A 2A 19 40 00 D4 0C 80 62    *d.....r.*.@....b*
M: 2019-10-11 01:28:23.406 0010:  02                                                 *.*
M: 2019-10-11 01:28:23.406 Data received from an unknown source - 127.0.0.1:42020
M: 2019-10-11 01:28:23.406 Data


Re: Bridging a P25Reflector and a YSFReflector?

Jake Litwin
 

Here’s a short video of what’s happening. 

On Thu, Oct 10, 2019 at 8:29 PM litwinjwi via Groups.Io <litwinjwi=gmail.com@groups.io> wrote:
The Reflector logs though say this

M: 2019-10-11 01:27:49.733 Adding N9KRG      (141.126.148.63:24186)
M: 2019-10-11 01:28:23.375 Transmission started from N9KRG      (141.126.148.63:24186)
M: 2019-10-11 01:28:23.385 Transmission from N9KRG at N9KRG      to TG 420
M: 2019-10-11 01:28:23.400 Data received from an unknown source - 127.0.0.1:42020
M: 2019-10-11 01:28:23.400 Data
M: 2019-10-11 01:28:23.400 0000:  62 02 02 0C 0B 12 64 00 00 80 18 72 8A 2A 19 40    *b.....d....r.*.@*
M: 2019-10-11 01:28:23.400 0010:  00 D4 0C 80 62 00                                  *....b.*
M: 2019-10-11 01:28:23.400 Data received from an unknown source - 127.0.0.1:42020
M: 2019-10-11 01:28:23.400 Data
M: 2019-10-11 01:28:23.400 0000:  63 18 72 8A 2A 19 40 00 D4 0C 80 62 00 02          *c.r.*.@....b..*
M: 2019-10-11 01:28:23.406 Data received from an unknown source - 127.0.0.1:42020
M: 2019-10-11 01:28:23.406 Data
M: 2019-10-11 01:28:23.406 0000:  64 00 00 00 00 18 72 8A 2A 19 40 00 D4 0C 80 62    *d.....r.*.@....b*
M: 2019-10-11 01:28:23.406 0010:  02                                                 *.*
M: 2019-10-11 01:28:23.406 Data received from an unknown source - 127.0.0.1:42020
M: 2019-10-11 01:28:23.406 Data


Re: Bridging a P25Reflector and a YSFReflector?

Jake Litwin
 

The Reflector logs though say this

M: 2019-10-11 01:27:49.733 Adding N9KRG      (141.126.148.63:24186)
M: 2019-10-11 01:28:23.375 Transmission started from N9KRG      (141.126.148.63:24186)
M: 2019-10-11 01:28:23.385 Transmission from N9KRG at N9KRG      to TG 420
M: 2019-10-11 01:28:23.400 Data received from an unknown source - 127.0.0.1:42020
M: 2019-10-11 01:28:23.400 Data
M: 2019-10-11 01:28:23.400 0000:  62 02 02 0C 0B 12 64 00 00 80 18 72 8A 2A 19 40    *b.....d....r.*.@*
M: 2019-10-11 01:28:23.400 0010:  00 D4 0C 80 62 00                                  *....b.*
M: 2019-10-11 01:28:23.400 Data received from an unknown source - 127.0.0.1:42020
M: 2019-10-11 01:28:23.400 Data
M: 2019-10-11 01:28:23.400 0000:  63 18 72 8A 2A 19 40 00 D4 0C 80 62 00 02          *c.r.*.@....b..*
M: 2019-10-11 01:28:23.406 Data received from an unknown source - 127.0.0.1:42020
M: 2019-10-11 01:28:23.406 Data
M: 2019-10-11 01:28:23.406 0000:  64 00 00 00 00 18 72 8A 2A 19 40 00 D4 0C 80 62    *d.....r.*.@....b*
M: 2019-10-11 01:28:23.406 0010:  02                                                 *.*
M: 2019-10-11 01:28:23.406 Data received from an unknown source - 127.0.0.1:42020
M: 2019-10-11 01:28:23.406 Data


Re: Bridging a P25Reflector and a YSFReflector?

Steve N4IRS
 

Run it in the foreground and show ALL output.

On 10/10/19 9:25 PM, litwinjwi@... wrote:
Yeah nothing at all on the gateway. I've stop and started it a couple times.


Re: Bridging a P25Reflector and a YSFReflector?

Jake Litwin
 

Yeah nothing at all on the gateway. I've stop and started it a couple times.


Re: Bridging a P25Reflector and a YSFReflector?

Steve N4IRS
 

None at all when you start the gateway?

On 10/10/19 9:00 PM, litwinjwi@... wrote:
Sorry that is from the P25 Reflector. Not showing any activity or connections on the Gateway.


Re: Bridging a P25Reflector and a YSFReflector?

Jake Litwin
 

Sorry that is from the P25 Reflector. Not showing any activity or connections on the Gateway.


Re: Bridging a P25Reflector and a YSFReflector?

Jake Litwin
 

I'm actually seeing alot of this


M: 2019-10-11 00:11:34.249 Data
M: 2019-10-11 00:11:34.249 0000:  6C 18 F6 13 33 15 F9 00 4B 79 D8 6B 00 02          *l...3...Ky.k..*
M: 2019-10-11 00:11:34.254 Data received from an unknown source - 127.0.0.1:42020
M: 2019-10-11 00:11:34.254 Data
M: 2019-10-11 00:11:34.254 0000:  6D 00 00 00 00 18 E6 B2 6A 5E D0 01 4D D4 B7 4A    *m.......j^..M..$
M: 2019-10-11 00:11:34.254 0010:  02                                                 *.*
M: 2019-10-11 00:11:34.254 Data received from an unknown source - 127.0.0.1:42020


Re: Bridging a P25Reflector and a YSFReflector?

Steve N4IRS
 

Does the P25Gateway log show it connecting and staying connected to the reflector?

On 10/10/19 8:13 PM, litwinjwi@... wrote:
Oh crud. That wasn't the whole gateway config. Here it is. I do have a startup configured. I've attached the whole gateway config and the hosts file


Re: Bridging a P25Reflector and a YSFReflector?

Jake Litwin
 

Oh crud. That wasn't the whole gateway config. Here it is. I do have a startup configured. I've attached the whole gateway config and the hosts file


Re: Bridging a P25Reflector and a YSFReflector?

Steve N4IRS
 

I don't see a startup value.
You want the gateway to connect to the reflector at startup

On 10/10/19 7:32 PM, litwinjwi@... wrote:
Got it. The path flow makes sense. I cannot get traffic to pass over to the p25gateway though. P25reflector still recognizes that I'm connected. So I'm thinking I don't have the gateway setup right. I have the gateway config attached.


Re: Bridging a P25Reflector and a YSFReflector?

Jake Litwin
 

Got it. The path flow makes sense. I cannot get traffic to pass over to the p25gateway though. P25reflector still recognizes that I'm connected. So I'm thinking I don't have the gateway setup right. I have the gateway config attached.

4961 - 4980 of 9925