[aprssig] Creating and maintaining a repeater object (RANT)

Robert Bruninga bruninga at usna.edu
Sat Sep 22 09:42:42 EDT 2012

Amen.  Landed at Atlanta Airport, turned on the APRS HT and first packet
received was for the "local repeater" 145.xx.  Hit the tune button and
within seconds would have been in contact with other local APRS ops...

NOT!  The repeater did not respond.  I went to the object screen and
noticed that the repeater was over 100 miles away!

This is NOT WHAT these repeater objects are for.  They are supposed to be
only sourced LOCALLY and only via DIRECT paths so that they are only
receivable only where they CAN BE USED.  Otherwise they are spam.

In the next few minutes, another repeater came in.  Again, no joy.  Checked
range, and again, it was over 100 miles away.  Checked the source screen
and they were being sourced by a home station via 2 HOPS over 88 miles
away.  In Georgia, 2 hops can SPAM almost 50% of the entire state.

Please folks. Repeater objects are not supposed to be spam.  Do it right.

Every KPC3 digi can source up to 3 or even 4 of these objects and can have
their own path (ONLY DIRECT) and ONLY to their footprint.  Other digis can
similarly source such objects.

We are a community.  Lets work like a community.  Get with the local digi
sysop and lets get this done right.

If you insist on sourcing these at home (and adding collisions and spam to
the local network) then use no more than one HOP and only via the SPECIFIC
CALLSIGN of the digi that best matches the area of coerage.

See http://aprs.org/localinfo.html


On Fri, Sep 21, 2012 at 5:06 PM, Sander Pool <sander_pool at pobox.com> wrote:

> Hi,
> almost two weeks ago I was hiking in Point Reyes National Seashore and
> received two repeater objects that my D72 would happily tune to. Very. One
> repeater I could hit, the other one I could not. I've always been a fan of
> repeater objects as it solves the age old problem of "I'm new here, what
> repeater should I listen to". None of the repeaters around here have
> repeater objects. I'd like to change that. The only way I know how to do
> this at the moment is to have create these objects in APRSIS/32 and have it
> run all the time so it injects these objects into the APRSIS servers for
> igates to pick up.
> This seems a bit cumbersome. Is there no way to tell some service
> somewhere what objects I have and how often they should announce
> themselves? If not then is this one of the reasons repeater objects aren't
> widely used? Most of the repeaters I know around here do not have a
> matching igate that could inject these objects.
> I've poked in the archives but didn't really find anything related.
> Perhaps I didn't look correctly or (likely) I don't understand at all how
> this works. Please correct me in that case.
> Thanks,
>     Sander W1SOP
> ______________________________**_________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/**mailman/listinfo/aprssig<https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20120922/7cbf0e1e/attachment.html>

More information about the aprssig mailing list