[nos-bbs] JNOS (#define B2F) - fwding problem/disaster with *older* systems
Bill V WA7NWP
wa7nwp at gmail.com
Tue Jan 18 18:47:25 EST 2011
On Tue, Jan 18, 2011 at 2:40 PM, Maiko Langelaar <maiko at pcs.mb.ca> wrote:
> Hi Bill,
>> Doesn't this B2F scheme have a special symbol in the [XYZ...-JNOS2.0]
>> log on prompt that controls the exchange protocols between the
>> communicating systems?
> Yes it does. For B2F a '2' is inserted into the SID.
> The problem is that if I give a '2' for incoming connects and those
> systems ignore the '2' because they do not have any support for it,
> and they proceed to forward anyways, then things get messed up.
If the connecting station is a '1' (regular FBB or whatever) and the
connected to station is a '2' (B2F) won't both use the lowest common
('1') protocol. If there is no common type -- then there's no way to
Does this mean the current JNOS is treating the incoming as B2F even
when it's not and the sending station has said it's a '1' only system.
Maybe there's no way to differentiate the incoming data and thus the
current JNOS is always picking B2F?
It seems there's something missing in the initial exchange of
capabilities if we need to manually tag the bbs's.
More information about the nos-bbs