[aprssig] Valid destination address in APRS packets?

[James Washer]

Keith, I'm KG7HH..

>From data collected from the western US over the past 48 hours. We have the following stations using WIDExxx for their destinations. If anyone cares to contact these individuals, that would be great.

 - jim

p.s. I especially love the WIDE7-7. Dunno if we should contact that guy, as I'd hate to see him 'fix' his destination and set WIDE7-7 as his path.


WIDE
        THORN
        XE1YMY
        N8QVR-10
        KC5YSM-2
WIDE1
        N7RXY
        VE5RON-15
WIDE1-1
        KO6JF
        N3KQX-15
        KD7JZ-1
        N7RXY
        KA0ADZ-1
        KB0VKT-2
        VE5RON-15
        KA9FLX
WIDE2
        N7NVP
WIDE2-1
        KD7ZMI-1
        KD7ZMI
WIDE2-2
        KA5WRG
        W2ALI-7
        N0YXV
        NOCALL
        WD0BIA
        KF6ECO
        KF7EU
        KB0VZQ
        N6EDL-10
        N7GPS
        W7AI
        KD7YOH-1
        KE6CBJ
        KC5CYY
        W5DCR-3
WIDE3-3
        W5DCR-3
WIDE4-4
        KL7JHR
WIDE5-5
        VE7IMD-1
        W5DCR-3
WIDE7-7
        W5DCR-3

On Tue, 16 Aug 2005 13:14:36 -0700
"Keith - VE7GDH" <ve7gdh at rac.ca> wrote:

> Jim (callsign?) wrote on 16/08/2005
> 
> > While looking at traffic from APRS-IS, I see about 0.5% of the packets
> > having the form below, where the destination address seems to contain the
> > "path" rather the destination/software_version/mic-e/etc.
> > 
> > Is this a "legal" use of the destination address?
> > 
> > Is this perhaps a hiccup where the sender left the destination address
> > null? (other beacons trimmed)
> > VE7IMD-1>WIDE5-5,qAo,VE7DID-1:@161649z4901.09N/12305.12W_022/000g000t065r000p000P000h65b10168wDAV> 
> 
> I dunno about the others, but I looked at VE7IMD-1 because it is not too far from me... well, it would be a long swim. I viewed the station details right on the map in UI-View32 and then went to findu.com to view the raw data: www.findu.com/cgi-bin/raw.cgi?call=ve7imd-1&start=24&length=24&time=1 and it does indeed appear to not have a destination address... unless the WIDE5-5 is actually erroneously entered as the destination. Either way, it is a bit strange. If the WIDE5-5 is really a path and not an odd-ball destination address, it isn't a very good path (detrimental to the APRS network) considering  it is located just south of Vancouver BC and north of Seattle WA and Victoria BC, with lots of activity on RF. At least if it is an erroneously entered destination, it won't be banging away as WIDE5-5... I think.
> 
> His other weather station has a TCPIP connection.
> 
> Plain no-SSID (OK... it's zero) VE7IMD is also using a not very "APRS-network friendly" TRACE2-2. All of the time. At least it is only every half hour. Paths that include RELAY, WIDE, TRACE, and TRACEn-n are obsolete and should not be used. Long paths like WIDE5-5 should not be used except in exceptional circumstances. It has long ago been hashed out (at least in North America) that WIDE2-2 is the acceptable path for home use, and WIDE1-1,WIDE2-1 for mobiles unless WIDE2-2 works for them. I don't know if Don is on this list, but I BCCd this reply to his @rac.ca address that is in his status text. If Don isn't on the list and if I get a reply directly from him either on the path or lack of destination address, I'll post a copy of his reply.
> 
> Comments from others?
> 
> 73 es cul - Keith VE7GDH
> --
> "I may be lost, but I know exactly where I am!"
> 
> 
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig