Order Tray | Contact Us | Home | SIG Lists

[aprssig] APRS routing strategies

Ryan Tourge k2rrt.lists at gmail.com
Wed Feb 16 19:38:34 UTC 2005


HA HA HA The world erupts into chaos! HA HA HA

Sorry... long day at work...

This may be hard to do without an external computer and would require major
retooling of the network, but what if the digipeater could determine how to
route a packet based on the position information sent with it? Then each
sysop could program their digi how ever it needed to be.

I know my idea may be a little off the wall, but maybe it will spark another
idea from someone else...

-----Original Message-----
From: aprssig-bounces at lists.tapr.org [mailto:aprssig-bounces at lists.tapr.org]
On Behalf Of Jason Winningham
Sent: Wednesday, February 16, 2005 2:15 PM
To: TAPR APRS Mailing List
Subject: Re: [aprssig] APRS routing strategies


On Feb 15, 2005, at 2:40 PM, Henk de Groot wrote:
> This proposal is to introduce 4 new generic digipeater calls, living
> besides the existing WIDE, TRACE and RELAY calls (thanks to Bill Vodal
> for the names :-)). These are:
>
> LOCAL, REGION, WORLD and IGATE

The LOCAL/REGION/WORLD idea is simpler for the end user, but it doesn't 
necessarily give a good feel for how far a packet will really go, since 
the actual number of hops is based on local load and configuration, and 
the distance between those hops is a geographical issue.  It would be 
great for appliance operators, but a ham should be more sophisticated, 
IMO (at least enough to understand the idea of a hop count).

Is there any mechanism to suppress/modify a bad configuration?  For 
example, what happens if my path is WORLD,WORLD,WORLD?

-Jason
kg4wsv


_______________________________________________
aprssig mailing list
aprssig at lists.tapr.org
https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig





More information about the aprssig mailing list