• Re: Kannons and Katapults

    From Mike Powell@1:2320/105 to STEPHEN HURD on Sunday, December 07, 2025 11:13:35
    It's possible that the telnet support doesn't do anything with NVT CRs, I didn't dig in too deeply into the source, just noticed that it does do at leas
    some option negotiation and will track the current state.

    N/p, thanks for the tip nonetheless!

    So likely you only need to do this if you need to accept or send character 255
    (which is a special telnet character) such as for uploads and downloads.

    That is *very* interesting. Since moving away from Vmodem / OS/2, putting
    the DOS BBS behind any "proper" telnet server (like mystic's matrix menu) *breaks* file transfers, so apparently those don't necessarily do the right thing, either. ;)

    I have it set up to be accessible via two ports. The primary allows folks
    who have a terminal program capable of RAW mode to call in without the double-CR while also being able to do things like download a QWK packet.
    The other port is behind a telnet server/listener that allows folks whose terminal program doesn't do RAW mode to call in and do just about
    everything but transfer files.

    Mike

    * SLMR 2.1a * LSD: Virtual Reality without all the fancy hardware
    --- SBBSecho 3.28-Linux
    * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)
  • From Stephen Hurd@1:103/1 to Mike Powell on Sunday, December 07, 2025 19:52:01
    Re: Re: Kannons and Katapults
    By: Mike Powell to STEPHEN HURD on Sun Dec 07 2025 11:13 am

    I have it set up to be accessible via two ports. The primary allows folks who have a terminal program capable of RAW mode to call in without the double-CR while also being able to do things like download a QWK packet.

    To be clear, it's a CR LF, not a double-CR... but a lot of old software will interpret an LF as a CR, so it acts like a double-CR.

    The other port is behind a telnet server/listener that allows folks whose terminal program doesn't do RAW mode to call in and do just about
    everything but transfer files.

    That is odd... a pcap would be elightening. Basically, for telnet, any IAC (character 255) needs to be converted to two IACs (ie: convert 0xFF to 0xFF 0xFF). Not doing that in one direction or the other is what the normal problem with file transfers over telnet ends up coming down to.
    --- SBBSecho 3.32-FreeBSD
    * Origin: BBSDev.net - The BBS Developers Network (1:103/1)