Hello,

Well, I just realized that despite I can setup the port for my Binkd server at Mystic, I can't select the port if my uplink / downlink port is different than the default one.

I will have it here on record in case g00r00 takes a look at this echo and can comment if this support will come in future releases.

Regards,
Flavio

... A Mystic asking for a hot-dog: "Make me one with everything"

--- Mystic BBS v1.12 A48 (macOS/64)
* Origin: Saturn's Orbit BBS - Back from the ashes (4:801/188)

Hello Flavio,

On Fri, Apr 26 2024 04:42:22 +0000, you wrote:

Well, I just realized that despite I can setup the port for my Binkd server at Mystic, I can't select the port if my uplink / downlink port
is different than the default one.

I will have it here on record in case g00r00 takes a look at this echo
and can comment if this support will come in future releases.

Wait, what?

You can definitely specify the port of the binkp link you're connecting to.

Regards,
Nick

... Take my advice, I don't use it anyway.
--- slrn/pre1.0.4-9 (Linux)
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

On 25 Apr 2024 at 08:42p, Flavio Bessa pondered and said...

Hello,

Well, I just realized that despite I can setup the port for my Binkd server at Mystic, I can't select the port if my uplink / downlink port
is different than the default one.

for your uplink just state the port in your domain name e.g. net4.fsxnet.nz:24560 as an example in Zone 21 for the NET 4 HUB

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

On 26 Apr 2024, Paul Hayton said the following...

for your uplink just state the port in your domain name e.g. net4.fsxnet.nz:24560 as an example in Zone 21 for the NET 4 HUB

Nice! I tested it here and it works... I even found another issue on the nodelist: If I try to poll a node that has a binkp port different from the default, the MIS POLL does not acknowledge the IBN flags and will poll with the default port only...

... Everyone is entitled to my opinion!

--- Mystic BBS v1.12 A48 (macOS/64)
* Origin: Saturn's Orbit BBS - Back from the ashes (4:801/188)

Well, I just realized that despite I can setup the port for my Binkd server at Mystic, I can't select the port if my uplink / downlink port
is different than the default one.

I will have it here on record in case g00r00 takes a look at this echo
and can comment if this support will come in future releases.

Yes you can as it shows in the help line at the bottom of the configuration you use the hostname:port format for the hostname field if you need to change the port. If you don't configure a port it will use the default ports (which varies depending on if you are using SSL or cleartext connection)

... Old musicians never die. They just decompose!

--- Mystic BBS v1.12 A49 2024/05/13 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

Nice! I tested it here and it works... I even found another issue on the nodelist: If I try to poll a node that has a binkp port different
from the default, the MIS POLL does not acknowledge the IBN flags and
will poll with the default port only...

Mystic pulls from the INA value not IBN.

I need to review those flags (or if someone has good knowledge of it and can clarify) to figure out what the correct login should be when INA and IBN are available. I believe having it take the address only from INA was a more recent change and the logic used to be different.

Once that is done I can check to make sure the port is getting parsed.

... Everyone smiles in the same language.

--- Mystic BBS v1.12 A49 2024/05/13 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

On Mon, 13 May 2024 05:47:46 -0400, G00r00 -> Flavio Bessa wrote:

Mystic pulls from the INA value not IBN.

I need to review those flags (or if someone has good knowledge of it and can clarify) to figure out what the correct login should be when INA and IBN are available. I believe having it take the address only from INA
was a more recent change and the logic used to be different.

I believe correct practice is INA:<hostname> and IBN:<port>, only if the port being used is *not* the default port. Otherwise, "IBN" with no port specified assumes the default.

Once that is done I can check to make sure the port is getting parsed.

By the way, HI AND LONG TIME NO SEE. :D

Regards,
Nick

... Take my advice, I don't use it anyway.
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

On 13 May 24 18:48:56, Nicholas Boel said the following to G00R00:

Once that is done I can check to make sure the port is getting parsed.

By the way, HI AND LONG TIME NO SEE. :D

I'm extremely upset. You did not return with Mystic 10 More Cowbell Edition.

For shame...

Atreyu

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)

On 13 May 2024 at 06:48p, Nicholas Boel pondered and said...

I believe correct practice is INA:<hostname> and IBN:<port>, only if the port being used is *not* the default port. Otherwise, "IBN" with no port specified assumes the default.

this is how I set up the fsx nodelist entries.

Once that is done I can check to make sure the port is getting parsed.

By the way, HI AND LONG TIME NO SEE. :D

I agree :)

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

Hi g00r00,

On 2024-05-13 18:48:56, Nicholas Boel wrote to you:

Mystic pulls from the INA value not IBN.

I need to review those flags (or if someone has good knowledge of it and
can clarify) to figure out what the correct login should be when INA and
IBN are available. I believe having it take the address only from INA
was a more recent change and the logic used to be different.

I believe correct practice is INA:<hostname> and IBN:<port>, only if the port
being used is *not* the default port. Otherwise, "IBN" with no port specified
assumes the default.

