[nos-bbs] JNOS bleeding doesn't work with BPQ

Tue Apr 19 21:25:20 EDT 2016

The results of testing plain JNOS 2.0j.7v (no "bleeding" fixes) using
compressed FBB (mbox fbb 2) are as follows:

*  Inbound forwarding from BPQ to JNOS works

*  Outbound forwarding from JNOS to BPQ does not work.  Example below.

With JNOS 2.0j.7v+bleeding+forward.c, we have the following results:

Inbound:  As Maiko has pointed out, the new "noiac" option with the bleeding
fixes applies only to outbound.  So inbound forwarding from BPQ to JNOS
2.0j.7v+bleeding+forward.c is now broken, as expected.

Outbound:  telnet and "mbox fbb 2" and "noiac" still doesn't work.  This is
not a new problem since it also didn't work in 2.0j.7v.

Following is log and telnet trace of an outbound (JNOS to BPQ) forwarding
session.  I doubt there is enough here to fix the problem, since the BPQ
error is not very specific.  I'll ask the BPQ sysop if he has any additional
log information that would indicate what the problem is.

Also, for any BPQ experts:  

The BPQ sysop gave me two ports to try.  He suggested one that he says
others use without a problem.  But when I telnet to that port manually, I
get a connection, but no response (no SID, no user prompt, nothing).  When I
try from JNOS, of course, nothing happens.  When I telnet to the other port,
which the BPQ sysadmin says is obsolete and not used, I get the proper user
and password prompts, followed by the SID.  But attempting to forward from
JNOS to BPQ using that port results in errors (whether I use noiac or not).
Perhaps BPQ doesn't allow forwarding on that port?  I'll try to get more
info from the sysop.  But if anyone here knows more about BPQ forwarding
over telnet, can you provide details?

Michael

N6MEF

Here's an example of the JNOS to BPQ forwarding failure.  This is with jnos
2.0j.7v+bleeding+forward.c:

Nos.log:

Tue Apr 19 18:19:04 2016  CONSOLE - mbox kick ag6qo

Tue Apr 19 18:19:04 2016  x.x.x.x:yyyy - MBOX (ag6qo) connected

Tue Apr 19 18:19:09 2016  x.x.x.x:yyyy - MBOX (ag6qo) forwarding

Tue Apr 19 18:19:09 2016  x.x.x.x:yyyy - MBOX (ag6qo) proposal FA P N6MEF
AG6QO.#NCA.CA.USA.NOAM AG6QO 58516_N6MEF 437

Tue Apr 19 18:19:09 2016  x.x.x.x:yyyy - MBOX (ag6qo) got response FS +

Tue Apr 19 18:19:09 2016  x.x.x.x:yyyy - MBOX (ag6qo) lzhuf compress 97/103
= 5 percent

Tue Apr 19 18:19:10 2016  x.x.x.x:yyyy - MBOX (ag6qo) FBB error *** Protocol
Error - Invalid Binary Message Format (Invalid Block Type)

Tue Apr 19 18:19:10 2016  x.x.x.x:yyyy - MBOX (ag6qo) fwd exit

telnet trace:

Date/Time                                                    Src         Dst
Telnet Data

Apr 19, 2016 18:19:05.001013000           ag6qo   N6MEF user:

Apr 19, 2016 18:19:06.928595000           N6MEF ag6qo   N6MEF\x0d\x0a

Apr 19, 2016 18:19:07.005785000           ag6qo   N6MEF password:

Apr 19, 2016 18:19:08.933325000           N6MEF ag6qo   ********\x0d\x0a

Apr 19, 2016 18:19:09.049141000           ag6qo   N6MEF \x0d\x0a

Apr 19, 2016 18:19:09.080840000           ag6qo   N6MEF Welcome to AG6QO's
BPQ Node\x0d\x0a,Press ? For list of commands \x0d\x0a,\x0d\x0a,\x0d

Apr 19, 2016 18:19:09.260195000           ag6qo   N6MEF WINTER:AG6QO-4}
Connected to BBS\x0d\x0a

Apr 19, 2016 18:19:09.365113000           ag6qo   N6MEF
[BPQ-6.0.12.25-B1FWIHJM$]\x0d\x0a,NTS traffic handlers are needed all over
CA. If you are interested, talk to Joe about how to get involved.de
AG6QO>\x0d\x0a

Apr 19, 2016 18:19:09.366071000           N6MEF ag6qo
[JNOS-2.0j.7v.XSC32.4-B1FHIM$]\x0d\x0a,FA P N6MEF AG6QO.#NCA.CA.USA.NOAM
AG6QO 58516_N6MEF 437\x0d\x0a,F>\x0d\x0a

Apr 19, 2016 18:19:09.791086000           ag6qo   N6MEF FS +\x0d\x0a

Apr 19, 2016 18:19:09.793467000           N6MEF ag6qo   \x01\x0dtest noiac

Apr 19, 2016 18:19:09.823240000           N6MEF ag6qo
\x02g\xebYg,\xc3\xb9\x87\xf9A\x1a\xdccX\xbe\xbf:O\xdc\xec\x1b\x88\\\x047

Apr 19, 2016 18:19:10.198885000           ag6qo   N6MEF *** Protocol Error -
Invalid Binary Message Format (Invalid Block Type)\x0d\x0a

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/nos-bbs_lists.tapr.org/attachments/20160419/2859a61a/attachment.html>