I'm getting bad packets from somewhere within zone 21. I've no idea who. Maybe someone has upgraded recently...or failed to upgrade. Would really like to trace who is causing bad packets. Anyone else seeing similar issues?

2020-11-24 21:33:28 Importing /sbbs/fido/inbsecure/0eca0240.pkt (Type 2e, 10.0KB) from 21:2/100 to 21:2/101
2020-11-24 21:33:28 FSX_GEN: Failed to parse Origin Line in message from paulie420 (21:2/100) in packet from 21:2/100: /sbbs/fido/inbsecure/0eca0240.pkt
2020-11-24 21:33:28 Grunged message (type 2) from 21:2/100 at offset 617 in packet: /sbbs/fido/inbsecure/0eca0240.pkt
2020-11-24 21:33:28 Bad packet detected: /sbbs/fido/inbsecure/0eca0240.pkt bbs@bbs:/sbbs/fido/inbsecure$ grep -i 0f34bc48 /sbbs/data/sbbsecho.log 2020-11-25 13:12:32 Importing /sbbs/fido/inbsecure/0f34bc48.pkt (Type 2e, 1.0KB) from 21:2/100 to 21:2/101
2020-11-25 13:12:32 FSX_GEN: Failed to parse Origin Line in message from Adept (21:2/100) in packet from 21:2/100: /sbbs/fido/inbsecure/0f34bc48.pkt
2020-11-25 13:12:32 Grunged message (type 2) from 21:2/100 at offset 612 in packet: /sbbs/fido/inbsecure/0f34bc48.pkt
2020-11-25 13:12:32 Bad packet detected: /sbbs/fido/inbsecure/0f34bc48.pkt bbs@bbs:/sbbs/fido/inbsecure$ grep -i 0ff2b65a /sbbs/data/sbbsecho.log 2020-11-26 20:00:57 Importing /sbbs/fido/inbsecure/0ff2b65a.pkt (Type 2e, 4.3KB) from 21:2/100 to 21:2/101
2020-11-26 20:00:57 FSX_MYS: Failed to parse Origin Line in message from Barmed (21:2/100) in packet from 21:2/100: /sbbs/fido/inbsecure/0ff2b65a.pkt
2020-11-26 20:00:57 Grunged message (type 2) from 21:2/100 at offset 1743 in packet: /sbbs/fido/inbsecure/0ff2b65a.pkt
2020-11-26 20:00:57 Bad packet detected: /sbbs/fido/inbsecure/0ff2b65a.pkt
--- SBBSecho 3.11-Linux
* Origin: End Of The Line BBS - endofthelinebbs.com (21:2/101)

Re: Bad Packets
By: Nigel Reed to FSXNET.FSX_GEN on Mon Nov 30 2020 03:54 pm

I'm getting bad packets from somewhere within zone 21. I've no idea who. Maybe someone has upgraded recently...or failed to upgrade. Would really like to trace who is causing bad packets. Anyone else seeing similar issues?

I don't have any ATM but I have gotten bad packets that won't toss. I think they are created on Mystic BBSs. I would report to g00r00 if I knew what was happening, but I don't.

Some messages just seem to end mid paragraph with no tear or origin line.

Ttyl :-),
Al

... Sir, the Romulans do not take prisoners!
--- SBBSecho 3.11-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

On 30 Nov 2020, Al said the following...

Re: Bad Packets
By: Nigel Reed to FSXNET.FSX_GEN on Mon Nov 30 2020 03:54 pm

I'm getting bad packets from somewhere within zone 21. I've no idea w Maybe someone has upgraded recently...or failed to upgrade. Would rea like to trace who is causing bad packets. Anyone else seeing similar issues?

I don't have any ATM but I have gotten bad packets that won't toss. I thinkthey are created on Mystic BBSs. I would report to g00r00 if I knew what washappening, but I don't.

Some messages just seem to end mid paragraph with no tear or origin line.

