Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: Richard Adams <pa3gcu@zeelandnet.nl>
To: Shane Deering <vk3bvp@qsl.net>, linux-hams@vger.kernel.org
Subject: Re: netrom
Date: Sun, 14 Apr 2002 10:11:07 +0000	[thread overview]
Message-ID: <0204141011070V.00302@unix.pa3gcu> (raw)
In-Reply-To: <200204140557.g3E5vZX11801@msv02-kent-syd.comindico.com.au>

On Sunday 14 April 2002 05:58, Shane Deering wrote:
> G'day all.
> Wonder if someone can help me out.
> I've just set up my good computer (this one) for packet.
> Using kernel 2.4.9-31 and the latest libs, tools and apps.
> AX25 seems to work ok on the 2 test ports I've set up (call, mheard).
> But i'm having problems setting up netrom. Doing what the ax25 how-to say
> to do (I think), but I get the following-
>
> [root@vk3bvp-6 root]# nrattach netrom
> NET/ROM port netrom bound to device nr0
> [root@vk3bvp-6 root]# /usr/sbin/netromd -i
> nrconfig: port netrom not active
> netromd: no NET/ROM ports defined

Have you tryed.
nrattach [-i inetaddr] [-m mtu] [-v] port

>
> My axports file-
>
> # /etc/ax25/axports
> #
> # The format of this file is:
> #
> # name callsign speed paclen window description
> #
> vhf	VK3BVP-8	2400	255	2	144.825 MHz (1200  bps)
> win	VK3BVP-9	57600	255	2	link to winfbb
>
> My nrports file-
>
> # /etc/ax25/nrports
> #
> # The format of this file is:
> #
> # name callsign alias paclen description
> #
> netrom	VK3BVP-10 LINODE	235	Switch Port
>
> The kissatach commands and responses have scrolled off my xterm but from
> history I used these to create ax0 and ax1 -
> [root@vk3bvp-6 root]# /usr/sbin/kissattach /dev/ttyS0 vhf 44.135.96.242
> [root@vk3bvp-6 root]# /usr/sbin/kissattach /dev/ttyS1 win 44.135.96.241
>
> Don't worry about the IP addresses , they are just for testing.
>
> Any idea why NET/ROM isn't working?

-- 
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/


  parent reply	other threads:[~2002-04-14 10:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-14  5:58 netrom Shane Deering
2002-04-14  7:25 ` netrom Arno Verhoeven
2002-04-14  8:24   ` netrom Shane Deering
2002-04-14 10:11 ` Richard Adams [this message]
2002-04-14 12:45   ` netrom Shane Deering
2002-04-14 22:06 ` netrom M Taylor
2002-04-14 22:55   ` netrom Riley Williams
2002-04-15  0:23     ` netrom Walter R Fletcher
2002-04-15 17:55       ` netrom Riley Williams
2002-04-15 19:25         ` netrom Richard Adams
2002-04-15  1:16   ` netrom Shane Deering
  -- strict thread matches above, loose matches on Subject: below --
2004-02-20 18:32 netrom Tom Vavra
2004-02-20 19:12 ` netrom Tomi Manninen
     [not found] <20130708115635.A4B233700A5@n1uro.ampr.org>
     [not found] ` <51DABEDA.8020905@junglevision.com>
     [not found]   ` <1373314487.13641.19.camel@n1uro.ampr.org>
2013-07-09  4:37     ` Netrom on kernel version 3.9.6-200 Cathryn Mataga
2013-07-09 12:05       ` Netrom Brian Rogers
2013-07-09 22:34         ` Netrom Thomas Osterried
2013-07-10  2:08           ` Netrom Cathryn Mataga
2013-07-10  2:13             ` Netrom Cathryn Mataga
2013-07-10  3:17               ` Netrom Nate Bargmann
2013-07-10  4:51                 ` Netrom Brian Rogers

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=0204141011070V.00302@unix.pa3gcu \
    --to=pa3gcu@zeelandnet.nl \
    --cc=linux-hams@vger.kernel.org \
    --cc=vk3bvp@qsl.net \
    /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