[aprssig] Blocking and filters
Lynn W. Deffenbaugh (Mr)
ldeffenb at homeside.to
Tue Jan 14 18:26:52 CST 2014
So that's another way of saying that you can't block messages addressed
to your station no matter who they come from, right? Just trying to
provide a clear, unambiguous answer to the original question.
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
On 1/14/2014 6:45 PM, Pete Loveall AE5PL Lists wrote:
> Server-side filters are -additive- (described before on this SIG as "subscriptions"). A filter (either negative or positive) is in -addition- to the standard packets that are passed to the client by the port. Filter ports, by definition, pass all message packets addressed to the client, all message packets addressed to stations the client has "recently" gated to APRS-IS, associated posits (associated with the prior 2 categories of messages), and packets seen inserted directly to APRS-IS by stations "recently" gated to APRS-IS by the client (helps client not clutter RF with gated messages for other IGates). You cannot "block" any of these packets.
> Hope this helps clarify.
> Pete Loveall AE5PL
> pete at ae5pl dot net
>> -----Original Message-----
>> From: Patrick Wood
>> Sent: Tuesday, January 14, 2014 3:11 PM
>> Looking for clarification for the application of blocks to the aprsis feed. I
>> added a -b/VE3SLM* block to my filter which should block all messages from
>> that call sign to my client. However what I'm seeing is that indirect data
>> seems to be blocked so I do not see position packets, however direct
>> messages go through the block and I do receive the messages.
> aprssig mailing list
> aprssig at tapr.org
More information about the aprssig