[aprssig] HELP! Digipeat storm in SE PA
esarfl at gmail.com
Tue Mar 20 15:53:45 CDT 2012
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
2012-03-20 13:05:07 KA2DDO>APJYC1,N3TJJ-8*,WIDE1*,qAR,N3TUQ-5::KA2DDO
:LOCAL(1): AA3GN-1 AA3JC-3 AB3LT-1 K2GE-15 K3BZG-3 K3XY-3 K3ZMC-1
:LOCAL(2): KA1UDX KA1UDX-1 KA2DDO KB3RNL-3 KB3SVY-2 KC2TXX-15
: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.
More information about the aprssig