[nos-bbs] mbox fbb 2 errors with FBB

['Gustavo Ponza']

Yes, Maiko you are right.

'N 1' parameter should be the ONLY F6FBB pure protocol.

Other MODES featuring the (x)FBB software have nothing
to do with the F6FBB PROTOCOL!

REPEAT: the JNOS2 *without any switch* setup inside the
'autoexec.nos' and I want to intend:

#mbox fbb 0
#mbox nob2f <callsign> # not more needed as of JNOS-2.0j.4

and by using the *AX.25 connection mode* functions OK
(i.e. 100%) with all the major and diffused systems, by using
the *batched and the compressed* FBB forwarding.
The ONLY lack should be the RESUME mode but this is another
thing.

 From years, here, the incoming versions of obcm PBBS forward
correctly, in the above way, with all the JNOS2 versions and so
without any errors and in two way forwarding modes.

For what concerns the *TELNET mode* connection: my JNOS2,
current version, is forwarding with a xdfbb-708b ('N 1' setup)
and with a TNOS-2.30 by using the *batched and the compressed*
FBB forwarding. The obcm and some other versions of FBB may or
may not function.
Naturally the B2F mode implemented on JNOS2 is OK in all cases!

gus

------------------

XDFBB-7.0.8b and TNOS-2.30:

00:12:13  44.135.83.21:6300 - MBOX (ve3cgg) connected
00:12:13  44.135.48.40:telnet - MBOX (ve2har) connected
00:12:13  174.46.122.124:8772 - MBOX (wl2k) connected
00:12:14  44.135.83.21:6300 - MBOX (ve3cgg) forwarding
00:12:14  44.135.48.40:telnet - MBOX (ve2har) forwarding
00:12:14  44.135.48.40:telnet - MBOX (ve2har) proposal FA B CX2SA WW 
SWPC 41911-CX2SA 4764
00:12:15  44.135.83.21:6300 - MBOX (ve3cgg) fwd exit
00:12:15  174.46.122.124:8772 - MBOX (wl2k) forwarding
00:12:15  44.135.48.40:telnet - MBOX (ve2har) got response FS +
00:12:15  44.135.48.40:telnet - MBOX (ve2har) lzhuf compress 931/4467 = 
79 percent
00:12:15  174.46.122.124:8772 - MBOX (wl2k) fwd exit
00:12:17  44.135.48.40:telnet - MBOX (ve2har) $41911-cx2sa sent
00:12:17  44.135.48.40:telnet - MBOX (ve2har) fwd exit

TNOS-2.30:

01:55:24  44.135.48.45:1072 - MBOX (ve2har) login
01:55:24  44.135.48.45:1072 - MBOX (ve2har) open
01:55:24  44.135.48.45:1072 - MBOX (ve2har) forwarding
01:55:24  44.135.48.45:1072 - MBOX (ve2har) incoming proposal FA B CX2SA 
ARL KEP ARLK027 3986
01:55:24  44.135.48.45:1072 - MBOX (ve2har) incoming proposal FA B CX2SA 
WW SWPC 41913-CX2SA 3131
01:55:24  44.135.48.45:1072 - MBOX (ve2har) already have ARLK027
01:55:24  44.135.48.45:1072 - MBOX (ve2har) already have 41913-CX2SA
01:55:24  44.135.48.45:1072 - MBOX (ve2har) our response FS --
01:55:24  44.135.48.45:1072 - MBOX (ve2har) exit

OBCM:

00:27:37  I0OJJ-9 on port xnet - MBOX (i0ojj) open
00:27:39  I0OJJ-9 on port xnet - MBOX (i0ojj) forwarding
00:27:39  I0OJJ-9 on port xnet - MBOX (i0ojj) incoming proposal FA B 
CX2SA WW SWPC 41913-CX2SA 2449
00:27:39  I0OJJ-9 on port xnet - MBOX (i0ojj) our response FS +
00:27:41  I0OJJ-9 on port xnet - MBOX (i0ojj) lzhuf uncompress 1243/2477 
= 49 percent
00:27:41  I0OJJ-9 on port xnet - MBOX (i0ojj) 41913-CX2SA received
00:27:44  I0OJJ-9 on port xnet - MBOX (i0ojj) exit


On 04/09/2016 01:40 AM, Maiko Langelaar wrote:
>
> What ???
>
> As far as I know, N=1 will still let you do compression, the
> documentation says allow FBB forwarding (it does not say you
> can not do compression).
>
> The FBB+BIN (N=2) is something different (that's what I observed
> when I was trying to get things to work a year or more ago). That
> is why the recommendation of N=1 came up in the first place.
>
> GUS ? help me on this please, I'm sure you would have told me
> if the compression was not happening.
>
> I'm away from the internet for a while, so take your time replying.
>
> Maiko
>
>
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org
> http://www.tapr.org/mailman/listinfo/nos-bbs