Hey DM, I question on routing. I've been doing some testing.

I have 2 SBBS setups (on FSXnet) - one is 2/116, the other is 3/100.

2/116 in sbbsecho.ini, there is no definition for 3/100 - but a definition for 21:ALL, so that all netmail goes via the hub (2/100).

On 3/100 it is similar, with 21:2/ALL sending everything to 2/100.

I could send a message happily from 2/116 to 3/100 (it would go via 2/100).

On 3/100, I then setup a config for 2/116 in sbbsecho.ini, but I had "Direct: no" "Route To: disabled".

On 3/100, if I now send a message to 2/116, it will end up in BSO to go direct to 2/116, instead of being packed for 2/100. I would have thought with "Direct: no", it would be routed?

Do I have it wrong?
...ëîå*

... Hypochondria is the only disease I haven't got.

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

Re: Netmail Routing
By: Alterego to Digital Man on Mon Nov 18 2019 08:03 pm

Hey DM, I question on routing. I've been doing some testing.

I have 2 SBBS setups (on FSXnet) - one is 2/116, the other is 3/100.

2/116 in sbbsecho.ini, there is no definition for 3/100 - but a definition for 21:ALL, so that all netmail goes via the hub (2/100).

On 3/100 it is similar, with 21:2/ALL sending everything to 2/100.

I could send a message happily from 2/116 to 3/100 (it would go via 2/100).

On 3/100, I then setup a config for 2/116 in sbbsecho.ini, but I had "Direct: no" "Route To: disabled".

On 3/100, if I now send a message to 2/116, it will end up in BSO to go direct to 2/116, instead of being packed for 2/100. I would have thought with "Direct: no", it would be routed?

Do I have it wrong?

It would be routed if there was a wildmatch (e.g. for 21:2/ALL) with a route-to address configured *and* direct was set to "No".

Here's the relevant logic in sbbsecho.c:

nodecfg=findnodecfg(&cfg, dest,0);
lprintf(LOG_INFO,"Sending packet (%s, %1.1fKB) from %s to %s"
, tmp_pkt, flength(tmp_pkt)/1024.0, smb_faddrtoa(&orig, str)
, smb_faddrtoa(&dest,NULL));

if(cfg.flo_mailer) {
if(nodecfg!=NULL && !nodecfg->direct && nodecfg->route.zone) {
dest=nodecfg->route;
lprintf(LOG_NOTICE,"Routing packet (%s) to %s",tmp_pkt
, smb_faddrtoa(&dest,NULL));
}
}


digital man

Synchronet "Real Fact" #101:
Alternate and loadable font support was added to Synchronet in February 2018. Norco, CA WX: 91.4øF, 9.0% humidity, 1 mph WSW wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Netmail Routing
By: Digital Man to Alterego on Mon Nov 18 2019 01:03 pm

It would be routed if there was a wildmatch (e.g. for 21:2/ALL) with a route-to address configured *and* direct was set to "No".

Well, that is what I thought, but it appears to not be...
#--#
I created a test message:
Attr: Deleted
To : deon (21:2/116)
From: Deon George #1 (21:3/100)
Date: Tue Nov 19 2019 09:41 am UTC (20 seconds ago)

test
test
#--#

It was tossed direct:
#--#
2019-11-19 09:41:58 Created NetMail (1.msg) from Deon George (21:3/100) to deon (21:2/116), attr: 0181, subject: test
2019-11-19 09:41:58 Packing NetMail (1.msg) from Deon George (21:3/100) to deon (21:2/116), attr: 0181, subject: test
2019-11-19 09:41:58 SBBSecho (PID 5436) exiting with error level 0, NetMail(0 imported, 1 exported, 1 packed)

C:\MAILER\outbound.015>dir 0002*.*
Volume in drive C has no label.
Volume Serial Number is 1A0C-BF40

Directory of C:\MAILER\outbound.015

19/11/2019 09:41 AM 365 00020074.out
1 File(s) 365 bytes
0 Dir(s) 12,697,571,328 bytes free
#--#

The entry for 2/116 in sbbsecho.cfg was just created, all defaults: [node:21:2/116@fsxnet]
Name = Deon George
Archive = None
PacketType = 2+
PacketPwd =
AreaFix = false
Inbox =
Outbox =
Passive = false
Direct = false
Notify = false
Status = Normal

There is a corresponding 21:2/ALL
[node:21:2/ALL@fsxnet]
Name = FSXnet HUB2
PacketType = 2+
PacketPwd =
Inbox =
Outbox =
Passive = false
Direct = false
Notify = false
Status = Normal
Route = 21:2/100

So, shouldnt this netmail have been routed via 21:2/100?
...ëîå*

... When Chuck Norris has surgery, the anesthesia is applied to the doctors.

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

Re: Netmail Routing
By: Alterego to Digital Man on Tue Nov 19 2019 09:40 am

Re: Netmail Routing
By: Digital Man to Alterego on Mon Nov 18 2019 01:03 pm

It would be routed if there was a wildmatch (e.g. for 21:2/ALL) with a route-to address configured *and* direct was set to "No".

Well, that is what I thought, but it appears to not be...
#--#
I created a test message:
Attr: Deleted
To : deon (21:2/116)
From: Deon George #1 (21:3/100)
Date: Tue Nov 19 2019 09:41 am UTC (20 seconds ago)

test
test
#--#

