| |
PY2BIL > BPQ 08.02.20 01:51l 112 Lines 3769 Bytes #999 (0) @ WW
BID : 14752PY2BIL
Read: GAST
Subj: F>
Path: DB0FFL<OE2XZR<OE5XBR<OE1XAB<HG8LXL<CX2SA<N9PMO<VE1MPF
Sent: 200207/2344Z 12517@VE1MPF.#MCTN.NB.CAN.NOAM BPQ6.0.19
Re: Anomailes in 6.0.19.1
R:200207/2344Z 23694@PY2BIL.SP.BRA.SOAM LinBPQ6.0.19
+------------------------------------------------------------------------------+
Red,
I have not seen that behaviour. I'm running beta versions of BPQ and the latest
from today 6.0.19.30 does not present that, et leas to me.
I have also a msg fwd with OK2PEN (hosted in Brazil, btw) set up here, but he
runs a FBB instance. Maybe that is what it is, but again, I haven't seen it
here.
The best way to get in touch with John with these issues is his goups.io mailing
list. He's *very* active over there.
73
Quoting from a previous message...
> From: PE1RRR
> To: BPQ
> Type/Status: B
> Date/Time: 07-Feb 05:31Z
> Bid: 4498_PE1RRR
> Title: Anomailes in 6.0.19.1
>
>
> HI folks,
>
> I've been seeing this not only from first hand experience but also
> seen in traffic passing through the node there between other BBSes.
> After forwarding is complete, in some situations the BBSes remain
> connected and fall into a loop of exchanging errors which trigger
> more errors.
> To show you what I mean, here's a snippet from my monitor log to
> show you what I mean. Please ignore the extranous lines but for
> the ones between K6EQ and PE1RRR.
>
> -----
> PE1RRR-3 to K6EQ ttl 20 cct=02A9 <INFO S2 R4>:
> *** Protocol Error - Line should start with 'F'
> 18:26:04R K6EQ>PE1RRR-7 Port=11 <I C S0 R6> NET/ROM
> K6EQ to PE1RRR-3 ttl 25 cct=123C <INFO S4 R2>B:
> Invalid Command
> de K6EQ>
> 18:26:04R K6EQ>PE1RRR-7 Port=11 <I C S1 R6> NET/ROM
> K6EQ to PE1RRR-3 ttl 25 cct=123C <INFO S5 R2>B:
> Invalid Command
> de K6EQ>
>
> 18:26:28T PE1RRR-7>K6EQ Port=11 <I C P S7 R3> NET/ROM
> PE1RRR-3 to K6EQ ttl 20 cct=04E1 <INFO S2 R4>:
> *** Protocol Error - Line should start with 'F'
> 18:26:29R K6EQ>PE1RRR-7 Port=11 <I C S3 R7> NET/ROM
> K6EQ to PE1RRR-3 ttl 25 cct=10A0 <INFO S4 R2>:
> Invalid Command
> de K6EQ>
> 18:26:29R K6EQ>PE1RRR-7 Port=11 <I C P S4 R7> NET/ROM
> K6EQ to PE1RRR-3 ttl 25 cct=10A0 <INFO S5 R2>:
> Invalid Command
> de K6EQ>
>
> 19:18:03R LU9DCE-4>PE1RRR-7 Port=11 <I C P S6 R6> NET/ROM
> OK2PEN-1 to GB7CIP ttl 14 cct=2776 <INFO S1 R1>:
> *** Protocol error: Line starting with a letter which is not "F" or "*".
>
>
> I've included one of the ones i managed to catch from OK2PEN and GB7CIP.
>
> But it is slightly different so may be unrelated.
>
> The status on the node circuit shows that the node has been instrcuted to
> disconnect after the fwd, but looking at the status the node appears
> to be hanging onto the circuit until it times out instead of a clean
> disconnect.
>
> (Closing) Circuit(SRDG:K6EQ PE1RRR-3)
> (Closing) Circuit(SRDG:K6EQ PE1RRR-3)
> (Closing) Circuit(SRDG:K6EQ PE1RRR-3)
>
> ---
> I am on the chat with G8BPQ quite frequently but unfrotunately I don't
> have a mail route to his system so this is the next best thing, plus
> if you have seen similar behaviour it would be nice to collect the
> info to maybe get a clearer picture of what is going on, whether it
> be a bug or something else.
>
> 73's
> Red @ PE1RRR
>
>
> [End of Message #23658 from PE1RRR]
>
What follows is just a Tagline....
If you want a place in the sun, you must leave the shade of the family tree.
+-------------------------- SAO PAULO PACKET NODE ---------------------------+
| Grid GG66 Sao Paulo - SP - Brazil 144.390MHz |
| Sysop: PY2BIL PY2BIL.SP.BRA.SOAM py2bil@gmail.com |
+------------------------------------------------------------------------------+
(Message sent with Sally 7.2.035)
Timed 07-fev-2020 20:39 E. South America Standard Time
BBS: PY2BIL
Lese vorherige Mail | Lese naechste Mail
| |
