[aprssig] fix kpc3 tncs

[Wes Johnston]

The only way I know of with the kpc3's to enforce a limited number of hops is to
 explicitly put WIDE2-2, WIDE3-3 in the UIDIGI parm, and you limit folks to ONE 
hop since under UIDIGI rules, the callsign and ssid of the digipeaters listed 
in UIDIGI are not modified, but rather just get the "has been digipeated" bit 
set (ie the * you see beside the callsign in conv mode).

Bob, we would not be having any of these discussions if there was some way to
limit the number of hops WIDEn-n would respond to.  I'd love to be able to
program my TNC to respond only to WIDE2-2 or less.... or WIDE3-3 or less.  But
in the scheme of things, kantronics isn't likely to make this change for us,
and if they do, it'll cost us $80 a copy for the eprom.  I don't have a problem
with this, they _are_ in business to make money.

Two things that would be nice....
1) we collectively decide on the extra bells and whistles we'd like to have the 
KPC3plus's do, and approach Kantronics with our requests.  Then _we_ (tapr help 
coordinate, maybe) take up a fund from the aprs community... $20 here, $50 
there... and pool our money like we did during the great APRS QSY 6 years ago. 
When we have enough money, we go to kantronics and have them implement our 
changes.  How much is it worth to _all_ of us on the east coast and LA to fix 
our networks?

2)I wish since the kpc3 has long since been out of production, they would 
release the souce code.  But again, they are in business to make money, and 
helping us make changes to our "long since discontinued" tncs isn't going to 
make them any money.


To start the ball rolling, let's get a wish list together....

1) limit the number of hops in UIFLOOD and UITRACE (make sure the TNC can't be
tricked by WIDE1-7.  Packets such as this should be dropped on the floor)

 2) add more digi alias names to UIFLOOD and UITRACE

 3) checksum dupe supression in UIDIGI coordinated with UIFLOOD and UITRACE.

 4) Preemptive digipeating (digipeater will search the path of each packet and 
digipeat the last path element it finds that it is programmed to digipeat. This
means that a R,W packet will emerge from the digi as R,W* instead of R*,W)

 5) ability to take GPS input and put out compressed APRS packets.

 6) smart beaconing for tracker mode TNCs

 Wes

--



Quoting Robert Bruninga <bruninga at usna.edu>:

> >From this New n-N Paradigm we have learned a new
> >universal path that can be made to work Everywhere:
> >
> >  VIA WIDE2-2
> >
> ><snip>
> >  Now, carefully set  UITRACE WIDE2, 30 which enforces only
> >  two hop use of WIDEn-N.  Only WIDE2-2 or 2-1 is supported
>
> ARGH!!!!
> This does not appear to work.  This is very disappointing
> to me.  When I designed WIDEn-N back in 1994 and presented
> it to Kantrnonics, I defined it to work as WIDEx-y where x was
> a wildcard with no restrictions.  Apparently they implemented
> it as a required digit.  Thus we have no flexibility to use it
> as an enforcer.... DRATS.
>
> Back to square 1.  Looks like the best approoach so far remains
> the New n-N Paradigm and the enforcement of large N's through
> the use of SSn-N and LINKn-N and adding WIDE2-2 as an alias
> in non-n-N digis so that it is supported everywhere...
>
> de Wb4APR, Bob
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
>