All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David A. Ranch" <dranch@trinnet.net>
To: Collin Hockey <hockeyc@umich.edu>
Cc: Matti Aarnio <matti.aarnio@zmailer.org>,
	"Curt, WE7U" <archer@eskimo.com>,
	Alan Crosswell <alan@columbia.edu>,
	"linux-hams@vger.kernel.org" <linux-hams@vger.kernel.org>
Subject: Re: mkiss in ubuntu kernels?
Date: Sun, 13 Sep 2009 23:36:17 -0700	[thread overview]
Message-ID: <4AADE461.6000805@trinnet.net> (raw)
In-Reply-To: <3013ad3b0909130948y348b011ej712d5713bdc997d0@mail.gmail.com>


I hope those patches make it upstream and into the main kernel sources.
 Until that day comes, I had similar problems for bringing up a JNOS
setup.  I hacked it in using net2kiss and some kludges in my init scripts:


   #start net2kiss
   PTSRPORT=`/usr/sbin/net2kiss -i sm1 /dev/ptmx &`
   PTSPORT=`echo $PTSRPORT | awk -F / '{print $4}'`
   echo -en "[net2kiss on /dev/pts/$PTSPORT ] "


Hope this helps someone

--David, KI6ZHD


> These improvements to mkiss and kissattach are great. After a few
> minutes fussing with the install and getting my other apps reading the
> right axports file, everything is working wonderfully. Thanks a ton
> everyone, hopefully someday soon I'll be able to answer some questions
> as well :-)
> 
> Collin
> 
> On Fri, Sep 11, 2009 at 3:38 AM, Matti Aarnio <matti.aarnio@zmailer.org> wrote:
>> On Fri, Sep 11, 2009 at 01:10:01AM -0400, Collin Hockey wrote:
>>> Hi Curt,
>>>
>>> Yes, I did go through that tutorial. It got me going to the point
>>> where I am now :)
>>>
>>> I think I understand how mkiss works, but my problem is with the newer
>>> linux kernel pseudo tty setup. Mkiss doesn't report which slave tty it
>>> has connected each port to because it was designed at a time when
>>> there were a bunch of matched pairs (ptm0 and pts0 for instance, m
>>> being for master and s being for slave), whereas now, a program opens
>>> the single master pseudo tty and it gets a new slave tty from the OS.
>>> I'm trying to find a reliable way to figure out which tty mkiss has
>>> connected each port to.
>>>
>>> Perhaps I'm barking completely up the wrong tree, but that's my
>>> understanding of it anyway.
>>>
>>> Thanks a lot for your answers, they're definitely helping me get
>>> closer to a solution.
>> You are not at wrong tree, that program is from era before present
>> pseudo-tty system, when the stupid way it does things did work.
>>
>> mkiss users are very rare indeed...
>>
>>
>> I have rewritten mkiss a bit to use modern pty:s, and it is in this
>> package:
>>
>>  http://ham.zmailer.org/oh2mqk/libax25/ax25-tools-0.0.9-3.tar.gz
>>
>> but to use it, you will need also my  libax25  from same directory.
>> After you take it into use, the information on HOWTO is plain wrong.
>> See  "man mkiss".   The mkiss will also need associated kissattach.
>>
>> I did also rework the  kissattach   so that you do not need to set
>> IP address on AX.25 interface.
>>
>> My libax25 changes have made it to  cvs@cvs.linux-ax25.org:/home/ax25-cvs
>> but tools changes are still in the pipeline..  Apparently I have to push
>> at them again.
>>
>>> Collin Hockey
>>   73 de Matti, OH2MQK
>>
>>
>>> On Thu, Sep 10, 2009 at 11:51 PM, Curt, WE7U <archer@eskimo.com> wrote:
>>>> On Thu, 10 Sep 2009, Collin Hockey wrote:
>>>>
>>>>> I was looking at the information in the mkiss man page
>>>>> (http://linux.die.net/man/8/mkiss), it seems to claim to be the one
>>>>> attached to the physical serial port, routing KISS frames through two
>>>>> or more pseudo ttys whose slave ends are attached with kissattach to
>>>>> separate ax.25 network interfaces.
>>>> Did you look up the Linux AX.25 HOWTO document?  That may give you
>>>> additional practical info for setting up MKISS.
>>>>
>>>> --
>>>> Curt, WE7U.                         <http://www.eskimo.com/~archer>
>>>>   APRS:  Where it's at!                    <http://www.xastir.org>
>>>>  Lotto:  A tax on people who are bad at math. - unknown
>>>> Windows:  Microsoft's tax on computer illiterates. - WE7U.
>>>> The world DOES revolve around me:  I picked the coordinate system!"
>>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
>>> the body of a message to majordomo@vger.kernel.org
>>> 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@vger.kernel.org
>> 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@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2009-09-14  6:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-10 22:44 mkiss in ubuntu kernels? Collin Hockey
2009-09-11  2:39 ` Alan Crosswell
2009-09-11  2:48   ` Collin Hockey
2009-09-11  3:25     ` Alan Crosswell
2009-09-11  3:51     ` Curt, WE7U
2009-09-11  5:10       ` Collin Hockey
2009-09-11  7:38         ` Matti Aarnio
2009-09-13 16:48           ` Collin Hockey
2009-09-14  6:36             ` David A. Ranch [this message]

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=4AADE461.6000805@trinnet.net \
    --to=dranch@trinnet.net \
    --cc=alan@columbia.edu \
    --cc=archer@eskimo.com \
    --cc=hockeyc@umich.edu \
    --cc=linux-hams@vger.kernel.org \
    --cc=matti.aarnio@zmailer.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.