LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

updated

This commit is contained in:
gferg 2000-12-01 05:48:45 +00:00
parent a82ec786f4
commit 051eeacb2e
1 changed files with 180 additions and 71 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

251
LDP/howto/linuxdoc/FBB.sgml
View File

@ -6,7 +6,7 @@
<title>FBB Packet-radio BBS mini-HOWTO
<author>Miroslav "Misko" Skoric, YT7MPB,
<tt/m.skoric@eunet.yu/
<date>v1.5, 15 November 2000
<date>v1.6, 30 November 2000
<abstract>
<nidx>linux windows nt amateur packet radio</nidx>
This mini-HOWTO covers the installation and use of
@ -102,6 +102,10 @@ LinFBB ...
<tscreen><verb>x700f01.tgz</verb></tscreen>
and <tscreen><verb>x700g.tgz</verb></tscreen>
are "upgrades" to any previous "full" package.
For example, after I have upgraded to <tt>x700g.tgz</tt>
I started to run X11 LinFBB 7.00g (04. August 1998).
BTW, X11 versions are not maintained anymore, so
I still run it here. It has some bugs but I like it.
<p>
<item>Copy the archive file in <bf>/tmp</bf> directory.
@ -151,7 +155,7 @@ LinFBB ...
all configuration files, you may start the
software: <bf>./xfbb.sh</bf> (<-- type this within
an xterm or something similar). When you
start FBB for the first time, it will ask
start your BBS for the first time, it will ask
you to create some files it needs, so you
should answer "yes" to the questions.
@ -168,7 +172,7 @@ and file system). I wanted to have 'independent'
operating systems that won't see each other. So I
made two NT's partitions as NTFS partitions and
rest of the space used Linux as ext2 partitions.
Well, first I have installed WinFBB under NT and
Well, first I have installed WinFBB under NT and X11
LinFBB under Linux. Both of them worked, but there
was a big "problem": I could not share their
system files. You might say: So, what a big deal.
@ -185,12 +189,12 @@ versa, of course).</em>
<item>Well, in order to allow both WinFBB under
Windows NT and LinFBB under Linux to use
some common files, it is needed to put these
files in a place both operating systems can
"see" them. So I do that by re-installing
files in a place where both operating systems can
"see". So I do that by re-installing
WinFBB onto a FAT (FAT16) partition that is
seen by NT and Linux. The best way to do
that is to install a fresh copy of WinFBB on
a FAT partition and to copy complete old
recognized by NT and Linux too. The best way to do
that is to install a "fresh" copy of WinFBB on
a FAT partition and to copy complete "old"
WinFBB from NTFS partition over the fresh
installation (whenever you are asked to
rewrite existing files, you should answer
@ -201,20 +205,21 @@ versa, of course).</em>
of the existing old WinFBB, but this time on
the FAT partition that is visible from under
Linux. Anyway, you should check if the "new"
installation might be properly run as earlier.
installation is able to run as the "old" one.
<p>
<item>I could also recommended you to check the file
<item>I could also recommend you to check the file
tree of WinFBB in order to become more
familiar with that. The file tree of LinFBB
familiar with it. The file tree of LinFBB
is a bit different so it is advisable to
note various details.
note various details here and there.
<p>
<item>Some files can't be used as such under both
<item>Some files can't be used as they are under <em>both</em>
operating systems (without some neccesary
changes). That's why some file names should
be renamed:
be renamed (or, at least, you should make
appropriate copies of some files):
<p>
<tscreen><verb>
@ -225,21 +230,26 @@ versa, of course).</em>
</verb></tscreen>
<p>
FBB is able to recognize those changes.
FBB is able to recognize and accept those renamed files.
<p>
<item>Make a backup of the new WinFBB (I do this
by copying the whole FBB file structure into
the other Windows partition that won't be
shared with Linux, like NTFS one).
<item>Make a backup of the actual WinFBB (I do this
by copying the whole WinFBB file structure into
the other Windows partition that <em>won't</em> be
shared with Linux, like NTFS one). You'll never
know when a catastrophe may happen, so as a result,
you won't be able to start neither of WinFBB or new
LinFBB. As a precaution, the backup might be the
easiest way to recover at least the old WinFBB for
a while (until you configure your new LinFBB, ok?).
<p>
<item>Now you should restart your machine and boot
Linux. Log on as 'root' or make 'su' from a
<item>Now, you should restart your machine and boot
into Linux. Log on as 'root' or make 'su' from a
user's account.
<p>
<item>Mount a shared FAT directory:
<item>Mount a shared FAT directory (where FBB files are):
<bf>mount -t vfat /dev/hda2 /mnt/win</bf>
(for example).
@ -268,12 +278,12 @@ versa, of course).</em>
<p>
<item>Copy <bf>/usr/local/fbb</bf> to <bf>/mnt/win/fbb</bf> but do
*not* over-write existing files with the new files
*not* rewrite existing files with the new files
having the same names.
<p>
<item>Copy <bf>/mnt/win/fbb/init_w.srv</bf> to a file
<bf>/mnt/win/fbb/init_l.srv</bf>
<item>Copy <bf>/mnt/win/fbb/init_w.srv</bf> to
<bf>/mnt/win/fbb/init_l.srv</bf> file.
<p>
<item>Edit <bf>/mnt/win/fbb/init_l.srv</bf> to what is
@ -284,7 +294,7 @@ versa, of course).</em>
<item>Copy newly edited <bf>/mnt/win/fbb/init_l.srv</bf>
over the <bf>/mnt/win/fbb/init.srv</bf> (if you do
not do that, maybe you wouldn't be able to start LinFBB
using <bf>./xfbb.sh</bf>, like me).
using <bf>./xfbb.sh</bf>, like me at first).
<p>
<item>Copy <bf>/mnt/win/fbb/system/port_w.sys</bf> to
@ -308,7 +318,14 @@ versa, of course).</em>
<item>Start the script <bf>./xfbb.sh</bf> to run LinFBB.
If everything is ok, your LinFBB under Linux
should run with the same configuration as
your "old" WinFBB under Windows.
your "old" WinFBB under Windows. From this point,
both FBB's should behave very similar (actually,
I must admit that WinFBB has much better visual
quality than X11 LinFBB, but probably the reasons
for that you may find in Windows-vs.-Linux-GUI
quality battles). FYI, my actual WinFBB is v7.00g25
(05. January 2000) and X11 LinFBB is v7.00g (04.August
1998).
</itemize>
@ -354,22 +371,22 @@ Protus offers several interesting features:
<p>
<item>It can send messages to new users who have
connected for the first time, informing
connected the BBS for the first time, informing
them about the password utility.
<p>
<item>It can send messages to users who entered
<item>It can send messages to users who have entered
wrong password (before disconnecting them),
<p>
<item>It can inform sysop about quite everything
<item>It can inform sysop about almost everything
related to users' connections (new user on
the system, unsuccessful connections etc),
<p>
<item>Messages mentioned above could be translated
into various languages, similar to various
languages FBB uses,
into various languages and used similarly as various
language files that FBB uses,
<p>
<item>Messages mentioned above could be different
@ -380,7 +397,7 @@ Protus offers several interesting features:
intervals of time using CRON.SYS system file,
<p>
<item>Passwords could be remotely managed, using an
<item>Passwords could be managed remotely, using an
external server, developed by Jose EB5IVB,
<p>
@ -403,7 +420,7 @@ radio BBS, using Protus type of <em>c_filter</em>:
files should be placed. In addition, the
main C_FILT*.DLL files should be copied
into <bf>\FBB\BIN</bf> as well as a couple of "system",
i.e. config *.PRT files that are going to be
(i.e. config) *.PRT files that are going to be
within <bf>\FBB\SYSTEM</bf> directory.
<p>
@ -420,10 +437,10 @@ radio BBS, using Protus type of <em>c_filter</em>:
connect to the BBS). For your information,
I usualy don't care much about, because my
BBS's are so called "open systems". It means
they work quite normal for all users in the
same way as they worked before using Protus.
they work quite normal for <em>all</em> users in the
same way as they worked <em>before</em> implementing Protus.
Only a couple of callsigns have password
implemented and, when connecting, they know
installed and, when connecting, they know
what they are doing, so, they don't need
any additional info. Your mileage may vary.
@ -434,16 +451,16 @@ radio BBS, using Protus type of <em>c_filter</em>:
connections to your BBS (including console),
you should see a line like this: <bf>{PROTUS-4.0}</bf>
just after a line [[FBB-7.00-AB1FHMRX$]. It
only designates that Protus is active on the
only gives an information that Protus is active on the
system. Users of your system who don't have
their password, connect normally as before.
their passwords, connect just normally as before.
Users who's callsigns have password implemented,
are prompted for password just after their connections.
<p>
<item>The author of Protus, Jesus EB5AGF, has made
several working "modes" of its utility. It
is possible for users to have various kinds
is possible for users to get various kinds
of security: a fixed phrase as a password
(similar when you connect to the Internet
via telephone line, but this way the phrase
@ -453,27 +470,32 @@ radio BBS, using Protus type of <em>c_filter</em>:
that uses automatic answer from user's client
packet programs; implementation of MD2 and
MD5 algorythms; FBB-to-FBB automatic forward
protection etc.
protection etc. FYI, my WinFBB is equipped
with 16-bit Protus 4.0 (13. August 1999).
There is also a 32-bit module of the same date
that would be called from within 32-bit WinFBB
(I haven't tested those two).
<p>
<item>Well, the situation regarding the position
of files under LinFBB is somewhat different.
I have become used to the directory structure
<item>Well, the situation regarding working location
of Protus files under LinFBB is somewhat different.
I have become familiar to the directory structure
that DosFBB and WinFBB versions of Protus have
been using, so I considered that it was enough
just to copy the same directory structure when
I started the installation of Protus under LinFBB.
It was wrong. After having pulled out the
remaining hair, the thing started to work, so,
remaining hair, the things started to work, so,
now I am going to tell you what to do.
<p>
<item>I think I have already told you that I have
<item>I have already told you that I have
been running here both WinFBB under Windows NT
and LinFBB under Linux (see also <tt>Linux+WinNT
mini-HOWTO</tt> and <tt>Lilo mini-HOWTO</tt>). That means
all Protus stuff has already been installed,
except Linux executable of <em>c_filter</em> file. I
all Protus stuff has already been installed in
a way WinFBB has required, except <em>Linux</em>
executable of <em>c_filter</em> file. I
put that file into <bf>/fbb/bin</bf> directory and,
after the next restart of LinFBB, I got the
info mentioned above: {PROTUS-4.0}. But the
@ -486,21 +508,21 @@ radio BBS, using Protus type of <em>c_filter</em>:
still didn't want to run, unless I copied
<em>also</em> *.PRT files from <bf>\FBB\SYSTEM</bf> to the
new location (<bf>/var/ax25/fbb/protus</bf>). After I
did that, Protus became functional.
did that, Protus became fully functional.
<p>
<item>Well, I suppose, the above info would be
useful for those of you who intend to run
both Windows and Linux on the same machine.
*both* Windows and Linux FBB's on the same machine.
For the majority of LinFBB-only users, it is just
important to make <bf>/var/local/fbb/protus</bf>
important to make <bf>/var/ax25/fbb/protus</bf>
where <em>all</em> *.prt files should be placed. <em>Only</em>
c_filter executable should go to <bf>/fbb/bin</bf>
and that's it.
<p>
<item>About FBB-to-FBB protection: *both* partners
have to install Protus and password for the
have to install Protus. Password for the
forwarding partner's callsign must be the
same at *both* sides of the link. The versions
of Protus don't need to be the same (neither
@ -509,14 +531,14 @@ radio BBS, using Protus type of <em>c_filter</em>:
work if both parties have Protus 4.x and
above (I still don't use that, but it is not
a problem, because my two boxes, DosFBB/Protus3.3 and
WinFBB/LinFBB/Protus4.0, make all things ok).
WinFBB/LinFBB/Protus4.0, make all things ok with MD2).
<p>
<item>One of the interesting features of Protus is to
log unsuccessful connections. Due to the
<em>different</em> locations of *.prt files here, I have
separate logs for WinFBB and LinFBB. Those of
you who are going to run only one version of
separate logs for WinFBB and LinFBB c_filtering.
Those of you who are going to run only one version of
FBB, will have <em>one</em> complete log of connection
errors, your users make when they try
connecting your BBS.
@ -535,12 +557,25 @@ radio BBS, using Protus type of <em>c_filter</em>:
Then, there is no way a user could enter your
FBB unless its callsign has given a password
within your Protus. Any unauthorized try to
connect your BBS is logged. In addition,
connect your BBS is logged.
<p>
<item>In addition,
you may decide to have a "guest" access or
a "read-only" as <em>default</em> for some ports
and/or for users who enter the wrong password.
Many combinations are possible. You could
even password protect your own FBB console!
even password protect your own FBB console!
<p>
<item>To finish with this topic for now, just to
inform you that my X11 LinFBB is equipped
with Protus v4.1b7 (15. February 2000). It
has some minor bugs, for example, it logs
incoming connections with a SSID of -48 if
a user doesn't have a SSID at all (of
course, a SSID of -0 would be expectible
in such case).
</itemize>
@ -556,15 +591,15 @@ reading these words now). What I think when mention
learned how to get both WinFBB and LinFBB for X11 on
the same computer. But, that's not all. There is a
variety of daemon versions of LinFBB. In this section
we are going to discuss how to *add* a daemon FBB
we are going to discuss how to *add* a daemon LinFBB
to the existing two: X11 LinFBB and WinFBB!</em>
<p>
<itemize>
<item>Well, many amateurs suggested me to install some
packages that looked to me not too much needed
for LinFBB itself to be run. Anyway, I have installed
packages that looked to me as not too much needed
for LinFBB itself - to be run. Anyway, I have installed
those packages <em>before</em> the installation
of LinFBB daemon version itself:
@ -578,7 +613,10 @@ to the existing two: X11 LinFBB and WinFBB!</em>
<p>
<item>Now it is the right time to install <tt>fbbsrv.rpm</tt>
package. The archive is composed to make its
own directories, as "base" directories.
own directories, as "base" directories. The last new
daemon version to start with, that I managed to find as
a <tt>.rpm</tt> package, was 7.01f Release 4 (09. December
1999).
<p>
<item>A file <bf>fbb.conf</bf>, that serves as the
@ -586,9 +624,9 @@ to the existing two: X11 LinFBB and WinFBB!</em>
following location: <bf>/etc/ax25/fbb.conf</bf>
<p>
<item><em>Unless</em> you are going to install daemon-only
<item><em>Unless</em> you are going to install daemon-<em>only</em>
system, you should make a backup of the
following files:
existing following files:
<p>
<tscreen><verb>
@ -681,11 +719,81 @@ to the existing two: X11 LinFBB and WinFBB!</em>
also be activated within another <em>xterm</em>.
<p>
<item>When you finish your xfbbC session, it is suitable
to use the same <em>xterm</em> to eventually stop
daemon. First of all, using the command <bf>ps ax</bf>
you should locate PIDs of daemon, that you may
<bf>kill</bf> after that.
<item>If you are like me, you would like to activate one
more <em>xterm</em> with xfbbC in a way to monitor
your radio frequency. If you have enough room on
your screen, you may place all three <em>xterm</em>
windows side by side.
<p>
<item>When you finish your xfbbC console session, it is suitable
to use the same <em>xterm</em> to eventually stop the
daemon. First of all, with the command <bf>ps ax</bf>
you should locate PIDs of xfbb.sh shell and daemon itself,
that you may <bf>kill</bf> after that.
</itemize>
<p>
<sect1>How to install an "upgrade" to daemon version of LinFBB
<p>
<em>Notice: Well, the main trouble I discovered with this daemon
was the absence of Protus c_filter protection. As I told you
before, Protus is a "third-party" product, so it might have
some problems with the compatibility to LinFBB itself. Anyway,
it is also possible that a daemon version of LinFBB has some
minor requirements over some files locations.</em>
<p>
<itemize>
<item>So, it looked to me that my version of Protus was newer
than the version of daemon LinFBB I was using. Beside
that, some hams as well as F6FBB himself, suggested me
to upgrade. The "problem" I have found was that I am
still new in compiling Linux software, so, I'd rather
look for some new pre-compiled packages.
<p>
<item>Jose, HI8GN, has offered daemon LinFBB v7.02g as a
<tt>.rpm</tt> package (18. September 2000). I got it
from his site:
<url url="http://hi8gn.dynip.com/indice.html" name=
"http://hi8gn.dynip.com/indice.html">. When I tried
to install it above the previous daemon LinFBB, it
complained about some existing old files.
<p>
<item>Then I had to de-install the existing installation, but
some main config files have remained as <tt>.rpmsave</tt>
files. It is good because you may use them to update
your new-installed config files. So I did.
<p>
<item>The installation of Jose's package was performed
without problems, but daemon was not likely to run
as I expected. I have decided to copy new <tt>xfbbd</tt>
and some other executables from this package and
*remove* it in order to install back the previous
version of LinFBB - that worked ok.
<p>
<item>So far - so good. The "old" version was installed and
tested again one more time. Then, I just copied the
previously saved executables from the new package,
over the "old" executables. After some more minor config
adaptations, the new daemon LinFBB v7.02g has come
in place and function. Comments...?
<p>
<item>Well, its daemon looks for some more directories
than the older version, mostly regarding <tt>7plus</tt>
operations. Next, its xfbbC console client looks better
than the previous version. But, I still miss the
functional X11 client that I have found out of
order. I hope it will be fixed soon. Finally, Protus
c_filter utility is active too.
</itemize>
@ -697,9 +805,9 @@ to the existing two: X11 LinFBB and WinFBB!</em>
<em>Copyright is a source of much and continuous
debate on the LDP mailing list. For more in depth
information please consult the Manifesto at the
</em> <url url="http://www.LinuxDoc.org/"
name="LinuxDoc"> site.
<em>The purpose of having a license is to allow
</em> <url url="http://www.linuxdoc.org/"
name="LinuxDoc"> <em>site. The purpose of having
a license is to allow
appropriate distribution. You can use any license
that meets the Manifesto. What follows is a
boilerplatte license.
@ -786,6 +894,7 @@ homepage.
Jean-Paul Roubelat, F6FBB, the author of FBB.
Per Olsen, LA6CU, the author of FBB documentation.
Jesus R., EB5AGF, the author of Protus.
Jose Marte, HI8GN, the packager of 7.02g package.
</verb></tscreen>