bbs@bbs:/sbbs/fido/inbsecure$ pktdump 03d08fe2.bad|more
pktdump rev 1.12 - Dump FidoNet Packets

Opening 03d08fe2.bad
03d08fe2.bad Packet Type 2+ (prod: FEFE, rev: 0.0) from 21:2/100 to 21:2/101 0000003A
03d08fe2.bad 00003A Packed Message Type: 2 from 2/100 to 2/101
Attribute: 0000
Date/Time: 06 Apr 20 00:00:00
To :
From :
# Origin: If you build it he will come (2:2
000000AF
03d08fe2.bad 0000AF Packed Message Type: 21057 from 22611/16709 to
16991/17978
Attribute: 544F
Date/Time: EEN-BY: 1/1 100 101
To : 102 103 104 105 106 107 109 110 111
SEEN-BY: 1/117 14 115 116
SEEN-BY: 19 120 121 122 124 125 126 127 128 129 130 131 133 134 135
00000408
03d08fe2.bad 000408 Packed Message Type: 2 from 2/100 to 2/101
Attribute: 0000
Date/Time: 06 Apr 20 11:05:02
To : Lupine Furmen
From : Atreyu
Subj : Re: Fido
00000A67


I get this on a number of networks, fsx, fido, pas and a few others.

They all seem to have the same "you build" line in it. Who's responsible for this?

bbs@bbs:/sbbs/fido/inbsecure$ grep "you build" *.bad
Binary file 03d08fe2.bad matches
Binary file 03d32508.bad matches
Binary file 0402f6a8.bad matches
Binary file e8b445b7.bad matches
Binary file e8bb9137.bad matches
Binary file e8bbaabb.bad matches
Binary file e8bc1ac8.bad matches


I guess it's going through one BBS that's mangling the data.
--- SBBSecho 3.10-Linux
* Origin: End Of The Line BBS - endofthelinebbs.com (21:2/101)

Hello Nigel,

They all seem to have the same "you build" line in it. Who's
responsible for this?

I guess it's going through one BBS that's mangling the data.

I'm not sure what is up. I got only two bad packets yesterday. I took a quick look but couldn't determine just what had happened and being in a hurry a deleted the bad packets.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Nigel wrote (2020-04-07):

bbs@bbs:/sbbs/fido/inbsecure$ pktdump 03d08fe2.bad|more
pktdump rev 1.12 - Dump FidoNet Packets

Opening 03d08fe2.bad
03d08fe2.bad Packet Type 2+ (prod: FEFE, rev: 0.0) from 21:2/100 to 21:2/101 0000003A

Product code FEFE is Mystic BBS, 21:2/100 is your uplink. Is there any reason to believe that these packets are not from 2/100?

I get this on a number of networks, fsx, fido, pas and a few others.

They all seem to have the same "you build" line in it. Who's responsible for this?

Some bug in Mystic or file system corruption?

I guess it's going through one BBS that's mangling the data.

What do the logs tell you? Who sent you this packets?

---
* Origin: (21:3/102)

Hello Oli,

I guess it's going through one BBS that's mangling the data.

What do the logs tell you? Who sent you this packets?

I got two of these bad packets yesterday. One came from 1:261/38 and another came from 21:4/100.

Here's a log snippet for the first one..


=== Cut ===
---------- Mon 06 Apr 20, hpt/lnx 1.9.0-cur 2019-12-05
7 07:58:00 bundle /usr/local/fido/inbound/b5c66e72.mo1: renaming to .tos
7 07:58:00 pkt: /usr/local/fido/inbound/tmp/b5c66e87.tos [1:261/38]
A 07:58:00 wrong msg header: toUserName (D'Bridge 4
+ Origin: If you build it he will come (2:292/854)
SEEN+BY: 14/5 15/0 19/36 34/999 106/201 116/18 120/331 123/140 128/2 153/757 SEEN+BY: 153/7715 218/700 230/150 152 240/1120 250/1 261/38 100 266/512 267/155 SEEN+BY: 275/100 282/1031 1056 291/100 111 292/854 320/119 219 340/400 342/13 SEEN+BY: 396/45 640/1321 712/848 801/161 189 2320/105 3634/12 5020/1042
) is longer than 35 bytes.
A 07:58:00 wrong msg header: fromUserName () is longer than 35 bytes.
A 07:58:00 wrong msg header: renaming pkt to bad.
A 07:58:00 Renaming pkt/arc to .bad
4 07:58:00 Statistics:
4 07:58:00 arc: 1 netMail: 0 echoMail: 0 CC: 0 4 07:58:00 pkt's: 1 dupe: 0 passthru: 0 exported: 0 4 07:58:00 msgs: 0 bad: 0 saved: 0 empty: 0 4 07:58:00 Input: 0.00 mails/sec Output: 0.00 mails/sec
4 07:58:00 72.84 kb/sec
4 07:58:00 1.60 kb total, processed in 0.022 seconds
4 07:58:00 Areas summary:
9 07:58:00 Nothing to link. Use "hpt link *" to perform linking all areas
=== Cut ===

