[aprssig] UIFLOOD dual-dupes?

[Lynn W. Deffenbaugh (Mr)]

I've noticed that Kenwood radios do indeed digipeat their own originated 
packets if they hear the packet back from another digipeater with a 
configure path component still not consumed.  I agree that this is 
really foolish operation, but that's the way I've observed it happening.

Of course, with dupe detection in the APRS-IS, you really only see this 
on RF and only if you're in earshot of the Kenwood digipeater.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 7/18/2011 3:31 PM, Bob Bruninga wrote:
> Has anyone seen double packets from digipeaters?
>
> I'm testing two digipeaters set to support UIFLOOS of HOPn-N.
>
> When the digipeater originates its own packet as 7-7, the other digi does
> digipeat as HOP6-7, but then the sending digi sees that copy and digipeats
> it again as HOP5-7.
>
> It appears that these digipeaters are not recognizing their OWN originated
> packets as a "dupe" when they see them again, digipeted by another UIFLOOD
> digi.  They should ignore their own packets always.
>
> Both of these digis are kenwoods, a D700 and a D72.  Also the D72 throws out
> a totally useless CALLSIGN/R ID packet too.
>
>
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>