[aprssig] APRS-IS Duplicate Packets

[Joel Maslak - N7XUC]

Agreed. I would rather see both the corrupted and the uncorrupted packet than just the corrupted one. 

Pete made yet another great choice in how to handle this issue.  He made the choice that does the least harm (occasional "almost dupe"). 

On May 4, 2010, at 5:25 AM, Jason KG4WSV <kg4wsv at gmail.com> wrote:

> On Tue, May 4, 2010 at 4:06 AM, Matti Aarnio <oh2mqk at sral.fi> wrote:
>> 
>> Essentially for duplicate lookup hashing and subsequent comparison one
>> really needs to ignore all 0x20 bytes at the end of the packet.
> 
> No, you don't.  Pete is absolutely correct, you do not modify the payload!
> 
> It is ridiculous to say that you need to screw up a packet just
> because some other system may have already screwed it up.
> 
> If packet payloads are being modified, the correct solution is to find
> out what system is (incorrectly!) modifying them and fix it.
> 
> -Jason
> kg4wsv
> 
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig