Re: Bad packets.
By: Stephen Walsh to deon on Tue Jan 10 2023 10:52 am
I've just pulled the latest code and re-comiled HPT.
Is there a config option to set to catch bad packets? (I'm not seeing it myself), but anyway check your inbound for "ftnmail.zip" it contains the last three day's worth of mail from all links.
I have the packet in question (and a couple of others) - and here is where the problem is:
00000a30 38 20 36 33 33 2f 32 38 30 0d 00 02 00 18 01 fd |8 633/280.......| 00000a40 01 79 02 79 02 01 00 00 00 20 20 20 20 31 20 4b |.y.y..... 1 K| 00000a50 62 0d 0d 00 2e 41 30 36 0d 0d 20 2d 2d 2d 2d 2d |b....A06.. -----| 00000a60 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d |----------------| 00000a70 2d 2d 2d 2d 2d 2d 2d 00 0d 20 52 65 70 6c 61 63 |-------.. Replac| 00000a80 65 73 20 20 20 20 20 20 20 2d 3d 3a 3d 2d 20 20 |es -=:=- | 00000a90 20 20 20 20 4e 4f 44 45 44 49 46 00 2d 2d 2d 2d | NODEDIF.----|
0xaa is the end of the previous message (0x00), and the start of the next one is jibberish (its part of a message).
The end of that partial message is:
00006a40 6b 79 20 48 50 54 20 50 6f 77 65 72 65 64 21 20 |ky HPT Powered! | 00006a50 28 31 3a 33 31 37 2f 33 29 0d 53 45 45 4e 2d 42 |(1:317/3).SEEN-B| 00006a60 59 3a 20 31 2f 31 32 33 20 31 35 2f 30 20 31 38 |Y: 1/123 15/0 18| 00006a70 2f 32 30 30 20 39 30 2f 31 20 31 30 35 2f 38 31 |/200 90/1 105/81| ...
00006bc0 2f 31 0d 01 50 41 54 48 3a 20 33 31 37 2f 33 20 |/1..PATH: 317/3 | 00006bd0 32 32 39 2f 34 32 36 20 37 31 32 2f 38 34 38 20 |229/426 712/848 | 00006be0 36 33 33 2f 32 38 30 0d 00 00 00 |633/280....|
IE: It came from 1:317/3 and it's path is shown.
(The other two messages in the packet are from 1:229/700)
From that zip file you gave me it looks like it came in with packet 09/63bbfe06.pkt - and that packet has the same bad packet and messages:
000009c0 54 48 3a 20 32 32 39 2f 37 30 30 20 34 32 36 20 |TH: 229/700 426 | 000009d0 37 31 32 2f 38 34 38 0d 00 02 00 50 03 18 01 c8 |712/848....P....| 000009e0 02 79 02 01 00 00 00 20 20 20 20 31 20 4b 62 0d |.y..... 1 Kb.| 000009f0 0d 00 2e 41 30 36 0d 0d 20 2d 2d 2d 2d 2d 2d 2d |...A06.. -------| 00000a00 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d 2d |----------------| 00000a10 2d 2d 2d 2d 2d 00 0d 20 52 65 70 6c 61 63 65 73 |-----.. Replaces|
0x9d8 is the end of the previous message, and starting at 0x9d9 is the same jibberish.
It looks like that packet came from 1:229/700 (by the first 2 messages in it).
...лоеп
--- SBBSecho 3.15-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)