Further leaving that system and returning to my BBS, my BBS session is messed up, so I have to log off and login again. My point was - when I login originally to my BBS via SSH, telgate's connection to an upstream system is messed up. I'm not intending to use telgate as an SSH session to an upstream system.
You could log onto another board and change your default Mo> you ssh into a bbs and use the telgate door it will no longer be an ssh anyway, telgate is just that, a telnet_gateway so if Terminal mode to ANSI instead out auto-detect You ssh into a bbs and use the telgate door it will no longer be an ssh Personally I disabled telgate on my system to avoid 'spoofed' ip address > If I initially use telnet (instead of SSH) - I can hop to other BBSes > I also telgated into another BBS (Ezycom) - and on connection it did > a different terminal and everything is messed up. After logging in it has obviously guessed > * I choose a menu option to telgate to another SBBS - on connect some > Anyway, it guessed the wrong terminal and after logging on, screen > on connection (which I'm guessing you are probing for a terminal
> I telgate out to another SBBS environment - and I noticed some strange > I setup SSH into my BBS, which works well. * Vertrauen - Riverside County, California - telnet:// Ş Synchronet ş Alterant | an SBBS in Docker on Pi! I gave my wife a hint: I bought a love seat. (My menu option is just "?telgate " if that helps) If I initially use telnet (instead of SSH) - I can hop to other BBSes with telgate just fine. I also telgated into another BBS (Ezycom) - and on connection it did not detect ANSI. (EG: "D" for default is rendered as a "B".) After logging in it has obviously guessed that I'm a different terminal and everything is messed up. * I choose a menu option to telgate to another SBBS - on connect some strange chars are shown. However, I have a menu item where I telgate out to another SBBS environment - and I noticed some strange chars on connection (which I'm guessing you are probing for a terminal type).Īnyway, it guessed the wrong terminal and after logging on, screen rendering was screwed up. Only recommended if you cannot use SyncTERM or Netrunner.I setup SSH into my BBS, which works well.
Recommended only if you are unable to use SyncTERM.Ī Windows telnet client no longer in development, with fairly good ANSI graphics compatibility. Guaranteed 100% compatible and recommended above all other clients.Īnother free, multi-platform client with fairly good ANSI graphics compatibility.
Problems? Try just the IP address: 192.71.245.43Ī free, compact, simple, multi-platform client with Telnet, RLogon and SSH capabilities written by the authors of Synchronet, the BBS server software that we use. SyncTERM is by far the best client, but if you are unable to use it for some reason, try some of the alternatives below.Ĭonnect to the BBS using address: We suggest you access the BBS using one of the clients below. Any terminal emulator capable of these protocols will work, but may not offer the correct ANSI graphics. You can connect to Toxic Laboratory BBS using Telnet, RLogin or SSH.
A selection of telnet clients for you to download Find out about our system and the BBS's history