Re: mkiss in ubuntu kernels?

Alan Crosswell <alan@xxxxxxxxxxxx> · Thu, 10 Sep 2009 22:39:55 -0400

You only kissattach once;  if the TNC supports mkiss then the port is  

encoded in the kiss header for each packet.

/a

On Sep 10, 2009, at 6:44 PM, Collin Hockey <hockeyc@xxxxxxxxx> wrote:

Hi everyone, and thanks in advance for any help.

I've been working for the past several days on getting a Kantronics
9612 paired with an iCom IC-910 for packet communication over KISS
working using the linux AX.25 stack. I have successfully set up
kissattach and related utilities to be able to send data back and
forth at 1200 baud.

I also need to communicate at 9600 baud. For the Kantronics TNC, this
requires talking to the radio over Port 2. My current understanding is
that packet routing is done using parts of the KISS protocol and that
this is achieved by using mkiss to split the physical serial port into
two pseudo ttys, which I can then use kissattach on separately to talk
to each port.

All of the documentation I have been able to find though assumes the
old style psuedo-tty setup, where master and slave pairs are numbered,
and plenty are pre-loaded by the kernel for use by user programs.
However, at least in my kernel (2.6.28), the client program is
supposed to request the single pseudo-tty master file, and the kernel
creates a new slave for each connection. There tends to be a pile of
these in my pseudo-tty slave directory, so I never know which one to
connect to. We do need to automate and script most of these
connections, so I do need to reliably be able to tell which slave tty
I need to connect to.

Hopefully I've explained the problem well enough to be understood, and
I would appreciate any help or suggestions you might have.

Thanks again,
Collin Hockey
--

To unsubscribe from this list: send the line "unsubscribe linux- 

hams" in

the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html