It was tossed direct:
#--#
2019-11-19 09:41:58 Created NetMail (1.msg) from Deon George (21:3/100) to deon (21:2/116), attr: 0181, subject: test
2019-11-19 09:41:58 Packing NetMail (1.msg) from Deon George (21:3/100) to deon (21:2/116), attr: 0181, subject: test
2019-11-19 09:41:58 SBBSecho (PID 5436) exiting with error level 0, NetMail(0 imported, 1 exported, 1 packed)

C:\MAILER\outbound.015>dir 0002*.*
Volume in drive C has no label.
Volume Serial Number is 1A0C-BF40

Directory of C:\MAILER\outbound.015

19/11/2019 09:41 AM 365 00020074.out
1 File(s) 365 bytes
0 Dir(s) 12,697,571,328 bytes free
#--#

The entry for 2/116 in sbbsecho.cfg was just created, all defaults: [node:21:2/116@fsxnet]
Name = Deon George
Archive = None
PacketType = 2+
PacketPwd =
AreaFix = false
Inbox =
Outbox =
Passive = false
Direct = false
Notify = false
Status = Normal

There is a corresponding 21:2/ALL
[node:21:2/ALL@fsxnet]
Name = FSXnet HUB2
PacketType = 2+
PacketPwd =
Inbox =
Outbox =
Passive = false
Direct = false
Notify = false
Status = Normal
Route = 21:2/100

So, shouldnt this netmail have been routed via 21:2/100?

No, because you have linked node entry for 21:2/116, so the 21:2/ALL node won't be matched against. And your 21:2/116 linked node is configured to *not* route. When looking for an outbound node configuration, a "best match" search is performed and since you have an exact-match node configured, that's the node config that will be used.

digital man

Synchronet "Real Fact" #12:
Synchronet was the first BBS software to ship with built-in RIPscrip support. Norco, CA WX: 85.0øF, 12.0% humidity, 1 mph SE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Netmail Routing
By: Digital Man to Alterego on Mon Nov 18 2019 04:28 pm

No, because you have linked node entry for 21:2/116, so the 21:2/ALL node won't be matched against. And your 21:2/116 linked node is configured to *not* route. When looking for an outbound node configuration, a "best match" search is performed and since you have an exact-match node configured, that's the node config that will be used.

Ahh, ok, got it...

Tks...
...ëîå*

... Religions change; Beer and Wine remain.

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

Re: Netmail Routing
By: Alterego to Digital Man on Tue Nov 19 2019 12:13 pm

No, because you have linked node entry for 21:2/116, so the 21:2/ALL
node won't be matched against. And your 21:2/116 linked node is
configured to *not* route. When looking for an outbound node
configuration, a "best match" search is performed and since you have
an exact-match node configured, that's the node config that will be
used.

Oh, wait, I've thought about this a little more...

Whats the difference between Direct=false and Direct=true in this scenario? ...ëîå*

... Massachusetts has the best politicians money can buy.

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

Re: Netmail Routing
By: Alterego to Digital Man on Tue Nov 19 2019 01:17 pm

Re: Netmail Routing
By: Alterego to Digital Man on Tue Nov 19 2019 12:13 pm

No, because you have linked node entry for 21:2/116, so the 21:2/ALL
node won't be matched against. And your 21:2/116 linked node is
configured to *not* route. When looking for an outbound node
configuration, a "best match" search is performed and since you have
an exact-match node configured, that's the node config that will be
used.

Oh, wait, I've thought about this a little more...

Whats the difference between Direct=false and Direct=true in this scenario?

The FLO file created will be .dlo (for direct) or a different extension (e.g. .flo) otherwise.
http://wiki.synchro.net/ref:fidonet_files

digital man

This Is Spinal Tap quote #2:
Nigel Tufnel: Well, this piece is called "Lick My Love Pump".
Norco, CA WX: 70.1øF, 25.0% humidity, 0 mph WSW wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Netmail Routing
By: Digital Man to Alterego on Mon Nov 18 2019 09:04 pm

Whats the difference between Direct=false and Direct=true in this
scenario?

The FLO file created will be .dlo (for direct) or a different extension (e.g. .flo) otherwise.
http://wiki.synchro.net/ref:fidonet_files

Now, I'm confused even more.

With my intention to define a node in sbbsecho.ini, but still have any netmails routed via it's hub - Direct=false/Direct=true do not help me here - correct?

It will still be "direct" unless I edit "Route =" for said entry.
...ëîå*

... Don't hit me, Mr. Moderator! I'll go back on topic, I swear!

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

Re: Netmail Routing
By: Alterego to Digital Man on Tue Nov 19 2019 05:22 pm

Re: Netmail Routing
By: Digital Man to Alterego on Mon Nov 18 2019 09:04 pm

Whats the difference between Direct=false and Direct=true in this
scenario?

The FLO file created will be .dlo (for direct) or a different extension (e.g. .flo) otherwise.
http://wiki.synchro.net/ref:fidonet_files

Now, I'm confused even more.

With my intention to define a node in sbbsecho.ini, but still have any netmails routed via it's hub - Direct=false/Direct=true do not help me here - correct?

It will still be "direct" unless I edit "Route =" for said entry.

It will be non-routed unless you have a "Route" value for that linked node, yes.

digital man

Synchronet/BBS Terminology Definition #1:
ANSI = American National Standards Institute
Norco, CA WX: 68.4øF, 34.0% humidity, 0 mph SE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net