[aprssig] Excessive beacons/connects by "smart" IS clients

[Keith VE7GDH]

Lynn KJ4ERJ wrote...

> If there's an APRS-IS client out there that is connecting, beaconing,
> and disconnecting, then I would consider that to be a busted client
> which needs to be fixed, regardless of the beacon frequency.

It isn't your typical APRS client, but the script that generates the
APRS IRLP status script connects, sends an object to the APRS-IS
and then disconnects. It does this each time the node status changes,
or at a rate set by the node operator via a cron job. For timed
"beacons" of the script, I recommend every 10 minutes so when
they get gated to RF (the ideal situation) they don't go more often
than that.

Servers all over the world (if the operator used the then-recommended
rotate.aprs2.net:14580) ended up with dozens or scores of connections
from the same IRLP node with earlier versions of the script. The
current script is better behaved.

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