Hey folks,

I've noticed a few packets in my inbound that clrghouz hasnt fully processed.

It ultimately has rejected the last message in the packet, because the packet has ended with 2 NULLs, where I'm ultimately expecting 3.

(I'm looking for a 1 NULL to signify the end of the message, and then 2 NULLs to signify the end of the packet - or 02 00 for the next message).

I guess I ultimately have to put in some code to work around this, but wondering if anybody knows what it should be?

Looking further, strangely, I have some from synchronet, that only have 1 NULL... so that might be a symptom of a different problem...


...ëîåï
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Re: Some bad packets on clrghouz
By: deon to All on Thu Dec 07 2023 04:25 pm

Looking further, strangely, I have some from synchronet, that only have 1 NULL... so that might be a symptom of a different problem...

Alas, I think it was.

I'll keep tabs on it...


...ëîåï
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)