Hey DM,
I've been stumped with a test setup - and I've probably spent too much time trying to figure out what I've broken. So asking in case its' obvious.
I have a test setup of SBBS - compiled master/70898b5bb. It's configured as 21:3/999.
Sending a netmail from it to 21:2/116 works well.
Sending a netmail from 21:2/116 to 21:3/999 results in this:
2022-02-18 16:11:59 Importing /opt/sbbs/fido/inbound/0a452fa6.pkt (Type 2e, 0.4KB) from 21:3/2744 to 21:3/999
2022-02-18 16:11:59 Deon George (21:2/116) To: deon (21:0/0) Exported to /opt/sbbs/fido/netmail/1.msg
2022-02-18 16:11:59 Packing NetMail (1.msg) from Deon George (21:2/116) to deon (21:0/0), attr: 0001, subject: Test netmail
Why would it not recognise 21:3/999 as itself, and its trying to forward it on to 21:0/0?
I have a test setup of SBBS - compiled master/70898b5bb. It's configured as 21:3/999.
Sorry, I don't memorize the git SHAs, so not sure what version that is/was. :-)
Sending a netmail from it to 21:2/116 works well.
Sending a netmail from 21:2/116 to 21:3/999 results in this:
2022-02-18 16:11:59 Importing /opt/sbbs/fido/inbound/0a452fa6.pkt (Type 2e, 0.4KB) from 21:3/2744 to 21:3/999
Where does 21:3/2744 come in? You didn't mention that address in your intro.
Why would it not recognise 21:3/999 as itself, and its trying to forward it on to 21:0/0?
Well, 21:0/0 isn't a local address on your system, so naturally it'll be packed up to be sent on... somewhere.
Now 21:0/0 does sound like a bad packet. Use a tool pktdump to inspect the packet more closely.
Are you running the latest and greatest SBBSecho on both systems?
Now 21:0/0 does sound like a bad packet. Use a tool pktdump to inspect the packet more closely.
I'll explore the packet in detail and double check it's not bad (it's possible that it is...)
Sysop: | Coz |
---|---|
Location: | Anoka, MN |
Users: | 2 |
Nodes: | 4 (0 / 4) |
Uptime: | 189:16:06 |
Calls: | 183 |
Files: | 5,413 |
Messages: | 222,737 |