Order Tray | Contact Us | Home | SIG Lists

[aprssig] Gating Objects from Internet to RF (fina?l)

Chris Kantarjiev cak at dimebank.com
Wed Jul 22 23:32:26 UTC 2009

> But I agree that the full load is a show-stopper.  We have got
> to find a more regional way to distribute this.  Note that this
> is WORLDWIDE Echolink nodes.  Yet any one Igate only needs to
> see ONLY what is within his local area.
> Yes, there are ways to solve this by changing Igate code, and
> changing Echolink, and channging the APRS-IS, but NONE OF THAT
> IS GOING TO HAPPEN.  SO, we either find a way to do this with
> what we have, or it aint gonng work.

How about ... rather than pushing the data out to Igate through
APRS-IS, have a new server that provides a "port 14580 compatible" 
stream of Echolink node status updates. Then my igate could 
connect to it with a suitable filter expression (as well as connecting
to the core or tier2 server) and send it to RF.

This could run on the Echolink core, since they're the ones who
should be interested in providing the data.

aprs4r will support multiple IP connections; I don't know about
other igate implementations.

73 de chris K6DBG

More information about the aprssig mailing list