[aprssig] Packet routing, path specification.

[Wes Johnston]

OK, just to keep beating this dead horse.... I took 10minutes playing
with my TNC in my house watching how it would digipeat various path
elements as transmitted from my truck.  In this test, I used the alias
TEMPn-n to set my TNC apart from all others for this test... so if
anything happend to TEMP2-2, I'd know it was my TNC that did it. 
Again... I am the only TEMPn-n in the area.  (and yes, I know field day
is tomorrow and we're supposed to use TEMPn-n for that).

Here is the version of my kpc3, and the settings you need to know about
for this test.
cmd:ver      
KPC3-3F427265-8.2 
cmd:uid
UIDIGI   ON WIDE1-1
cmd:uit
UITRACE  TEMP,30
cmd:uif
UIFLOOD  disabled,30,NOID

*************************************************************
Here is the packet I sent from my truck. 
KD4RDB-15>SS5V0Y,WIDE1-1,WIDE2-1,TEMP2-2:'l4
l mj/]"4N}

My station transmitted the packet under UIDIGI rules:  It swapped
WIDE1-1 for KD4RDB.  No problem.
KD4RDB-15>SS5V0Y,KD4RDB*,WIDE2-1,TEMP2-2:'l4
l mj/]"4N}

It was heard by kc4pl direct, digi'ed by him and n4bam-3 no problem
KD4RDB-15>SS5V0Y,KC4PL,N4BAM-3,WIDE2*,TEMP2-2:'l4
l mj/]"4N}

My TNC heard the packet come around from n4bam-3, and digipeated under
UITRACE rules.  This is the dupe I'm talking about.  My station should
have never digipeated this twice if what you guys are saying about
kpcv8.2 7265 is correct.
KD4RDB-15>SS5V0Y,KC4PL,N4BAM-3,WIDE2,KD4RDB*,TEMP2-1:'l4
l mj/]"4N}

Note that n4bam-3 (firmware unknown) digipeated the first copy my TNC
transmitted... no problem.... If n4bam-3 had been a kpc3 9.x this would
not have happened...
KD4RDB-15>SS5V0Y,KD4RDB,N4BAM-3,WIDE2*,TEMP2-2:'l4
l mj/]"4N}

*************************************************************
Ok, now I'm gunna do the same thing with UIFLOOD...
cmd:uid
UIDIGI   ON WIDE1-1
cmd:uit
UITRACE  disabled,30
cmd:uif
UIFLOOD  TEMP,30,NOID
*************************************************************
Here I transmitted the same packet...
KD4RDB-15>SS5V0Y,WIDE1-1,WIDE2-1,TEMP2-2:'l4
l mj/]"4L}

My digi transmitted the packet under UIDIGI rules....
KD4RDB-15>SS5V0Y,KD4RDB*,WIDE2-1,TEMP2-2:'l4
l mj/]"4L}

This time k2jlb digi'ed it as UIDigi rule (I know how his TNC is
setup).  He heard my car direct, only about 5 miles away from me.
KD4RDB-15>SS5V0Y,K2JLB*,WIDE2-1,TEMP2-2:'l4
l mj/]"4L}

This one, kc4pl is running digined and rewrites odd paths, so he
truncated my TEMP2-2 that had been on the end.  This is expected.
KD4RDB-15>SS5V0Y,K2JLB,KC4PL,WIDE2*:'l4
l mj/]"4L}

kd4ebr-3 south of me digipeated it too under his UIWIDE rule...
KD4RDB-15>SS5V0Y,KD4EBR-3,WIDE2*,TEMP2-2:'l4
l mj/]"4L}

And finally, my station decremented the TEMP2-2 to TEMP2-1.  Since I am
the only TEMPn-n in my area, even though my TNC didn't stamp the packet,
I know it was mine.  This is the dupe I keep talking about!
KD4RDB-15>SS5V0Y,KD4EBR-3,WIDE2*,TEMP2-1:'l4
l mj/]"4L}
*************************************************************

So, the behavior I'm seeing with my KPC3 v8.2 7265 is that the left hand
(UITRACE and UIFLOOD) do not know what the right hand (UIDIGI) is
doing.  In areas with kpc3 8.2 7265 roms, we are not any better off than
we were when we used RELAY.  This is not to say that as a whole we
aren't better off.... The new WIDE1-1 system works in areas served by
kpc3 8.3 and up.... That's just not my area.... my kpc3+ with 8.3
firmware is being used with our MIC-e repeater, so it's not available to
use as a stand alone digi right now.

Have I beat this one to death yet?  8-)
Wes