[aprssig] Smart TX igate message routing?

[Lynn W. Deffenbaugh (Mr)]

There have been periodic discussions about "smart" or "reverse path" 
routing for messages, but it all come down to the fact that just because 
your IGate heard a packet via a given path doesn't mean that the reverse 
of that path will get back to the station.  You are better off relying 
on the digipeater infrastructure to deliver packets than to try to 
thread a packet's way back through a specific digipeater path, 
especially when you consider congestion and packet collisions.

Also, just because the most recent packet you received from a station 
came from a certain set of digipeaters does not mean that the station is 
actually still in that same path some time later when a message may be 
addressed to him/her.

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

On 3/6/2017 3:01 PM, Jess Haas wrote:
> Maybe it is a stupid idea but I do think we could do a bit better than 
> a wide path. If we know a more specific path can't we decrease channel 
> congestion and QRM while increasing range without needing any 
> modification to the digipeater infrastructure?
>
> Wouldn't the target station be more likely to receive the message if 
> it is only hearing it from the closest digipeater instead of a bunch 
> of them transmitting at the same time creating QRM?
>
> When a mobile station is right next to an igate and they can hear each 
> other directly why should we spam the whole region with the traffic 
> via digipeaters?
>
> Also it allows for using other stations not just digipeaters to extend 
> your range for receiving messages not just transmitting. So if im in a 
> valley and cant hit/hear a digipeater I can set the first hop in my 
> path to another station i can hit and then when an igate tries to get 
> a message back to me it will route it through that station.
>
> -Jess
>
>
> On Mon, Mar 6, 2017 at 10:11 AM, Robert Bruninga <bruninga at usna.edu 
> <mailto:bruninga at usna.edu>> wrote:
>
>     APRS by design will be digipeated by EVERY digipeater that hears
>     it.  So if the one farther south hears it, it is already going to
>     digipeat it anyway. Nothing you need to do to make that happen…
>
>     And in SoCal, there are so many digis, that your path should be
>     just one hop and it will still hit every digi that hears it that
>     first hop.
>
>     Bob
>
>     *From:*aprssig [mailto:aprssig-bounces at tapr.org
>     <mailto:aprssig-bounces at tapr.org>] *On Behalf Of *Jess Haas
>     *Sent:* Monday, March 06, 2017 1:08 PM
>     *To:* TAPR APRS Mailing List
>     *Subject:* [aprssig] Smart TX igate message routing?
>
>     Where I am located in Southern California I can hit many
>     digipeaters. For home station beaconing setting a single one of
>     them as my route seems to be the way to go but for tx message
>     igating I was thinking it may make more sense if the outgoing path
>     was the one that the station was last heard on. Has anyone
>     implemented anything like this?
>
>     For example the digipeater I have the strongest path to may not be
>     able to get a message to a station farther south but I can hear
>     and hit a digipeater rather far south that the station can hear
>     easily. Also if I have heard a station directly recently than I
>     should have no problem getting a message to them directly even if
>     they have moved some with my basestation antenna and possibly
>     higher power so digipeating to the whole area may be unnecessary.
>
>     Another advantage of this would be that a station that is in an RF
>     hole such as a valley that can't hear or hit a digipeater but has
>     a path to another station that can could set that station as a
>     path and messages would automatically be routed back to them.
>
>     Thoughts?
>
>         Jess
>
>
>     _______________________________________________
>     aprssig mailing list
>     aprssig at tapr.org <mailto:aprssig at tapr.org>
>     http://www.tapr.org/mailman/listinfo/aprssig
>     <http://www.tapr.org/mailman/listinfo/aprssig>
>
>
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> http://www.tapr.org/mailman/listinfo/aprssig


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20170306/854181e4/attachment.html>