[OZAPRS] VK2RHR-1 raw

Thu Nov 16 17:26:53 AEDT 2017

If your local TX iGate is configured correctly, you should still see the traffic. It’ll just come from the APRS-IS not direct via the original RF.

Don’t forget, the region paths should really only apply to fixed stations. Mobiles should still be WIDE1-1,WIDE2-1 (or 2-2 if they must), as if they used regional paths, they would not be digi’d if they travelled outside their local area.

Pete
2MPJ

> On 16 Nov 2017, at 7:13 am, Warren_Brown <warbn at telstra.com> wrote:
> 
> The draw back for me on Area or Region based paths is it hides traffic from the near neighbours.
> This could result in a station just south of the VK2 border in VK3 not seeing any traffic from Albury.
> 
> 73,
> Warren vk3byd
> 
> -----Original Message-----
> 
> Just quickly while i have a few minutes
> 
> This idea of region or area based digipeating is something I tried to implement a while ago, but it fell by the wayside This is where the “SENSW” came from. Back when I first become involved with RGI-1 & RBM-1, it was when we were upgrading to the “new” WIDEn-N paradigm.
> The idea behind SENSW would serve an area of VK1, Riverina, the Snowy region, and out towards the coast with Nowra being the eastern most point. 
> Riverina though by the looks of it only adopted “NSW"
> 
> Then from memory there was “SYD” which I THINK also incorporated down into the highlands?? I cannot remember for certain.
> 
> Looking at the BTEXT coming from RHR-1, it says it’s a W1 digi aka Fill-In, but it’s overlay does not agree. The overlay should be a ‘1’
> If it was a WIDE1-1, then it should only respond to stations with a path of WIDE1-1 and nothing else. The quick cursory look I just had, seems to indicate this is so, I’ll look closer later
> 
> If a station were to hit RHR-1 with a path of WIDE1-1,WIDE2-1, then yep it’ll hit RGI-1 and RGI will digi accordingly, there endeths the packet though.
> 
> I think the traffic issue is more to do with users and their paths rather than digi configs.  WIDE1-1,WIDE2-2 is excessive to many stations.
> 
> Pete
> 2MPJ
> 
>> On 15 Nov 2017, at 4:20 pm, Glen English VK1XX <glenlist at pacificmedia.com.au> wrote:
>> 
>> With well sited digipeaters that look over populated areas as well as 
>> gateways inland I am sure this is not a new problem, like all the 
>> canberrra UI aprs traffic being digi'ed over into the riverina.
>> 
>> Over the next couple of months, we'll fix that with a combination user 
>> education, user path change (like WIDE1-1, CBR) etc, UHF facility, in 
>> addition to more certain measures (temporal filters, !budlists....)
>> 
>> -glen
>> 
>> On 15/11/2017 4:06 PM, Josh VK2HFF wrote:
>>> Maybe we south-western sydney folk should adopt a path of just 
>>> WIDE1-1 for fixed stations etc, to reduce the amount of unnecessary 
>>> traffic sent south with hops remaining?
>>> A quick check of my last few months logs shows that only about 100 
>>> unique VK2 callsigns have been digipeated by RHR.
>>> I'm #6 on the list by packet count, so will change my path tonight.
>>> 
>>> - Josh VK2HFF
>>> 
>>> 
>>> On 15/11/2017 2:43 PM, Graeme wrote:
>>>> Hello Glen,
>>>> 
>>>> Sydney proper does not hit RHR - it's mostly only after leaving 
>>>> Sydney that RHR comes into play and vehicles travelling south are 
>>>> not necessarily heading into Canberra, bypassing Canberra mostly 
>>>> past or through the Riverina heading into Victoria or SA, with 
>>>> others heading west from Yass. Users wouldn't reconfigure their 
>>>> paths for out of Sydney travelling so would remain wide1, wide2-1 
>>>> then get dropped prematurely by RGI after only having been first heard by RHR.
>>>> 
>>>> I don't agree with VK2XRX-9>S3T8P9,VK2RHR-1,WIDE1*,WIDE2-1 being 
>>>> dropped/ignored by RGI unless all people who might travel out of 
>>>> urban areas change to wide1,wide2-2 permanently which I suspect will 
>>>> cause far more congestion.
>>>> 
>>>> Graeme
>>>> 2HFG
>>>> 
>>>> -----Original Message----- From: Glen English VK1XX
>>>> Sent: Wednesday, November 15, 2017 1:32 PM
>>>> To: ozaprs at aprs.net.au
>>>> Subject: Re: [OZAPRS] VK2RHR-1 raw
>>>> 
>>>> 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
>>>> 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
>> 
>> 
>> _______________________________________________
>> 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
> 
> _______________________________________________
> OZAPRS mailing list
> OZAPRS at aprs.net.au
> http://lists.aprs.net.au/mailman/listinfo/ozaprs