>I have seen suggestions for setting the alias to a specified alias of >WIDE1 and a hop limit of 1. Does anyone have evidence that this does >in fact act upon WIDE1-1 paths?
A hop limit of 1 will allow abusers running WIDE1-2 an extra WIDE1 hop. Believe it or not, I see "appliance users" running WIDE1-2,WIDE2-2 or WIDE2-1,WIDE1-1 almost daily. Set alias 1 WIDE1 and HOPLIMIT to 0 for a single hop from a mobile running WIDE1-1. More info below: Fill-in digi's are the most courteous digi's. They only forward fresh first hop from WIDE1-1 mobiles. The used up WIDE1-1 is replaced with MYCALL, and any additional paths are forwarded. Mobiles running the recommended new paradigm path of WIDE1-1,WIDE2-1 benefit from Fill-in's. All other WIDEn-N's are ignored to limit forwarding stale QRM. Fill-in's won't clog up the network forwarding old stale WIDE2-2 digi id's, beacons, WX, stale mobile traffic, and abusive paths. Fill-in digi's can be added into a busy APRS area without much adverse impact to the network load. The beacon PATH should be left blank, when possible, so as to not add QRM to the network. If the fill-in is not heard directly by an I-gate, a PATH of WIDE2-1, or even WIDE1-1, is acceptable. Especially if scripting <http://wiki.argentdata.com/index.php/Scripting> is used to only send a WIDEn-1 path once, or twice an hour, to keep it on the maps. Local beacons are OK every 10 minutes, advertise your accepted path, local systems, and information. Keep you local info local for folks traveling nearby. See http://www.aprs.org/newN/WIDE1-1settings.txt <http://www.aprs.org/newN/WIDE1-1settings.txt> for more fill-in information. To setup a fill-in set: ALIAS 1 WIDE1, HOPLIMIT 1 0, USEALIAS 1 on, DIGI on, DIGIID on, PATH -.
