From: "Ian McLaughlin" <ian@platinum.net>
To: M Taylor <mctylr@privacy.nb.ca>
Cc: linux-hams@vger.kernel.org
Subject: Re: KPC 9612+ and kissattach
Date: Mon, 2 Sep 2002 20:05:00 -0700 [thread overview]
Message-ID: <001201c252f6$b12639a0$fe5d34d1@platinum.net> (raw)
In-Reply-To: 20020903032949.A17023@pull.privacy.nb.ca
Thanks for the quick response. I did consult the HOWTO, and my commands are
based on the ones you listed. I'm only using the 9600 baud port, so I only
have a kissattach line for the second port. This is not working, however.
What I wanted to confirm is that I'm correctly putting the 9612+ into kiss
mode. I'm using a factory default config, with MYCALL set, and then INTFACE
KISS. Is this correct? All of my configs work just fine connecting to the
TNC in a Kenwood D7A handheld, but not the KPC9612.
Thanks.
----- Original Message -----
From: "M Taylor" <mctylr@privacy.nb.ca>
To: "Ian McLaughlin" <ian@platinum.net>
Cc: <linux-hams@vger.kernel.org>
Sent: Monday, September 02, 2002 7:29 PM
Subject: Re: KPC 9612+ and kissattach
> On Mon, Sep 02, 2002 at 04:01:58PM -0700, Ian McLaughlin wrote:
> > Hello All,
> > I have searched the archives, but cannot find a solution to my
problem.
> >
> > 2 machines trying to talk to each other. One seems to work, one
doesn't.
> >
> > Software config the same on each one - RedHat 7.3 with the ax25 libs and
> > utils installed. Kernel recompiled to support ax25 and kiss devices.
> >
> > The machine that works is using a Kenwood D7A radio at 9600 baud in kiss
> > mode. kissattach seems to work, and if I ping the other end of the
radio
> > link, I get the radio going in to transmit mode in sync with the ping
> > packets.
> >
> > The other end, however is a different story. It's a Kantronics KPC
9612+,
> > with no radio on the first port, and a 9600 baud radio on the second
port.
> > Minicom works fine, and I can connect to the tnc and send and receive
data
> > on the TNC. My problem appears to be with mkiss. Am I correct in
assuming
> > that I need to run mkiss because the KPC 9612 is a dual-port TNC? I am
> > running the foillowing commands:
> >
> > mkiss -s 9600 /dev/ttyS0 /dev/ptyq0 /dev/ptyq1
> > kissattach /dev/ttyq1 RADIO 172.16.0.2
> >
> > The commands are accepted, and a network device is create, but if I
ping, I
> > get no radio traffic at all.
>
> Check the AX25-HOWTO section 6.1.1.1 ("Configuring for Dual Port TNC's")
> <http://www.tldp.org/HOWTO/AX25-HOWTO/x495.html>
>
> (the short form:)
>
> # /usr/sbin/mkiss -s 9600 /dev/ttyS0 /dev/ptyq0 /dev/ptyq1
> # /usr/sbin/kissattach /dev/ttyq0 port1 44.135.96.242
> # /usr/sbin/kissattach /dev/ttyq1 port2 44.135.96.242
>
> -ve1mct
>
next prev parent reply other threads:[~2002-09-03 3:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-02 23:01 KPC 9612+ and kissattach Ian McLaughlin
2002-09-03 2:29 ` M Taylor
2002-09-03 3:05 ` Ian McLaughlin [this message]
2002-09-03 5:33 ` Wilson G. Hein
2002-09-03 6:07 ` Stewart Wilkinson
2002-09-03 19:08 ` Mike Fenske
2002-09-03 19:47 ` Stewart Wilkinson
-- strict thread matches above, loose matches on Subject: below --
2002-09-03 19:16 Mike Fenske
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='001201c252f6$b12639a0$fe5d34d1@platinum.net' \
--to=ian@platinum.net \
--cc=linux-hams@vger.kernel.org \
--cc=mctylr@privacy.nb.ca \
/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.