[Dxspider-support] node connecting to other nodes not as dxsp
Dirk Koopman
djk at tobit.co.uk
Fri Feb 4 21:39:11 GMT 2022
I finally got around to looking at this.
DK7ET-4 is logging in as DK7ET-4 in its connect script to GB7DJK. But it
is signing (i.e. $mycall in DXVars.pm) as to DK7ET-2.
21:11:00 (chan) -> D DK7ET-4 PC18^DXSpider Version: 1.57 Build: 439 Git:
mojo/6e3c63cd[r] pc9x^5457^
21:11:00 (state) DK7ET-4 channel func state 0 -> init
21:11:02 (chan) -> D DK7ET-4 PC17^YT3E^S50ARX^H10^
21:11:02 (chan) -> D DK7ET-4 PC17^SP6OJE^S50ARX^H10^
21:11:02 (chan) -> D DK7ET-4 PC17^LZ9W^S50ARX^H10^
21:11:02 (chan) -> D DK7ET-4 PC17^YT9TP^S50ARX^H10^
21:11:02 (chan) -> D DK7ET-4 PC17^S57XZ^S50ARX^H10^
21:11:02 (chan) -> D DK7ET-4 PC19^1^S50ARX^0^5000^1^S50ARX^0^5000^H10^
21:11:02 (chan) -> D DK7ET-4 PC16^S50ARX^S53RA - 1^IV3FPX - 1^IV3VFR -
1^IQ3RK - 1^E77DX - 1^YT8T - 1^IK5TBK - 1^E7CW - 1^9A3SM - 1^DL3NCI -
1^IZ8JFL - 1^9A4AE - 1^E75AA - 1^4U9A - 1^IK2QEI - 1^E73QI - 1^E74A - 1^H10^
*21:11:02 (chan) <- I DK7ET-4
PC92^DK7ET-2^76262^A^^5GB7DJK:163.172.11.79^H99^
21:11:02 (chan) <- I DK7ET-4
PC92^DK7ET-2^76262.01^K^5DK7ET-2:5455:248^1^0^H99^*
21:11:02 (chan) <- I DK7ET-4 PC20^
21:11:02 (*) DK7ET-4 send_local_config: traditional
As you can see the node is claiming to be DK7ET-2.
Now, legitimate questions might be:
1. Why don't I get fix it in the code if this sort of thing happens. To
which I could answer: but then no-one would ever know. But see next answer.
2. A more important question is: "why does it think this is a
traditional node based on seeing a PC92 K?". And that would be because
*DK7ET-2 *is some other node, not*DK7ET-4*and so it isn't really
recognising what sort of node it is (because it has not yet yet see a
PC92 K from the login node *DK7ET-4*and those PC92s could have come from
*anywhere* and just been passed "en passant" during node initialisation
(like the PC17s etc GB7DJK is sending you). The moment a PC20 is sent,
the initialisation from an incoming node has finished. If no valid PC92
K has been sent then it is treated as a "traditional" node.
And, of course, rcmds to DK4ET-4 go unanswered because it doesn't exist
anywhere.
Hope that helps
73 Dirk G1TLH
On 02/02/2022 19:45, Erik Tunsch via Dxspider-support wrote:
>
> Hey,
>
> both clusters are dxspiders and connecting to dxspiders... but i also
> did set/spider on the to connect spider...
>
> Am 02.02.2022 um 09:54 schrieb Joaquin . via Dxspider-support:
>> Hi,
>>
>> Have you defined the non dxspider nodes correctly with set/...?
>>
>> Kin
>> EA3CV
>>
>> El mar, 1 feb 2022 a las 22:49, Erik Tunsch via Dxspider-support
>> (<dxspider-support at tobit.co.uk>) escribió:
>>
>> Hello,
>>
>> I currently have the problem, that the incoming spots in my
>> cluster are not beeing decoded, caused by unknown protocol.
>>
>> When i issued who on gb7djk (where I want connect to) it showed
>> me, that my two clusters would connect as EXT.
>>
>> The two clusters are: DK7ET-4 and DK7ET-5
>>
>> they are both running the latest version.
>>
>>
>> 73 Erik
>>
>> --
>>
>>
>>
>>
>>
>> ErikTunsch
>>
>>
>> +49 (0)152 56299673 <tel:+49%20(0)152%2056299673>
>>
>> DK7ET at darc.de <mailto:DK7ET at darc.de>
>>
>> www.DK7ET.de <//www.DK7ET.de>
>>
>> Landjägerstraße 34, 12555 Berlin, GERMANY
>>
>>
>> _______________________________________________
>> Dxspider-support mailing list
>> Dxspider-support at tobit.co.uk
>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support and
>>
>>
>> _______________________________________________
>> Dxspider-support mailing list
>> Dxspider-support at tobit.co.uk
>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
> --
>
>
>
>
>
> ErikTunsch
>
>
> +49 (0)152 56299673 <tel:+49 (0)152 56299673>
>
> DK7ET at darc.de <mailto:DK7ET at darc.de>
>
> www.DK7ET.de <//www.DK7ET.de>
>
> Landjägerstraße 34, 12555 Berlin, GERMANY
>
>
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20220204/affc4220/attachment-0001.htm>
More information about the Dxspider-support
mailing list