[aprssig] RADIO paths in APRS Servers

[Andrew Rich (Home)]

Here is one for you, who or what is "WIDE2" ?

VK4UN-1>APU25N,VK4RSR-3,WIDE2*,qAR,VK4HW-4:=2621.48SS15259.33E#VHF Igate & 
Digipeter {UIV32}


----------------------------------------------------------
Andrew Rich
Amateur Radio Callsign VK4TEC
email: vk4tec at tech-software.net
web: www.tech-software.net
----- Original Message ----- 
From: "Lynn W. Deffenbaugh (Mr)" <ldeffenb at homeside.to>
To: <bruninga at usna.edu>; "TAPR APRS Mailing List" <aprssig at tapr.org>
Sent: Saturday, August 08, 2009 2:21 AM
Subject: Re: [aprssig] RADIO paths in APRS Servers


> Robert Bruninga wrote:
>>
>> Good question.  Yes, but with the caveat that I mentioned:
>> "(Some WIDE1-1's will never be)."
>> And a few other cases of WIDE1-1 digipeating:
>>
>> VAST MAJORITY:  Even though most mobiles use the path of
>> WIDE1-1,WIDE2-1 so that they can use any convenient fill-in
>> digis, I would guess that 98% of the time, those packets are
>> first picked up by a full-new-N digi.  Hence the vast majority
>> of these will get the call insertion and traceability:
>> K4HG>APRS,W4XYZ*,WIDE1,WIDE2-1:...
>>
>> SMALL MINORITY:  Next, some WIDE1-1 fill-in digi's do use fully
>> capable TNC's and these also will do callsign insertion, or
>> substitution:
>> K4HG>APRS,W4XYZ*,WIDE1,WIDE2-1:...
>>
>>
> Wouldn't these two cases actually come out with the WIDE1 marked used
> (WIDE1*) with their callsign inserted before that as in:
>
> K4HG>APRS,W4XYZ,WIDE1*,WIDE2-1:...
>
> There's documentation on http://www.nwaprs.info/widen-n.htm that implies 
> that some buggy KPC-3 (xxxx-7265 or earlier) that will show what you show, 
> but it also describes that as "incorrect behavior" (in yellow at the 
> bottom of the page).
>
> Lynn (D) - KJ4ERJ - Still testing my understanding
>
> PS.  Although I HAVE seen what you show in your example, most of the 
> digi'd packets I've looked at show the WIDE1*, not W4XYZ*.
>
> PPS.  However, if you actually have a chance to see the raw AX.25 packet, 
> there's an amazing lack of consistency on whether or not stations prior to 
> the final used one are marked used or not.  Consider the following paths 
> intercepted from my TT4's KISS stream directly off the RF.  Note how 
> AI4LE-1 and KA1VRF-7 mark their source call "used" and the fact that all 
> inserted calls are actually marked used although if you look at the raw 
> packets coming over APRS-IS, only the last used station is so marked.
>
> W9DVM>APTW01,WC4PEM-10*,WX4MLB-3*,WIDE2*:....
> AI4LE-1*>RXRV4T,KC4ZVV-2*,WC4PEM-14*,WX4MLB-3*,WIDE3*:....
> KF4KCI-7*>R7RQ2S,W4OT-3*,WIDE1*,WIDE2-2:`l:....
> KF4KCI-7*>R7RQ2S,W4OT-3*,WIDE1*,WC4PEM-13*,WIDE2-1:`l:....
> NI4CE-12>APN391,WC4PEM-14*,WC4PEM-15*,WIDE2*:....
> WC4PEM-11>APN391,WIDE2-2:....
> WC4PEM-13>APN391,WIDE2-2:....
> WC4PEM-13>APN391,WX4MLB-3*,WIDE2-1:....
> W9GPI>APT311,KC4JQH-10*,WIDE1*,WC4PEM-14*,WIDE2-1:....
> W9GPI>APT311,KC4JQH-10*,WIDE1*,WC4PEM-14*,WX4MLB-3*,WIDE2*:....
> KG4JSZ>APTW01,WC4PEM-15*,WC4PEM-13*,W4OT-3*,WIDE3*:....
> AI4LE-1*>RXRV4T,WC4PEM-15*,WX4MLB-3*,WIDE3-1:....
> KA1VRF-7*>R7SV6P,W4OT-3*,WIDE1*,WIDE2-1:....
> KG4CWC-9>2VTV6V,K4PKT-3*,W4OT-3*,WIDE2-1:....
> KG4CWC-9>2VTV6V,K4PKT-3*,W4OT-3*,WX4MLB-3*,WIDE2*:....
> N4APD-1>APTW01,WC4PEM-14*,WIDE1*,WX4MLB-3*,WIDE2-1:....
> AI4LE-1*>RXRV4T,W4OT-3*,WX4MLB-3*,WIDE3*:....
> KG4YZY-11>APU25N*,WC4PEM-14*,WIDE2-1:....
> KG4YZY-11>APU25N*,WC4PEM-14*,WX4MLB-3*,WIDE2*:....
>
> Unfortunately, none of these packets show the non-used before used that I 
> was trying to show, but now that I think about it, those may result from a 
> Digi responding to a preemption (out of order) path as described on 
> http://wiki.argentdata.com/index.php?title=Digipeater_Setup#Preemption?
>
>
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig


--------------------------------------------------------------------------------



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.392 / Virus Database: 270.13.45/2286 - Release Date: 08/06/09 
18:17:00