<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Liz,<br>
<br>
It looks like your path is:<br>
<br>
<span class="raw_line">2014-10-14 04:10:42 UTC: <b><a
href="http://aprs.fi/?c=raw&limit=&call=VK2XSE-9">VK2XSE-9</a></b>>ST16Q3,WIDE2-2,qAR,<a
href="http://aprs.fi/?c=raw&limit=&call=VK2XSE-1">VK2XSE-1</a>:`J]cmRp>\]"53}Escaped from work=</span><br>
<span class="raw_line"></span><br>
You have captured a 2ACT record direct:<br>
2014-10-13 07:19:21.491 VK2XSE-1 R
VK2ACT-8>APTT4,WIDE1-1,WIDE2-1:/071920h3416.08S/14613.83Ea328/021007
out and about/A=003281<br>
<br>
So (s)he uses WIDE1-1,WIDE2-1.<br>
<br>
... and RGF repeats this path setup:<br>
<br>
2014-10-13 06:57:34.174 VK2XSE-1 R
VK2ACT-8>APTT4,VK2RGF-1*,WIDE2-1:/065731h3431.49S/14618.43Ea276/056007
out and about/A=003281<br>
<br>
Likewise for KNV:<br>
<br>
<span class="raw_line">2014-10-14 04:43:30 UTC: <b><a
href="http://aprs.fi/?c=raw&limit=&call=VK2KNV-9">VK2KNV-9</a></b>>STS1P7,WIDE1-1,WIDE2-1,qAR,<a
href="http://aprs.fi/?c=raw&limit=&call=VK2XSE-1">VK2XSE-1</a>:`J,I!"}v/]"5B}=</span><br>
<span class="raw_line">2014-10-14 04:45:33 UTC: <b><a
href="http://aprs.fi/?c=raw&limit=&call=VK2KNV-9">VK2KNV-9</a></b>>STS0S2,<a
href="http://aprs.fi/?c=raw&limit=&call=VK2RGF-1">VK2RGF-1*</a>,WIDE2-1,qAR,<a
href="http://aprs.fi/?c=raw&limit=&call=VK2XSE-1">VK2XSE-1</a>:`J*r!"|v/]"5J}=</span><br>
<span class="raw_line"><br>
<br>
So, that suggests that RGF is set to repeat WIDE1-1 and NOT
WIDE2-?... setup as a so called 'fill in' digi.<br>
<br>
Try setting a path of WIDE1-1,WIDE2-2 in your radio and see if
that solves the problem.<br>
<br>
The whole source routing this is a failure and outdated, the NEW N
Paradigm is a botch.<br>
<br>
The better way to configure a fill in dig is to set it so that it
will only repeat packets that have not yet been repeated (ie that
there are no ,CALLSIGN*, strings in the VIA list.<br>
<br>
</span><br>
<span class="raw_line"><img
src="cid:part8.07060008.07080104@owenduffy.net" alt=""><br>
<br>
Here is a graph of distribution of hop counts received here
yesterday. It was calculated without looking at WIDE strings, in
fact I strip them from the log to get to the real data. It does
depend on digis doing TRACE substitution... and that cannot be
guaranteed (see rule #1, it is all a botch), but most end users
request WIDE which by Bob's rules should be traced in the digis.
Good digis are setup to trace WIDE, TRACE and RELAY.<br>
<br>
Who does 4 hops? in recent days here, VK2TRB (who apparently
thinks his WX has wide appeal) and VK2XSO (isn't he one of the
guiding lights on APRS in NSW).<br>
<br>
Anyway, try WIDE1-1,WIDE2-2 (rather than </span><span
class="raw_line"><span class="raw_line">WIDE1-1,WIDE2-1 as aprs.fi
reports are not correct if you originate this path).<br>
<br>
People may object to this as they say it orders up 3 hops, but
it should be the digi that applies its own rules (tailored to
its location, existence of iGates, neighbours etc) about whether
it is appropriate to repeat a packet further.<br>
<br>
</span>Owen<br>
</span><br>
<pre class="moz-signature" cols="72">--
========================================================================
Owen Duffy (<a class="moz-txt-link-abbreviated" href="mailto:owen@owenduffy.net">owen@owenduffy.net</a>)
VOIP Phone: +61 2 4858 0458 (02) 4858 0458
Note: VOIP phone quality is degraded due to Telstra/Bigpond failure to
deliver reasonable speed on an 8Mb/s ADSL service. Fortunately we still
have a POTS line to fall back on, well until NBN eliminates POTS!!!
Mobile: +61 4 27 105 937 0427 105 937
========================================================================
</pre>
</body>
</html>