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

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