[OZAPRS] APRS- UI digi question
Matthew Cook
vk5zm at bistre.net
Tue Oct 31 16:30:27 AEDT 2017
I'd suggest that there is some gating from the APRS-IS servers to RF going
on.
This is the weather station that is being forwarded;
https://aprs.fi/info/a/NEUTBAY
I've seen this before with some iGates doing weird things with filters.
If anyone from VK5 beacons interstate or overseas and it hits the APRS-IS
servers we see it here locally gated on RF. Makes for some fun when you
see local stations that report being 10,000kms to your North East, you take
a second closer look.
Might be worth contacting the local OP and asking them to investigate a
little further.
73
Matthew
VK5ZM
On 31 October 2017 at 15:26, Josh <vk2hff at vk2hff.ampr.org> wrote:
> Yes, something does look a bit strange there.
> Here's some packets copied from my igate console log:
>
> Heard direct, path is actually just WIDE1-1:
>
> 2017-10-29 06:03:15 VK2NR-5 audio level = 33(11/12) [NONE] |||||||__
> [0.3] VK2NR-5>APRS,WIDE1-1:}NEUTBAY>APRS,TCPIP,VK2NR-5*::BLN2SYDTD:Tide
> 1.19M, Vis 16Km, Cloud 03 Okt, Air Qual 58, UV idx<0x20>
> Source Address is too long. "NEUTBAY" has more than 6 characters.
> Failed to create packet from text. Bad source address
>
> Digipeated through VK2RHR - callsign was inserted but WIDE1-1 not
> substituted?
>
> 2017-10-29 06:03:18 Digipeater VK2RHR-1 audio level = 29(12/13) [NONE]
> |||||||__
> [0.3]
> VK2NR-5>APRS,VK2RHR-1*,WIDE1-1:}NEUTBAY>APRS,TCPIP,VK2NR-5*
> ::BLN2SYDTD:Tide
> 1.19M, Vis 16Km, Cloud 03 Okt, Air Qual 58, UV idx<0x20>
> Source Address is too long. "NEUTBAY" has more than 6 characters.
> Failed to create packet from text. Bad source address
>
>
> Beacon packet from VK2NR-5, path WIDE2-1 (doesn't get digipeated through
> VK2RHR because the path doesn't contain WIDE1-1):
>
> 2017-10-29 06:11:34 VK2NR-5 audio level = 32(12/13) [NONE] |||||||__
> [0.3] VK2NR-5>APRX28,WIDE2-1:=3356.31SI15050.38E&Test Igate -
> APRX-Linux-RaspberryPi
> Position, Igate Generic (please use mor, >40 APRSmax
> S 33 56.3100, E 150 50.3800
> Test Igate - APRX-Linux-RaspberryPi
>
>
> - Josh VK2HFF
>
> On 31/10/2017 3:33 PM, Matthew Cook wrote:
> > I was wondering if you had received that off Air or not, makes more
> > sense now.
> >
> > The path is always processed left to right... WIDE2's (wide area digis)
> > are typically configured to also intercept WIDE1 (fill in digi) as well
> > if they hear them locally on RF. I used to find it easier to read when
> > WIDE1-1 was simply called RELAY...
> >
> > There is something not right with that packet, if I didn't know better
> > it looks like a telemetry packet that has been thrown out onto the
> > network via RF which has promulgated thru the network to VK1RBM via
> > VK2RHR. It appears to me that the packet originated at VK2NR-5 which is
> > itself a APRX digi.. strange... not enough coffee yet to nut that one
> > out... speaking of which time for a brew.
> >
> > 73
> >
> > Matthew
> > VK5ZM
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > On 31 October 2017 at 14:37, Glen English VK1XX
> > <glenlist at pacificmedia.com.au <mailto:glenlist at pacificmedia.com.au>>
> wrote:
> >
> > HI Josh
> >
> > (Carlos- I included a raw TNC dump in my email I am hearing it here)
> >
> > Josh-
> >
> > OK so RHR is using WIDE1-1, and RBM sees WIDE2-1 and that's the end
> of
> > the line.
> >
> > but..... so I misunderstood that a high level WIDE2 digi would 'use
> the
> > WIDE1 address slot ?
> >
> > I thought : IF a high level DIGI used WIDE1-1 then it would
> > automatically decrement the WIDE2-1 in the packet to 2-0 because the
> > 'wide job' had been done by it. IE there has been one WIDE hop and
> the
> > packet was to have no more ?
> >
> > -glen
> >
> >
> > On 31/10/2017 2:21 PM, Josh VK2HFF wrote:
> > > Hi Glen,
> > > VK2RHR is a wide1 digi only, and does callsign substitution in the
> > path.
> > > VK2NR-5 original path would have been WIDE1-1,WIDE2-1, with both
> used
> > > up by the time you see it.
> > >
> > > Josh VK2HFF
> > >
> > >
> > >
> > > -------- Original message --------
> > > From: Glen English VK1XX <glenlist at pacificmedia.com.au
> > <mailto:glenlist at pacificmedia.com.au>>
> > > Date: 31/10/2017 13:32 (GMT+10:00)
> > > To: ozaprs at aprs.net.au <mailto:ozaprs at aprs.net.au>
> > > Subject: [OZAPRS] APRS- UI digi question
> > >
> > > Can anyone tell me why I am seeing VK2NR-5 and not other traffic
> > out of
> > > sydney.
> > >
> > > Someone in sydney might be able to tell me why, or someone else
> might
> > > shed some light. Yes I understand the WIDE etc nomenclature.
> > >
> > > I see there are a few digipeaters and users still expecting/using
> > RELAY
> > > and TRACE ...
> > >
> > > ALot of old digipeaters around on hills that are neglected.
> > >
> > > VK2NR-5>APRS,VK2RHR-1,VK1RBM-1*:
> > > <UI>:
> > > }NEUTBAY>APRS,TCPIP,VK2NR-5*::BLN2SYDTD:Tide 0.73M, Vis 30Km,
> Cloud 01
> > > Okt, Air
> > > Qual 50, UV idx
> > >
> > > I cannot see his original packets of course- that is BEFORE the
> > > substitutions.
> > >
> > > as I understand it if he used WIDE2-2, then VK2RHR-1 would be the
> next
> > > and send WIDE2-1
> > > and VK2RBM-1 would hear WIDE2-1 and since that's the end, just
> > subs its
> > > own call in there.
> > >
> > > The question is also, how come I am not hearing other WIDE2-2s out
> of
> > > sydney via VK2RHR-1 ?
> > >
> > > There is something I do not understand yet.
> > >
> > > I had a look at the igate raw packet dump but that was for some
> other
> > > packets he sent.
> > >
> > > Thanks
> > >
> > > glen
> > >
> > >
> > >
> > > _______________________________________________
> > > 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 <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 <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/20171031/45ba7eef/attachment.html>
More information about the OZAPRS
mailing list