Alan N6VUD wrote... > To setup a fill-in set: > ALIAS 1 WIDE1 > HOPLIMIT 1 0 (0 will allow WIDE1-N one hop) > USEALIAS 1 on > DIGI on [will allow digi on MYCALL] > DIGIID on [should actually be DIGIID 1 ON] > PATH - > > http://wiki.argentdata.com/index.php/Digipeater_Setup
Thanks for that. I didn't think to try a hop limit of zero! It has been a while since I had looked at the wiki too. It explains that with the HOPLIMIT set to 0, "only an exact match will trigger use of the alias". It also has a pretty good explanation of the way it implements trapping abusive paths. That's a good point about not entering any path. That way, it's own beacons will only be heard locally. The only downside is that if it isn't heard direct by an IGate, people looking at the area remotely won't know that there's a fill-in digi there. The wiki does suggest that if it only beacons once or twice an hour, a path of WIDE2-1 could be used to "keep it on the map" if the nearest IGate is one hop away. However, better to have no path if the frequency is busy in the area so the only "QRM" it causes is only heard locally. A setting of INT 1200 would have it beacon just every 20 minutes. If the frequency was very quiet, it could be set to 600, especially if it's going out with no path. A "must have" setting to add to what you listed would be DUPETIME 30 so it will do dupe checking for anything already digipeated in the previous 30 seconds. Just to list the settings for a WIDE1-1 fill-in digi all in one go... ALIAS 1 WIDE1 HOPLIMIT 1 0 USEALIAS 1 ON DIGIID 1 ON PATH - INT 1200 DIGI ON SYM 1# MYCALL (your callsign) 73 es cul - Keith VE7GDH -- "I may be lost, but I know exactly where I am!"