I couldn't make any sense of it. I think they were messages that got corrupted at some point and then went a little screwey!

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Al wrote (2020-04-08):

Hello Oli,

I guess it's going through one BBS that's mangling the data.

What do the logs tell you? Who sent you this packets?

I got two of these bad packets yesterday. One came from 1:261/38 and another came from 21:4/100.

Here's a log snippet for the first one..

=== Cut ===
---------- Mon 06 Apr 20, hpt/lnx 1.9.0-cur 2019-12-05
7 07:58:00 bundle /usr/local/fido/inbound/b5c66e72.mo1: renaming to .tos
7 07:58:00 pkt: /usr/local/fido/inbound/tmp/b5c66e87.tos [1:261/38]
A 07:58:00 wrong msg header: toUserName (D'Bridge 4
+ Origin: If you build it he will come (2:292/854)
=== Cut ===

I couldn't make any sense of it. I think they were messages that got corrupted at some point and then went a little screwey!

I thought it is most likely that these mails are corrupted at the node you are getting them from and that a corrupted packet or mail will be detected by other
tossers too - before they get forwarded.

The "Origin: If you build it he will come" is interesting though. Different echomail feeds, very similar error.

2:292/854 is Ward Dossche's node number and I'm not sure he posted anything recently.

---
* Origin: (21:3/102)

Hello Oli,

I couldn't make any sense of it. I think they were messages that
got corrupted at some point and then went a little screwey!

I thought it is most likely that these mails are corrupted at the node
you are getting them from and that a corrupted packet or mail will be detected by other tossers too - before they get forwarded.

I found it odd that Nelgin got these also.

The "Origin: If you build it he will come" is interesting though. Different echomail feeds, very similar error.

2:292/854 is Ward Dossche's node number and I'm not sure he posted anything recently.

AFAIK Ward is recovering. I hope he has or will recover soon but I haven't seen
anything from him in a while.

The packets I looked at didn't have enough in them to determine what area or when/where they originated.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Hello Oli,

2:292/854 is Ward Dossche's node number and I'm not sure he posted anything recently.

I just got another one from 21:4/100 with all the same junk. Destined for FSX_BOT from 21:1/106 by the looks of it.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Al wrote (2020-04-08):

I just got another one from 21:4/100 with all the same junk. Destined for FSX_BOT from 21:1/106 by the looks of it.

I'm not surprised anymore. It's just the usual mess ;-P

|: ... rolling a boulder up a hill ... :|

---
* Origin: (21:3/102)

Hello Nigel,

I get this on a number of networks, fsx, fido, pas and a few others.

They all seem to have the same "you build" line in it. Who's
responsible for this?

I have seen a few of these. Looking at the pkt I received yesterday it has no from or to name and has a date of 30 Nov 99 and looking at the path it originated at 21:1/106.

The above depends on the fact what I am seeing is not corrupt and it may very well be.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Al wrote:

Hello Oli,

2:292/854 is Ward Dossche's node number and I'm not sure he posted
anything recently.

I just got another one from 21:4/100 with all the same junk. Destined for FSX_BOT from 21:1/106 by the looks of it.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Yes, I got some FSX_BOT ones.

bbs@bbs:/sbbs/fido/inbsecure$ pktdump 0402f6a8.bad
pktdump rev 1.12 - Dump FidoNet Packets

Opening 0402f6a8.bad
0402f6a8.bad Packet Type 2+ (prod: FEFE, rev: 0.0) from 21:2/100 to 21:2/101 0000003A
0402f6a8.bad 00003A Packed Message Type: 2 from 2/100 to 2/101
Attribute: 0000
Date/Time: 00 00 00:00:00
To :
* Origiidge 4STIC
Subj : If you build
00000092
0402f6a8.bad 000092 Packed Message Type: 21057 from 22611/16709 to
16991/17978
Attribute: 544F
Date/Time: EEN-BY: 1/100 2/100
To : 101 102 103 104 105 106 107 108 109
SEEN-BY: 2/115 12 113 114
SEEN-BY: 18 119 120 1202 121 123 124 125 126 127 128 129 130 131 132
00000207


There is only one message in this packet, so one of these nodes is the
cuplrit. Still, "If you build"... seems to be common amongst all these.
--- SBBSecho 3.10-Linux
* Origin: End Of The Line BBS - endofthelinebbs.com (21:2/101)

Al wrote:

Hello Nigel,

I get this on a number of networks, fsx, fido, pas and a few others.

They all seem to have the same "you build" line in it. Who's
responsible for this?

I have seen a few of these. Looking at the pkt I received yesterday it has

no

from or to name and has a date of 30 Nov 99 and looking at the path it originated at 21:1/106.

The above depends on the fact what I am seeing is not corrupt and it may

very

well be.

I wonder if someone has an autopost script that's gone bad.
--- SBBSecho 3.10-Linux
* Origin: End Of The Line BBS - endofthelinebbs.com (21:2/101)

Hello Nigel,

The above depends on the fact what I am seeing is not corrupt and
it may very well be.

I wonder if someone has an autopost script that's gone bad.

I'm not sure just what the cause is but I suspect a bit of file system corruption somewhere.

I'm going to zip up that bad packet and send it to 21:1/106 so the sysop there can inspect it and see if maybe it originates there.

It's a shot in the dark. It looks like it originated there but since the packet
is corrupt my data is not really trusted.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Nigel wrote (2020-04-08):

There is only one message in this packet, so one of these nodes is the cuplrit. Still, "If you build"... seems to be common amongst all these.

One of which nodes?

---
* Origin: (21:3/102)

Hello Oli,

There is only one message in this packet, so one of these nodes
is the cuplrit. Still, "If you build"... seems to be common
amongst all these.

One of which nodes?

I got a few of these also. Looking at the path line it looks like they originated at 21:1/106. I sent one of those bad packets directly to 21:1/106 to
inspect.

I don't know that is really so since those packets were corrupt. Those messages
never moved beyond here.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

On Wednesday, April 8th Al was heard saying...

I'm not sure what is up. I got only two bad packets yesterday. I took a quick look but couldn't determine just what had happened and being in a hurry a deleted the bad packets.

I've noticed a influx of these as well lately.


--

NuSkooler
Xibalba BBS @ xibalba.l33t.codes / 44510(telnet) 44511(ssh)
ENiGMA 1/2 BBS WHQ | Phenom | 67 | iMPURE | ACiDic

--- ENiGMA 1/2 v0.0.11-beta (linux; x64; 12.13.1)
* Origin: Xibalba -+- xibalba.l33t.codes:44510 (21:1/121)

Hello NuSkooler,

I'm not sure what is up. I got only two bad packets yesterday. I
took a quick look but couldn't determine just what had happened
and being in a hurry a deleted the bad packets.

I've noticed a influx of these as well lately.

I have not recieved any more of these so I still don't know what happened.

Reading in Fidonet I see another node having an issue with these bad packets. They do look like corrupt packets from what I have been reading and did not originate at 21:1/106 as it looked from what I had seen. They did originate in fidonet and not fsxNet Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Al wrote:

Hello NuSkooler,

I'm not sure what is up. I got only two bad packets yesterday. I
took a quick look but couldn't determine just what had happened
and being in a hurry a deleted the bad packets.

I've noticed a influx of these as well lately.

I have not recieved any more of these so I still don't know what happened.

Reading in Fidonet I see another node having an issue with these bad

packets.

They do look like corrupt packets from what I have been reading and did not originate at 21:1/106 as it looked from what I had seen. They did originate

in

fidonet and not fsxNet Ttyl :-),

