<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font face="Arial">Thanks Matthew.</font></p>
<p><font face="Arial">Ray vk2tv</font><br>
</p>
<br>
<div class="moz-cite-prefix">On 15/11/17 14:02, Matthew Cook wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAE+2d_1N=9fEiedTnVWTfihaMHeFaQN6g2Edv2ZjYU9SpWAyHg@mail.gmail.com">
<div dir="ltr">Hi Gordo,
<div><br>
</div>
<div>The "new method" is simply how digipeaters insert their
call signs into the proto path and do the respective
termination. You'll find two implementations of this in use,
as per my original email to Glen. Both are valid and in use
within APRS networks across the world. The following URL goes
into a little more information.</div>
<div><br>
</div>
<div><a href="http://info.aprs.net/index.php?title=Digipeater"
moz-do-not-send="true">http://info.aprs.net/index.php?title=Digipeater</a><br>
</div>
<div><br>
</div>
<div>Unfortunately all digipeaters are not equal, some better
than others. You need a lot of RAM in a digipeater to be able
to have enough cache to make intelligent decisions, which
rules out many Z80 based TNC's.</div>
<div><br>
</div>
<div>73</div>
<div><br>
</div>
<div>Matthew</div>
<div>VK5ZM</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 15 November 2017 at 12:00, Gordon
Taylor <span dir="ltr"><<a
href="mailto:gordon@thetaylorclub.com" target="_blank"
moz-do-not-send="true">gordon@thetaylorclub.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Watching
this with interest as it helps get a better understanding of
the traffic flows.<br>
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.<br>
<br>
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.<br>
<br>
<br>
Regards<br>
<br>
Gordo VK4VP<br>
<span class=""><br>
-----Original Message-----<br>
From: OZAPRS [mailto:<a
href="mailto:ozaprs-bounces@aprs.net.au"
moz-do-not-send="true">ozaprs-bounces@aprs.<wbr>net.au</a>]
On Behalf Of Glen English VK1XX<br>
Sent: Wednesday, 15 November 2017 10:06<br>
To: <a href="mailto:ozaprs@aprs.net.au"
moz-do-not-send="true">ozaprs@aprs.net.au</a><br>
Subject: Re: [OZAPRS] VK2RHR-1 raw<br>
<br>
</span>
<div>
<div class="h5">Hi Matthew<br>
<br>
thanks for the write up.<br>
<br>
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<br>
<br>
Something for me to write into the source code.<br>
<br>
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) .<br>
<br>
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 ....<br>
and it is also '2nd adjacent WIDE'. no benefit for
users for RGI to digi its traffic.<br>
<br>
-glen<br>
On 15/11/2017 10:51 AM, Matthew Cook wrote:<br>
> I'd be suggesting that VK2RHR-1 is an older APRS
implementation<br>
> (possibly a TNC-2 clone with UI-DIGI or Kantronics
TNC) than VK1RGI.<br>
> If you watch the asterisk that is telling you
what's happening.<br>
><br>
> The old WIDEn-N technique was to decrement N and
insert the digi<br>
> callsign, when -0 was achieved to append WIDEn* to
show it has been<br>
> terminated. The new WIDEn-N technique is to drop
the WIDEn* on the<br>
> end and simply use the Callsign of the digi
terminated with an asterisk.<br>
><br>
> So in your example VK2RHR-1 has used the old
digipeter method and<br>
> VK1RGI-1 has used the new, , *_both are still
valid_ !!!*<br>
><br>
> There were flame wars on the APRS TAPR mailing list
over this issue<br>
> for many years, the argument was the WIDEn* on the
end was redundant<br>
> and the newer method was more efficient....
however legacy equipment<br>
> meant it was difficult (read people reluctant) to
change, that horse<br>
> had bolted.<br>
><br>
> 73<br>
><br>
> Matthew<br>
> VK5ZM<br>
><br>
><br>
> On 15 November 2017 at 08:36, Glen English VK1XX<br>
> <<a href="mailto:glenlist@pacificmedia.com.au"
moz-do-not-send="true">glenlist@pacificmedia.com.au</a>
<mailto:<a href="mailto:glenlist@pacificmedia.com.au"
moz-do-not-send="true">glenlist@pacificmedia.<wbr>com.au</a>>><br>
> wrote:<br>
><br>
> here is what it looks like going into 1RGI :<br>
><br>
> Now I thought that RHR should have REPLACED
WIDE1 with its<br>
> callsign ????<br>
> ------<br>
><br>
> Digipeater WIDE1 (probably VK2RHR-1) audio
level = 69(34/18) [NONE]<br>
> __|||||||<br>
><br>
> [0.5] VK2XRX-9>S3T8P9,VK2RHR-1,<wbr>WIDE1*,WIDE2-1:`O&ilSpk/'"54}|<wbr>3<br>
> MIC-E, truck, Byonics TinyTrack3, In Service<br>
><br>
><br>
> ginini generates :<br>
><br>
> [0H] VK2XRX-9>S3T8P9,VK2RHR-1,<wbr>WIDE1,VK1RGI-1*:`O&ilSpk/'"54}<wbr>|3<br>
><br>
><br>
<br>
______________________________<wbr>_________________<br>
OZAPRS mailing list<br>
<a href="mailto:OZAPRS@aprs.net.au"
moz-do-not-send="true">OZAPRS@aprs.net.au</a><br>
</div>
</div>
<a href="http://lists.aprs.net.au/mailman/listinfo/ozaprs"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.aprs.net.au/<wbr>mailman/listinfo/ozaprs</a><br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<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>