[Xastir] findy trails

[BDonnell at ar-northwest.com]

> -----Original Message-----
> From: xastir-bounces at xastir.org [mailto:xastir-bounces at xastir.org]On
> Behalf Of Curt, WE7U
> Sent: Wednesday, June 09, 2004 1:40 PM
> To: soldering fun
> Cc: xastir at xastir.org
> Subject: Re: [Xastir] findy trails
> 
> 
> On Wed, 9 Jun 2004, Curt, WE7U wrote:
> 
> > 
> N4YLC-1>APT311,W6CX-3*,wIDE2-2,qAR,AA6VN-5:/230323h3746.27N/12
> 223.84Wk349/042/A=000052/soldering fun!
> 
> > I ran it through Xastir as a log file in debug mode.  Got this:
> >
> > decode_ax25_line: start parsing
> > 
> N4YLC-1>APT311,W6CX-3*,wIDE2-2,qAR,AA6VN-5:/230323h3746.27N/12
> 223.84Wk349/042/A=000052/soldering fun!
> > valid_path: Bad Path: Anti-loop stuff from aprsd
> > decode_ax25_line: invalid path: APT311,W6CX-3*,wIDE2-2,qAR,AA6VN-5
> > decode_ax25_line: exiting
> >
> > So..  There's a problem with the path, not the payload.  Change the
> > small 'w' to a capital 'W' made Xastir parse it properly.  Since the
> > AX.25 packet cannot contain lower-case charactes in these positions
> > in the header, perhaps it was an igate that corrupted it?
> 
> This is done by util.c:valid_path()
> 
> Anyone know why this should be dropped?  The anti-loop code that is
> catching it, but it's the 'w' in "wIDE2-2" that is the problem, not
> the Q-construct stuff.
> 
> I have no idea why AA6VN-5 changed that to a small 'w' when it
> injected the packet, but that looks to be the source of the problem.
> Whether we should allow it through our decoding is the next question
> of course.
> 

This could be a 'PASSALL ON' kind of problem, where corrupted packets
are allowed to be received and displayed?  Or it could be someone with a
shakey RS-232 serial port - that a bit didn't get encoded/decoded
correctly.  Or - was this packet hand-typed?

73, Bob, KD7NM