Incoming D-Plus message from unknown source

[K7ZER]

I am new to DStar and am having a problem connecting to some reflectors. Can anyone point me in the right direction of why a reflector would return this error.

My setup is: pi-star (4.9.35-v7+) with DVMEGA VHF/UHF Radio (FW HR3.26) on a Pi 3.

I am able to connect to REF001C, REF030C and many XRF reflectors but many others reflectors I get the following error.

Here is the error I receive form my ircDDBGateway log using REF014C and many others:

M: 2019-01-16 17:53:00: Linking K7ZER N to REF014 C
M: 2019-01-16 17:53:00: D-Plus reply is OKRO
M: 2019-01-16 17:53:00: D-Plus NAK message received from REF014 C
M: 2019-01-16 17:53:00: D-Plus link to REF014 C was refused
M: 2019-01-16 17:53:00: Incoming D-Plus message from unknown source

I googled and searched many forums for information on this error and found very little. I did find the source code for "DPlusHandler.cpp" and see this error on line:320 but have not idea what conditions cause this error to be returned.
https://github.com/dl5di/OpenDV/blob/ma ... andler.cpp

I feel I eliminated registration problems as the cause by having the gateway administrator completely delete and renew my records and I re-setup my terminals <space>,B and N. When I check pistar.uk DStar-Gateway Registration Check it reports "Registration OK! (17)". Also I don't think this is a radio (ID-51A+2) programming problem because it also happens when I use pi-star admin dashboard to connect not involving the radio at all only the Pi.

If anyone has any information on what would causes a reflector to refuse a connection with a " Incoming D-Plus message from unknown source" message please let me know.

Thanks

Sean
K7ZER

[M1DNS]

Usually the OKRO reply on a connection is ok Read Only.

Indicating the call is not registered for use on REF (DPlus) Reflectors.
So it's then dropping you.

Check you have the correct call entered in ur config.
Occasionally the entry gets fumbled, and is easily overlooked.
Also check the entry is upper case.

Andrew M1DNS, (Mod)

[w7efs]

Do you get the same results using mode "K7ZER B" instead of "K7ZER N"? I notice on the dashboard http://ref014.dstargateway.org/ that the "Remote Users" section is usually null or A-D; other reflectors may be more permissive. Also a quick verification seems justified:

Code: Select all

$ grep -i ref014 /usr/local/etc/*txt
/usr/local/etc/DPlus_Hosts.txt:REF014  ref014.dstargateway.org

$ host ref014.dstargateway.org
ref014.dstargateway.org has address 64.250.229.185

[K7ZER]

Thanks for the reply.

Andrew: My call sign is correct and is all caps on the config page.

w7efs: Here is what I get from the code you posted slightly different result.

$ grep -i ref014 /usr/local/etc/*txt
/usr/local/etc/DPlus_Hosts.txt:REF014 64.250.229.185
$ host ref014.dstargateway.org
ref014.dstargateway.org has address 64.250.229.185

Here is trying to link using 'B'
Still fails on REF014 C:
M: 2019-01-17 17:17:19: Linking K7ZER B to REF014 C
M: 2019-01-17 17:17:19: D-Plus reply is OKRO
M: 2019-01-17 17:17:19: D-Plus NAK message received from REF014 C
M: 2019-01-17 17:17:19: D-Plus link to REF014 C was refused
M: 2019-01-17 17:17:19: Incoming D-Plus message from unknown source

Also tried and fails on REF020 A with an added error message 'Incoming poll from unknown D-Plus dongle':
M: 2019-01-17 18:13:50: Remote control user has linked "K7ZER B" to "REF020 A" with reconnect 0
M: 2019-01-17 18:13:50: Incoming poll from unknown D-Plus dongle
M: 2019-01-17 18:13:50: Incoming poll from unknown D-Plus dongle
M: 2019-01-17 18:13:50: Incoming poll from unknown D-Plus dongle
M: 2019-01-17 18:13:50: Incoming poll from unknown D-Plus dongle
M: 2019-01-17 18:13:50: Incoming poll from unknown D-Plus dongle
M: 2019-01-17 18:13:51: D-Plus reply is OKRO
M: 2019-01-17 18:13:51: D-Plus NAK message received from REF020 A
M: 2019-01-17 18:13:51: D-Plus link to REF020 A was refused
M: 2019-01-17 18:13:51: Incoming D-Plus message from unknown source

Still works on REF012 A:
M: 2019-01-17 17:16:43: Linking K7ZER B to REF012 A
M: 2019-01-17 17:16:43: D-Plus reply is OKRW
M: 2019-01-17 17:16:43: D-Plus ACK message received from REF012 A
M: 2019-01-17 17:16:43: D-Plus link to REF012 A established

I also tested using terminator 'B' on 'REF001 C' and 'REF030 C'. They link with no problem.

That is all I know at this point.

Thanks,
Sean
K7ZER

[MW0MWZ]

I believe the Unknown source issues relate to some NAT traversal / Hole Punching code that is new in the new version of ircDDBGateway, for the time being at least, its disabled, so those will mostly die away as there are not that many mavericks running self complies that had it, most of them were other Pi-Star users, so by the time you read this they may well have stopped.

[KE2N]

I am being plagued with this error message for my new mmdvm setup (Pi-Star:3.4.17) when I try to link to REF repeaters.
This repeater was formerly linked through a G4KLX gateway without problems.

I can link via DCS, although this generates a periodic error message in the gateway log
"CCS: Connection has failed (poll inactivity) for W4BRM B, reconnecting"

I can link to XRF, but get the log message:
"Unknown incoming DCS poll from DCS006 D"

These errors generate a repeated spoken message about connecting

Does all this suggest some specific problem?

My connection to the internet is via an OpenVPN connection to a VPS service.

Thanks
Ken

[KE2N]

OK - I figured out the unknown source error. The menu config put in the repeater call sign for DPlus ID. In this case the repeater is registered with ircDDB but not USTrust. Going to the "advanced" configuration pages let me put in my personal call sign for the DPlus login ID whilst leaving the repeater call sign unchanged.

Now if I could only figure out why DCS and XLX reflectors give me this error and corresponding announcement about a dozen times

Unknown incoming DCS poll from DCS006 A

after a while I got this

DCS link to DCS006 A has failed (poll inactivity)
M: 2020-05-20 22:10:00: DCS link to DCS006 A has failed, relinking
M: 2020-05-20 22:10:00: Unknown incoming DCS poll from DCS006 A
M: 2020-05-20 22:10:00: DCS ACK message received from DCS006 A
M: 2020-05-20 22:10:00: DCS link to DCS006 A established

But I still hear announcements from time to time

[KE2N]

OK - here is another clue
right at the very start it seems that my CCS connection was refused

I: 2020-05-22 02:30:20: Connecting to ircDDB
M: 2020-05-22 02:30:20: CCS: Connection refused for W4BRM B
I: 2020-05-22 02:30:25: Connected to ircDDB

now W4BRM *does* have a CCS7 ID and I entered it in the place where I think it goes.
That same number is in use for a DMR repeater - if that matters