[aprssig] qAR & qAr, same igate

[AE5PL Lists]

Do you have multiple feeds for your IGate into APRS-IS?  If so, change
to a single feed.

I am not aware of which server software inserts an asterisk in the q
paths.  The software that is doing this is mangling the q construct.  I
would guess that since that software is also reinserting the packet with
the qAr construct, somebody has some bad server software out there that
isn't even dupe checking properly.

73,

Pete Loveall AE5PL
mailto:pete at ae5pl.net 

> -----Original Message-----
> From: Curt, WE7U
> Posted At: Wednesday, August 16, 2006 10:03 AM
> Subject: [aprssig] qAR & qAr, same igate
> 
> 
> 
> I'm seeing some of my packets duplicated on the APRS-IS stream.
> Packets come across first with "qAR,CALLSIGN" as the 
> identifying igate, then again a few minutes later with 
> "qAr,CALLSIGN*" as the igate.  The Q-construct is different 
> plus there's an asterisk after the callsign.
> 
>     qAr - Packet was received indirectly (via an intermediate
>     server) from an IGate using the ,I construct.  The callSSID
>     following the qAr it the callSSID of the IGate.
> 
>     qAR - Packet was received directly (via a verified connection)
>     from an IGate using the ,I construct.  The callSSID following
>     the qAR it the callSSID of the IGate.
> 
> So... Is this expected behavior or is something else going on?
> 
> --
> Curt, WE7U.   APRS Client Comparisons: http://www.eskimo.com/~archer
> "Lotto:    A tax on people who are bad at math." -- unknown
> "Windows:  Microsoft's tax on computer illiterates." -- WE7U 
> "The world DOES revolve around me:  I picked the coordinate system!"
> 
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
>