CLX archive - 1998: Re: Problem initiating a connection to a DXNet Node

Re: Problem initiating a connection to a DXNet Node

Franta Bendl (ujub@kerailya.tunkki.fi)
Thu, 23 Apr 1998 11:40:18 +0200

Franta Bendl wrote:
>
> Benoit Filteau wrote:
> >
> > Hello all,
> >
> > I would like to know if someone else is experiencing the same problem i
> > have here.
> >
> > It seems CLX has a problem decoding PC38 and PC18 lines coming from a DXNet
> > node, but according to CLX documentation the syntax for a PC38 is
> > PC38^node,node,node,...^~
> > The PC38 line comming from DXNet seems to be correct except the "^M" that
> > means CR-LF
> >
> > In the second example, CLX recognize correctly PC11 lines and they also
> > have "^M"
> >
> > First example (coming from ~clx_us/log/io.log)
> >
> > Apr 19 20:01:23 ve2qdx syslog: ve9pt-9->:PC38^K1XX^~^M PC18^Cluster: 2
> > nodes, 3 local / 258 total users Max users 1416^5029^~^M
> > Apr 19 20:01:23 ve2qdx syslog: icl_com/us_ctrl.cc: Message is not correct
> > "PC38" /3 from ve9pt.
> > Apr 19 20:01:23 ve2qdx syslog: icl_com/us_ctrl.cc: Message is not correct
> > "PC18" /4 from ve9pt.
> >
> > Another example with another DXNet node
> >
> > Apr 19 23:40:31 ve2qdx syslog:
> > ve2dx->:PC38^VE2PWI,KD1R,K2TR,N1TU,K1KI,W1RM,KB1H
> > ,W1JO,K1EA,KC1XX,NO1A,NK1K,K1EU,W1AO,K1UO,K1AJ,K1XX,NE1R,N1MPY,WA2UEC,KD1F,W
> > 8KZM
> > ,KE2AY,W2XX,W2JT,K2SG,K3WW,W3FRC,W3LPL,N3RS,WT3Q,W3EA,K4FJ,WR3L,K3MQH,NE3H,K
> > 2TW,
> > N2NT,AA1K,N4SR,
> > Apr 19 23:40:31 ve2qdx syslog: ve2dx->:N3RR,N4OHE,N2M
> > Apr 19 23:40:34 ve2qdx syslog: ve2dx->:T,K2GX,K2LS,K2ZZ,N2TX,WB2ETR,VE^~^M
> > PC18^
> > Cluster: 70 nodes, 0 local / 241 total users Max users 474^5030^~^M
> > Apr 19 23:40:34 ve2qdx syslog: icl_com/us_ctrl.cc: Message is not correct
> > "PC38"
> > /2 from ve2dx.
> > Apr 19 23:40:34 ve2qdx syslog: icl_com/us_ctrl.cc: Message is not correct
> > "PC18"
> > /4 from ve2dx.
> > Apr 19 23:40:43 ve2qdx syslog:
> > ve2dx->:PC11^28026.6^VK4XA^20-Apr-1998^0033Z^ ^WA
> > 8VSJ^K8TME^H88^~^M
> > Apr 19 23:40:55 ve2qdx syslog:
> > ve2dx->:PC11^3795.6^ZP5CGL^20-Apr-1998^0031Z^Loud
> > ^W0BV^NJ0M^H83^~^M
> >
> > Someone had this problem and correct it???
> >
> > TNX
> >
> > Benoit VE2QDX
>
> hi benoit,
>
> you are right. there is an error in clx. any PC38 will be not recognized
> correctly. the problem is not the ^M but an error in code. the situation
> in the second example is a littel bit other. the maximum length of the
> body of a PC38 may be about 200 bytes in this moment. i will check it
> to encrease the maximum length in the next version.
>
> the problem of the PC18s in your log ist the '~' at the end. i have
> never seen a PC18 like it. the reason is maybe the "old" version of
> the ak1a cluster software of your partner - 5029. i have seen till
> now only versions about 5446/5447, hi. i can fix it in the next version
> to accept also PC18s with '~' at the end but i don't plan to
> differentiate between different versions of ak1a software to send
> a PC18 with or without a '~'.
>
> there is unfortunately not work arround. but for your quiet,
> neither PC38 nor PC18 are interpreted from clx. so both
> error-messages are harmless for the correct operation of clx.
>
> 73 de franta/dj0zy

Hi benoit,

im very sorry! the last statement in my last mail is not correct.
ben/dl6rai told me you have a problem that connects from other clusters
don't going through. the reason is realy the PC18-error. clx don't
accept
PC18 with '~' at the end and so will be this message not as start of
the init to partner cluster identified. therefore the init of
PC-connection
to partner will be not started (no PC20 will be sent).
to go around of this problem you must either

1. reverse the direction of all connections going from outside to your
cluster (flag '2' in cluster-file) or

2. try a filter between your interface and clx to convert "PC18^....^~"
to
"PC18^....^" (but only for PC18!)

i will fix it in the next version.

73 de franta