From: "Richard Vonzel" <richard.vonzel@1:154/110.remove-1s5-this>

Hello All!

I'm getting bad packets from one of my hubs. I am sending them areamgr request using the %help option, and it returns with the info but is marked as *.bad. Is there a way to tell why it's going bad? A log maybe?

RickV

=== GoldED+/W64-MSVC 1.1.5-b20240306
# Origin: The File Cabinet BBS (filecabi.casacam.net:1025) (1:154/110)
--- SBBSecho 3.24-Win32
* Origin: The File Cabinet BBS (filecabi.casacam.net:1025) (1:154/110)
--- Synchronet 3.20e-Linux NewsLink 1.2
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
--- NewsGate v1.0 gamma 2
* Origin: News Gate @ Net396 -Huntsville, AL - USA (1:396/4)

From: "MRO" <[email protected]-sb0-this>

To: Richard Vonzel
Re: Bad packets
By: Richard Vonzel to All on Sun Mar 23 2025 08:47 am

Hello All!

I'm getting bad packets from one of my hubs. I am sending them areamgr request using the %help option, and it returns with the info but is marked as *.bad. Is there a way to tell why it's going bad? A log maybe?

RickV

yes, when we have problems we look at the logs.
---
■ Synchronet ■ ::: BBSES.info - free BBS services :::
--- Synchronet 3.20e-Linux NewsLink 1.2
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
--- NewsGate v1.0 gamma 2
* Origin: News Gate @ Net396 -Huntsville, AL - USA (1:396/4)

From: "Digital Man" <[email protected]-sbm-this>

To: Richard Vonzel
Re: Bad packets
By: Richard Vonzel to All on Sun Mar 23 2025 08:47 am

Hello All!

I'm getting bad packets from one of my hubs. I am sending them areamgr request using the %help option, and it returns with the info but is marked as *.bad. Is there a way to tell why it's going bad? A log maybe?

Yes, sbbsecho.log (assuming you're using SBBSecho). Also, usually the *reason* for the bad-packet determination is in the filename, when echocfg->Global Settings->Incoming Bad Packets is set to "Rename *.reason.bad" (the default), again, assuming you're using SBBSecho.
--
digital man (rob)

Sling Blade quote #16:
Karl Childers (to Doyle, re: lawn mower blade): I aim to kill you with it. Mmm. Norco, CA WX: 75.5°F, 46.0% humidity, 7 mph WSW wind, 0.00 inches rain/24hrs --- Synchronet 3.20e-Linux NewsLink 1.2
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
--- NewsGate v1.0 gamma 2
* Origin: News Gate @ Net396 -Huntsville, AL - USA (1:396/4)

From: "Richard Vonzel" <[email protected]-109d-this>

To: Digital Man
Re: Bad packets
By: Digital Man to Richard Vonzel on Sun Mar 23 2025 15:59:12

Yes, sbbsecho.log (assuming you're using SBBSecho). Also, usually the *reason* for the bad-packet determination is in the filename, when echocfg->Global

Settings->> Incoming Bad Packets is set to "Rename *.reason.bad" (the
Settings->> default),

Thank you, that helps.

RickV
---
■ Synchronet ■ The File Cabinet BBS
--- Synchronet 3.20e-Linux NewsLink 1.2
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
--- NewsGate v1.0 gamma 2
* Origin: News Gate @ Net396 -Huntsville, AL - USA (1:396/4)

From: "Richard Vonzel" <richard.vonzel@1:154/110.remove-5fi-this>

To: Richard Vonzel
Hello RickV!

Thursday July 02 1970 01:16, I wrote to Digital Man:

Re: Bad packets
By: Digital Man to Richard Vonzel on Sun Mar 23 2025 15:59:12

Yes, sbbsecho.log (assuming you're using SBBSecho). Also, usually
the *reason* for the bad-packet determination is in the filename,
when echocfg->Global

Settings->> Incoming Bad Packets is set to "Rename *.reason.bad" (the
Settings->> default),

Thank you, that helps.

RickV
---
■ Synchronet ■ The File Cabinet BBS

I have that setup that way for a bad packet, when a packet comes in it's still call just *.bad, not that reason.bad. I'm not sure why it's bad anyways, it a netmail from a hub.

RickV

=== GoldED+/W64-MSVC 1.1.5-b20240306
# Origin: The File Cabinet BBS (filecabi.casacam.net:1025) (1:154/110)
--- SBBSecho 3.24-Win32
* Origin: The File Cabinet BBS (filecabi.casacam.net:1025) (1:154/110)
--- Synchronet 3.20e-Linux NewsLink 1.2
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
--- NewsGate v1.0 gamma 2
* Origin: News Gate @ Net396 -Huntsville, AL - USA (1:396/4)

From: "Digital Man" <[email protected]-qny-this>

To: Richard Vonzel
Re: Bad packets
By: Richard Vonzel to Richard Vonzel on Mon Mar 24 2025 06:29 am

Hello RickV!

Thursday July 02 1970 01:16, I wrote to Digital Man:

Re: Bad packets
By: Digital Man to Richard Vonzel on Sun Mar 23 2025 15:59:12

Yes, sbbsecho.log (assuming you're using SBBSecho). Also, usually
the *reason* for the bad-packet determination is in the filename,
when echocfg->Global

Settings->> Incoming Bad Packets is set to "Rename *.reason.bad" (the
Settings->> default),

Thank you, that helps.

RickV
---
■ Synchronet ■ The File Cabinet BBS

I have that setup that way for a bad packet, when a packet comes in it's still call just *.bad, not that reason.bad.

What's the exact filename? The "reason" is a variable here and will be replaced with the actual reason (e.g. "pkt-len", "pkt-term", "file-read", etc).

I'm not sure why it's bad anyways, it a netmail from a hub.

What does your sbbsecho.log say about it?
--
digital man (rob)

Steven Wright quote #19:
I intend to live forever ... So far, so good.
Norco, CA WX: 90.9°F, 18.0% humidity, 3 mph S wind, 0.00 inches rain/24hrs
--- Synchronet 3.20e-Linux NewsLink 1.2
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
--- NewsGate v1.0 gamma 2
* Origin: News Gate @ Net396 -Huntsville, AL - USA (1:396/4)