IBN:<hostname>[:<port>] is also correct.
or
The hostname in the system name field, and just a plain IBN.

I think both forms are in the current Fidonet nodelist. The first one for sure.


Bye, Wilfred.

--- FMail-lnx64 2.3.2.3-B20240423
* Origin: FMail development HQ (2:280/464)

I believe correct practice is INA:<hostname> and IBN:<port>, only if the port being used is *not* the default port. Otherwise, "IBN" with no port specified assumes the default.

Thank you for that information.

I took a look in a nodelist which is quite outdated at this point, but the results are not what I expected:

I see some like "INA:weather-station.org,IBN:24555"
Then I see one with no INA and an IBN:theoraclebbs.com
Then I see INA:shenks.synchro.net,IBN:shenks.dyndns.org
Then I see INA:vintagebbsing.com:24555,IBN

This logic should handle all of those situations and may be what I experiment with:

Set default port to binkp default
Check for INA. If not blank then get hostname
If INA hostname has ":" in it then pull the port replacing the default
Check IBN:
If not blank then check for all numbers. If all numbers then replace default port
If blank hostname then pull hostname from IBN

First example would return weather-station.org:24555
Second example would return theoraclebbs.com:default
Third example would return shenks.dyndns.org:default
Fourth example would return vintagebbs.com:24555

By the way, HI AND LONG TIME NO SEE. :D

Hey man happy to see you around. I am still lurking! The message backlog can be overwhelming when on limited time because usually each message comes with a queue of work or research for me to respond to.

... Radioactive cats have 18 half-lives

--- Mystic BBS v1.12 A49 2024/05/13 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

I believe correct practice is INA:<hostname> and IBN:<port>, only if port being used is *not* the default port. Otherwise, "IBN" with no p specified assumes the default.

this is how I set up the fsx nodelist entries.

Thank you for that.

Having looked at a couple nodelists briefly it does appear there are some results that are not following it but many do. I probably tried to come up with something that handles many things I saw but missed the mark last time I looked at it.

I have come up with some new logic that will take care of all the examples I pulled out and I will experiment with that. I put a little more detail in my respond to Nick if you're interested.

... I'm not a complete idiot... Several parts are missing!

--- Mystic BBS v1.12 A49 Maximum Cowbell Extreme 2K24 2024/05/26 (Windows/32)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

I'm extremely upset. You did not return with Mystic 10 More Cowbell Edition.

For shame...

Atreyu

I have done you a great disservice my friend, for that I apologize!

... Enter any 12-digit prime number to continue.

--- Mystic BBS v1.12 A49 Maximum Cowbell Extreme 2K24 2024/05/26 (Windows/32)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

Hi g00r00,

On 2024-05-26 23:13:30, you wrote to Nicholas Boel:

I see some like "INA:weather-station.org,IBN:24555"
Then I see one with no INA and an IBN:theoraclebbs.com
Then I see INA:shenks.synchro.net,IBN:shenks.dyndns.org

These 3 are correct.

Then I see INA:vintagebbsing.com:24555,IBN

This one is wrong! You can't specify a port after an INA, only a hostname! This entry should be ignored.

Btw: This entry is already corrected in the current nodelist. And the RC that was responsible for it, has been removed.

Btw2: Why don't you stick to FTS-5001 for this, instead of relying on examples from the nodelis? It's all in there!


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)

I see some like "INA:weather-station.org,IBN:24555"
Then I see one with no INA and an IBN:theoraclebbs.com
Then I see INA:shenks.synchro.net,IBN:shenks.dyndns.org

These 3 are correct.

Then I see INA:vintagebbsing.com:24555,IBN

This one is wrong! You can't specify a port after an INA, only a
hostname! This entry should be ignored.

Thanks for clearing that up!

Btw2: Why don't you stick to FTS-5001 for this, instead of relying on examples from the nodelis? It's all in there!

The logic I outlined would properly parse all of the FTS complaint examples I believe, but I will of course double check if Mystic has a problem now and any adjustments if it does need will be tested to properly parse all 3 of those.

Thank you for providing the FTS so I don't have to dig to find it! I will note it in the code for reference! :)

... They say there's always one weirdo on the bus, but I couldn't find them!

--- Mystic BBS v1.12 A49 Maximum Cowbell Extreme 2K24 2024/05/26 (Windows/32)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

Hi g00r00,

On 2024-05-27 07:10:29, you wrote to me:

Thank you for providing the FTS so I don't have to dig to find it! I
will note it in the code for reference! :)

And put a printed copy under your pillow! ;-)


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)

Nice! I tested it here and it works... I even found another issue on the nodelist: If I try to poll a node that has a binkp port different
from the default, the MIS POLL does not acknowledge the IBN flags and
will poll with the default port only...

This shoud be fixed in the latest prealpha build but still would of course be mostly untested.

Thank you for reporting!

... Error, no Keyboard - Press F1 to Continue.

--- Mystic BBS v1.12 A49 2024/05/29 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

Thank you for providing the FTS so I don't have to dig to find it! I will note it in the code for reference! :)

