Re: Configuring Point Node in sbbsecho.ini
By: Tom Moore to Digital Man on Fri Dec 06 2024 09:42 am

Normally your "additional echolists" (configured in echocfg->echolists) would be in BACKBONE.NA format, not AREAS.BBS format.

That said, if the echoes of interest are already carried on your BBS (listed in SCFG->Message Areas and have messages that you can read on your BBS), then these areas are already in your SBBSecho "Area File" (e.g. areas.bbs file) or you
can export from SCFG to the areas.bbs file and then your downlinks (this new "point node") should be able to query/list/add areas using Area Manager (a.k.a. "AreaFix") netmail messages.

Based on how my mailer works for my phone I will need to figure out a way to define two points.
I will need one for zone 1 and a second for zone 21.
I will need to have the areafix system set so that when I do a request for zone 21 it only gives me the list of areas that route over that particular ftn.

Configure an echolist in echocfg->EchoList for each network and set "Required Key" to unique value for each (e.g. "FIDO" for Zone 1 and "FSX" for Zone 2) and then give the appropriate key to each point in echocfg->Linked Nodes.

Also, make sure you have echocfg->EchoMail->Allow Nodes to Add Areas from Area File to "No".

What would the proper way be to handle areas that I wish to export that are not ftn based such as Dovenet?

Nothing special. But those message areas aren't going to be in official echoes in any zone you're a part of, so make sure you're not sending any DOVE-Net messages that receive via QWK upstream to your FTN uplinks.

How might I be able to read / reply to areas that do not have a matching ftn on the upstream?

If the subs are in your area file, you should be able to read/reply to them
via a linked FTN node.
--
digital man (rob)

Synchronet/BBS Terminology Definition #5:
ATASCII = ATARI Standard Code for Information Interchange
Norco, CA WX: 75.3øF, 21.0% humidity, 2 mph S wind, 0.00 inches rain/24hrs
--- SBBSecho 3.23-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Configuring Point Node in sbbsecho.ini
By: Digital Man to Tom Moore on Fri Dec 06 2024 10:17 am

What would the proper way be to handle areas that I wish to export that are not ftn based such as Dovenet?

Nothing special. But those message areas aren't going to be in official echoes in any zone you're a part of, so make sure you're not sending any DOVE-Net messages that receive via QWK upstream to your FTN uplinks.

Correction: you would need to enable "Gate Between Net Types" for the DOVE-Net sub-boards in SCFG (under Network Options for each). Otherwise, messages received via QWKnet won't be exported to FTN and vice versa.
--
digital man (rob)

Synchronet "Real Fact" #59:
Synchronet swag used to be available for purchase at cafepress.com/synchronet Norco, CA WX: 78.6øF, 18.0% humidity, 1 mph SE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.23-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Configure an echolist in echocfg->EchoList for each network and set "Required Key" to unique value for each (e.g. "FIDO" for Zone 1 and "FSX" for Zone 2) and then give the appropriate key to each point in echocfg->Linked Nodes.

Also, make sure you have echocfg->EchoMail->Allow Nodes to Add Areas from Area File to "No".

I have configured both settings you listed here.
When I sent my areafix request I got a netmail back on my point node stating that the areas I had set the key for were added to the export list for my point.

When I took a look at the areas.bbs file on my main system beside each of them I got the following text added to the uplink list.
One of the entries looked like the following:

fsx_gen FSX_GEN 21:2/100 48280:11682/32766
I am completely unsure how this weird node number was generated.
This should of been:
fsx_gen FSX_GEN 21:2/100 21:2/153.1

I can go ahead and do a search / replace on this invalid string, but I'm wondering how I can fix the issue the right way.

Thanks,
Tom
--- SBBSecho 3.23-Linux
* Origin: Cw Shack Bbs - kf4yey.com (1:135/205)

Re: Configuring Point Node in sbbsecho.ini
By: Tom Moore to Digital Man on Fri Dec 06 2024 07:13 pm

Configure an echolist in echocfg->EchoList for each network and set "Required Key" to unique value for each (e.g. "FIDO" for Zone 1 and "FSX" for Zone 2) and then give the appropriate key to each point in echocfg->Linked Nodes.

