[aprssig] APRS IS weirdness

[Steve Dimse]

On 2/27/05 at 7:22 PM Gerry Creager N5JXS <gerry.creager at tamu.edu> sent:

>None on first
>
If you mean no bad packets, that is not correct, I just verified this grepping
on both first and second simultaneously, the bad data appears on both:

[~/perl] sdimse% ./aprsis.pl 1.aprs.net 23 | grep DB9AZ-10
DG1RWT>5R5S67,DB0DEQ,DF0HHH*,qAo,DB9AZ-10:''W/l K\]Andreas QTH:Quitzoebel  Y40
DG1RWT>5R5S67,DB0DEQ,DF0HHH*,qAo,DB9AZ-10:''W/l K]Andreas QTH:Quitzoebel  Y40

[~/perl] sdimse% ./aprsis.pl 2.aprs.net 23 | grep DB9AZ-10
DG1RWT>5R5S67,DB0DEQ,DF0HHH*,qAo,DB9AZ-10:''W/l K\]Andreas QTH:Quitzoebel  Y40
DG1RWT>5R5S67,DB0DEQ,DF0HHH*,qAo,DB9AZ-10:''W/l K]Andreas QTH:Quitzoebel  Y40

This would be expected regardless of how or where the bad data gets injected, it
ought to propagate around the APRS IS...

Steve K4HG