OpenBCM V1.07b12 (Linux)

Packet Radio Mailbox

IW8PGT

[Mendicino(CS)-Italy]

 Login: GUEST





  
I0OJJ  > PACKET   22.11.19 16:13l 129 Lines 4492 Bytes #999 (0) @ WW
BID : MBTI0OJJ_001
Read: GUEST
Subj: Re: lu9dce: Line should start with 'F',>
Path: IW8PGT<IR2UBX<EA2RCF<I0OJJ
Sent: 191122/1510z @:I0OJJ.ITA.EU [Rome] obcm1.08-3-g9b42
From: I0OJJ @ I0OJJ.ITA.EU (Gustavo)
To:   PACKET @ WW
X-Info: Sent with login password
X-Info: Received by SMTP-gateway

Hi all,

> Date: 21 Nov 19 11:28:00 GMT
> From: lu9dce@lu9dce.tor.ba.arg.soam
> To: all@ww
> Subject: Line should start with 'F'
> 
> There are several reasons (at least) which can be at
> the root of the subject forwarding error.
> 
> One such scenario is when forwarding to another BBS
> via an intervening node (such as a KPC3).
> 
> This problem is not really much of a problem, because it usually
> occurs AFTER forwarding has successfully completed. The reason
> for it is that the receiving node requests a disconnect before the
> initiating system has received the >FQ. You can probably just ignore
> this, but John (BPQ) is looking into a way to avoid the message.
> 
> A more significant scenario is in the case of a misconfigured
> "Welcome Msgs and Prompts" configuration.
> 
> In this scenario, if you configure a welcome message that
> ends with a '>' charcter, such as 'Welcome to AG6QO>', for
> example, and then add a 'user Prompt' such as 'de AG6QO>',
> this can cause the protocol error.
> 
> Unfortunately, it can block any forwarding between your systems.
> 
> The reason? When your forwarding partner connects to you, your system
> will transmit the welcome message 'Welcome to AG6QO>'. The connecting
> station receives this '>' as your user prompt. Then, your system
> subsequently will send its user prompt, 'de AG6QO>', which will be
> queued on the receiving side, and taken to the response to your forwarding
> partner's forwarding protocol initiation: 'FC EM ...'. etc. Of course
> your forwarding partner's system will be expecting a line beginning with 'F'
> in response, but instead receives 'de AG6QO>', resulting in the error.
> 
> The solution? Don't use a '>' at the end of your welcome prompt,
> and be sure the end of the welcome message and your user Prompt
> contain a new line character!!! That should fix you right up!
> 
> - Joe, AG6QO
> 
> http://ag6qo.com/RpiBPQnode.html


the major fault on the matter is the freedom left
to incapable operators to permit to manipulate the
forwarding prompt, or better the texts before the
prompt, when the PBBSs act as forwarders.

So, the many PBBS running at I0OJJ strictly release
the following forwarding prompts:

[JNOS-2.0m-uro-B1FHIM$]
 >

[OpenBCM-1.08-3-g9b42-AB1D1FHMRW$]
 >

[FBB-7.0.8-AB1FHMRX$]
I0OJJ Mailbox, QTH Rome
(1) I0OJJ BBS>

and no problems.

Also the latest versions of linbpq, as the previous,
when no defaced by stupid welcome messages results
almost simple as shown below:


191121 22:53:49 <I0OJJ     [JNOS-2.0m-uro-B1FHIM$]
191121 22:53:49 <I0OJJ     >
191121 22:53:49 >I0OJJ     [BPQ-6.0.19.13-B1FIHJM$]
191121 22:53:49 >I0OJJ     FF
191121 22:53:50 <I0OJJ     FQ
191121 22:53:50 |I0OJJ     I0OJJ Disconnected
191121 22:53:56 |I0OJJ-8   Incoming Connect from I0OJJ
191121 22:53:56 >I0OJJ-8   [BPQ-6.0.19.13-B1FWIHJM$]
191121 22:53:56 >I0OJJ-8   Hello Gus. Latest Message is 0, Last listed is 0

191121 22:53:56 >I0OJJ-8   IR0AAB>

191121 22:53:57 <I0OJJ-8   [JNOS-2.0m-uro-B1FHIM$]
191121 22:53:57 <I0OJJ-8   FF
191121 22:53:57 >I0OJJ-8   FQ
191121 22:53:57 |I0OJJ-8   I0OJJ-8 Disconnected


The problem of empty lines before and after the prompt
has already been reported to the author John G8BPQ
yesterday.

Then, no problem, or it is a false problem when
forwarding protocol initiation is 'FC EM ...'
because it is referred almost exclusively when
we are with the 'B2F' protocol (that used on the
Winlink 2000 environment), so remaining on BPQ
software it is correctly used when connect the
WL2K CMS. And then it is impossible the fact
that when the PBBS contacted show a SID as
[B1FHIM$] the other propose a line FC EM ... !

Instead uses the correct forwarding protocol
as shown below.

Hope everything is clear understandable :)

--------------
08:09:37  44.134.32.240:6300 (1791) - MBOX (i0ojj) connected
08:09:37  44.134.32.240:6300 (1791) - MBOX (i0ojj) forwarding
08:09:37  44.134.32.240:6300 (1791) - MBOX (i0ojj) proposal FA B LU9DCE 
WW ALERT 2920_LU9DCE 5911
08:09:37  44.134.32.240:6300 (1791) - MBOX (i0ojj) got response FS +
08:09:37  44.134.32.240:6300 (1791) - MBOX (i0ojj) lzhuf compress 
2898/5935 = 51 percent
08:09:37  44.134.32.240:6300 (1791) - MBOX (i0ojj) $2920_LU9DCE sent
08:09:37  - only if we get FF send FQ
08:09:37  44.134.32.240:6300 (1791) - MBOX (i0ojj) fwd exit
-------------

-- 
73 and ciao, gustavo i0ojj/ir0aab/ir0eq



Read previous mail | Read next mail


 23.12.2024 03:47:50lGo back Go up