I had that for several networks but all with that "you build it".

I have another bad one today

-rw------- 1 bbs bbs 67037 Apr 11 10:57 06d030c3.bad
--- SBBSecho 3.10-Linux
* Origin: End Of The Line BBS - endofthelinebbs.com (21:2/101)

Hello Nigel,

I had that for several networks but all with that "you build it".

I have another bad one today

-rw------- 1 bbs bbs 67037 Apr 11 10:57 06d030c3.bad

I got a similar one this morning..

-rw-r-r--r-- 1 alan users 64005 Apr 11 08:58 06c53bd6.bad

It contain all messages I have been sending to 21:1/133 for a week or so and he
just tossed this morning (I think).

One message in there seems corrupt. No to, no from and no subject in the AFTERSHOCK area with a D'Bridge 4 tearline and the "you build it" origin.

Then the packet seems to continue on with fsxnet areas.

Still not sure what's up there.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Hello Nigel,

-rw-r-r--r-- 1 alan users 64005 Apr 11 08:58 06c53bd6.bad

It contain all messages I have been sending to 21:1/133 for a week or
so and he just tossed this morning (I think).

One message in there seems corrupt. No to, no from and no subject in
the AFTERSHOCK area with a D'Bridge 4 tearline and the "you build it" origin.

Then the packet seems to continue on with fsxnet areas.

