I seem to have the same issue as Jeffs, but with Telnet and ssh! I found
your right:
telnet localhost -l bcw142
does let me login with both Telnet and SSH, rlogin works normally.
Is there a way to pass port information to telnet/ssh when used that way?
I notice it changes the setup and I have to answer 1 for Ansi and then
1 for UTF-8 to get the correct look even though I have it set that way
in configuration (Login/Matrix Settings: Default CodePage CP437, Local CodePage UTF8). I have settings to Ask so I get around it that way.
It seems to be effecting binkp as well:
Dec 04 11:21:25 FIDOPOLL Version 1.12 A36 2017/12/03
Dec 04 11:21:25 Scanning 21:1/145
Dec 04 11:21:25 Queued 1 files (1607 bytes) to 21:1/145
Dec 04 11:21:25 Polling BINKP node 21:1/145 by IPV4
Dec 04 11:21:25 Connecting to 10.0.0.21:24556
Dec 04 11:21:26 Connected
Dec 04 11:21:26 RB Socket read result 111
Dec 04 11:21:26 C: Data 0/24828
Dec 04 11:21:26 Connection lost
Dec 04 11:21:26 Authorization failed
Dec 04 11:21:39 FIDOPOLL Version 1.12 A36 2017/12/03
Dec 04 11:21:39 Scanning 80:603/0
Dec 04 11:21:39 Queued 0 files (0 bytes) to 80:603/0
Dec 04 11:21:39 Polling BINKP node 80:603/0 by IPV4
Dec 04 11:21:39 Connecting to 10.0.0.21:24556
Dec 04 11:21:40 Connected
Dec 04 11:21:40 RB Socket read result 111
Dec 04 11:21:40 C: NUL
Dec 04 11:21:40 Connection lost
Dec 04 11:21:40 Authorization failed
At that point my main Hub running A35 hung badly with mystic. Had to hard reboot it (power down and up) to get it working again. Then sent this from
my main A35 hub as AlphaTest (the .2 the fidopoll log above came from) errors as noted above and seemed to kill my Hub. It could be the constant hacker attacks that cause the Hub to die. Will update all my point test systems and test that.

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