All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Hast <wchast@gmail.com>
To: linux-hams@vger.kernel.org
Subject: Re: Trying to get Ax25 running.
Date: Fri, 15 Oct 2004 19:52:12 -0700	[thread overview]
Message-ID: <620c90570410151952635eb635@mail.gmail.com> (raw)
In-Reply-To: <200410160128.i9G1Sk2M028098@yagi.h-net.msu.edu>

On Fri, 15 Oct 2004 21:28:46 -0400, Dennis Boone <drb@msu.edu> wrote:
>  > Now if I can just get the BPQKISS part running (CRC kiss)
>  >
>  > echo -e "\r\033@K1\r" > /dev/ttyUSB0
>  > modprobe ax25; modprobe kiss; modprobe mkiss
>  > /usr/sbin/kissattach -i 44.1.1.1 /dev/ttyUSB0 kiss0
>  > /usr/sbin/kissparms -p kiss0 -r 254 -s 1 -l 10 -t 100
> 
> If I understand correctly, only the mkiss utility speaks frame
> check on kiss ports.  Even if you don't need multiple ports, you
> need to run mkiss to get your checksums.  That would mean doing
> the following with the above, following Tomi's suggestion from
> earlier:
> 
>         echo -e "\r\033@K1\r" > /dev/ttyUSB0
>         modprobe ax25; modprobe kiss; modprobe mkiss
>         /usr/sbin/kissattach -i 44.1.1.1 /dev/ptyz0 kiss0
>         /usr/sbin/kissparms -p kiss0 -r 254 -s 1 -l 10 -t 100
>         /usr/sbin/mkiss -c -l /dev/ttyUSB0 /dev/ttyz0
> 
> You may need the "-s baudrate" option to mkiss as well.
> 

You were right. That worked. I am noticing one thing, when I establish
a connection that goes through a digi or two, it looks like the
frame counters get screwed up not sure what is going on, but
what I see is the I frame is sent, the far end ask for a repeate
and off it goes again, it looks ike the far end is not getting the
right frame number. If I send a new line again, the previous
line is sent on to the target.

  reply	other threads:[~2004-10-16  2:52 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
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 [this message]
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=620c90570410151952635eb635@mail.gmail.com \
    --to=wchast@gmail.com \
    --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 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.