<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font face="Arial">Gordon, all,<br>
</font></p>
<p><font face="Arial">The "new", WIDEn-N, paradigm was introduced in
1994 and AFAIK it's still the current format for specifying APRS
paths. I'd be happy to take advice if I'm wrong!<br>
</font></p>
<p><font face="Arial">You might be interested in this 2014 item on
the TAPR sig which goes into a detailed discussion (with
examples) for various WIDEn-N configurations.
<a class="moz-txt-link-freetext" href="http://www.tapr.org/pipermail/aprssig/2014-May/043317.html">http://www.tapr.org/pipermail/aprssig/2014-May/043317.html</a></font></p>
<p><font face="Arial">Ray vk2tv<br>
</font></p>
<p><font face="Arial"></font><br>
</p>
<div class="moz-cite-prefix">On 15/11/17 12:30, Gordon Taylor wrote:<br>
</div>
<blockquote type="cite"
cite="mid:015201d35db1$50231f70$f0695e50$@thetaylorclub.com">
<pre wrap="">Watching this with interest as it helps get a better understanding of the traffic flows.
However I note there is a 'new' method. I was under the impression that the WIDEn-N was the new method. Is this newer method something we are going to adopt, I imagine to change the UI-Digi code would require the source code owner to update.
What would be nice in a simplistic sense is when a packet gets digipeated by a local digi, bounces down to another and comes back, the local digi had the intelligence to know that it is the same packet of information just with some extra path info so it doesn’t repeat it again.
Regards
Gordo VK4VP
-----Original Message-----
From: OZAPRS [<a class="moz-txt-link-freetext" href="mailto:ozaprs-bounces@aprs.net.au">mailto:ozaprs-bounces@aprs.net.au</a>] On Behalf Of Glen English VK1XX
Sent: Wednesday, 15 November 2017 10:06
To: <a class="moz-txt-link-abbreviated" href="mailto:ozaprs@aprs.net.au">ozaprs@aprs.net.au</a>
Subject: Re: [OZAPRS] VK2RHR-1 raw
Hi Matthew
thanks for the write up.
Hmm so the 'new' method and code, in this case direwolf, really needs to be smarter about the way it handles the old (but still valid ) RHR method. It's really a defficiency in handling the legacy stuff at RGI
Something for me to write into the source code.
On a separate argument, I consider RHR-1 a WIDE digi, and stations digipeating through it with W2-1 should be sent and terminated at RHR (IE will be the last digi) .
I've added RHR to the blacklist for UI digi for the moment so we don't digi a whole load of sydney APRS traffic over the entire Riverina ....
and it is also '2nd adjacent WIDE'. no benefit for users for RGI to digi its traffic.
-glen
On 15/11/2017 10:51 AM, Matthew Cook wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I'd be suggesting that VK2RHR-1 is an older APRS implementation
(possibly a TNC-2 clone with UI-DIGI or Kantronics TNC) than VK1RGI.
If you watch the asterisk that is telling you what's happening.
The old WIDEn-N technique was to decrement N and insert the digi
callsign, when -0 was achieved to append WIDEn* to show it has been
terminated. The new WIDEn-N technique is to drop the WIDEn* on the
end and simply use the Callsign of the digi terminated with an asterisk.
So in your example VK2RHR-1 has used the old digipeter method and
VK1RGI-1 has used the new, , *_both are still valid_ !!!*
There were flame wars on the APRS TAPR mailing list over this issue
for many years, the argument was the WIDEn* on the end was redundant
and the newer method was more efficient.... however legacy equipment
meant it was difficult (read people reluctant) to change, that horse
had bolted.
73
Matthew
VK5ZM
On 15 November 2017 at 08:36, Glen English VK1XX
<<a class="moz-txt-link-abbreviated" href="mailto:glenlist@pacificmedia.com.au">glenlist@pacificmedia.com.au</a> <a class="moz-txt-link-rfc2396E" href="mailto:glenlist@pacificmedia.com.au"><mailto:glenlist@pacificmedia.com.au></a>>
wrote:
here is what it looks like going into 1RGI :
Now I thought that RHR should have REPLACED WIDE1 with its
callsign ????
------
Digipeater WIDE1 (probably VK2RHR-1) audio level = 69(34/18) [NONE]
__|||||||
[0.5] VK2XRX-9>S3T8P9,VK2RHR-1,WIDE1*,WIDE2-1:`O&ilSpk/'"54}|3
MIC-E, truck, Byonics TinyTrack3, In Service
ginini generates :
[0H] VK2XRX-9>S3T8P9,VK2RHR-1,WIDE1,VK1RGI-1*:`O&ilSpk/'"54}|3
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
OZAPRS mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OZAPRS@aprs.net.au">OZAPRS@aprs.net.au</a>
<a class="moz-txt-link-freetext" href="http://lists.aprs.net.au/mailman/listinfo/ozaprs">http://lists.aprs.net.au/mailman/listinfo/ozaprs</a>
</pre>
</blockquote>
<br>
</body>
</html>