[OZAPRS] more strange stuff coming out of VK2RHR-1

[Josh]

I think they're both sending a path of WIDE1-1,WIDE2-1 and RGI is
messing it up.
They're leaving RHR-1 with the path ,VK2RHR-1*,WIDE1,WIDE2-1 and RGI is
replacing WIDE2-1 with its own callsign.

I hear the original packet as:
VK2XRC-9>ST04U0,WIDE1-1,WIDE2-1:`OX_nz<0x1f>R/'"5t}|"8%T'n|!wd5!|3
Then from RHR-1:
VK2XRC-9>ST04U0,VK2RHR-1,WIDE1*,WIDE2-1:`OX_nz<0x1f>R/'"5t}|"8%T'n|!wd5!|3

I'd be taking a look at RGI's digipeat rules.

- Josh VK2HFF

On 12/11/2017 3:00 PM, Peter VK2MPJ wrote:
> I may be incorrect, but I read that as the two mobile stations may have configs such as
> VK2RHR-1,WIDE1-1
> 
> which if the case is far from ideal, and really would limit their coverage should they leave RHR-1s foot print?
> 
> 2MPJ
> 
>> On 12 Nov 2017, at 2:09 pm, Glen English VK1XX <glenlist at pacificmedia.com.au> wrote:
>>
>> VK2TEQ-9>S3T7V2,VK2RHR-1,WIDE1,VK1RGI-1*:
>> <<UI>>:                              
>> `O[mz[S/]"4{}=  
>>
>> VK2XRC-9>SS56Q0,VK2RHR-1,WIDE1,VK1RGI-1*:
>> <UI>:                                
>> `O'[m-GR/'"3y}|"y%S'n|!w-t!|3 
>>
>>
>>
>>
>> _______________________________________________
>> 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
>