[nos-bbs] JNOS + FBB

Miroslav Skoric (YT7MPB) skoric at ptt.yu
Tue Feb 27 02:07:46 EST 2007

Dear hams,

I have been trying to persuade my new-installed JNOS 1.11e to run
properly. I used SV1UY's installation tool dated 1999 from his web site
and after that I also implemented G4ZXI's executable that he compiled
for me. Seems that executables from both the installation utility and
the compiled one work although their set of commands slightly differ, I
suppose due to the different options they have chosen during the

Somehow it looks to me that JNOS does not store messages properly (or
just doesn't handle them after storing). For example, when I post a
message to myself, say SP YT7MPB [@YT7MPB] - I expect it to be read
either locally at JNOS or be forwarded to the FBB system in the LAN
(ethernet). What happens after CTRL-Z or /EX is that JNOS says 'Msg
cueued' but when I try to list or read the message, there is nothing. In
addition, when I initiate forwarding session (or reverse forward) from
FBB, JNOS answers with FQ as if it has nothing for exchange. So it looks
that message 'storing mechanism' does not work. It makes me wonder if
something else should be defined or something like that. I enclose
config.c that G4ZXI have been using when compile the exe for me.

And in fact, at the moment I am only interested in a tiny JNOS BBS that
is capable to forward to the other comp running WinFBB/LinFBB (Other
JNOS services, features, are not actually needed - just to let VHF users
to connect and read bulletins from the JNOS box):

VHF port + TNC2 + 80286 JNOS box > LAN < P2 WinFBB/LinFBB + Internet

So, that means no other services are needed, but full capability BBS
(mailbox), ethernet (packet) and AX.25 radio access to it, forwarding
capability compatible to WinFBB/LinFBB and telnet access to JNOS with
open gateway to radio port. That's all to begin and later some more
services might be added.

Also ...

It seems that I have several issues
with forwarding now, for example:

- Do I need to have different callsigns for 1) WinFBB (ie LinFBB),
2) JNOS, 3) myself as the user (sysop) ?
- If not, should I have different SSID (<callsign>-SSID) for each of
them - in order to differentiate them in between?
- For several reasons, I prefer running WinFBB and it can not access
JNOS properly (I mostly get a situation where WinFBB's callsign is not
recognized by JNOS and the password which follows the callsign gets
interpreted as the callsign - resulting in failure. Is there anything
you can suggest you to do here? Sometimes it passes through and looks
like (from WinFBB's point of view):

[PORT 2 (TELNET) - 20 - YT7MPB-0] 15:24 Connect
*** Connected to YT7MPB
.YT7MPB-9                 <--- FBB's callsign sent once

yt7mpb-9                  <--- FBB's callsign sent again

password                  <--- FBB's password sent once

JNOS (yt7mpb.ampr.org)

login: login: Password:  v n


... and here it wait for forever :-( Looks as if FBB does not sent its
">" after the [FBB-7.00i-AHM$] line and I don't know what to do (with
the same setup, LinFBB sends its ">", see next:

- When running LinFBB (which has the same setup as WinFBB, because
Windows and Linux read the same FAT partition where common FBB files
reside), then it manages to access JNOS with the callsign and password,
but whatever FBB offers to exchange, JNOS refuses as if it already got it.


Misko YT7MPB

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: config.h
URL: <http://lists.tapr.org/pipermail/nos-bbs_lists.tapr.org/attachments/20070227/0930ae04/attachment.h>

More information about the nos-bbs mailing list