[Xastir] Extra data

[Curt, WE7U]

On Mon, 4 Apr 2005, Tapio Sokura wrote:

> I'm using KISS (TM-D700) and Xastir is from CVS (compiled March 3rd). I
> ran into this when writing a small igate application. I noticed that
> some packets that looked identical to the eye weren't flagged as
> duplicates. I looked more closely and noticed there was extra whitespace
> at the end of those packets. Now I just ignore all trailing whitespace
> in duplicate detection.
>
> I haven't really looked at the KISS packets coming in from the TM-D700,
> but rather looked at the packets as they come back via APRS-IS (I have
> Xastir set up to be an igate) via another TCP connection. Those packets
> arriving via APRS-IS that have my Xastir's callsign in the digipath
> often contain an extra whitespace character at the end of the packet.
> Often I also see the same packet gated to APRS-IS via some other igate
> and that packet doesn't have the extra space at the end. I guess it is
> also possible that the packets contain whitespace in the RF form as well
> and it is the other igate that is stripping away extra trailing
> whitespace in a packet before passing the packet onto APRS-IS.

Is there an easy way for you to investigate that last possibility?
I think there are some debug fprintf's in interface.c that can be
used to see the hex characters in an incoming KISS packet.  That
should prove it one way or another.

--
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!"