Hi,
I'm not sure if this has been logged as a bug or not, but just in case...

If I send a ping request to certain Mystic systems, the response returns as a bad packet, with the message that the DateTime is grunged

As an example, I sent a netmail to ping@4:80/1, and when the packet returned it was seen as a bad packet by the Synchronet tools with the message "Corrupted Message Header (DateTime)"

all the best
John




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

*** Quoting John Dovey from a message to All ***

As an example, I sent a netmail to ping@4:80/1, and when the packet returned it was seen as a bad packet by the Synchronet tools with the message "Corrupted Message Header (DateTime)"

Try sending a ping to 1:229/664 & see if that comes back ok. g00r00
recently made a change to the date on ping responses.


Jay

... Friends, Romans, countrymen, lend me your taglines!

--- Telegard v3.09.g2-sp4/mL
* Origin: Northern Realms/TG ∞ tg.nrbbs.net ∞ Binbrook, ON (1:229/664.2)

*** Quoting John Dovey from a message to All ***

As an example, I sent a netmail to ping@4:80/1, and when the packet
returned it was seen as a bad packet by the Synchronet tools with the
message "Corrupted Message Header (DateTime)"

Try sending a ping to 1:229/664 & see if that comes back ok. g00r00 recently made a change to the date on ping responses.

Thanks. Test on the way.
I tested to 1:219/225 and it wormed perfectly.

Could you send a ping test and see if it works for you to ping@4:80/1?

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

*** Quoting John Dovey from a message to Jay Harris ***

Thanks. Test on the way. I tested to 1:219/225 and it wormed
perfectly.

Yup, I see it here:

----------------- MUTIL v1.12 A48 2022/07/13 Thu, Jul 14 2022 (loglevel 2)
+ Jul 14 10:36:32 Startup using mailin.ini
+ Jul 14 10:36:32 Process: Toss FDN/TIC Files
+ Jul 14 10:36:32 Waiting for BUSY nodes
+ Jul 14 10:36:32 Scanning Hatches
+ Jul 14 10:36:32 Results: 0 import, 0 toss, 0 hatch, 0 bad in 0.01s
+ Jul 14 10:36:32 Process: Importing EchoMail
+ Jul 14 10:36:32 Waiting for BUSY nodes
+ Jul 14 10:36:32 Importing 41003210.PKT (1:229/426 to 1:229/664)
+ Jul 14 10:36:32 Importing 41013597.PKT (1:229/426 to 1:229/664)
+ Jul 14 10:36:32 Importing 41015320.PKT (1:229/426 to 1:229/664)
+ Jul 14 10:36:32 Importing 41016319.PKT (1:229/426 to 1:229/664)
+ Jul 14 10:36:32 Importing 41022042.PKT (1:229/426 to 1:229/664)
+ Jul 14 10:36:32 Importing 41022300.PKT (1:229/426 to 1:229/664)
+ Jul 14 10:36:32 Importing 41030311.PKT (1:229/426 to 1:229/664)
+ Jul 14 10:36:32 PING received from 4:920/1.1 to 1:229/664
+ Jul 14 10:36:32 Sending PING response to John Dovey@4:920/1.1 via 1:229/426
+ Jul 14 10:36:32 Importing 41034580.PKT (1:229/426 to 1:229/664)
+ Jul 14 10:36:32 Bundling Messages
+ Jul 14 10:36:32 Results: 14 echo, 0 net, 0 dupes, 29 tossed in 0.28s
+ Jul 14 10:36:32 Process: Linking Messages
+ Jul 14 10:36:36 Base: COOKING: National Cooking Echo
+ Jul 14 10:36:40 Base: RBERRYPI
+ Jul 14 10:36:50 Results: Linked 8 msgs in 17.47s
+ Jul 14 10:36:50 Shutdown Normal (0)

Could you send a ping test and see if it works for you to
ping@4:80/1?

Sure, I'll send one now.


Jay

... When people are free to do as they please, they usually imitate each other

--- Telegard v3.09.g2-sp4/mL
* Origin: Northern Realms/TG ∞ tg.nrbbs.net ∞ Binbrook, ON (1:229/664.2)

If I send a ping request to certain Mystic systems, the response returns as a bad packet, with the message that the DateTime is grunged

Thanks for the report. This has already been fixed in the latest A48 build along with another PING related bug as well! If notice it from any recent Mystic (say July 2022+) please let me know because then it'd mean its still broken!

... A Skydiver is taken by the gravity of his situation.

--- Mystic BBS v1.12 A48 2022/07/13 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

If I send a ping request to certain Mystic systems, the response returns
as a bad packet, with the message that the DateTime is grunged

Thanks for the report. This has already been fixed in the latest A48 build along with another PING related bug as well! If notice it from any recent Mystic (say July 2022+) please let me know because then it'd mean its still broken!

Thank you.
JD
--- AfterShock/Android 1.6.8
* Origin: Firecat Mobile (4:920/1.1)

*** Quoting Jay Harris from a message to John Dovey ***

Could you send a ping test and see if it works for you to
ping@4:80/1?

Sure, I'll send one now.

I didn't receive a response from your system. I got a trace reply from 1:229/426 once the packet left here, but nothing after that.

Do you see the ping hitting your system in mutil.log?


Jay

... Ambition is the last refuge of the failure

--- Telegard v3.09.g2-sp4/mL
* Origin: Northern Realms/TG ∞ tg.nrbbs.net ∞ Binbrook, ON (1:229/664.2)

*** Quoting Jay Harris from a message to John Dovey ***

Could you send a ping test and see if it works for you to
ping@4:80/1?

Sure, I'll send one now.

I didn't receive a response from your system. I got a trace reply from 1:229/426 once the packet left here, but nothing after that.

Do you see the ping hitting your system in mutil.log?

It's not my system. Check your bad packets. If its not there, it probably got grunged at some intermediate system.

JD

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

*** Quoting John Dovey from a message to Jay Harris ***

It's not my system. Check your bad packets. If its not there, it
probably got grunged at some intermediate system.

I have anything new in my bad since June. That's why I was asking if you
saw it hit your system in mutil.log. If you didn't then we know it never reached you.

I remember Nick posting his routing table once upon a time but I can't find
it at the moment. I know it passed through his system as I got a ping reply from there, where it went after that I'm not sure.


Jay

... Don't force it, get a larger hammer

--- Telegard v3.09.g2-sp4/mL
* Origin: Northern Realms/TG ∞ tg.nrbbs.net ∞ Binbrook, ON (1:229/664.2)