[Xastir] What am I doing????

[Chip G.]

Hi James,

Good to see you on this list (one of several we share). Do you think that is getting munged on my end or the servers? Is it Xastir or something else?

There are a few things going on here. I had the problem with Xastir the other day and regressed to the last stable release (according to CVS). I was still there when this was reported. My normal server is newengland.aprs2.net:14580. Right now I'm using rotate.aprs.net:14580. I've been using each setup for a long time with no changes. The first defaults to be on at startup. Today after the second email I rebuilt to the latest CVS release (not stable). When I started up there was an error on the first server so I went to the second (manually stopped the first). So right now I am using a different version and different server than when the problem was reported. We'll see in time if the problem still exists.

On Feb 21, 2010, at 16:52, James Ewen wrote:

> Well, actually that page is showing that you are hearing stations from all over the east coast, it does not show that you are being heard by them. Now, if you look at the raw packets that the site is using to determine what you are hearing, it tells a tale:
> 
> W4ALG-1>S5Q8,WIDE-1,A,4A,qAR,N1MIE-5:g^JR]3}
> W4ALG-1>S5Q9,IE-,IE-,A,4A,qAR,N1MIE-5:gAR]3}
> KX4NC-3>APO,X,IE-,A,4A,qAR,N1MIE-5:35.88
> WT4M-5>APU25N,D4UFD-5,qAR,N1MIE-5:<GT,LSD
> 
> All of the packets are damaged, none of the long distance packets are intact.
> 
> Here's a packet sent to the APRS-IS as seen on aprs.fi
> 
>> 2010-02-21 14:46:36 MST: VA2CMQ-3>APN8V2M,qAR,N1MIE-5:44.8N62.6#H50
>> iietrd tLc [Destination callsign is not a valid AX.25 call]
>> 
> 
> Something is getting munged up in the program, causing stations that you are seeing on your internet feed to be mangled, and fed back out the feed.



--
    Chip