Hi Curt, No luck there either... looking closer it almost looks like it's actually some extra cr/lf preceding the missing characters, but not quite sure if this is coming across well due to email auto-formatting, this is localhost telnet on the server: ------------- # Welcome to Xastir's server port, callsign: KB1MTS # javAPRSSrvr 3.12b12 18 Jul 2007 22:11:54 GMT FIRST 165.91.140.28:14580 # javAPRSSrvr 3.12b12 18 Jul 2007 22:12:14 GMT FIRST 165.91.140.28:14580 KB1ESR-1>TRSU4V,WIDE2-2:'c=l Qk/]"56}
1ESR-1>TRSU4V,WIDE2-2,KB1MTS,I:'c=l Qk/]"56} # javAPRSSrvr 3.12b12 18 Jul 2007 22:12:34 GMT FIRST 165.91.140.28:14580 KB1ESR-1>ID:KB1ESR/R N8VIM>APRS:!4240.85N/07133.99W_PHG2230/Pepperell WX station, LT1 VIM>APRS,KB1MTS,I:!4240.85N/07133.99W_PHG2230/Pepperell WX station, LT1 N8VIM>APRS,RELAY:$ULTW0000000002C21481278EFFF18883000103C500C60445000B0000 VIM>APRS,RELAY,KB1MTS,I:$ULTW0000000002C21481278EFFF18883000103C500C60445000 B0000 # javAPRSSrvr 3.12b12 18 Jul 2007 22:12:54 GMT FIRST 165.91.140.28:14580 N8VIM>APRS,KB1ESR-1*:$ULTW0000000002C21481278EFFF18883000103C500C60445000B00 00 VIM>APRS,KB1ESR-1*,KB1MTS,I:$ULTW0000000002C21481278EFFF18883000103C500C6044 5000B0000 ------------- If I disable RF->Internet igate'ing, it stops so it's definitely related to igate'ing all of sudden. I've been running Xastir for almost 1.5 years so something is different somewhere. I don't think I've updated anything in Linux on this box in probably a year other than Xastir thru the versions. -Mike KB1MTS -----Original Message----- From: Curt, WE7U [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 18, 2007 1:17 PM To: Mike Loebl Cc: xastir@xastir.org Subject: Re: [Xastir] Bad iGate messages being passed thru server port? On Wed, 18 Jul 2007, Mike Loebl wrote: > Thank you for the reply. I'll have to double check the version when I get > home, but I believe it's FC5. It had been working great up until recently > (I updated it to one of the Jun builds a couple weeks ago but not sure TBH > when it started acting up.) It's also just not the first character knocked > off, but also seeing garbage characters as well where it would be some odd > ASCII non-numeric code, several spaces and then the callsign followed by the > rest of the message. After looking at it a bit yesterday I noticed it was > intermittent, as well as always on the igated messages and never on the > incoming message. In the mean time I rewrote my app to throw out > bad/invalid callsigns. Could it be a character-set issue? Try this: export LANG=C telnet localhost 2023 -- 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!" _______________________________________________ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir