[aprssig] "station which heard ... directly on the radio"

Lynn W. Deffenbaugh (Mr) ldeffenb at homeside.to
Mon May 20 18:39:50 CDT 2013


On 5/20/2013 6:15 PM, Kristoff Bonne wrote:
>
> Well, althou these application where not written by me, I did take the 
> time to have a look at the source-code  of multimonNG. It seams there 
> is no code to add a '*' of the C-bit is set in the SSID part of an 
> address.
>
> However, it's not realy clear how exactly this should be corrected.
>
> I noticed that when you just set the asterisk everywhere where that 
> bit is set, you get paths like this:
> ... to U0QRQ5-0 via ON0WTO-2*,WIDE1-0*,ON0OST-0*
> (just copied this off the air 5 minutes ago).
>
> Is this correct? When I look in the archive of "raw" messages on 
> aprs.fi, I do not see such an paths overthere! The asterisk in only on 
> the last message or the one before that?

The APRS-IS servers "clean up" the used bits and only retain the last 
one.  But if you receive the bit off the air, then I believe you should 
set it in the humanly readable packet and let upstream APRS-IS servers 
do what they feel inclined to do.

>
> On what addresses in the path does there need to be a asterisk?

On every one that has the bit set.

> All addresses with the C-bit set? Only the last? Only the last, or the 
> one before that if the last address in the path is a "WIDE"?

The AX.25 used bit doesn't know anything about aliases.  If the bit is 
set, set the *.


> But what if that WIDE-address at the end of the path does not have a 
> '*' itself?

If it doesn't have an *, then it must not have had a used bit, in which 
case it's still an unused path component.  Who knows, the packet 
originator might have wanted a WIDE as the final component.

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



More information about the aprssig mailing list