[aprssig] HELP! Digipeat storm in SE PA

Andrew P. andrewemt at hotmail.com
Tue Mar 20 16:12:06 CDT 2012

True, but the YAAC instance at that time wasn't I-gating (digipeating WIDE1-1, yes, but not I-gating). Notice that two other local I-gates were repeating the message back to me over RF after forwarding it via APRS-IS.

YAAC was sending responses every 30 seconds because it was receiving a digipeated copy of the original query every 30 seconds (until I took it off the air). I confirmed that from the debug logs. So, I'm trying to track down who kept that query message packet repeating so much. I don't have a record of an ack packet going out or coming in, so that may be part of it..

No one responded on part of my original question: is it OK to query your own station via a digipeater bounce? Anybody know the answer to that one?

Andrew Pavlin, KA2DDO

------Original Message------
From: Tom Hayward
To: aprssig at tapr.org
To: yaac-alpha-testers at yahoogroups.com
Sent: Mar 20, 2012 4:53 PM
Subject: Re: [aprssig] HELP! Digipeat storm in SE PA

On Tue, Mar 20, 2012 at 13:05, Lynn W. Deffenbaugh (Mr)
<ldeffenb at homeside.to> wrote:
> Opentracker digipeat bust with WIDE1-1 becoming an unused WIDE1 which the
> Tracker2 family digipeats anyway?

What makes you think it was digipeating an already used path? I don't
see any packets (in your log) that appear to be N3TJJ-8 acting on an
unused path.

2012-03-20 13:05:07 KA2DDO>APJYC1,N3TJJ-8*,WIDE1*,qAR,N3TUQ-5::KA2DDO
2012-03-20 13:07:31
:LOCAL(1): AA3GN-1 AA3JC-3 AB3LT-1 K2GE-15 K3BZG-3 K3XY-3 K3ZMC-1
2012-03-20 13:07:31
2012-03-20 13:07:32
:LOCAL(3): KF3M-1 N2IGU-1 N3FCX N3FYI-1 N3KTX-2 N3KTX-9 N3MYB-13

It looks to me like KA2DDO's YAAC i-gate is replying to the query with
a path generated by reversing the path of the received query packet
(the log above doesn't contain the actual query packet with the path
that was reversed, but the first one is similar). From the log, it
appears YAAC is responding to the same query multiple times (this log
contains all dupes, right?). I wouldn't be surprised if this is a
problem with YAAC--it claims "alpha" status.

N3TJJ-8*,WIDE1* is converted to WIDE1,N3TJJ-8 by YAAC.

I'm curious what caused it to send query responses every 30 seconds
(sometimes longer) for the 40 minutes of logged data.


aprssig mailing list
aprssig at tapr.org

Sent from my Verizon Wireless BlackBerry

More information about the aprssig mailing list