Settings for HIGH DENSITY WIDEn-N DIGIPEATERS (CUTOFF Solution) 5 May 05 --------------------------------------------------------------------------- Update 18 Nov 2005: This approach is no longer recommended. This CUTOFF solution is a drastic approach to cutting off out of area large N traffic. As more an more areas adopt the New-N-Paradigm and begin trapping our large values of N at their source, this CUTOFF solution will not typically be needed. In fact, this method is NOT RECOMMENDED now that the New-N is taking hold and we are not seeing much, if any, large hop abuse anymore... This file is only maintained for historical purposes, and to show how we can use the flexibility of the added ALIASES in a TNC to actually TRAP hops. This CUTOFF approach basically forces everything to only ONE hop in an area and is only applicable on very high digis or very dense populated areas. Most of the other settings in these digis are identical to the typical New-N-Paradigm settings in other digis except for these settings: A. Set UIFLOOD SS,30,ID to support SSn-N routing for your State or section. Since the geographic area covered by these digis is limited, then the damage for large n-N QRM is also limited. (this is actually the same as all other New n-N Paradigm digis are using) B. Set UITRACE to NONE (or maybe it is "OFF") or maybe it takes a "%" to disable it? Anyway, TRACEn-N is obsolete and UITRACE is not used. C. Set UIDIGI ON, WIDE1-1, WIDE2-2, WIDE2-1, WIDE3-3. Only these specific aliases are supported in this area. They all get just ONE hop and die. But 2-2 and 2-1 packets from surrounding normal digis will get in and local's using 3-3 will be heard. It is basically a ONE-HOP solution for very high density areas only. For more on this approach be sure to see how we did it in Los Angeles, to prevent anything above two hops into the LA Basin. http://www.ew.usna.edu/~bruninga/aprs/fixingLA.html Make all the other settings the same as a normal New n-N WIDEn-N digi. de WB4APR, bob