[nos-bbs] JNOS mbox fbb # vs. FBB forward.sys N #

['Gustavo Ponza']

Ah ah, briefly saying, all the items you exposed below are
incommensurable among them.

Fbb forwarding protocols can operate either in ASCII or binary 
compressed modes.

The three versions of FBB protocol are :

  * Ascii basic protocol <http://www.f6fbb.org/protocole.html#Basic>
  * Binary compressed protocol version 0
    <http://www.f6fbb.org/protocole.html#version0>
  * Binary compressed protocol version 1
    <http://www.f6fbb.org/protocole.html#version1>


Each version is backwards compatible with the previous one.

The values related to the N switch below are referred to some
features (BIN, BIN+RESUME, XForwanding) added to *FBB PBBS*,
repeat the *PBBS software*, and have nothing to do with the so
called *FBB protocol*.
So, indicating N 1, simply means to force the FBB *PBBS* to use
ONLY the standard FBB protocol.

On 04/03/2016 07:32 AM, Michael Fox - N6MEF wrote:
>
> Gus, can you explain further your comment below about mandatory “N 1” 
> on the FBB side compared to the following …
>
> From http://www.f6fbb.org/fbbdoc/fmtforwa.htm I read that the FBB 
> forward.sys file can contain:
>
> N (number)
>
> Assigns the standard forward protocol (MBL/RLI) for the specified BBS.
>
> 1 = FBB forwarding allowed
>
> 2 = FBB+BIN forwarding
>
> 4 = FBB+BIN+Resume
>
> 8 = XFWD
>
> Ex: N 15 = Sum of all protocols (default)
>
> My understanding is that “N 0” is actually just old-style, non-batched 
> forwarding, like our “mbox fbb 0”.
>
> If you are correct that “N 1” is required on the FBB side for 
> FBB-style forwarding with JNOS, then according to the above info, “N 
> 1” is apparently just standard, batched FBB forwarding with no 
> compression (SID option “F”).  And that would be the equivalent of 
> “mbox fbb 1” on the JNOS side.
>

Today, I understand that saying the word "FBB protocol"
it is intended the Binary compressed protocol version 1 
<http://www.f6fbb.org/protocole.html#version1>
and then how this is related and matching to the "mbox fbb (x)"
switch, being the JNOS2 a work in progress (see my previous msg),
how can be demonstrated?

> Michael
>

gus

>
> *From:*nos-bbs [mailto:nos-bbs-bounces at tapr.org] *On Behalf Of 
> *'Gustavo Ponza'
> *Sent:* Saturday, April 2, 2016 4:03 PM
> *To:* TAPR xNOS Mailing List <nos-bbs at tapr.org>
> *Subject:* Re: [nos-bbs] mbox fbb setting
>
> [clipped]
>
>
> The 'telnet' setup on the side of xfbb should be:
>
> # Linux AX.25 port
> #P A
> # Telnet port
> P B
> #
> # No compression [N 0]
> N 1
> #
> IF H 00-23
>  S connected failure busy
>  C C IR0RM-1 44.134.32.233 23
>  V i0ojj$Wxxxnnnxxx$W
> ENDIF
>
> mandatory, for now, is to setup 'N 1'.
>
> Note for Maiko: the problem seems reside on the fact that
> the FBB and some other terminal packet programs need a
> transparent TCP connection rather than the full TELNET
> protocol.
>
> On the JNOS2 side set the connection to:
>
> # for xfbb 7.05g/7.0.8 [ir0aab-1] <- telnet fwd OK (N 1)
> telnet 44.134.32.240 6300
>
>
>
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org
> http://www.tapr.org/mailman/listinfo/nos-bbs

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/nos-bbs_lists.tapr.org/attachments/20160403/48763ef4/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: blue.gif
Type: image/gif
Size: 104 bytes
Desc: not available
URL: <http://lists.tapr.org/pipermail/nos-bbs_lists.tapr.org/attachments/20160403/48763ef4/attachment.gif>