Also, make sure you have echocfg->EchoMail->Allow Nodes to Add Areas from Area File to "No".

I have configured both settings you listed here.
When I sent my areafix request I got a netmail back on my point node stating that the areas I had set the key for were added to the export list for my point.

When I took a look at the areas.bbs file on my main system beside each of them I got the following text added to the uplink list.
One of the entries looked like the following:

fsx_gen FSX_GEN
21:2/100 48280:11682/32766
I am completely unsure how this weird node number was generated.
This should of been:
fsx_gen FSX_GEN
21:2/100 21:2/153.1

I can go ahead and do a search / replace on this invalid string, but I'm wondering how I can fix the issue the right way.

It sounds like a bug in SBBSecho. Can you search your data/sbbsecho.log file for lines that say "AreaMgr (for x) Linking area: y" where x is the node address and y is teh echo-tag?

Is the node number "weird" in that/those log messages?
--
digital man (rob)

Synchronet "Real Fact" #53:
Synchronet Blackjack was the first multi-node/multi-user game for Synchronet Norco, CA WX: 76.6øF, 19.0% humidity, 1 mph WNW wind, 0.00 inches rain/24hrs --- SBBSecho 3.23-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Configuring Point Node in sbbsecho.ini
By: Digital Man to Tom Moore on Fri Dec 06 2024 04:31 pm

When I took a look at the areas.bbs file on my main system beside each of them I got the following text added to the uplink list.
One of the entries looked like the following:

fsx_gen FSX_GEN
21:2/100 48280:11682/32766
I am completely unsure how this weird node number was generated.
This should of been:
fsx_gen FSX_GEN
21:2/100 21:2/153.1

I can go ahead and do a search / replace on this invalid string, but I'm wondering how I can fix the issue the right way.

It sounds like a bug in SBBSecho. Can you search your data/sbbsecho.log file for lines that say "AreaMgr (for x) Linking area: y" where x is the node address and y is teh echo-tag?

Is the node number "weird" in that/those log messages?

Or it could be sbbsecho.log lines like this:
"AreaMgr (for x) Adding area from EchoList (y): z" where x is the node address, y is the echolist and z is the echo-tag. Look for either/both. Heck, look at all teh AreaMgr lines for clues! :-)
--
digital man (rob)

This Is Spinal Tap quote #37:
David St. Hubbins: We are Spinal Tap from the UK - you must be the USA!
Norco, CA WX: 76.6øF, 19.0% humidity, 1 mph WNW wind, 0.00 inches rain/24hrs --- SBBSecho 3.23-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

When I took a look at the areas.bbs file on my main system beside each of them I got the following text added to the uplink list.
One of the entries looked like the following:

fsx_gen FSX_GEN
21:2/100 48280:11682/32766
I am completely unsure how this weird node number was generated.
This should of been:
fsx_gen FSX_GEN
21:2/100 21:2/153.1

It sounds like a bug in SBBSecho. Can you search your data/sbbsecho.log file for lines that say "AreaMgr (for x) Linking area: y" where x is the node address and y is teh echo-tag?

Is the node number "weird" in that/those log messages?

