I upgraded to A39 a few days back and ran in to a problem: I couldn't login with nodespy, but could using ./mystic -l
There appear to be two issues:
If ip2location db doesn't exist it kicks everyone and everything (I think).
If it does exist, localhost is still often '1-Country Unknown (-)' and kicked.

I can login with nodespy on another system in my network, but not locally.
Part of it stems from bcw142.zapto.org not appearing valid, so mis uses ::
That causes:
22:43:13 RLOGIN > Connect on slot 1/5 (::FFFF:7F00:0001)
22:43:13 RLOGIN 1-HostName localhost
22:43:13 RLOGIN 1-Country Unknown (-)
22:43:13 RLOGIN 1-Creating terminal process
22:43:13 RLOGIN 1-Closed terminal process
22:46:23 TELNET > Connect on slot 1/8 (::FFFF:0A00:0005)
22:46:23 TELNET 1-HostName leno
22:46:23 TELNET 1-Country Unknown (-)
22:46:23 TELNET 1-Creating terminal process
22:48:15 TELNET 1-Closed terminal process

It doesn't matter if I use rlogin or telnet above, the results will be the same. Why using a remote host makes a difference I don't know, but as you
can see, it makes all the difference and lets me in even though the country
is unknown. Not really sure why, but it's very repeatable and I'm sure you'll know why (or figure it out).
My current work around is to use another system to telnet in.

--- Mystic BBS v1.12 A38 2018/01/01 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)

Found the iplocation thing to be a red herring unrelated to what I see as the bug. I can login remotely with nodespy from any system on my network (none of which use that latest alpha), but can't login to anything on v1.12 A39
Linux/32 Compiled 2018/03/12 12:59:52 nodespy. I have no problems with local or remote on v1.12 A39 Linux/64 Compiled 2018/02/28 13:41:16. I did find I can't use nodespy on the Linux/32 system to remote login to the Linux/64 system either. The nodespy on Linux/32 doesn't login to anything I've found. So the issue may be the nodespy. The Linux/64 version nodespy (earlier alpha) reaches everything, the Linux/32 version I have (newest) doesn't reach anything. Hopefully that narrows it down.

--- Mystic BBS v1.12 A38 2018/01/01 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)

There appear to be two issues:
If ip2location db doesn't exist it kicks everyone and everything (I think). If it does exist, localhost is still often '1-Country Unknown (-)' and kicked.

It sounds like you're saying that Unknown countries are being blocked but the logs you're posting do not show people being blocked. It doesn't say its blocking anyone and you can see that its creating the terminal process (BBS node) which also means its not blocking. The time stamp also shows that the connection was open for ~1.5 minutes.

22:46:23 TELNET 1-Country Unknown (-)
22:46:23 TELNET 1-Creating terminal process
22:48:15 TELNET 1-Closed terminal process

There is no country for localhost. Localhost is the same IP for someone in New York City as it is for someone in New Zealand, for example. If you try to determine the country from localhost IP, you will always get an Unknown result.

--- Mystic BBS v1.12 A39 2018/03/26 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 03/28/18, g00r00 said the following...

There appear to be two issues:
If ip2location db doesn't exist it kicks everyone and everything (I think). If it does exist, localhost is still often '1-Country Unknow (-)' and kicked.

It sounds like you're saying that Unknown countries are being blocked
but the logs you're posting do not show people being blocked. It
doesn't say its blocking anyone and you can see that its creating the terminal process (BBS node) which also means its not blocking. The time stamp also shows that the connection was open for ~1.5 minutes.

22:46:23 TELNET 1-Country Unknown (-)
22:46:23 TELNET 1-Creating terminal process
22:48:15 TELNET 1-Closed terminal process

So it sounds like it times out with the default timeout. The issue for me is that it doesn't connect to the localhost. I can connect from another system on the internal network, just not localhost. Not sure what to look for to figure out why it doesn't connect (from nodespy on the same system). The versions all agree. The newer Alpha does seem a little better at connecting to things, but not localhost. Only seems true of Windows 10 versions (I have a desktop and laptop that can run them). Linux seems to be fine (same alphas).

There is no country for localhost. Localhost is the same IP for someone in New York City as it is for someone in New Zealand, for example. If
you try to determine the country from localhost IP, you will always get
an Unknown result.

I didn't know that, I figured localhost was like the local IP address and so
in my case should be New York time. I guess it's a simpler interface than
that, just a local loopback on the TCP/IP stack.

--- Mystic BBS v1.12 A39 2018/02/28 (Linux/64)
* Origin: Workpoint (21:1/145.3)

So it sounds like it times out with the default timeout. The issue for
me is that it doesn't connect to the localhost. I can connect from
another system on the internal network, just not localhost. Not sure

I see. Well to me that sounds like it could be the network adapter setting. Can you show me what you have for the following settings for your TELNET server in the Server Editor:

"IP Type"
"IPV4 Adapter"
"IPV6 Adapter"

--- Mystic BBS v1.12 A39 2018/03/26 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

bcw142 wrote to g00r00 <=-

I didn't know that, I figured localhost was like the local IP address
and so in my case should be New York time. I guess it's a simpler interface than that, just a local loopback on the TCP/IP stack.

But in an IP lookup, that doesn't make sense. It will be "unknown", because localhost has no relationship to geography. It's only "local" in the sense of being on that specific machine, regardless of where that machine is located. :)


... A day without sunshine is like night.
=== MultiMail/Win32 v0.49
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)