[aprssig] Bob Not Using His Own Advice?

[Keith VE7GDH]

Rick (callsign?) wrote...

> I don't see the asterisk which would indicate that the packet was
> actually digi'd by a RELAY, so it may not exist....

>From the one packet viewed yesterday, it was digi'd by a relay but I didn't
save the raw packet.

20070919213744,WB4APR-9>S8UYLZ,RELAY,KV3B-2*,WIDE2-1,
qAo,N8YSZ-4:'h9
l 
K\]147.075MHz & v-Alert=

The above went through a RELAY digi before getting to KV3B-2, and was gated
by N8YSZ-4...     www.aprs-is.net/q.htm
qAO - (letter O) Packet was received via a client-only port and the FROMCALL
does not match the login.

20070920040307,WB4APR-9>S9PPLZ,RELAY,WIDE2-2,
qAS,N3HU:'iX
l 
K\]147.075MHz & v-Alert=

In the above, it was heard direct by N3HU.
qAS - Packet was received from another server or generated by this server.
The latter case would be for a beacon generated by the server... The
callSSID following the qAS is the login or IP address of the first
identifiable server...

There be RELAYs out there! Someone living in the area could look around at 
all the APRS stations on the map that are conceivably in range and try 
digipeating through them to see which ones responded to their own callsign. 
With the APRS test station running low power and a 3-4 element beam, they 
could narrow down the direction of the whatever is responding to RELAY. RDF 
from another station could also be employed. It would be trickier if there 
was more than one, but someone with time on their hands could finally park 
in the shadow of the antenna at the suspect digi(s) and beacon with a path 
of RELAY into a dummy load and see if that particular digi responds.

73 es cul - Keith VE7GDH
--
"I may be lost, but I know exactly where I am!"