[aprssig] APRX aprs-is filtering

Keith VE7GDH ve7gdh at rac.ca
Fri Aug 6 21:56:57 EDT 2010


Pete AE5PL wrote...

> The javAPRSSrvr sysops (aprs.net core servers and aprs2.net servers)
> use port 14580 as a user-defined filter port (no default filter). If no
> filter is applied by the client, it functions properly for IGates (maintains
> a last-heard list for the client and performs proper message and related
> posit passing in addition to any messages and related posits for the
> logged in client). A filter is not needed for proper IGate operation and
> will make your IGate software use much less resources than a full feed
> simply because there will be very few packets your IGate will have to process.

Thanks for the clarification. My understanding in the past was that some
servers applied a default filter when none was specified. I agree that not
using a filter would be best for an IGate that is unattended or at least when
there won't be anyone sitting there looking at the screen. I think I was reading
more into Jaye's comments than he really said. I had assumed that he meant
that he was getting a feed of stations 200-300 km from his location without
specifying a filter. I should have read his comments more carefully!

> Adding filters is best suited for GUI clients because you want to see
> more than just what you might see on RF. Standalone and non-GUI IGates
> are best used on a user-defined port as you describe (port 14580) with
> no filter specified.  This will provide proper IGate operation while
> minimizing impact on your system and your bandwidth to the Internet.

I actually apply a filter to my IGate because I am interested in what is
going on around me when I'm sitting at the keyboard on that machine.
However, on my laptop, I just see what I'm receiving on RF, with a
few exceptions. It's a good way of seeing who is using excessive
paths... digis as well as users.

73 es cul - Keith VE7GDH
--
"I may be lost, but I know exactly where I am!"




More information about the aprssig mailing list