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?


...ëîåï

---
þ Synchronet þ Alterant | an SBBS in Docker on Pi!

Re: sbbsecho not importing netmail
By: deon to Digital Man on Fri Feb 18 2022 04:44 pm

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.

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.

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?

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?
--
digital man (rob)

Synchronet "Real Fact" #32:
The second most prolific contributor to Synchronet is Stephen Hurd (Deuce) Norco, CA WX: 50.6øF, 40.0% humidity, 1 mph NE wind, 0.00 inches rain/24hrs
---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: sbbsecho not importing netmail
By: Digital Man to deon on Thu Feb 17 2022 11:38 pm

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. :-)

https://gitlab.synchro.net/main/sbbs/-/commit/70898b5bb

(2 weeks ago).

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.

OK, 2/116 -> 3/1 -> 3/2744 -> 3/999 is the path of netmail. (The other direction is the reverse).

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?

I was wondering about the bad packet - and it's my next check. But sending netmail in the reverse direction works OK. (2/116 is quite old master/8f79438d2, which according to https://gitlab.synchro.net/main/sbbs/-/commit/8f79438d2 9 months ago).

I was discounting a bad packet, given the "Importing" line - but I guess that is the packet header, not the message header?

I'll explore the packet in detail and double check it's not bad (it's possible that it is...)


...ëîåï

---
þ Synchronet þ Alterant | an SBBS in Docker on Pi!

Re: sbbsecho not importing netmail
By: deon to Digital Man on Fri Feb 18 2022 09:39 pm

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...)

OK, thanks - got to the bottom of it (yes, a bad packet build). Looks like I need to do some more work on 3/2744...

Thanks for being the sounding board. :)



...ëîåï

---
þ Synchronet þ Alterant | an SBBS in Docker on Pi!