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)