[aprssig] Satellite server test

AE5PL Lists HamLists at ametx.com
Mon Nov 26 16:12:21 EST 2007


You can.  Feel free to set it up.  Be advised as other have already
stated: if someone sets up an IGate to connect to your isolated
"satellite server", no gated packets will make it to APRS-IS.  This is
what Steve, et. al. were commenting on.

SatGates, as a rule, have been implemented over the years to let earth
APRS stations be seen by others via the Internet when those earth
stations are being digipeated by the satellite.  The individual
satellite operators use other software and networks to gather their
telemetry.  Satellite-generated APRS bulletins, position reports, etc.
are really only of use to those receiving the satellite directly.  There
are many other, more effective ways of getting information out to the GP
than by trying to gate APRS packets originating from the satellite to
APRS-IS.  Also, as a rule, SatGates are unidirectional (satellite to
APRS-IS) to prevent unintended collisions by multiple IGates gating to
the satellite.

Hope this helps clarify.

73,

Pete Loveall AE5PL
pete at ae5pl.net

> -----Original Message-----
> From: Andrew Rich
> Posted At: Monday, November 26, 2007 2:51 PM
> Posted To: APRS SIG
> Conversation: [aprssig] Satellite server test
> Subject: RE: [aprssig] Satellite server test
> 
> Why cant we have a seperate satellite server?
> 
> 
>
-----------------------------------------------------------------------
> -----
> Andrew Rich VK4TEC
> vk4tec at people.net.au <mailto:vk4tec at people.net.au>
> http://www.tech-software.net
> 
> 
> 
> 
> -----Original Message-----
> From: aprssig-bounces at lists.tapr.org
> [mailto:aprssig-bounces at lists.tapr.org]On Behalf Of AE5PL Lists
> Sent: Monday, 26 November 2007 11:24 PM
> To: TAPR APRS Mailing List
> Subject: RE: [aprssig] Satellite server test
> 
> 
> > -----Original Message-----
> > From: Steve Dimse
> > Posted At: Monday, November 26, 2007 7:01 AM
> > Subject: Re: [aprssig] Satellite server test
> >
> > Sorry, I was repeating what Bob had said. I completely support the
> > intent of this, but why are the beacons being filtered?
> 
> Because javAPRSSrvr is not packet filtering per the original design
> requirements.  The only way to prevent the telemetry from propagating
> throughout APRS-IS was for the individual server owners to block the
> satellite's callsign-SSIDs.  Had they used a separate callsign-SSID
for
> non-streamed APRS-specific packets, then this would not be an issue
> since only the streaming callsign-SSID would be blocked.
> 
> When I was made aware of the situation with GO-32, I tried to work out
> that type of solution with Bob but I was told its operation was
> basically cast in stone due to the age of the equipment and limited
> configuration capabilities.  I am not familiar with the GO-32 hardware
> so I am taking Bob at his word on that.  Once the operation mode of
the
> satellite was confirmed and that hams were using standard IGate
> software
> to gate to APRS-IS, I informed the server owners.
> 
> There are now hundreds of javAPRSSrvrs in use world-wide and so
> ensuring
> any type of hard-coded changes to it for every special case that comes
> up does not seem reasonable or doable.  Even you proudly pointed out
> that you are using an ancient version of javAPRSSrvr, so depending on
> upgrades to occur across the board or asking the core server sysops to
> change out their systems every time a special case is thought up only
> threatens the stability of APRS-IS and the thousands of users
> world-wide.
> 
> 73,
> 
> Pete Loveall AE5PL
> pete at ae5pl.net
> 
> 
> 
> 
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
> 
> 
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig




More information about the aprssig mailing list