[aprssig] APRS-IS Server Port (was: APRS data via perl-to-tnc)
Lynn W. Deffenbaugh (Mr) ldeffenb at homeside.toSun Oct 2 18:43:38 UTC 2011
- Previous message: [aprssig] APRS data via perl-to-tnc
- Next message: [aprssig] APRS data via perl-to-tnc
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 10/2/2011 1:40 PM, Stephen H. Smith wrote: > One of the features that is unique (as far as I know) to UIview is > it's TCP/IP "local server". Everything UIview hears from the > attached radio/TNC --and/or-- it's Internet APRS-IS login is > replicated at a local TCP/IP server port. In turn, other APRS clients > and applications on the same LAN can connect to to the local server in > exactly the same way they would to the Internet APRS-IS. This > local server port is fully bi-directional. Other users on the LAN can > send messages either to RF (via the UIivew host's radio/TNC), --or-- > to stations on the APRS-IS --or-- to other stations on the LAN. UI-View is not unique in this area. According to the eyechart at http://www.eskimo.com/~archer/aprs_capabilities.html, in the category "Provides local APRS server socket", APRS+SA, OziAPRS, UI-View, USA PhotoMaps, and xastir provide this capability. APRSISCE/32 in development mode now also supports a downstream IS-Server port. This port supports full APRS-IS filters and also forwards packets upstream provided that the downstream client supplies a valid APRS-IS password. I need to get the current capabilities sent out to Curt for an update. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.tapr.org/pipermail/aprssig/attachments/20111002/ebe4ffc4/attachment.htm>
- Previous message: [aprssig] APRS data via perl-to-tnc
- Next message: [aprssig] APRS data via perl-to-tnc
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
