From: "Rodolfo Brasnarof" <rodob@ciudad.com.ar>
To: linux-hams@vger.kernel.org
Subject: New node questions
Date: Thu, 08 Apr 2004 16:15:27 -0300 [thread overview]
Message-ID: <40757A9F.32168.37596D@localhost> (raw)
Hi. I'm setting up a new bbs-node for my local club, to
replace a dos based one (fbb & bpq). It's based on slackware
9.1, on a 486, with 2 vhf ports.
Well, I have a lot of questions:
The node:
Slackware 9.1 includes linuxnode. I also found awznode. Is
there anybody using it, or any other one? Which is best?
There seems to be a standard for nodes to use callsign-4. Is
that correct?
I've seen some examples setting netrom names for a node
(mnemonic) preceded with a # as in #NODE. Is that correct.
Should I use NODE or #NODE as netrom mnemonic for the node?
And what ssid should I use for the netrom port in nrports?
Convers daemon:
I donwloaded and tried htpp-1.22. It works. Then I've found
htppu-1.5 and conversd-saupp. They seem to be derived one on
the other, with fixes and patchs. Again, which is best?
Digipeater:
I'm using digi_ned. It's working fine, as standard
digipeater. I want to enable cross port digipeating (as the
system has 2 ports). Is there any standard in defining the
SSIDs for a cross port digi? For example, I'm trying this:
LU6DG digipeat on the same port (standard digi)
LU6DG-1 digipeat on port 1 (regardless the input port)
LU6DG-2 digipeat on port 2 (regardless the input port)
When crossing ports, it does callsing swaping, and works
fine. Here's the config for this:
digipeat: 1 LU6DG 1
digipeat: 2 LU6DG 2
digipeat: 1 LU6DG-1 1 keep
digipeat: 2 LU6DG-1 1 swap LU6DG-2
digipeat: 2 LU6DG-2 2 keep
digipeat: 1 LU6DG-2 2 swap LU6DG-1
BBS:
A friend has been trying fbb, and it seems to have a problem
when doing compressed forward to a dos or windows fbb. Do
you know something about it?
What about using other bbs program than fbb? What about
dpbox? Any suggestion?
Thanks for all the help.
-----------------
Rodolfo Brasnarof
LW6EAH
Punta Alta
Argentina
next reply other threads:[~2004-04-08 19:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 19:15 Rodolfo Brasnarof [this message]
2004-04-09 12:28 ` New node questions Philip Maley
2004-04-09 14:38 ` Tomi Manninen
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=40757A9F.32168.37596D@localhost \
--to=rodob@ciudad.com.ar \
--cc=linux-hams@vger.kernel.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