And put a printed copy under your pillow! ;-)

Done! (And I fixed Mystic too!)

... A Meteor is an example of a rock star.

--- Mystic BBS v1.12 A49 2024/05/29 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

On 26 May 24 23:27:08, g00r00 wrote:

Im extremely upset. You did not return with Mystic 10 More Cowbell Edition.

For shame...

Atreyu

I have done you a great disservice my friend for that I apologize!

... Enter any 12-digit prime number to continue.

--- Mystic BBS v1.12 A49 Maximum Cowbell Extreme 2K24 2024/05/26 (Windows/32)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

We need more Cowbell!
-Nugax


--- CyberBBS v1.0.12 2024/03/31 [Debian Linux/x64]
* Origin: CyberBBS BBS WHQ System | whq.cyberbbs.net:6023 (1:19/40)

On 29 May 2024 at 10:12p, g00r00 pondered and said...

This shoud be fixed in the latest prealpha build but still would of
course be mostly untested.

Hi there.

Just a note that I tried the 32bit RPi build installer and it failed to allow me to install to /mystic/ from the root directory. I tried the sudo ./install option and that did not work either. Just hit the unable to create /mystic/ message.

If I opted for F5 use home directory it showed me the root path of /root/mystic so I can confirm I was acting with root privileges when I invoked sudo but hit the above mentioned problem.

Also during an earlier test on the last 64 bit build I found I was having problems using 'mis poll 21:1/100' when I set up 21:1/100 as a BinkP echomail node in Mystic.

For whatever reason it looked like mis was polling out to the BinkP server but the receiving system on another machine on my LAN did not see any incoming connection from MIS on the Rpi..

So just flagging there *may* be something in the Rpi code that *might* be amiss when 'mis poll' is calling a binkP style echomail node?

Another thing I spotted in the mutil.ini there's a reference in whatsnew.txt to the new function EchoUnlink.

; exclude=MYSTIC
; exclude=FSX_*

But the reason I mention this because I wanted to let you know that you've omitted the function call at the top of the mutil.ini

; EchoUnlink = false

[time passes]

I also ran a test using the exclude=FSX_* but have found it does not honour the switch, the reports I am generating 'action_mode=0' are still flagging fsxNet bases that should be excluded. So something is may be up there also.

I ran the function from mutil directly using ./mutil -run EcoUnlink

Best, Paul

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

On 30 May 2024 at 09:55p, Paul Hayton pondered and said...

Also during an earlier test on the last 64 bit build I found I was having problems using 'mis poll 21:1/100' when I set up 21:1/100 as a BinkP echomail node in Mystic.

Just as an addendum to this report, I tested the latest build for 32 bit and there was no problem getting mis poll to poll out to another system on my LAN.

Mystic BBS v1.12 A49 Raspberry Pi/32 Compiled 2024/05/29 19:07:23

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

Unaccceptable!
-Nugax


--- CyberBBS v1.0.12 2024/06/02 [Debian Linux/x64]
* Origin: CyberBBS BBS WHQ System | whq.cyberbbs.net:6023 (1:19/40)

Welcome back, hope you're doing well.

Just copying this post I sent you last year, not sure if you saw it / there is/was any issues with the 64 bit build but just wanted to spotlight this should you be doing any checking/work on Mystic in the coming period.

Also do you envisage a release of A49 in the coming months? If yes, I going to hold off any any video updates until after that's out.

On 30 May 2024 at 09:55p, Paul Hayton pondered and said...

On 29 May 2024 at 10:12p, g00r00 pondered and said...

This shoud be fixed in the latest prealpha build but still would of course be mostly untested.

Hi there.

Just a note that I tried the 32bit RPi build installer and it failed to allow me to install to /mystic/ from the root directory. I tried the
sudo ./install option and that did not work either. Just hit the unable
to create /mystic/ message.

If I opted for F5 use home directory it showed me the root path of /root/mystic so I can confirm I was acting with root privileges when I invoked sudo but hit the above mentioned problem.

Also during an earlier test on the last 64 bit build I found I was having problems using 'mis poll 21:1/100' when I set up 21:1/100 as a BinkP echomail node in Mystic.

For whatever reason it looked like mis was polling out to the BinkP
server but the receiving system on another machine on my LAN did not see any incoming connection from MIS on the Rpi..

So just flagging there *may* be something in the Rpi code that *might*
be amiss when 'mis poll' is calling a binkP style echomail node?

Another thing I spotted in the mutil.ini there's a reference in whatsnew.txt to the new function EchoUnlink.

; exclude=MYSTIC
; exclude=FSX_*

But the reason I mention this because I wanted to let you know that
you've omitted the function call at the top of the mutil.ini

; EchoUnlink = false

[time passes]

I also ran a test using the exclude=FSX_* but have found it does not honour the switch, the reports I am generating 'action_mode=0' are still flagging fsxNet bases that should be excluded. So something is may be
up there also.

I ran the function from mutil directly using ./mutil -run EcoUnlink

Best, Paul

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)