[nos-bbs] 2.0k.rc testing: BPQ working.

[Michael Fox - N6MEF]

Thanks to help from Bob Tenty, I've got forwarding working the BPQ.  

 

Connecting to Bob's BPQ station, I used a configuration like the example
here:

http://www.langelaar.net/jnos2/documents/examples_2.0k.txt

 

However, for the other BPQ station I forward with, AG6QO, the configuration
differs from the above example.  AG6QO evidently performs an automatic
connection to the BBS when I login.  So my forward.bbs differs from the
example on the above web page because it does not include:

+BPQ

.BPQBBS

 

In fact, if I send the BPQBBS command, I get an error and the connection is
dropped.  

 

So, my forward.bbs entry for this particular BPQ station looks like:

 

         ag6qo

         telnet <ipaddr> <fbb-port> cronly

         .<mycall>

         .<mypasswd>

         <mailbox-list>

 

A key point for people not familiar with BPQ (like me) is that a BPQ sysop
may give you two ports - a telnet port and an "FBB" port.  Use the FBB port
number.  Otherwise, you can connect and login, but you will get protocol
errors when you forward messages. 

 

So far, 2.0k.rc is working great with two different BPQ machines:  Bob's
VA3TOK machine and AG6QO here in Northern California.

 

Also, Maiko:  I don't think I've seen a premature session abort yet.  Prior
to 2.0k.rc, they used to occur a few times a day.  I'll continue to run the
traces for another day or so.

 

Michael

N6MEF

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/nos-bbs_lists.tapr.org/attachments/20160706/f315d6fc/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Untitled attachment 00218.txt
URL: <http://lists.tapr.org/pipermail/nos-bbs_lists.tapr.org/attachments/20160706/f315d6fc/attachment.txt>