[Dxspider-support] CLX - Spider connect

[Ian Morrison]

Hi Mike,
This is the same problem we has about a year ago trying to connect 
ve3bip-7 to va3mw-7.  We have been running va3pec-5 ( rf only) connected 
to ve3bip-7 via rf quite successfully now for some time.
Alas tho, the computer at ve3bip-7 just died so we are orphaned for 
awhile. DXSpider is really solid and is virtually problem free, thanks 
to Dirk's code.

Welcome to the "spider" world.
de ve3iem
Ian


Michael Walker wrote:

> Dirk
>
> That might be it.  The actual node call of VA3MW-7 as configured is 
> VA3MW (no ssid).
>
> However, in order to make Spider connect to a different cluster with 
> the same call, I had to apply an SSID, hence the -7.  CLX doesn't 
> normally care.
>
> Unfortunately, Spider can't connect to VA3MW as he feels he is already 
> connected.
>
> Looks like the option is to actually make VA3MW (clx) VA3MW-7
>
> Mike
>
> ----- Original Message ----- From: "Dirk Koopman" <djk at tobit.co.uk>
> To: "Michael Walker" <mike at portcredit.net>; "The DXSpider Support 
> list" <dxspider-support at dxcluster.org>
> Sent: Thursday, September 01, 2005 8:01 AM
> Subject: Re: [Dxspider-support] CLX - Spider connect
>
>
>> On Thu, 2005-09-01 at 07:35 -0400, Michael Walker wrote:
>>
>>> That is pretty much what I have.  Do I need to worry about case?
>>>
>>> On another note, the spider node was receiving spots just fine, and 
>>> then it
>>> stopped.  I can see the spots arriving on the console view, but they 
>>> are not
>>> on the Spider cluster. I haven't even started to play with filters yet.
>>>
>>> Here is the init log (va3mw-7 is clx, va3mw-6 is DX Spider).  At the 
>>> bottom,
>>> can you tell me if the PC51 is outbound from Spider or inbound from 
>>> CLX?
>>>
>>> DXChannel VA3MW-7 created (3)
>>> <- O VA3MW-7 telnet
>>> -> B VA3MW-7 0
>>> -> E VA3MW-7 0
>>> VA3MW-7 channel func  state 0 -> init
>>> <- I VA3MW-7 Hello va3mw-6, you were validated - now connecting to clx.
>>> <- I VA3MW-7 *** connected to clx
>>> <- I VA3MW-7 PC18^ ^5447^
>>> VA3MW-7 channel func  state init -> init
>>> -> D VA3MW-7 PC19^1^VA3MW-6^0^5451^H24^
>>> -> D VA3MW-7 PC16^VA3MW-6^VA3MW - 1^H24^
>>> -> D VA3MW-7 PC20^
>>> <- I VA3MW-7 Login at 1113Z: va3mw-6
>>> <- I VA3MW-7 PC19^0^VA3MW^0^5447^H10^
>>
>>
>> This is the clue. Although quite why clx is sending that spurious Login
>> line I don't know. It has obviously connected to the cluster engine
>> because you have received the PC18.
>>
>>> <- I VA3MW-7 PC22^
>>> VA3MW-7 channel func  state init -> normal
>>> -> D VA3MW-7 PC51^VA3MW-7^VA3MW-6^1^
>>
>>
>> You must be whom you say you are and SSID's matter. So if clx is VA3MW
>> (which is is what the PC19 says it thinks it is) then that has to be the
>> call that you set/clx and also CONNect to. A dim memory seems to be
>> saying that clx doesn't handle SSIDs for nodes, but that may be wrong.
>>
>> I cannot over emphasise the fact that, in order to maintain connections,
>> the callsigns used in protocol must match the callsigns that both you
>> think you are and also are connected to.
>>
>> The problem is that not sending out a PC19 with the correct callsign
>> cannot be detected as an error because it isn't (completely) one. What
>> you are running (should you switch the keep-alive pinging off) is,
>> effectively, "restricted" protocol.
>>
>> Hope this helps
>>
>> Dirk
>> -- 
>> Dirk Koopman <djk at tobit.co.uk>
>>
>>
>>
>
>
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at dxcluster.org
> http://www.tobit.co.uk/mailman/listinfo/dxspider-support
>
>


-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.10.18/88 - Release Date: 9/1/2005