All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ranch <linux-hams@trinnet.net>
To: folkert <folkert@vanheusden.com>, linux-hams@vger.kernel.org
Subject: Re: [Linux-ham] netrom
Date: Fri, 1 Apr 2016 12:37:21 -0700	[thread overview]
Message-ID: <56FECDF1.5090701@trinnet.net> (raw)
In-Reply-To: <20160401184009.GB25136@belle.intranet.vanheusden.com>


Hello Folkert,

> /etc/ax25/nrports contains:
> nr0      FH2LOR-2        svnnah   235     netrom

Don't use a name like "nr0" as this device name will be used and shown 
in the output of "ifconfig -a".  In the nrports file, I recommend to 
name it say "netrom" or "netrom0".  Anything will do really.



> /etc/ax25/nrbroadcast contains:
> ax0	5	192	100	1

This is your problem.. this needs to point to the AX25 interface name 
and NOT the device name.  This will be something like "vhfdrop" or 
whatever as defined in your /etc/ax25/axports file.  Btw, unless your 
machine is going to be a high level netrom node, I don't recommend you 
send out Netrom beacons to have stations route traffic THROUGH you.  As 
such, change the last parameter (called verbose) to 0.


> and /etc/ax25/axports contains:
> ax0	FH2LOR-1	115200	254	1	AX.25 over LoRa

Don't use a name like "ax0" as this device name will be used and shown 
in the output of "ifconfig -a".  In the axports file, I recommend to 
name it say "vhfdrop" or "d710".  Anything will do really.

--David
KI6ZHD

  reply	other threads:[~2016-04-01 19:37 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 [this message]
2016-04-01 20:12   ` folkert
2016-04-01 21:20     ` David Ranch
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=56FECDF1.5090701@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.