On Sun, Aug 9, 2009 at 1:19 PM, Phillip<[email protected]> wrote: > Before you rush out and make changes > > NOTE it is WIDEN-n Not WIDEn-N
Well, in this part of the world we use the notation WIDEn-N. > WIDE2-1 or WIDE2-2 NOT WIDE1-4 or WIDE1-2 Generally the concept was to launch a packet with 'n' and 'N' being equal, with the exception when wishing to get a single hop only from the WIDE digipeaters without triggering the fill-in digipeaters, using WIDE2-1. By putting WIDE7-7,WIDE6-6,WIDE5-5,WIDE4-4 aliases into the UIDIGI parameter of the KPC-3 and KPC-3+ units, we created a pseudo-trap to stop abusive paths. However, anyone knowing the operation of these units knows that this can be circumvented by using non-standard numeric values. You can escape the traps by using a path such as WIDE1-7 to get seven hops. Something like WIDE5-7 would get 2 hops before being trapped by the UDIGI WIDE5-5 (which would give one more hop, and then overwrite it). We were hoping that Scott would implement a smarter version of hop limiting, but that didn't happen. (I still haven't arm wrestled Scott over this yet...) I'm going to have to break down one day and look at the code that Scott uses to implement digipeating, and then rewrite it to do digipeating the "right" way. James VE6SRV
