[aprssig] Beaconing repeaters as stations?

[Andrew P.]

Pete,

I shoild mention that I got this via an APRS-IS filtered client feed, not over RF.

Now you've got me looking into whether this is a bug in my client's APRS-IS connection code. I'll check that before I go bother N3HF. It just seems odd because it's a station position report message instead of an object report. I am getting APRS-IS object reports for other repeaters in that area, so it's not a blanket typo in my code.

Does anybody else see this with other clients (UIView, APRSISCE, etc.)?

Andrew Pavlin, KA2DDO

------Original Message------
From: Pete Loveall AE5PL Lists
To: aprssig at tapr.org
Sent: Feb 6, 2012 4:28 PM
Subject: Re: [aprssig] Beaconing repeaters as stations?


Something is definitely amiss.  There are two major issues here: the invalid punctuation in the callsign and the IGate is gating a q construct to RF.  While 146.82- is obviously not a callsign, it also does not adhere to the rules for AX.25 or APRS-IS callsign composition of alphanumeric characters with a maximum of on hyphen followed by a maximum of 2 alphanumeric characters for a maximum of 9 characters and is therefore invalid.  The third-party header does not conform to APRS specifications (q constructs are never seen on RF and the only valid construct would be ",TCPIP,N3HF-5*:" if being gated to RF by N3HF-5).

I recommend that you contact N3HF and determine if his software is generating these invalid packets.  If it is, I would be happy to work with him -off list- to resolve these issues.

73,

Pete Loveall AE5PL
pete at ae5pl dot net

> -----Original Message-----
> From: Andrew P.
> Sent: Monday, February 06, 2012 1:30 PM
> 
> The actual record is:
> 
> }146.82->APOBJ,qAR,N3HF-5:!3830.10N/07544.13Wr PL 156.7 Net 9PM M.
> Salisbury MD
_______________________________________________
aprssig mailing list
aprssig at tapr.org
https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig


Sent from my Verizon Wireless BlackBerry