[OZAPRS] VK2RHR-1 raw

Matthew Cook vk5zm at bistre.net
Wed Nov 15 12:30:00 AEDT 2017


I lost hours grep-ing through logs and APRS.fi when I first started
launched my own self built APRS TX in a high altitude balloon.  A path of
WIDE1-1, WIDE2-1 wreaked havoc on the entire VK5 & VK3 network with a radio
horizon of 800kms in any direction, I don't think it caused much havoc in
VK2/1.

I'm curious about how RGI needs to be smarter in the way it handles the
traffic from RHR ?

I think Dom mentioned that RHR is configured as WIDE1 so using the black
list will stop the traffic over the hill both ways for those two nodes,
however if any other WIDE2's can hear RGI packets will escape for one more
hop.

73

Matthew
VK5ZM

On 15 November 2017 at 10:36, Glen English VK1XX <
glenlist at pacificmedia.com.au> wrote:

> 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:
> > 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
> > <glenlist at pacificmedia.com.au <mailto:glenlist at pacificmedia.com.au>>
> > 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
> >
> >
> >     _______________________________________________
> >     OZAPRS mailing list
> >     OZAPRS at aprs.net.au <mailto:OZAPRS at aprs.net.au>
> >     http://lists.aprs.net.au/mailman/listinfo/ozaprs
> >     <http://lists.aprs.net.au/mailman/listinfo/ozaprs>
> >
> >
> >
> >
> > _______________________________________________
> > OZAPRS mailing list
> > OZAPRS at aprs.net.au
> > http://lists.aprs.net.au/mailman/listinfo/ozaprs
>
>
> _______________________________________________
> OZAPRS mailing list
> OZAPRS at aprs.net.au
> http://lists.aprs.net.au/mailman/listinfo/ozaprs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.aprs.net.au/pipermail/ozaprs/attachments/20171115/180e1f93/attachment.html>


More information about the OZAPRS mailing list