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


Join main@DVSwitch.groups.io to automatically receive all group messages.