Re: Proportional beaconing feature request
toggle quoted messageShow quoted text
I can see that I got so distracted by the weird paths that I forgot to look for the "has-been-digipeated bit" in the packets.
2020-02-03 17:42:42 MST: KD1ELK>SSRPQU,KE7JVX-3*,WIDE1,WIDE2-1,qAO,K7EIR-12:`'Fmo4u>/`"8/}Justins Tacoma_%
This first packet with the incorrect mark up got me going down the wrong path.
Just about every packet after that was heard direct by W7JET-10 and gated. Because the packets all had the exact same content, I incorrectly assumed that they were duplicate packets that had been handled by a variety of digipeaters. I didn't catch the missing "has-been-digipeated bit", and incorrectly assumed the digipeaters had filled in the path elements, and not that you were manually setting fixed path elements.
I'm sure glad that your local digipeater network was not handling the packets incorrectly so as to add in hops by themselves. There are software digipeaters that can be configured to modify paths to cause this type of issue, but most of the digipeaters are Kantronics, and don't support that type of operation.
However, I stand by my first statement... user education, courteous operations, and a well planned and executed digipeater network are a better solution than trying to brute force your way into a network.
Proportional pathing can be a component of courteous operations if implemented properly.
On Wed, Feb 5, 2020 at 10:02 AM James Ewen via Groups.Io <firstname.lastname@example.org> wrote: