[aprssig] Maximum APRS Packet Lengths and 3rd party use?
scott23192 at gmail.com
Wed Nov 30 16:29:30 CST 2016
Thanks a million, Pete. That does help very much and I apologize for
taking the group's time.
But when I saw a reference to the filtering of a pattern, I just wanted to
inquire as to whether I was doing everything possible to be setup in the
most correct fashion -- but of course from lack of familiarity I was not on
the correct topic.
Thanks again & all the best to everyone.
On Wed, Nov 30, 2016 at 5:19 PM, Pete Loveall AE5PL Lists <
hamlists at ametx.com> wrote:
> Grr, once again caught by the default Reply action to go directly to
> Hi Scott,
> The blocking we are talking about is done in the IGate software and should
> not be configurable by the user. The server-side filters do not "filter"
> any packets going -to- the server and the IGates should be making their own
> decisions regarding what packets are gated to RF (server-side filters are
> -not- to be relied upon directly for this decision process as the server
> will provide more packets than should be gated to RF; this decision process
> is an IGate internal process).
> This thread is addressing software author concerns (maximum packet length,
> third-party packet formatting and blocking, etc.). In general, these
> should not be configurable by the user, novice or long-time expert. ;-)
> Hope this helps.
> Pete Loveall AE5PL
> pete at ae5pl dot net
> > -----Original Message-----
> > From: Scott
> > Sent: Wednesday, November 30, 2016 2:03 PM
> > Subject: Re: [aprssig] Maximum APRS Packet Lengths and 3rd party use?
> > As a novice, could I trouble the group for the correct filter syntax to
> > block *TCPIP* from being iGated?
> > And while we're at it, if there are any other filters that should
> > be included in any iGate setup, those would of course be welcome as well.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the aprssig