Okay, time to ask a silly question... We know that the way Scott has implemented the hop limits in the OT2 allows n values greater than the hop limit to be digipeated when the N value is less than or equal to the hop limit.
i.e alias 1 WIDE hoplimit 1 3 will digipeat WIDE3-3 and lower as below WIDE3-2 WIDE3-1 which we should expect. It also digipeats WIDE7-3 and lower WIDE6-3 and lower WIDE5-3 and lower WIDE4-3 and lower While Scott feels otherwise, I feel that this is an error in programming allowing paths beyond the hop limit to still be handled, even though we are attempting to inhibit exactly that behaviour with the hop limit. This is especially prevalent when attempting to set up a WIDE1-1 digipeater. Any packet on its last hop will activate what should only be a first hop digipeater. 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? If an alias of WIDE1 would work, it should also work for an alias of WIDE3, and a hop limit of 3. I set SPLSTD up the other day with WIDE3 as an alias, and a hop limit of 3. I drove out in the area, and did not get digipeated at all by the digi... Of course, I think I just found the flaw in my analysis... I'm using an outgoing path of WIDE1-1,WIDE2-2 neither of which will match WIDE3-N... Auuugggghhhh! I hate it when I outsmart myself! Off to the drawing board... Of course you can all feel free to smite me about the head and shoulders... Anyone using a specified n value on their WIDEn digipeaters? James VE6SRV
