[aprssig] Identifying TX Igates

[Lynn W. Deffenbaugh (Mr)]

On 9/19/2011 3:01 PM, la3qma at aprs.la wrote:
> The IGATE should also send messages the reverse path
>

That would only have a chance at working if the received path could be 
counted on to reflect exactly the digipeaters through which the target 
recipient is being heard at the IGate.  All to many digipeaters either 
a) don't insert their own call or b) replace other digi's calls with 
their own and is further complicated by on-the-fly alias paths that may 
or may not be digipeaters.

How would you reverse the following path?

....>....,KJ4ERJ-1,WIDE1,WX4MLB-3*,WIDE2-1

and

...>...,KJ4ERJ-1,WIDE1,WX4MLB-3,WIDE2*

Interesting conundrum, eh?

> or some system to give better success than now. 

The -IS to RF IGate operator should understand his local RF environment 
sufficiently to set an appropriate "local" hops limit and configure an 
outgoing path for packets to cover that area reasonably well.  If every 
IGate operator understood how to do this, there would be "better success 
than now" in many areas.

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