From: Thomas Osterried (znm@thyssenkrupp.com)
Date: Sun Oct 07 2001 - 04:54:50 EEST
> The problem arises when someone telnets in from a Windows machine (and
> some still try that!). The line terminators between Linux and Windows
> are not the same! (Windows telnet is expecting a CR/LF instead of
> just a LF).
as far as i understand rfc1123 (and considering how standard
implementations like smtp, nntp, .. follow it):
| The Telnet end-of-line sequence CR LF MUST be used to send
| Telnet data that is not terminal-to-computer (e.g., for Server
| Telnet sending output, or the Telnet protocol incorporated
| another application protocol).
|
| DISCUSSION:
| To allow interoperability between arbitrary Telnet clients
| and servers, the Telnet protocol defined a standard
| representation for a line terminator. Since the ASCII
| character set includes no explicit end-of-line character,
| systems have chosen various representations, e.g., CR, LF,
| and the sequence CR LF. The Telnet protocol chose the CR
| LF sequence as the standard for network transmission.
thus, every application you'll connect as user, MUST send <CR/LF> on the
application layer. rfc854 proposed, and rfc1123 concreted it.
so win$ may behave correct, if it refuses to handle "foo<LF>" data
as you may expect.
> Any suggestions on the best way to solve this? I have read the man
> pages on ax25spyd, and no mention is made of this problem. I suppose,
> one answer would be to run another daemon that listened to the 14091
> port and provided reformatted output on another port. Any other
> ideas?
if ax25sypd does not send <CR><LF> on a TCP connection for a user
application, this should be fixed first.
73,
- thomas, dl9sau
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to ava.pzmygjrj@lawson.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
This archive was generated by hypermail 2b30 : Sun Oct 07 2001 - 05:04:04 EEST