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
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->GlobalSettings->> Incoming Bad Packets is set to "Rename *.reason.bad" (the
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, usuallySettings->> Incoming Bad Packets is set to "Rename *.reason.bad" (the
the *reason* for the bad-packet determination is in the filename,
when echocfg->Global
Settings->> default),
Thank you, that helps.
RickV
---
þ Synchronet þ The File Cabinet BBS
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, usuallySettings->> Incoming Bad Packets is set to "Rename *.reason.bad" (the
the *reason* for the bad-packet determination is in the filename,
when echocfg->Global
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.
Sysop: | marcvandam |
---|---|
Location: | Utrecht |
Users: | 9 |
Nodes: | 4 (0 / 4) |
Uptime: | 172:43:35 |
Calls: | 80 |
Calls today: | 80 |
Files: | 72 |
U/L today: |
2 files (2,547K bytes) |
D/L today: |
345 files (251M bytes) |
Messages: | 10,335 |
Posted today: | 7 |