[OZAPRS] VK2RHR-1 raw

[Matthew Cook]

I think that is how it's supposed to work, again I've not actually played
with aliases in digi's like this before.

In your use case;

VK2XRX-9>S3T8P9,VK2RHR-1,WIDE1*,RIV1-2, WIDE2-1:

I'd have expected RGI to have generated

VK2XRX-9>S3T8P9,VK2RHR-1,WIDE1*,VK1RGI-1*,RIV1-1,WIDE2-1

Hmm thinking about that a little if that got to air then you'd then bounce
that off any adjacent WIDE2's as well, effectively looping that back into
Sydney.

There is nothing saying you need to use the WIDEn-N paradigm for the
concept of the RIV (ie ISS and satellites) so just perhaps getting users to
send;

VK2XRX-9>S3T8P9,WIDE1-1,RIV, WIDE2-1:

or

VK2XRX-9>S3T8P9,RIV, WIDE1-1, WIDE2-1:

It's then a question of what happens with some of the older generation of
digi's and how they process the proto path.

Again this doesn't get around the issues of looping traffic back off RGI
and into Sydney via the WIDE2 on the end...

Hmm... time to find a coffee and put the thinking hat back on.

73

Matthew
VK5ZM

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

> Hi Matt
>
> Yeah I accept. right... area nomenclature.
>
> Good idea.
>
> And yeah I agree 100%  with your traffic WIDE2-2 observation.
>
> Hmm, so if RHR transmits :
>
> VK2XRX-9>S3T8P9,VK2RHR-1,WIDE1*,RIV1-1, WIDE2-1:
>
> Ginini would look for the first non used field and find RIV1-1 , and
> generate :
>
> VK2XRX-9>S3T8P9,VK2RHR-1,VK1RGI-1*
>
> there might be extensions or ideas from that.
>
> if ginni received :
>
> VK2XRX-9>S3T8P9,VK2RHR-1,WIDE1*,RIV1-2, WIDE2-1:
>
> would ginini decrement the RIV section  and generate :
>
> VK2XRX-9>S3T8P9,VK2RHR-1,VK1RGI-1*,RIV1-1
>
> ??
>
>
> On 15/11/2017 2:13 PM, Matthew Cook wrote:
> > That's going to push the network congestion for all WIDE2's adjacent
> > to RHR through the roof, since you've now got three hops.
> >
> > Why not look at another alias that is specific to RGI (RIV1-1) that
> > would allow users that want to push traffic over the hill do so.   Off
> > the top of my head (without testing) the Digi's here in Adelaide have
> > a second alias of ADL2, meaning fixed stations don't send WIDE1-1,
> > WIDE2-1 they just send ADL2-2 to blast out two hops etc.   It would be
> > interesting to see if;
> >
> > WIDE1-1, RIV1-1, WIDE2-1 would work, so upon receipt of
> >
> > VK2XRX-9>S3T8P9,VK2RHR-1,WIDE1*,RIV1-1, WIDE2-1:
> >
> > you accept ?
> >
> > Regards
> >
> > Matthew
> > VK5ZM
> >
> > On 15 November 2017 at 13:02, Glen English VK1XX
> > <glenlist at pacificmedia.com.au <mailto:glenlist at pacificmedia.com.au>>
> > wrote:
> >
> >     Hi Graeme ,
> >
> >     I take ur point. we'll see what overs have to say .
> >
> >     The thing is the SPIRIT of WIDE2-1 in sydney would not include
> >     Ginini .....
> >
> >     For that, a user could run WIDE2-2
> >
> >     so, if I treat WIDE2-1 out of RHR as a drop  but 22-2 from RHR as a
> >     pass, that will be fine.
> >
> >     on receipt of this :
> >     VK2XRX-9>S3T8P9,VK2RHR-1,WIDE1*,WIDE2-1:
> >
> >     RGI should treat as DROP/IGNORE
> >
> >     on receipt of this :
> >     VK2XRX-9>S3T8P9,VK2RHR-1,WIDE1*,WIDE2-2:
> >
> >     RGI would generate this : (as it considers RHR a WIDE2)
> >
> >     VK2XRX-9>S3T8P9,VK2RHR-1,VK2RGI-1*,
> >
> >     you would get the traffic that way.
> >
> >     comments ?
> >
> >
> >     On 15/11/2017 12:59 PM, Graeme wrote:
> >     > Glen,
> >     >
> >     > RHR only draws from south of Sydney from around the
> >     > Campbelltown/Camden area which is easily a day's return drive that
> I
> >     > do myself from the eastern Riverina and therefore of interest to
> >     > people in the Riverina.  I don't think that RGI should exclude
> RHR's
> >     > messages.
> >     >
> >     > Graeme
> >     > 2HFG
> >
> >
> >     _______________________________________________
> >     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/b5ed3c61/attachment-0001.html>