[aprssig] xastir bug?
russo at bogodyn.org
Fri Jan 31 15:02:02 EST 2014
On Fri, Jan 31, 2014 at 01:48:16PM -0600, we recorded a bogon-computron collision of the <hamlists at ametx.com> flavor, containing:
> Not Xastir, I believe it is aprsx.
Correct. Xastir's TOCALL is "APX..." not "APRX.."
> > -----Original Message-----
> > From: Steve Dimse
> > Sent: Friday, January 31, 2014 1:46 PM
> > To: TAPR APRS Mailing List
> > Subject: [aprssig] xastir bug?
> > Here is one for all you xastir guys:
> > A few weeks ago I created a monitor tool to keep an eye on my parser, it
> > counts the number of raw packets processed every minute and then gives
> > me a graph. I saw periodic outbursts that made no sense, so I went hunting. I
> > identified it as thousands of telemetry packets like
> > YB6HJE-3>APRX28,TCPIP*,qAC,MYAPRS-1:T#987,0.0,0.1,0.0,0.0,0.0,00000000
> > The count increased with each packet. A flood of these (about 20,000 over
> aprssig mailing list
> aprssig at tapr.org
Tom Russo KM5VY SAR502 DM64ux http://www.swcp.com/~russo/
Tijeras, NM QRPL#1592 K2#398 SOC#236 http://kevan.org/brain.cgi?DDTNM
echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m]
More information about the aprssig