Order Tray | Contact Us | Home | SIG Lists

[aprssig] APRSLink and NEW-N

Robert Bruninga bruninga at usna.edu
Fri Jan 13 17:43:13 UTC 2006


>> APRSLink...,  especially because most  IGates use 
>> multiple hop paths... The collision issues could make 
>> the system unusable in many areas due to lost 
>> packets on a congested channel.

>>> wa7nwp at jnos.org 01/13/06 9:46 AM >>>
>It's time to upgrade messaging software to use direct 
>paths instead of flood paths.  We now have the new 
>wideN-N scheme that gives the full packet path so it's 
>a natural next step to start using that information.
>It's the FLOOD, not the messaging, that causes the 
>problems.

Well said! ANd so very true.  Now that the New-N is
the goal and we are making progress, (almost everyghing
now supports n-N paths)... BUT still more than HALF of
all digis that were WIDEn-N in the first place have never
switched over to TRACEABLE WIDEn-N instead of
untraceable WIDEn-N.  

We must be vigilant and encourage all of those hundreds
of old WIDEn-N digis to change their settings to New-N.
Most people thouht that New-N was just getting rid of
all the dupes caused by RELAY and WIDE, but that was
only the most obvious part.  The equally important part
is to get full WIDEn-N tracing and that will only work
if we get 100% of all digis including all the old WIDEn-N's
to switch over to UITRACE...

As users we simply look at all packets that arrive to make
sure there is a trace on the number of digis used.  If it
arrives as 2-1, or 3-2 there should be one digi in the
path  and it should.

If it arrives as WIDE2 or WIDE3-1, then there shouild
be two digis and they should be in order etc...

Bob


73
Bill - WA7NWP



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





More information about the aprssig mailing list