From: Thomas Osterried <thomas@osterried.de>
To: "Robert Steinhäußer" <robert@steinhaeusser.com>
Cc: linux-hams@vger.kernel.org
Subject: Re: Strange AXIP / AX25 Frames
Date: Wed, 8 Jan 2003 01:01:58 +0100 [thread overview]
Message-ID: <20030108000158.GA25575@osterried.de> (raw)
In-Reply-To: <200301071516.56542.robert@steinhaeusser.com>
> > > 9: fm [invalid] to [invalid] via 90gGB7-2* M0GB7-3* [invalid] [invalid]*
> > > [invalid] gGB7BM 0GB7CR [invalid] ctl [invalid]0^ [DAMA]
> >
> > Kernel 2.4.20 & latest AX25 apps, lib, tools. TNC-2 in KISS-mode.
>
> KISS mode normally has no checksumming, so any stray HF will mess up the data
> on your serial line between TNC and PC. Use shielded cabling and SMACK or
> RMNC-CRC-KISS or (even better for numerous reasons) 6PACK.
the initial question was for a problem with axip.
because axip frames have a checksum, these errors should not occur.
kiss: there are some checksum variants for kiss. one is crc-rmnc, the
other is smack. for crc-cmnc, there's no tnc software available. on the
other hand, smack is not implemented in the linux kernel kiss module.
considering this, 6pack is the better choice.
back to the problem. kernel 2.4.20 is quite new. it would be great if
you could test, if it is
- a kernel problem
- a problem with libax25 / ax25tools
- listen does not exactly match with the libax25 library - a recompile
may help
whil still running kernel-2.4.19, i could say nothing abt 2.4.20 issuses,
but if i remember correctly, there were only some scc driver fixes.
73,
- thomas dl9sau
prev parent reply other threads:[~2003-01-08 0:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-06 22:45 Strange AXIP / AX25 Frames Stewart Wilkinson
2003-01-07 9:12 ` Wilbert Knol
2003-01-07 14:16 ` Robert Steinhäußer
2003-01-08 0:01 ` Thomas Osterried [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=20030108000158.GA25575@osterried.de \
--to=thomas@osterried.de \
--cc=linux-hams@vger.kernel.org \
--cc=robert@steinhaeusser.com \
/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.