[aprssig] WIDE1-1,SSn-N update

[Cap Pennell]

So, all _fill-in_ digis will be set to provide "traceable WIDE1-1" but will
not operate any "SS"1-1 nor other aliases.

For a Kantronics TNC, this setting is
MYAlias NONE   ;not RELAY nor WIDE nor TRACE nor WIDE1-1
UIdigi  ON WIDE1-1
UIFlood %      ;disabled
UITrace %      ;disabled
UIDWait OFF

-- Setting up UI-View32 to act as a fill-in or event digi.--
This type of digi is the least harmful to our congested VHF network.
You must be running your TNC in KISS mode to enable the digipeater in
UI-View32.

Go to Setup -> Digipeater Setup
Enable Digi is checked
UI Only is checked
Alias substitution is checked
WIDEn-n is not checked
TRACEn-n is not checked
Alias(es) has W6UUU,WIDE1-1  <substitute your callsign for W6UUU>
Sub Alias has W6UUU  <substitute your callsign for W6UUU>
Dupe secs = 30
Digi routes has 1=1

Click on OK and you're done.

73, Cap KE6AFE


> -----Original Message-----
> From: aprssig-bounces at lists.tapr.org
> [mailto:aprssig-bounces at lists.tapr.org]On Behalf Of Robert Bruninga
> Sent: Monday, January 07, 2008 06:27 AM
> To: aprssig at lists.tapr.org
> Subject: [aprssig] WIDE1-1,SSn-N update
>
>
> I was reviewing the fix14439.html web page and noticed it still
> referred to SS1-1,SSn-N as the recommendation for state or
> section nets to make these packets traceable.
> http://www.ew.usna.edu/~bruninga/aprs/fix14439.html
>
> There is no need to use SS1-1, since WIDE1-1 already exists.  So
> I have changed all references to SS1-1,SSn-N to WIDE1-1,SSn-N.
>
> Background:  Most digipeaeters can support two types of XXXn-N
> digipeating.  One called UITRACE is fully traceable and the
> other one called UIFLOOD is not.  Originally WIDEn-N used the
> nontraceable UIFLOOD parameter.  This was bad for network
> management.
>
> The New-N paradigm made WIDEn-N fully traceable by swapping
> WIDEn-N support to the UITRACE parameter.  This left the
> "untraceable" UIFLOOD available for SSn-N routing.  But these
> packets can be marked with the LAST digipeater they used if the
> UIFLOOD-ID parameter is set.  By preceeding any SSn-N path with
> a WIDE1-1, then the initial digipeater is also marked in the
> packet.
>
> This is why the path of WIDE1-1,SSn-N is recommended for State
> or ARRL Section nets, because it lets all packets then be
> identified by where they entered the network and how they
> arrived.  This turns this previously untraceable parameter into
> a much more manageable path in the modern New-N paradigm
> network.
>
> Bob, WB4APR