On 01/30/2013 10:00 AM, jdow wrote:
On 2013/01/29 17:49, Ed Greshko wrote:
On 01/30/2013 09:37 AM, jdow wrote:
On 2013/01/29 06:23, Ed Greshko wrote:
On 01/29/2013 10:19 PM, Matthew Miller wrote:
On Tue, Jan 29, 2013 at 11:46:58AM +0800, Ed Greshko wrote:
First.... No need to bring up the ssh v.s. telnet stuff..... Has anyone configured telnetd for use on F18? Running 64 bit....but this shouldn't make a difference. Anyway, I did the normal procedure.....
I just did, and I didn't add -D, but I did change "disabled = yes" to "no" in the telnet xinetd config. And it just worked.
Thanks for testing.
That is what I did too.... And it fails as described. I'm stumped.
SELinux getting in the way in one of the two cases?
No, I eliminated that early on.... Another manifestation of the problem is "garbled" output....
Connected to f18x. Escape character is '^]'. Fedora release 18 (Spherical Cow) Kernel 3.7.4-204.fc18.x86_64 on an x86_64 (3) 18x login: assword: ast login: Wed Jan 30 08:27:30 on :0 ]0;egreshko@f18x:~[?1034hegreshko@f18x ~]$ [0mDesktop Documents Downloads Music Pictures Public Templates Videos
Erm, you said it's a very old machine. I get the impression it is using telnet to get to the Linux machine. What you're seeing looks for all the world like what people used to see on RS232 terminals when flow control was disabled. Is flow control disabled somewhere in your network path between the machines? If it is a very slow machine may get hit with data faster than it can parse it.
The justification for needing a working telnet server is that the client side is old.
The problem was discovered and occurs on F18 itself with "telnet localhost".