[aprssig] OpenTRAC vs. UIView I-gates
scott at opentrac.org
Wed Jan 29 11:59:10 CST 2014
Last time we had a discussion about OpenTRAC on 144.39, it turned into a
week-long blowup that had me and Bob posting about 50 times a day and a
bunch of subscribers bailed from the SIG - including Bob, for a bit.
Being self-employed now I have limited time to devote to flame wars, so
I'm just going to say for now that in my opinion a client should only
*originate* OpenTRAC packets by explicit user choice. Network
infrastructure should probably by default pass all traffic unless
filtering is specifically requested by the operator.
IGate operators should always keep in mind that PASSALL should be off,
and if they don't have the option of using KISS or a similar protocol,
they need to make sure their TNC is set properly to only pass plain text
On 1/29/2014 9:44 AM, Andrew P. wrote:
> Greetings, all.
> It looks like I may have stirred up a hornet's nest. My APRS client YAAC
> also supports the OpenTRAC protocol, but it seems like some APRS I-gates
> don't like receiving OpenTRAC packets. Specifically, I have noticed
> several UIView I-gates forwarding messages of the format
> [ PID 77 ]
> instead of ignoring the packets of the wrong protocol ID entirely. I
> have confirmed this with an I-gate near my home (and the YAAC
> development server within).
> Is this going to be a problem? Do I need to fix YAAC to prevent sending
> both APRS and OpenTRAC out the same RF port?
> Andrew Pavlin, KA2DDO
> aprssig mailing list
> aprssig at tapr.org
More information about the aprssig