home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!think.com!yale.edu!yale!mintaka.lcs.mit.edu!wyvern
- From: wyvern@gnu.ai.mit.edu (The Wyvern)
- Subject: More problems with telnetd/ftpd
- Message-ID: <1992Dec30.040050.14120@mintaka.lcs.mit.edu>
- Keywords: tcpip, telnet, ftp
- Sender: news@mintaka.lcs.mit.edu
- Organization: Free Software Foundation
- Date: Wed, 30 Dec 1992 04:00:50 GMT
- Lines: 48
-
- Well, I was optimistic after I downloaded the new net-src package
- from sunsite, since telnetd would allow me to log into my own
- machine via loopback again. But I've recently been having some
- serious problems with it, along with ftpd.
-
- When I'm using term (v0.9.9) with the tredir utility to redirect
- ports to my own system (i.e. tredir 6111 23 so people can log
- in via telnet) it'll work once, and then all subsequent attempts to
- telnet to that port will result in a connection that just hangs, with
- no login prompt, or anything. Interestingly enough, I can still
- telnet from my own machine to my own machine, but not for long -
- after a few more times, it fails even to do that, just locking up.
- I suspect this may have something to do with /bin/login, as I'm
- using the login from the shadow-password package, and it never did
- work well with telnetd (why?). Needless to say this problem
- pretty much trashes any hopes of using telnet(d) with term over
- the internet.
- It also may be worth noting that when someone connects and telnetd
- is executed, it is suspended in the state of tcp_read as shown
- in the WCHAN field of ps -l (similar to a previous problem I was
- having with another client/server system which now seems to be fixed
- with 0.99.1). It will stay suspended in this state until forcibly
- terminated by root with kill.
-
- Ftpd has a similar problem with working once (sometimes not at all)
- and then locking up on all subsequent attempts to connect.
- Part of this is probably due to my using shadow passwords which ftpd
- doesn't seem to support.
-
- Also, I've noticed some quirks with the tcp code that result in my
- having to reboot to get seemingly old dead nonvisible sockets cleared
- away. This seems to be related to the telnetd problem as well -
- if I reboot the system, telnetd will work again until I try to use it
- with term, or too many times, or whatever. It would be nice if the tcp
- code cleaned up after itself a bit more, I think (though this may not
- be the problem, I don't know).
-
- If anyone has an idea of what's wrong, I'd be grateful for some answers.
- It'd be nice to have a telnetd that never breaks. :)
-
- My system configuration:
- 486, Phoenix BIOS
- 200mb IDE drive
- No ethernet board
- X8514 with TCP/IP
- Linux Kernel version 0.99.1
-
-
-