Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: "J. Lance Cotton" <joe@lightningflash.net>
To: Wilbert Knol <zl2bsj@zl2tze.ath.cx>, linux-hams@vger.kernel.org
Subject: Re: XASTIR cross-port digipeating?
Date: Sat, 19 Jul 2003 16:38:28 -0500	[thread overview]
Message-ID: <200307191638.28825.joe@lightningflash.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0307181818460.5497-100000@zl2bsj.ampr.org>

On Saturday 19 July 2003 01:35, Wilbert Knol wrote:
> Thanks for reading this message. I am running (amongst other things)
> XASTIR on a small, two-port packet system. Is it possible to get XASTIR to
> digipeat on one port APRS broadcasts heard on another? Or do I need the
> separate 'aprsdigi' mentioned recently? (I have same-port digipeating
> working successfully)

Xastir doesn't digipeat, except for RELAY digipeating that home stations 
should do. You would need aprsdigi or digi_ned to do any further digipeating.

> Similarly, are there any Internet based APRS servers (preferably in
> VK/ZL). Will XASTIR re-transmit on any of the RF ports broadcasts heard on
> the Internet interface, and vice versa?

What is meant by "broadcasts"? Right now, Xastir will only dump from INET->RF 
messages intended for stations heard locally, their related position packets, 
and any NWS (US National Weather Service) packets that match callsigns listed 
in ~/.xastir/data/nws-stations.txt (only NWS weather report packets are gated 
to RF, so putting any callsign in nws-stations.txt won't cause Xastir to gate 
any matching packet).

> A separate question: XASTIR 1.2.1 complains about NUM/SCROLL/CAPSLOCK
> being engaged when I right-click the desktop. My notebook keyboard only
> has a CAPSLOCK, and it is off. Is there a work-around for this?

Xastir doesn't yet do the right filtering to determine if key modifiers like 
those listed above are enabled, which in some cases (with LessTif, I think) 
causes Xastir not to process those clicks. Look in the menu 
File->Configure->Defaults and un-check "Warn if modifier keys". That will 
disable the message.

> Wilbert, ZL2BSJ

-- 
J. Lance Cotton, KJ5O
joe@lightningflash.net
Three Step Plan: 1. Take over the world. 2. Get a lot of cookies. 3. Eat the 
cookies.

  reply	other threads:[~2003-07-19 21:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-19  6:35 XASTIR cross-port digipeating? Wilbert Knol
2003-07-19 21:38 ` J. Lance Cotton [this message]
2003-07-20  2:49   ` Wilbert Knol
2003-07-21 16:40     ` Curt Mills, WE7U
     [not found] <200307200851.47609.joe@lightningflash.net>
2003-07-21  9:54 ` Wilbert Knol
2003-07-21 16:42   ` Curt Mills, WE7U
2003-07-22 11:43     ` Wilbert Knol
2003-07-22 20:20       ` Curt Mills, WE7U
2003-07-23  5:15         ` Wilbert Knol

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=200307191638.28825.joe@lightningflash.net \
    --to=joe@lightningflash.net \
    --cc=linux-hams@vger.kernel.org \
    --cc=zl2bsj@zl2tze.ath.cx \
    /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