1. Forum
  2. DeveloperNet
  3. *nix

  • Telnet Server Bug

    From Mark Smith@FATCATS to All on Sat Sep 28 17:01:21 2013
    I'm currently trying to implement a TCP/telnet server, and unfortunely Linux telnet clients can't do anything other than connect. I've traced it enough to figure out that the problem is Linux sends different EOL chars than Windows. What are they, particularly in Perl?

    Mark Smith

    ---
    ■ Synchronet ■ fatcats bbs - fatcatsbbs.com
  • From Mercyful Fate to Mark Smith on Thu Feb 6 15:01:38 2014
    Re: Telnet Server Bug
    By: Mark Smith to All on Sat Sep 28 2013 17:01:21

    I'm currently trying to implement a TCP/telnet server, and unfortunely Linux telnet clients can't do anything other than connect. I've traced it enough to figure out that the problem is Linux sends different EOL chars than Windows. What are they, particularly in Perl?

    This might be a little old so you've probably figured out the issue. usually linux and sush use \r as a new line character where as windows users \r\n together. In most cases you send \r\n and it will get handeled properly accross both platforms, just when you are parsing you want to check for \r\n first, then \r by itself afterwards if you doing linemode, It usualy easier though when parsing input to do char input so you can handle each character as it's received.

    Hope this helps.
  • From Mark Smith@BATTLEST/FREEWAY to All on Sat Sep 28 17:01:00 2013
    I'm currently trying to implement a TCP/telnet server, and unfortunely Linux telnet clients can't do anything other than connect. I've traced it enough to figure out that the problem is Linux sends different EOL chars than Windows. What are they, particularly in Perl?

    Mark Smith

    ---
    ■ Synchronet ■ fatcats bbs - fatcatsbbs.com
  • From Mercyful Fate@BATTLEST/FREEWAY to Mark Smith on Thu Feb 6 15:01:00 2014
    Re: Telnet Server Bug
    By: Mark Smith to All on Sat Sep 28 2013 17:01:21

    I'm currently trying to implement a TCP/telnet server, and unfortunely Linux telnet clients can't do anything other than connect. I've traced it enough to figure out that the problem is Linux sends different EOL chars than Windows. What are they, particularly in Perl?

    This might be a little old so you've probably figured out the issue. usually linux and sush use \r as a new line character where as windows users \r\n together. In most cases you send \r\n and it will get handeled properly accross both platforms, just when you are parsing you want to check for \r\n first, then \r by itself afterwards if you doing linemode, It usualy easier though when parsing input to do char input so you can handle each character as it's received.

    Hope this helps.

    ---
    ■ Synchronet ■ Digital Distortion: digitaldistortionbbs.com