Still not sure what's up there.

After thinking about that some more.. ;)

I think that corrupt packet from the fido AFTERSHOCK area was sitting in his inbound this morning when he did a weeks worth of tossing.

The packet somehow was tossed in fsxnet, corrupt data and all. Hopefully it has
now done what it is going to do and we won't see it anymore.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

On 11 Apr 2020 at 03:30p, Al pondered and said...

@REPLY: 224908.fsx_gen@21:1/121 6232ea8a
@MSGID: 21:4/106 5e924621
@CHRS: UTF-8 2
@TZUTC: -0700
@TID: hpt/lnx 1.9.0-cur 2019-12-05
@PATH: 4/106 100 2/100 1/100
128
Hello NuSkooler,

I'm not sure what is up. I got only two bad packets yesterday. I
took a quick look but couldn't determine just what had happened
and being in a hurry a deleted the bad packets.

I've noticed a influx of these as well lately.

I have not recieved any more of these so I still don't know what
happened.

Reading in Fidonet I see another node having an issue with these bad packets. They do look like corrupt packets from what I have been reading and did not originate at 21:1/106 as it looked from what I had seen.
They did originate in fidonet and not fsxNet

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

This was the first post I got... and you can see the origin line. The next
one has no origin but same PATH.

--- Mystic BBS v1.12 A46 2020/03/29 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 11 Apr 2020 at 03:30p, Al pondered and said...

@REPLY: 224908.fsx_gen@21:1/121 6232ea8a
@MSGID: 21:4/106 5e924621
@CHRS: UTF-8 2
@TZUTC: -0700
@TID: hpt/lnx 1.9.0-cur 2019-12-05
@PATH: 4/122 100 2/100 1/100
128
Hello NuSkooler,

I'm not sure what is up. I got only two bad packets yesterday. I
took a quick look but couldn't determine just what had happened
and being in a hurry a deleted the bad packets.

I've noticed a influx of these as well lately.

I have not recieved any more of these so I still don't know what
happened.

Reading in Fidonet I see another node having an issue with these bad packets. They do look like corrupt packets from what I have been reading and did not originate at 21:1/106 as it looked from what I had seen.
They did originate in fidonet and not fsxNet

this is the second one...

--- Mystic BBS v1.12 A46 2020/03/29 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Hello Avon,

On 11 Apr 2020 at 03:30p, Al pondered and said...

@REPLY: 224908.fsx_gen@21:1/121 6232ea8a
@MSGID: 21:4/106 5e924621
@CHRS: UTF-8 2
@TZUTC: -0700
@TID: hpt/lnx 1.9.0-cur 2019-12-05
@PATH: 4/122 100 2/100 1/100
128
Hello NuSkooler,

I'm not sure what is up. I got only two bad packets

yesterday. I

took a quick look but couldn't determine just what had

happened

and being in a hurry a deleted the bad packets.

I've noticed a influx of these as well lately.

I have not recieved any more of these so I still don't know what
happened.

Reading in Fidonet I see another node having an issue with these
bad packets. They do look like corrupt packets from what I have
been reading and did not originate at 21:1/106 as it looked from
what I had seen. They did originate in fidonet and not fsxNet

this is the second one...

This one is an oddity I can't explain. The path looks like it originated at 4/122, but we know that isn't true, or maybe it bounced off 4/122. I'm not sure.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Al wrote to Avon <=-

This one is an oddity I can't explain. The path looks like it
originated at 4/122, but we know that isn't true, or maybe it bounced
off 4/122. I'm not sure.

I reprocessed a handful of .bad packets in my inbound. They ran just fine through my tosser, don't know why they wouldn't have been marked as seen-by
my uplink and left locally.

I'd just updated Synchronet from January 2020 or so. Not sure if that made a difference.


... Repetition is a form of change
--- MultiMail/XT v0.52
* Origin: http://realitycheckbbs.org (21:4/122)