[Xastir] Change to RELAY digipeat function

Curt, WE7U archer at eskimo.com
Wed May 4 11:30:19 EDT 2005


On Wed, 4 May 2005, Bennett, Joe wrote:

> The path information is not completely an ACII
> function. In the packet standard there are "H" and "C"
> bits that must be toggled depending on what action has
> been taken on the packet. Therefore you need to have
> bit level access to the packet in which a TNC in
> terminal mode (Serial TNC) cannot handle. The TNC can
> do this because what it receives over the air is at
> the bit level. What you see via terminal mode is the
> ASCII version. Therefore those types of interfaces
> trying to handle an ACSII packet via an off board
> means cannot support digipeating. KISS on the other
> hand, is a good example of a format that can
> participate in the digipeating function. You have the
> full ability to manipulate the source and destination
> fields as you need.

Yea.  What he said!

I think there was at least one other interface that COULD have
RELAY/WIDE1-1 digipeating enabled for it but it is currently
disabled.

Of course for command-mode TNC's, you can put in the commands to do
the type of digipeating you want in your tnc-startup files.

--
Curt, WE7U.   APRS Client Comparisons: http://www.eskimo.com/~archer
"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!"



More information about the Xastir mailing list