[aprssig] Why Not "Gate in Vicinity" (phones)

Lynn W. Deffenbaugh (Mr) ldeffenb at homeside.to
Mon Dec 26 15:25:24 EST 2011

Pardon my ignorance, but anything UDP based (assuming that's the correct 
implication of the axudp name) doesn't do "connections" so they cant 
"connect to one or more others".  They may "communicate" to other 
instances, but they don't connect.  And as such, I can imagine that 
anyone that can craft a suitable UDP packet and send it to one of these 
instances will basically have direct access to the connected radio?

This would be like running AGW's PEpro on an open port and inviting 
other people to come on down and key up my AX.25 transmitter, eh?  Or is 
an axudp link strictly point-to-point with a receiver only accepting UDP 
data from a specific transmitting IP address?  If that, it'd be a bear 
to keep working in the face of dynamic IP addresses used by many ISPs.

I thought the general discussion was how to better secure the APRS-IS, 
not open it up for even easier abuse of remote RF networks.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 12/26/2011 3:03 PM, Andre wrote:
> I would agree but there is already a way around it, for aplications 
> like this a axudp based network instead of a text based network does 
> work, the igate just acts like a xband digipeater, they all connect to 
> one or more others just like on aprs-is and dupechecking keeps the 
> chaos under controll, digipeaters can digipeat unaltered paths without 
> setting has been digied bits back to other gate digipeaters and only 
> digipeats to 2 meter where the next digicall is theirs.
> The clients for this system will just have to select the nearest 
> digipeater for the path.
> probably could program digined on linux to do this in one evening 
> maybe even one hour.
> 73 Andre PE1RDW
> Op 26-12-2011 19:30, Pete Loveall AE5PL Lists schreef:
>> IGates don't send gated packets with their APRS-IS paths.  They are 
>> sent using third-party format.  Paths on APRS-IS have no meaning when 
>> gated to RF other than to determine if the packet originated on 
>> APRS-IS or on RF.
>> Sorry, this won't work either.  Remember, on APRS-IS there are no 
>> "smart phones"; there are only APRS-IS-connected clients and RF gated 
>> clients.  While the intent to have everyone's packets seen on RF 
>> seems noble on the surface, the implementation is not so noble.
>> 73,
>> Pete Loveall AE5PL
>> pete at ae5pl dot net
>>> -----Original Message-----
>>> From: Bob Bruninga
>>> Sent: Monday, December 26, 2011 12:24 PM
>>> Can the APP be required to inject packets using the Proportional 
>>> Pathing
>>> Algorithm.  That is:
>> _______________________________________________
>> aprssig mailing list
>> aprssig at tapr.org
>> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig

More information about the aprssig mailing list