[aprssig] HELP! Digipeat storm in SE PA

[Lynn W. Deffenbaugh (Mr)]

N3TUQ-5 is an APRSIS32 instance that reports all received RF traffic to 
a central server.  Here's a copy of all of the non-dupe-suppressed 
packets it heard off the RF in the hour of question.  There definitely 
seems to be some liberal path mucking going on in your area somehow.  
I'm really wondering if there's a non-compliant IGate that is putting 
packets from -IS to RF without putting a 3rd party wrapper on them?

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

PS.  Hopefully the attachment comes through.  If not, go to

http://ldeffenb.dnsalias.net/20120320-KA2DDO.txt


On 3/20/2012 3:05 PM, Lynn W. Deffenbaugh (Mr) wrote:
> Opentracker digipeat bust with WIDE1-1 becoming an unused WIDE1 which 
> the Tracker2 family digipeats anyway?
>
> http://aprs.fi/?c=raw&call=KA2DDO shows N3TJJ-8 as digipeating the 
> packet repeatedly.
>
> http://aprs.fi/?c=raw&limit=&call=N3TJJ-8 shows N3TJJ-8 to be an OT2 
> (APOT21).
>
> But it looks like there was a WIDE2-1 in there as well, but the 
> initial WIDE1-1 looks like it replicated and kept pushing the WIDE2-1 
> towards the end.
>
> http://aprs.fi/?c=raw&limit=&call=K3XY-3 looks interesting as well 
> with a path of NULL?  It's UIdigi (APNU19).
>
> Lynn (D) - KJ4ERJ - Entering my guess...
>
> On 3/20/2012 2:35 PM, Andrew P. wrote:
>> I used the
>>
>>   :callsign:?APRSL
>>
>> query pointed at my own callsign KA2DDO. Path was WIDE1-1.
>>
>>
>> ------Original Message------
>> From: Stephen H. Smith
>> To: aprssig at tapr.org
>> Sent: Mar 20, 2012 2:26 PM
>> Subject: Re: [aprssig] HELP! Digipeat storm in SE PA
>>
>>
>> On 3/20/2012 2:21 PM, Andrew P. wrote:
>>> Greetings.
>>>
>>> I tried something that may or may not be uncool, which was to send a 
>>> message containing a directed query to my own callsign, figuring I 
>>> would bounce both the query and the answer off a local digipeater. 
>>> It worked, but now I have local digipeaters digipeating the queries 
>>> and replies back and forth. I shut down my station so it would stop 
>>> responding to the copies of the original query message, but the 
>>> messages are still bouncing, with max-length digipeater lists.
>>>
>>> Can anybody help me stop this, or will it fade out on its own (I 
>>> hope!)?
>>>
>>> Andrew Pavlin, KA2DDO
>>> Sent from my Verizon Wireless BlackBerry
>>>
>>>
>>> _______________________________________________
>>> aprssig mailing list
>>> aprssig at tapr.org
>>> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>> Did you do the directed query of a specific station or the global 
>> query to "All
>> stations within earshot"?
>>
>> What was your path setting when you sent out the query?
>>
>>
>>
>> _______________________________________________
>> aprssig mailing list
>> aprssig at tapr.org
>> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>>
>>
>> Sent from my Verizon Wireless BlackBerry
>>
>> _______________________________________________
>> aprssig mailing list
>> aprssig at tapr.org
>> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>>
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 20120320-KA2DDO.txt
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20120320/15a5fab4/attachment.txt>