[aprssig] APRS protocol

[Pete Loveall AE5PL Lists]

You are correct Steve, it is not a legal packet.  But as Rob pointed out, his software is not generating the " <>:" mangling.

It is possible that the software EA1RCT-3 is using as an IGate has an issue with the TNC in monitor mode.  According to packets originated by EA1RCT-3, it is a Kantronics KPC3(+) running 3.82 firmware which means that any IGate/client software connected to that TNC would have to be using the TNC's monitor mode (if the APN382 unproto is accurate in the EA1RCT-3 packets).  One reason I only supported KISS in my IGate software although the KPC-3(+) TNCs have issues with KISS mode also.

73,

Pete Loveall AE5PL
pete at ae5pl dot net

> -----Original Message-----
> From: Steve Dimse
> Sent: Saturday, March 28, 2009 4:52 PM
> 
> It is not a legal packet. The the first character after the (first) :
> is the data type identifier. The space is not a defined packet type,
> therefore it is not a legal APRS packet. Looks like aprs-go has a
> problem.
> 
> On Mar 28, 2009, at 5:33 PM, rfinesmith at aol.com wrote:
> 
> > I am not familiar with the ": <>" portion of the below packet.  When
> > the packet is transmitted by the originating station, it is not in
> > the packet, but gets added by one of the digipeaters.  I know this,
> > because I wrote the program that generated the packet.  Is it part