Here are the log messages from my sbbsecho.log file in relation to the area manager request I sent.
Dec 06 18:41:56 AreaMgr (for 21:2/153.1) Request received from Khronos
Dec 06 18:41:56 AreaMgr (for 21:2/153.1) Linking area: FSX_GEN
Dec 06 18:41:56 AreaMgr (for 21:2/153.1) Linking area: FSX_BBS
Dec 06 18:41:56 AreaMgr (for 21:2/153.1) Linking area: FSX_ENG
Dec 06 18:41:56 AreaMgr (for 21:2/153.1) Linking area: FSX_MYS
Dec 06 18:41:56 AreaMgr (for 21:2/153.1) Linking area: FSX_MAG
Dec 06 18:41:56 AreaMgr (for 21:2/153.1) Linking area: FSX_HAM
Dec 06 18:41:56 AreaMgr (for 21:2/153.1) Linking area: FSX_CRY
Dec 06 18:41:56 AreaMgr (for 21:2/153.1) Linking area: FSX_GAMING
Dec 06 18:41:56 AreaMgr (for 21:2/153.1) Linking area: FSX_LFE
Dec 06 18:41:56 AreaMgr (for 21:2/153.1) Linking area: FSX_VIDEO
Dec 06 18:41:56 AreaMgr (for 21:2/153.1) Linking area: FSX_MUSIC
Dec 06 18:41:56 AreaMgr (for 21:2/153.1) Linking area: FSX_RETRO
Dec 06 18:41:56 AreaMgr (for 21:2/153.1) Linking area: FSX_SPACE
Dec 06 18:41:56 AreaMgr (for 21:2/153.1) Linking area: FSX_NET
Dec 06 18:41:56 AreaMgr (for 21:2/153.1) Linking area: FSX_TST
Dec 06 18:41:56 AreaMgr (for 21:2/153.1) Linking area: FSX_ADS
Dec 06 18:41:56 AreaMgr (for 21:2/153.1) Linking area: FSX_STA
Dec 06 18:41:56 AreaMgr (for 21:2/153.1) Linking area: FSX_FIL
Dec 06 18:41:56 AreaMgr (for 21:2/153.1) Linking area: FSX_BOT
Dec 06 18:41:56 AreaMgr (for 21:2/153.1) Linking area: FSX_DAT
Dec 06 18:41:56 AreaMgr (for 21:2/153.1) Link-requested area not found in EchoLists: 10TH_AMD

The last area message in the log is in relation to Fidonet areas that are not being sent to this point because I need to also create a point off of my 1:135/205 node for that zone.

Tom
--- SBBSecho 3.23-Linux
* Origin: Cw Shack Bbs - kf4yey.com (1:135/205)

Re: Configuring Point Node in sbbsecho.ini
By: Tom Moore to Digital Man on Fri Dec 06 2024 07:49 pm

Here are the log messages from my sbbsecho.log file in relation to the area manager request I sent.
Dec 06 18:41:56 AreaMgr (for 21:2/153.1) Request received from Khronos
Dec 06 18:41:56 AreaMgr (for 21:2/153.1) Linking area: FSX_GEN

Thanks, I think this is now fixed in git.
--
digital man (rob)

Breaking Bad quote #42:
We have laws, detective. Have your kindergarten teacher read them to you. Norco, CA WX: 73.6øF, 14.0% humidity, 0 mph NW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.23-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Configuring Point Node in sbbsecho.ini
By: Tom Moore to Digital Man on Fri Dec 06 2024 07:49 pm

Here are the log messages from my sbbsecho.log file in relation to the area manager request I sent.
Dec 06 18:41:56 AreaMgr (for 21:2/153.1) Request received from Khronos Dec 06 18:41:56 AreaMgr (for 21:2/153.1) Linking area: FSX_GEN

Thanks, I think this is now fixed in git.
--

Hi,
I pulled the latest Git version and the issue is still there.
Node number I got added to /sbbs/data/areas.bbs is now:
4984:40652/32765
to each area I want to export.

Tom
--- SBBSecho 3.23-Linux
* Origin: Cw Shack Bbs - kf4yey.com (1:135/205)

Re: Configuring Point Node in sbbsecho.ini
By: Tom Moore to Digital Man on Fri Dec 06 2024 07:49 pm

Here are the log messages from my sbbsecho.log file in relation to the area manager request I sent.
Dec 06 18:41:56 AreaMgr (for 21:2/153.1) Request received from Khronos Dec 06 18:41:56 AreaMgr (for 21:2/153.1) Linking area: FSX_GEN

Thanks, I think this is now fixed in git.

Hi,
I worked with Dan my fido uplink who also runs Synchronet and he also confirmed the issue.
What we figured out is that if you subscribe to an echo with areafix the incorrect node number gets added.
If you hand edit the areas.bbs file and assign the proper node number as an uplink you can remove it properly with an areafix request as expected.
This bug seems to be limited to echo subscription requests and not remove requests.

Tom
--- SBBSecho 3.23-Linux
* Origin: Cw Shack Bbs - kf4yey.com (1:135/205)

Thanks, I think this is now fixed in git.

I can confirm that this bug seems to be fixed.
When I subscribed to echos from my point the areas.bbs file was modified properly.

Tom
--- SBBSecho 3.23-Linux
* Origin: Cw Shack Bbs - kf4yey.com (1:135/205)