Is it only in 21:2/* or anywhere in zone 21?
The output from the last message showed some 21:2/* addresses...

It could be my system, because one user posted from here the other day and someone said the exact same thing that he had no tear or origin line, but I've been through all the messages I have sent out from my other bbs and every one has a tear and origin so I don't know if somehow it's client based ... does this have a tear/origin?

If there is issues with my BBS, it's running Mystic Pi version, which if other people using the Pi version also missing tear/origin, then I reckon that's the issue, but if it's just random, I dunno.

Lemme know if this has a tear/origin or not.

---
|14Best regards,
|11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N

|07ÄÄ |08[|10eml|08] |15ml@erb.pw |07ÄÄ |08[|10web|08] |15www.erb.pw |07ÄÄÄ¿ |07ÄÄ |08[|09fsx|08] |1521:1/158 |07ÄÄ |08[|11tqw|08] |151337:1/101 |07ÂÄÄÙ |07ÄÄ |08[|12rtn|08] |1580:774/81 |07ÄÂ |08[|14fdn|08] |152:250/5 |07ÄÄÄÙ
|07ÄÄ |08[|10ark|08] |1510:104/2 |07ÄÙ

--- Mystic BBS v1.12 A47 2020/11/22 (OnePlus6T/arm32)
* Origin: phOnE In mY pOckEt BBS (21:1/158.6)

Re: Re: Bad Packets
By: MeaTLoTioN to Al on Mon Nov 30 2020 11:19 pm

Some messages just seem to end mid paragraph with no tear or origin
line.

Is it only in 21:2/* or anywhere in zone 21?
The output from the last message showed some 21:2/* addresses...

No, they could arrive from anywhere. Some of these messages were traveling around in Fidonet.

It could be my system, because one user posted from here the other day and someone said the exact same thing that he had no tear or origin line, but I've been through all the messages I have sent out from my other bbs and every one has a tear and origin so I don't know if somehow it's client based ... does this have a tear/origin?

Your messages are fine and they do have a tear and origin line. These messages that seem to end abrubtly with no tear or origin could be entered anywhere. They seem to pass through Mystic systems fine but will toss bad on others.

If there is issues with my BBS, it's running Mystic Pi version, which if other people using the Pi version also missing tear/origin, then I reckon that's the issue, but if it's just random, I dunno.

It's not an issue with your BBS. The last time I saw such a bad packet it contained a <CTRL>Z character from the sauce info in an ansi file description. That <CTRL>Z is an end a file marker from the CP/M days. I wonder if that is the issue.. but I really don't know.

Lemme know if this has a tear/origin or not.

Yes it does, you are fine.. :)

There is some character (<CTRL>Z, maybe) that causes issues. If we can identify what the issue is we can bring it up with g00r00 but it happens rarely.

Ttyl :-),
Al

... Every action has an equal and opposite government program
--- SBBSecho 3.11-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

El 1/12/20 a las 03:35, Al escribió:

Re: Re: Bad Packets
By: MeaTLoTioN to Al on Mon Nov 30 2020 11:19 pm

Al>> Some messages just seem to end mid paragraph with no tear or origin
Al>> line.

i still receive too many bad packets like this:

root@scarlet:/sbbs/fido/inbound# pktdump -ctrl -body 0feab3c1.bad
pktdump rev 1.17 - Dump FidoNet Packets

Opening 0feab3c1.bad
0feab3c1.bad Packet Type 2+ (prod: FEFE, rev: 0.0) from 21:2/100 to 21:2/151 0feab3c1.bad 00003A Packed Message Type: 2 from 2/100 to 2/151
Attribute: 0x0000 ()
Date/Time: 26 Oct 20 16:02:47
To : StiZzed
From : paulie420
Subj : Re: The ROCK III

-start of message text-
@TID: Mystic BBS 1.12 A47
@MSGID: 21:2/150 63ccbe69
@REPLY: 21:4/156 cf104401
@TZUTC: -0700

St> ��
SEEN-BY: 1/100 2/100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 SEEN-BY: 2/115 116 118 119 120 1202 121 122 123 124 126 127 129 130 131
132 133
SEEN-BY: 2/134 135 136 137 138 139 140 141 144 145 147 150 151 152 154
155 158
@PATH: 2/10059 160 161 162 163 164 165 166 167 3/100 4/100

-end of message text-
0feab3c1.bad 000226 Corrupted Message Header (variable-length fields) 0feab3c1.bad 0003A9 Corrupted Message Header (variable-length fields) 0feab3c1.bad 00052B Corrupted Message Header (variable-length fields) 0feab3c1.bad 0006B6 Corrupted Message Header (variable-length fields) 0feab3c1.bad 00083A Corrupted Message Header (variable-length fields) 0feab3c1.bad 0009C1 Corrupted Message Header (variable-length fields) 0feab3c1.bad 000A1D Corrupted Message Header (type: 5241)
0feab3c1.bad 000A1F Corrupted Message Header (type: 4145)
0feab3c1.bad 000A21 Corrupted Message Header (type: 463A)
0feab3c1.bad 000A23 Corrupted Message Header (type: 5853)
0feab3c1.bad 000A25 Corrupted Message Header (type: 425F)
[------snippet -----]


the sbbs log:
-------------
2020-12-13 14:09:00 Importing /sbbs/fido/inbound/0d7a0c31.pkt (Type 2e,
2.8KB) from 21:2/100 to 21:2/151 |
2020-12-13 14:09:00 FSX_GEN: Failed to parse Origin Line in message from
Avon (21:2/100) in packet from 21:2/100|
: /sbbs/fido/inbound/0d7a0c31.pkt
|
2020-12-13 14:09:00 Added FSX_GEN message from Avon (21:2/100) to
packets for 0 links (exceptions: 1 seen) |
2020-12-13 14:09:00 Grunged message (type 2) from 21:2/100 at offset
1069 in packet: /sbbs/fido/inbound/0d7a0c31|
.pkt
|
2020-12-13 14:09:00 Bad packet detected: /sbbs/fido/inbound/0d7a0c31.pkt ----------------

Most are from mystic systems, i fill a bug report against sbbs but i try
to find who cause it.

https://gitlab.synchro.net/main/sbbs/-/issues/186

Any idea?

thanks!
--- SBBSecho 3.11-Linux
* Origin: Dock Sud BBS - bbs.docksud.com.ar - Argentina (21:2/151)

Re: Re: Bad Packets
By: Ragnarok to Al on Sun Dec 13 2020 05:06 pm

i still receive too many bad packets like this:

root@scarlet:/sbbs/fido/inbound# pktdump -ctrl -body 0feab3c1.bad
pktdump rev 1.17 - Dump FidoNet Packets

Opening 0feab3c1.bad
0feab3c1.bad Packet Type 2+ (prod: FEFE, rev: 0.0) from 21:2/100 to 21:2/151 0feab3c1.bad 00003A Packed Message Type: 2 from 2/100 to 2/151

Yes, I think they do come from Mystic but I am not sure of the cause.

I think g00r00 is aware but may not have found a cause or solution yet.

If you could send those bad packet to g00r00 so he can inspect them it might help him to get to the solution. You can post in the fido MYSTIC echo or email those to him.

I'm going from memory here, I think his email is mysticbbs[at]gmail[dot]com.

Ttyl :-),
Al

... This login session: $13.99, but for you $11.88
--- SBBSecho 3.11-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)