[nos-bbs] linFBB outgoing compressed fwd to JNOS - a discovery

[Boudewijn (Bob) Tenty]

I may add: No mbox fbb setting in my autoexec.nos.

N 1 is the setting in the bbs fwd file of fbb.

Bob VE3TOK

Maiko,

The N 1 setting still gives an error

VE3MCH = JNOS,  VE3TOK = FBB  See the jnos log below (jnos version 2.0j7j)

Wed Feb 11 01:45:03 2015  44.135.85.151:40072 - MBOX (ve3tok) forwarding
Wed Feb 11 01:45:03 2015  44.135.85.151:40072 - MBOX (ve3tok) FA B CX2SA 
WW SWPC 15443_CX2SA 4075
Wed Feb 11 01:45:03 2015  44.135.85.151:40072 - MBOX (ve3tok) FBB error, 
last read : FB B KI5CT USA PONDER 47070_N0KFQ 3543

Bob VE3TOK

On 15-02-10 03:38 PM, Maiko Langelaar wrote:
>
>> Since I'm not familiar with FBB, can you elaborate on how the linFBB "N"
>> setting below correlates with the JNOS mbox fbb setting ? ...
>
> In short I don't know, I'm playing around, and probably I should have
> waiting before posting all this crap on the list and just confuse
> everyone. I don't see the N having anything to do with FBB level.
>
>> Also, pardon my ignorance.  But isn't there some sort of negotiation
>> of the
>> protocol based on the capabilities of each end?
>
> For the FBB yes, but the N seems to define how the compression internally
> works to me. I'm confused, I should stop now. All I can say is that it
> seems the use of N 1 alluviates the original problem I had from remote
> systems. I'm actually trying to figure this out via code, but it's in
> french so that makes it a bit difficult to figure out in 5 minutes.
>
> Sorry guys, here I go again :)
>
> M
>
>
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org
> http://www.tapr.org/mailman/listinfo/nos-bbs