Order Tray | Contact Us | Home | SIG Lists

[aprssig] Packet routing, path specification.

Robert Bruninga bruninga at usna.edu
Fri Jun 24 18:28:19 UTC 2005


Yep, that is exaclty what will happen until that
digi supports the New N paradigm.  Until a digi
is updated to support WIDEn-N or WIDE1-1
then it should be clear that WIDE1-1 wont work.
That is why we need to get all digi owners to
get on board and change their paramters...

>>> needhame1 at plateautel.net 06/24/05 1:44 PM >>>
At 11:07 AM 6/24/2005, Wes Johnston wrote:
>I differ with you.... simply adding WIDE1-1 to UIDIGI does _not_ fix the 
>dupe problems.
>
>I send a packet WIDE1-1,WIDE2-2.
>
>an 8.2 kpc digi (with UIDIGI WIDE1-1 set as you recommend) hears my 
>packet.  It is digipeated like this:
>DigiCall*,WIDE2-2.

         I thought I would try the same.  Now, I don't know exactly what 
KA5B has for a TNC, but this is what I sent:

11:42:44T KD5XB-2>APU25N,WIDE1-1,WIDE2-2 Port=1 <UI C Len=53>:
=/=)1Q4Eiz-  BPHG70304/Probe NOT Enabled now {UIV32}

And this is what happened:

11:41:56R KD5XB-2>APU25N,KA5B*,WIDE1,WIDE2-2 Port=1 <UI C Len=54>:
=/=)1Q4Eiz-  BPHG70304/Probe NOT Enabled now {UIV32}

         Of course, after the first hop, the packet died.

         More experimentation to follow, but first I have to go to 
Stephenville, Texas, and back.
         Earl


Earl Needham, KD5XB, Clovis, New Mexico DM84jk
http://kd5xb-2.no-ip.info 



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





More information about the aprssig mailing list