Corrected the guessed "original" packet...
toggle quoted message
Show quoted text
On 10/20/2020 3:12 PM, Lynn Deffenbaugh wrote:
I've been monitoring here.? To my eyes that packet looks like something concatenated the beginning of one packet, the center of another, and the beginning of yet a third, along with some data that isn't even part of a packet, and finally introduced the whole thing to the APRS-IS.? If this occurs a lot, there's some really bad software out there.? If it occurs sometimes, there's some bad software out there that has issues under some type of (probably high) load.? If it occurs once or twice, there's still some bad software out there, but only when put under extreme stress of some kinds.
AFAIK, that software is NOT APRSISCE/32 because if it were, we would have heard about it a long time ago.
2020-10-17 04:36:47 CDT:
KD5BIG-1>APWW11,WINN,WIDE1,DEGRU25N,qAR,WA5LUY-10:;146.715-R*071108z3429.06N/09336.46WrPL
RQ1R,MONTGO,HOTSPR,WIDE2*/2: <<UI>>:
Suspected 1st part of some packet: KD5BIG-1>APWW11,WI
Suspected part of another packet: NN,WIDE1,DEGR
Likely part of an original actual object: U25N,qAR,WA5LUY-10:;146.715-R*071108z3429.06N/09336.46WrPL
Part of yet another packet: RQ1R,MONTGO,HOTSPR,WIDE2*/2:
And this part is a TNC in CONVerse mode:? <<UI>>:
I'm guessing the following is the "correct" original object?? Or did you add additional comment to it when re-creating it in your UI-View?
2020-10-20 03:05:12 EDT: WA5LUY-10>APU25N,TCPIP*,qAC,FIRST:;146.715-R*181620z3429.06N/09336.46WrPL 127.3 Joe Baldwin Memorial Rep.
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
On 10/20/2020 2:39 PM, Randy Love wrote:
Well, according to the aprs TO-CALL id, that packet was generated by KD5BIG
using APWWxx APRSISCE win32 version.
Perhaps a question to Lynn, the author of APRSIS32 in his support group
could help sleuth the issue.
73,
Randy
WF5X
On Tue, Oct 20, 2020 at 12:55 PM wa5luy <wa5luy@...> wrote:
Gentlemen,
My post was to see if anyone had any input as to how the digipeater /
Igate ,KD5BIG-1 sent a packet with my object information not a discussion
of weather some packets are annoying or superfluous to some people.? Now
looking at the digipeater transmission that caused the problem it is the
only "<<UI>>" unnumbered information frame that I could see that was sent
by this station.? I realize the packet is very corrupted involving several
digipeaters due to the band being open. I was hoping that someone with AX25
protocol knowledge might look at the packet and shed some light as to what
happened. Again here is the packet.
2020-10-17 04:36:47 CDT:
KD5BIG-1>APWW11,WINN,WIDE1,DEGRU25N,qAR,WA5LUY-10:;146.715-R*071108z3429.06N/09336.46WrPL
RQ1R,MONTGO,HOTSPR,WIDE2*/2: <<UI>>:
