Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: "Gérard / F6FGZ" <f6fgz@free.fr>
To: Linux-Hams <linux-hams@vger.kernel.org>
Subject: Re: Trying to get Ax25 running.
Date: Fri, 15 Oct 2004 19:59:43 +0200	[thread overview]
Message-ID: <4170100F.F5F43579@free.fr> (raw)
In-Reply-To: 200410151737.i9FHbiZW031272@yagi.h-net.msu.edu

Dennis Boone a écrit :

>         mkiss -c -l -s 19200 /dev/ttyS0 /dev/ptyz0 /dev/ptyz1
>         kissattach /dev/ptyz0 hfport 44.135.96.242
>         kissattach /dev/ptyz0 vhfport 44.135.96.243

I correct your memory ;-)
kissattach /dev/ttyz0 hfport 44.135.96.242
kissattach /dev/ttyz1 vhfport 44.135.96.243

It is important to have ptyxx from one side corresponding to ttyxx on the other
side.
From /usr/src/linux/Documentation/devices.txt:
  2 char        Pseudo-TTY masters
                  0 = /dev/ptyp0        First PTY master
                  1 = /dev/ptyp1        Second PTY master
                    ...
                255 = /dev/ptyef        256th PTY master

                Pseudo-tty's are named as follows:
                * Masters are "pty", slaves are "tty";
                * the fourth letter is one of pqrstuvwxyzabcde indicating
                  the 1st through 16th series of 16 pseudo-ttys each, and
                * the fifth letter is one of 0123456789abcdef indicating
                  the position within the series.

Choose some pairs !


--
73 Gérard F6FGZ
-
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:[~2004-10-15 17:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <620c9057041013094421cbf279@mail.gmail.com>
     [not found] ` <20041014025505.66938.qmail@web40824.mail.yahoo.com>
2004-10-14 13:00   ` Trying to get Ax25 running Chuck Hast
2004-10-14 13:13     ` Dennis Boone
2004-10-15 16:57       ` Chuck Hast
2004-10-15 17:15         ` Tomi Manninen
2004-10-15 17:37         ` Dennis Boone
2004-10-15 17:59           ` Gérard / F6FGZ [this message]
2004-10-15 18:26             ` Tomi Manninen
2004-10-15 18:33               ` Pontus Falk
2004-10-15 18:53                 ` Tomi Manninen
2004-10-15 19:22                   ` Curt, WE7U
2004-10-15 19:55                     ` Chuck Hast
2004-10-15 23:18                       ` Chuck Hast
2004-10-16  1:15                         ` Chuck Hast
2004-10-16  1:28                           ` Dennis Boone
2004-10-16  2:52                             ` Chuck Hast
2004-10-16  3:40                               ` Dennis Boone
2004-10-16 12:45                             ` Tomi Manninen
2004-10-16 13:16                               ` Chuck Hast
2004-10-16 13:52                                 ` Tomi Manninen
2004-10-16 15:08                                   ` Chuck Hast
     [not found]           ` <41700FDB.383C6084@free.fr>
2004-10-15 18:02             ` Dennis Boone
2004-10-13  2:40 Ron
2004-10-14  1:55 ` Chuck Hast
  -- strict thread matches above, loose matches on Subject: below --
2004-10-12 13:32 Chuck Hast
2004-10-12 13:41 ` Jeroen Vreeken

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=4170100F.F5F43579@free.fr \
    --to=f6fgz@free.fr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox