> Here are a couple more...
I've got a few more samples too:
2009-10-27 15:12:48 PDT:
KD7QCJ>APT311,BALDI,WIDE1,BALDI*,qAS,KB7UVC:>TinyTrak3 v1.1
2009-10-27 22:24:55 UTC:
W7MCK-9>TWRPXV,BALDI,WIDE1,BALDI*,qAR,KD7DVD:`2^en\Uk/]"5+}Maple
Valley ARES W7MCK Matt=
2009-10-27 22:25:24 UTC:
W7MCK-9>TWRPXU,BALDI*,WIDE2-2,qAR,KD7DVD:`2^Eo59k/]"5/}Maple Valley
ARES W7MCK Matt=
That last one is properly handled.
> 2009-10-26 15:13:01 MDT:
> N7NJO-14>T7QUWX,BALDI,WIDE1,BALDI*,WIDE6-2,qAR,KD7DVD:`23rlA*u/]"3{}=
> 2009-10-26 15:13:03 MDT:
> N7NJO-14>T7QUWX,BALDI,WIDE1,BALDI,ETIGER,KOPEAK*,WIDE6,qAR,AC7YY-12:`23rlA*u/]"3{}=
> 2009-10-26 15:14:30 MDT:
> N7NJO-14>T7QUWX,BALDI,WIDE1,BALDI,TWOODS*,WIDE6-1,qAS,KJ7XE-11:`23rlA*u/]"3{}=
> [Duplicate position packet]
>
> The second and third packets listed are actually the same packet, but
> being handled by different digipeaters after BALDI, and also being
> injected into the APRS-IS via different i-gates. Looks like KJ7XE-11
> is probably running a KPC-3 in KISS mode with his UI-View station,
> since he's showing the tell-tale delayed packet symptoms.
That's an astute observation. I've already sent Casey an email about
the delayed packets and I believe he reset UI-View and restarted the
TNC remotely. He'll be at the site tomorrow if anything more needs to
be done.
> What's your anti-dupe time on BALDI? You'll notice that in both cases,
> BALDI acted upon the WIDE1-1, and then later on acted upon the WIDE6,
> but at WIDE6-3 in both instances. Yet in the rules that you listed,
> you have WIDE2 as an alias, with a hop limit of 2. Something doesn't
> jive here... According to the rules, you'll only act upon WIDE2-2 and
> WIDE2-1... you also say that WIDE1-1 with a hop limit of 1 is
> disabled. The packets above tells us that this is not so. Unless
> there's another BALDI out there, your rules are not what is in the
> digipeater.
The dupetime is 30 (default?). If you look at my message traffic
today, you'll see that I changed the digipeating rules. Before
2009-10-27 20:20:10 UTC, the hoplimit was 3, so that's why it was
digipeating WIDE6-3. I changed the settings to quiet BALDI down a bit.
It sits very high above a dense APRS area and doesn't need to be
passing 3-hop packets (WA7-7 is a special case).
Another BALDI out there? There's a back-story there. N7OEP used to
operate a BALDI digipeater from the next building over, but the
digipeater has gone down for multiple times for an extended period.
One time it was an antenna problem and as soon as our backup BALDI
went on the air, original BALDI started getting out to the world. The
last time it went down, he did not fix it. We haven't heard it. Maybe
for some reason old BALDI is alive again and feebly digipeating on
WIDE1-1?
Tom KD7LXL
