| |
I0OJJ > BPQ 09.11.23 22:02l 68 Lines 1443 Bytes #116 (0) @ WW
BID : 110-I0OJJ
Read: GUEST
Subj: LinBPQ failures
Path: IW8PGT<I3XTY<I0OJJ
Sent: 231109/1857Z 110@I0OJJ.ITA.EU [Rome] $:110-I0OJJ
From: I0OJJ@I0OJJ.ITA.EU
To : BPQ@WW
Headers:
From: I0OJJ@I0OJJ.ITA.EU
To: BPQ@WW
Hi Sergej,
> From: UT1HZM
> To: BPQ
> Type/Status: BF
> Date/Time: 09-Nov 12:23Z
> Bid: 21765_UT1HZM
> Title: Re^2: G8BPQ Please!!!
> Hello, Gus
>
> Tks for pointing, its seems some problem with telnet session,
> maybe differents in CR, LF bytes or some similar data flow control...
technically there are two more carriage returns on BPQ
that destroy the FBB protocol and this should be easy
to correct on the BPQ part :)
Other BPQ areas could be refined, but ...
> To compare can you try incomming connect to a BPQ's telnet-port,
> instead of fbb-port?!
It's even worst :) The simple goal should be
to telnet the TCPPORT of node and then
connect to BBS, like this:
---------
$ telnet rmgate.mooo.com 8010
Trying 79.46.5.23...
Connected to rmgate.mooo.com.
Escape character is '^]'.
login:i0ojj
password:
Connected to IR0AAB-2's Telnet Server
bbs
SICDRM:IR0AAB-2} Connected to BBS
[BPQ-6.0.24.19-B1FWIHJM$]
Hello Gustavo.
IR0AAB>
----------
but this is possible ONLY 'by hand' since
by doing that on forwarding the protocol
'FREEZE' :((
> BTW you can contact John by e-mail or in groups.io list...
I lost his e-mail address and my internet
search gave no result... however I was excluded
on a previous ML group and so, it is enough
for me :)
> 73, Sergej.
--
73 and ciao, gustavo i0ojj/ir0aab/ir0eq
Quidquid latine dictum sit, altum videtur
Read previous mail | Read next mail
| |
