| |
ZL3AI > APRDIG 31.10.03 15:17l 260 Lines 10409 Bytes #999 (0) @ WW
BID : 2248-ZL3AI
Read: GUEST
Subj: TAPR Digest, Oct 29, 3/3
Path: DB0FHN<DB0RGB<OK0PPL<DB0RES<ON0AR<7M3TJZ<JE7YGF<LU6DTS<ZL2TZE<ZL3VML
Sent: 031031/1242Z @:ZL3VML.#80.NZL.OC #:11692 [Chch-NZ] FBB7.00i $:2248-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Re: APRS Packet Errors
From: David VanHorn <dvanhorn@cedar.net>
Date: Wed, 29 Oct 2003 22:54:03 -0500
X-Message-Number: 22
One reason that they will be sending junk packets, is that they don't know
what's right or wrong. Sure, it's an RTFM problem, but look at it as an
outsider, WHERE's the FM? :)
I wouldn't know if my IP packets from here are right or wrong either, nor
would I want to go digging through the RFCs to find out.
If I had the tools handy, it would be tempting to write a parser to strip
these packets, and point at the errors. The first one is easy, but after
that it may become impossible to parse further.
Still, it should be possible to do, and to suggest what's wrong.
A friend of mine and I, wrote a parser for this little bag of fun:
http://www.verifone.com/support/documents/
The TCL manual is the ref.
What we'd get is a dump of stuff that looks like:
269=B.5GA919.21A918.20GA948I1.2.'1'L37GJ'Q'I13.4.'6'GJ'C'I11.4.'27'GA947I8.3.'5J
'G'BC'*Q#3.5GA358*Q#4.5+A#4.0.#3.1L270*M
270=B5.5GJ'KE'D*Q#3.5GA917.3D*Q#4.5+A#4.0.#3.1*ML37
282=*R6.2.2
283=B1.1U60GA284*Q#9..0GA60
284=176
Picture 50-100k of this.. :)
Some is data, some is code, some is unused data or code, and some is
self-modifying code.
This is what's in all those credit card terminals.
----------------------------------------------------------------------
Subject: Re: APRS Packet Errors
From: "Georgette Sampson" <georgette.sampson@cox.net>
Date: Wed, 29 Oct 2003 22:01:31 -0600
X-Message-Number: 23
Who cares? It's just a hobby.
----- Original Message -----
>On 10/29/03 at 9:17 PM Steve Dimse <k4hg@tapr.org> sent:
>
>I wasn't disappointed. It was less than a half hour after the message appeared
>before someone sent me a grossly malformed packet asking me to explain what was
>wrong.
>
>Would anyone volunteer to interpret any errors people are too lazy to interpret
>for themselves?
>
>Steve K4HG
----------------------------------------------------------------------
Subject: Re: APRS Packet Errors
From: Steve Dimse <k4hg@tapr.org>
Date: Wed, 29 Oct 2003 23:12:20 -0500
X-Message-Number: 24
On 10/29/03 at 10:54 PM David VanHorn <dvanhorn@cedar.net> sent:
>>Would anyone volunteer to interpret any errors people are too lazy to
interpret
>for themselves?
>
>One reason that they will be sending junk packets, is that they don't know
>what's right or wrong. Sure, it's an RTFM problem, but look at it as an
>outsider, WHERE's the FM? :)
It is linked to on the page. One click and it is on their computer. Easiest I
could make it...
>I wouldn't know if my IP packets from here are right or wrong either, nor
would >I want to go digging through the RFCs to find out.
I have used Ethereal to look at TCP packets at times when I've been
debugging things on my network. The fact is, know how your communication
tools work is part of being a ham...it is what makes hams so good in
emergencies...if you understand your tools, you can troubleshoot them in
the field.
Would you want a pilot that didn't understand the mechanics of his
aircraft, a doctor that didn't understand the human body?
My reason for requsting people not bring the problems to me is three-fold.
First, I have limited time and every email takes time away from something
useful I could do to findU. Second, I really believe that if you use APRS,
you ought to understand something about the way it works, and where to go
for the answers. Finally, I believe that people should learn to solve their
own problems...it is the difference between giving a man a fish, and
teaching him to fish!
>If I had the tools handy, it would be tempting to write a parser to strip
these >packets, and point at the errors. The first one is easy, but after that
it may
>become impossible to parse further.
Yes, it would be possible to do some of this automatically, but it also
would be quite a bit of work, I doubt it would be worth the effort. If
someone needs a machine to tell them where the error is, they probably need
it to tell them what they meant, a tougher job.
Easier, and potentially equally, if not more useful, would be to simply
determine what the format of the bad packet is, and link to a short form
format page...one page for the @ format, one for !, one for _, and so on.
If someone wrote those pages I could generate the links within the cgi...
Steve K4HG
----------------------------------------------------------------------
Subject: Re: APRS Packet Errors
From: "Scott Miller" <scott@3xf.com>
Date: Wed, 29 Oct 2003 20:18:46 -0800
X-Message-Number: 25
>One reason that they will be sending junk packets, is that they don't know
what's right or wrong. >Sure, it's an RTFM problem, but look at it as an
outsider, WHERE's the FM? :)
And can you imagine if a TCP stack required the user to compose packet
headers by hand? People have complained about OpenTrac being difficult to
edit by hand since it's a binary protocol, but at least when you have to use
software to compose a packet, the only people who need to worry about packet
assembly are programmers, and not the end users.
How hard would it be for TNC makers to add a menu-driven config for APRS
beacons? The uWeather station does it. Just enter the parameters and it
builds the packet itself. No reason users should ever have to generate
their own packets...
Scott
N1VG
----------------------------------------------------------------------
Subject: Re: APRS Packet Errors
From: "B. Hildebrand" <bhildebrand@earthlink.net>
Date: Wed, 29 Oct 2003 20:41:28 -0800
X-Message-Number: 26
A quick look - no guarantees. Formating may even fail!
Call count Last Bad Packet Problem
W8BUG 340
W8BUG>APT310,WA4KJH-7*,WIDE2-2,qAS,KF4ZUX:!0000.000/00000.000>000/000 zero
data
W5MLE 287
W5MLE>APRS,TCPXX*,qAX,W5MLE:@300415z30.3315/92..0552_115/000g000t063r000p000
P000h00b10124.Ult Missing N/S E/W, Extra decimal point
K9AEG-10 279 K9AEG-10>APRS,qAR,KC9BWF-2:!4449.66n/08909.75w&phg7370
k9aeg, Wittenberg, wi APRS Nueske Hill lower case n and w
KD7CHR-15 252
KD7CHR-15>APT310,SKYLIN,WIDE2*,qAo,K7UHP:!0000.000/00000.000>000/000 zero
data
WD4ROJ 181
WD4ROJ>APZ18,WY8O-8*,qAR,N0CTM:!3129.23n/08558.11w#phg5260/n4ryc@snowhill.co
m lower case n and w
OZ3WT 156 OZ3WT>APU16N,TCPXX*,qAX,OZ3WT:=5600.23N/O1158.77E- {UIV23} O
in place of 0
WB5BBW 151 WB5BBW>APX121,WD5IYT-2,qAR,KA5KTH:)aus_3025.51N9731.98W!
Missing symbol table designator
WB4BDP 136 WB4BDP>APR840,KG4OLD-2*,qAo,KC4ZGQ-10:=330 . N8400.00Wd
ByCall/140 dg frm KC4ZGQ-2 144.390 Missing symbol table designator, Latitude
misformated
EB3GFC-1 130
EB3GFC-1>APRSWX,EA2K-15*,WIDE4-1,qAS,EA2AAA-1:!4134.83N/0049.59E_.../...g...
t032h..b.....pXAVIER--TORREGROSSA--WXPIC Misformated Longitude
W4GPS-7 124 W4GPS-7>APZ186,qAo,N8DEU-4:!3444.29NU08632.06W "U"
overlay - probably correctly formated - Check FindU? <g>
PI1EHV-2 121
PI1EHV-2>APD225,WIDE3-3,qAo,PD0SBH-5:;STN8600>APRS:!5126.94NI00529.21E0PHG34
30.430100+71.9IDLE______eme FUBAR
KB8LYL-12 111
KB8LYL-12>BEACON,W8GK-5*,WIDE,qAo,KN0BY:_3836.96N/8175.93WI APRS Linux
Internet Server Misformated Longitude
K5RGD-1 108
K5RGD-1>APRS,N0VH-1*,qAS,KB5LS-1:!2928.18NTO09752.48W#K5RGD-1 SEGUIN WIDE/R
RELAY/R TRACE/R O in place of 0
EA1ERJ-5 106
EA1ERJ-5>APZ186,ED1ZAB-7*,EA4CQV-8*,qAR,EB4BCS-8:!4049.54N/00517.12w#phg3340
/Penaranda/Salamanca Misformated Longitude
W0BIS-1 94 W0BIS-1>BEACON,WIDE,WIDE,qAC,W0BIS-1:_4646.46W/10044.84WI
APRS Linux Internet Server Look OK to me
HS0AC-1 66
HS0AC-1>APU25H,TCPIP*,qAS,EA2AAA-1:;KD7KPD/MM*250110z0000.00S/10400.00EYHS0A
C-Winlink-Pactor-Net-AirMail-APRS Look OK to me
PI1APV-2 62 PI1APV-2>WIDE3,WIDE7-6,qAo,ON7EQ:!5130.88n/00343.98E#DIGI
MIDDEN ZEELAND lower case n and w
NOCALL 54
NOCALL>APX121,TCPXX*,qAS,WA7NWP-3:=0000.00N/00000.00WxXASTIR-Linux zero data
W8EHH 49
W8EHH>WX,WC4PEM-10*,WIDE3-3,qAO,KQ4KX:!2833.41/08135.85_PHG7160 WX From
Winter Garden, FL Missing N/S E/W
W5UK-9 47
W5UK-9>APRS,WIDE,WY8O-8*,WIDE,TRACE,qAR,N0CTM:!2954.38N09002.39W#PHG6660/A=0
00500 New Orleans WIDE-RELAY-TRACE Missing symbol table designator
K3GJ 45
K3GJ>APRS,TCPIP*,qAC,K3GJ:@300330z3834.47N/-7659.47W_226/000g000t042r000p059
P058b10163h97.WD "-" in place of "0" ?
WX9MKX 44 WX9MKX>APRS,WIDE,qAS,N9UUR-10:!4258.06N08833.05W#PHG5000
Missing symbol table designator
AB0UO 41 AB0UO>BEACON,qAR,AB0XK-10:!3853.39N/9851.35W-AB0UO RUSSELL,
KS APRS Misformated Longitude
AUS 38 AUS>APX121,WD5IYT-2*,qAo,WB5BBW:_3024.17N9733.58W!AUS test
Missing symbol table designator, Longitude misformated
W6CX-3 37
W6CX-3>APRS,WIDE,qAR,K6TPK-7:!3748.57NN12203.41w#PHG7550/A=002380/Rocky
Ridge, W of Danville lower case n and w
VA3DGS-1 35
VA3DGS-1>APD215,VE3KSR,VE3YAP,VA3BAL*,qAS,VA3CKI:!4328.66/08030.51 aprsd
Linux APRS Server Missing N/S E/W
WA2UEM-4 31
WA2UEM-4>APRS,WA2JNF-15*,qAo,KE2LJ-8:!4052.63NT07424,10W#Pwr4230/W-R-T Digi
Parsippany,N.J Looks OK to me
PI1RWD-4 27 PI1RWD-4>APRS,WIDE4-4,qAR,PI1RWD-9:!5318.45NI0602.15E&
aprsd Linux APRS Server Misformated Longitude
WA1WOK-5 27
WA1WOK-5>APR846,NS1RA-1*,WIDE2,TRACE,qAS,ns1ra-2:=4311.9NN/07132.9WWo000/000
/NHOEM State EOC o000/000
DL0TOL-1 25
DL0TOL-1>APRS,WIDE5-3,qAR,DG9BJU-3:=53.08.35N/00813.05E#PHG2260/APRS
Test-Digi Z53 SYS DJ6UA QRV 145,475 Extraneous "."
OH9GGY 25
OH9GGY>APRS,OH9RDB-2,WIDE,OH9RDA-8*,WIDE7-6,qAr,OH8RCA:=6600.90N/2408.19E#R#
** OH9GGY-1 ** BBS ** Tornio ** KP26BA Misformated Longitude
K0BSJ-3 24
K0BSJ-3>BEACON,WIDE,GATE,GATE,WIDE,qAr,KC0NWS*:!3920.04NT0913.16W#PHG4380
W-R-T EXCELSIOR SPRINGS, MO. Misformated Longitude
N5SGT 24 N5SGT>APRS,WIDE2,qAo,KD7QOT-1:!3858.13nn07801.68w#phg2770
lower case n and w
K5WTC-3 23
K5WTC-3>APRS,KD5JTM-5*,WIDE3-2,qAr,N5ZXD*:!32.43.32.7NN102.41.54W#PHG45200
FUBAR
WB4FAY-7 22 WB4FAY-7>APZ18,WIDE2-2,qAR,WB4FAY-4:!3317.04NUvU64 FUBAR
K7UHP 22
K7UHP>APRS,WIDE,qAR,K7UHP:!4038.78N11154.09#&PHG2228/A=004317/K7UHP SL
I-gate Missing Symbol table designator
VE6DEP 21
VE6DEP>APRSDY,WIDE7-7,qAR,VE6TOT:!0000.00N0000.00W.PHG0000/APRS DIGIPEATER
(UIDIGI 1.8) 3 zero data
SV4BHA-12 20
SV4BHA-12>APNU19,J44UAB,SV2BZQ-12*,TRACE5-3,qAS,sv2dfr-12:!3956.82NB02226.72
#PHG2840/sv4bha1@otenet.gr / WIDEn-n / TRACEn-n Missing E/W
---
END OF DIGEST
Read previous mail | Read next mail
| |
