From: David Ranch <linux-hams@trinnet.net>
To: folkert <folkert@vanheusden.com>
Cc: linux-hams@vger.kernel.org
Subject: Re: [Linux-ham] netrom
Date: Fri, 1 Apr 2016 14:20:47 -0700 [thread overview]
Message-ID: <56FEE62F.40003@trinnet.net> (raw)
In-Reply-To: <20160401201200.GE25136@belle.intranet.vanheusden.com>
Hello Folkert,
> Ah I thought it was actually the network-devicename that you needed to
> put in there!
Yeah... I agree this is NOT obvious nor intuitive
> netrom FH2LOR-2 svnnah 235 netrom
/etc/ax25/nrports Looks ok.
> axport0 5 192 100 0
/etc/ax25/nrbroadcast looks ok but maybe try renaming this to say
"axport". Maybe the trailing 0 is messing things up. Be sure to update
the /etc/ax25/axports file with the same name too
> axport0 FH2LOR-1 115200 254 8 AX.25 over LoRa
Looks ok though what is the RF link speed you're using? I've seen some
funny buffering problems in the past so I actually use 9600 baud to the
TNC for a 1200baud RF link
> Unfortunately it still fails:
>
> root@savannah:~# modprobe netrom
> root@savannah:~# nrattach netrom
> nrattach: cannot find free NET/ROM device
What do you have in /etc/ax25/nrbroadcast
Are you sure the netrom module is loaded? Check:
$ lsmod | grep netrom
netrom 47709 2
ax25 65384 16 netrom,mkiss
The way I load my system via my packetrig.sh startup script, I use:
$NRATTACH -i $AMPRIP -m 236 $VHFD710NRPORT
I would also recommend you to show each of the commands you're using to
load up your stack:
- Are you using the mkiss approach with PTYs or using kissattach
directly?
- Are you seeing any errors when you run each command?
See
http://www.trinityos.com/HAM/CentosDigitalModes/usr/local/sbin/packetrig.sh
for the script but it is a pretty complex script for new Linux users.
--David
KI6ZHD
next prev parent reply other threads:[~2016-04-01 21:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 18:40 [Linux-ham] netrom folkert
2016-04-01 19:37 ` David Ranch
2016-04-01 20:12 ` folkert
2016-04-01 21:20 ` David Ranch [this message]
2016-04-08 9:44 ` folkert
2016-04-08 15:03 ` David Ranch
2016-04-10 19:36 ` folkert
2016-04-10 21:41 ` David Ranch
2016-04-03 11:13 ` Miroslav Skoric
2016-04-03 16:41 ` David Ranch
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=56FEE62F.40003@trinnet.net \
--to=linux-hams@trinnet.net \
--cc=folkert@vanheusden.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.