From: David Ranch <linux-hams@trinnet.net>
To: Stuart Longland VK4MSL <me@vk4msl.yi.org>, linux-hams@vger.kernel.org
Subject: Re: Packet BBSes on ax25d
Date: Sun, 23 Mar 2014 11:00:59 -0700 [thread overview]
Message-ID: <532F215B.3040600@trinnet.net> (raw)
In-Reply-To: <i2h20b-t7c.ln1@atomos.longlandclan.yi.org>
Hello Stuart,
FBB does get some attention now and then but I wouldn't call it active
development. I would make sure you're running the newer version to void
known issues:
"xd705f" is the newest as of 6/2013 is the newest -
http://f6bvp.free.fr/logiciels/BBS-f6fbb/xd705f-src.tar.bz2
There is also Jnos which is probably under more development than FBB:
http://www.langelaar.net/projects/jnos2/about.html
Speaking of BBSes and Outpost, the local ARES/RACES team here in Silicon
Valley (Santa Clara) have done a bang up job at building a multi-node
packet system using JNOS supporting multi-port RF and Internet backups
for full local messaging, BBS forwarding, and SMTP forwarding. This
system was co-developed by Jim Oberhofer KN6PE (Outpost developer) and
many other local HAMs. You can learn more about this system and maybe
save yourself a LOT of time and headaches by contacting that group:
http://www.scc-ares-races.org/packet.html
That team has developed some installer scripts that take a lot of the
pain out of configuring the JNOS, various forwarding rules, etc. to
support tactical callsigns, backup relays, etc.
--David
next prev parent reply other threads:[~2014-03-23 18:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-23 8:02 Packet BBSes on ax25d Stuart Longland VK4MSL
2014-03-23 8:08 ` Gordon JC Pearce
2014-03-23 10:13 ` Ray Wells
2014-03-24 11:27 ` Stuart Longland
2014-03-23 12:40 ` Brian
2014-03-24 11:29 ` Stuart Longland
2014-03-24 12:54 ` Brian
2014-03-23 18:00 ` David Ranch [this message]
2014-03-24 11:35 ` Stuart Longland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=532F215B.3040600@trinnet.net \
--to=linux-hams@trinnet.net \
--cc=linux-hams@vger.kernel.org \
--cc=me@vk4msl.yi.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox