Hi,
I've been banging my head against a wall with this and I wonder if someone else might have some insight.

My betmail connection with 4:80/1 works perfectly normally, but as soon as I send a message to ping@4:80/1 the packet that comes back is a bad packet.
Could someone else test this and see if they get the same thing please?

sbbsecho.log says:
2022-04-12 22:22:36 Importing C:\sbbs\fido\inbound\07a5e952.pkt (Type 2e, 2.8KB) from 4:80/1 to 4:920/1
2022-04-12 22:22:36 Grunged message (type 2) from 4:80/1 at offset 58 in packet: (null)
2022-04-12 22:22:36 Bad packet detected: C:\sbbs\fido\inbound\07a5e952.pkt

and pktdump says
C:\sbbs\fido\inbound\bad> C:\sbbs\exec\pktdump.exe .\077feb12.bad
pktdump rev 1.17 - Dump FidoNet Packets

Opening .\077feb12.bad
.\077feb12.bad Packet Type 2+ (prod: FEFE, rev: 0.0) from 4:80/1 to 4:920/1 .\077feb12.bad 00003A Corrupted Message Header (DateTime)
PS C:\sbbs\fido\inbound\bad>

All the best
John
--- AfterShock/Android 1.6.8
* Origin: Firecat Mobile (4:920/69.1)

Re: Grunged packet
By: John Dovey to All on Tue Apr 12 2022 10:34 pm

Hi,
I've been banging my head against a wall with this and I wonder if someone else might have some insight.

My betmail connection with 4:80/1 works perfectly normally, but as soon as I send a message to ping@4:80/1 the packet that comes back is a bad packet. Could someone else test this and see if they get the same thing please?

sbbsecho.log says:
2022-04-12 22:22:36 Importing C:\sbbs\fido\inbound\07a5e952.pkt (Type 2e, 2.8KB) from 4:80/1 to 4:920/1
2022-04-12 22:22:36 Grunged message (type 2) from 4:80/1 at offset 58 in packet: (null)
2022-04-12 22:22:36 Bad packet detected: C:\sbbs\fido\inbound\07a5e952.pkt

and pktdump says
C:\sbbs\fido\inbound\bad> C:\sbbs\exec\pktdump.exe .\077feb12.bad
pktdump rev 1.17 - Dump FidoNet Packets

Opening .\077feb12.bad
.\077feb12.bad Packet Type 2+ (prod: FEFE, rev: 0.0) from 4:80/1 to 4:920/1 .\077feb12.bad 00003A Corrupted Message Header (DateTime)

It looks like the system that's responding to the PING request has an issue. Most likely, its EchoMail program (tosser) is performing this PING service and has the issue (generating a bad response packet).
--
digital man (rob)

This Is Spinal Tap quote #2:
Nigel Tufnel: Well, this piece is called "Lick My Love Pump".
Norco, CA WX: 69.4øF, 21.0% humidity, 4 mph E wind, 0.00 inches rain/24hrs
--- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Grunged packet
By: John Dovey to All on Tue Apr 12 2022 10:34 pm

Hi,
I've been banging my head against a wall with this and I wonder if someone
else might have some insight.

My betmail connection with 4:80/1 works perfectly normally, but as soon as
I send a message to ping@4:80/1 the packet that comes back is a bad packet.
Could someone else test this and see if they get the same thing please?

sbbsecho.log says:
2022-04-12 22:22:36 Importing C:\sbbs\fido\inbound\07a5e952.pkt (Type 2e,
2.8KB) from 4:80/1 to 4:920/1
2022-04-12 22:22:36 Grunged message (type 2) from 4:80/1 at offset 58 in
packet: (null)
2022-04-12 22:22:36 Bad packet detected: C:\sbbs\fido\inbound\07a5e952.pkt

and pktdump says
C:\sbbs\fido\inbound\bad> C:\sbbs\exec\pktdump.exe .\077feb12.bad
pktdump rev 1.17 - Dump FidoNet Packets

Opening .\077feb12.bad
.\077feb12.bad Packet Type 2+ (prod: FEFE, rev: 0.0) from 4:80/1 to 4:920/1
.\077feb12.bad 00003A Corrupted Message Header (DateTime)

It looks like the system that's responding to the PING request has an issue. Most likely, its EchoMail program (tosser) is performing this PING service and has the issue (generating a bad response packet). --
digital man (rob)

This Is Spinal Tap quote #2:
Nigel Tufnel: Well, this piece is called "Lick My Love Pump".
Norco, CA WX: 69.4øF, 21.0% humidity, 4 mph E wind, 0.00 inches rain/24hrs

Rob,
I note that there was a commit for a fix on this issue in sbbsecho.c ??
John
--- AfterShock/Android 1.6.8
* Origin: Firecat Mobile (4:920/69.1)

Re: Grunged packet
By: John Dovey to Digital Man on Thu Apr 14 2022 10:13 am

Re: Grunged packet
By: John Dovey to All on Tue Apr 12 2022 10:34 pm

Hi,
I've been banging my head against a wall with this and I wonder if someone
else might have some insight.

My betmail connection with 4:80/1 works perfectly normally, but as soon as
I send a message to ping@4:80/1 the packet that comes back is a bad packet.
Could someone else test this and see if they get the same thing please?

sbbsecho.log says:
2022-04-12 22:22:36 Importing C:\sbbs\fido\inbound\07a5e952.pkt (Type 2e,
2.8KB) from 4:80/1 to 4:920/1
2022-04-12 22:22:36 Grunged message (type 2) from 4:80/1 at offset 58 in
packet: (null)
2022-04-12 22:22:36 Bad packet detected: C:\sbbs\fido\inbound\07a5e952.pkt

and pktdump says
C:\sbbs\fido\inbound\bad> C:\sbbs\exec\pktdump.exe .\077feb12.bad
pktdump rev 1.17 - Dump FidoNet Packets

Opening .\077feb12.bad
.\077feb12.bad Packet Type 2+ (prod: FEFE, rev: 0.0) from 4:80/1 to 4:920/1
.\077feb12.bad 00003A Corrupted Message Header (DateTime)

It looks like the system that's responding to the PING request has an issue. Most likely, its EchoMail program (tosser) is performing this PING service and has the issue (generating a bad response packet). --

Rob,
I note that there was a commit for a fix on this issue in sbbsecho.c ??

The commit I made yesteray? It was just for that "null" in the logged error message. That was supposed to be the packet filename. That change is not going to fix your issue with your that bad PING response packet.
--
digital man (rob)

Rush quote #26:
Too many hands on my time, too many feelings, too many things on my mind
Norco, CA WX: 64.4øF, 36.0% humidity, 1 mph E wind, 0.00 inches rain/24hrs
--- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Rob,
I note that there was a commit for a fix on this issue in sbbsecho.c ??

The commit I made yesteray? It was just for that "null" in the logged error message. That was supposed to be the packet filename. That change is not going to fix your issue with your that bad PING response packet. --
digital man (rob)

Damn. OK, thanks. Understood.

JD
--- AfterShock/Android 1.6.8
* Origin: Firecat Mobile (4:920/69.1)