Date: Fri, 29 Sep 1995 20:05:35 +1000 (EST) From: David Dawes <dawes@Physics.usyd.edu.au> To: kuku@gilberto.physik.rwth-aachen.de (Christoph P. Kukulies) Cc: freebsd-hackers@freefall.freebsd.org Subject: Re: WD8013 problem Message-ID: <199509291005.UAA15300@physics.su.oz.au> In-Reply-To: <199509290848.JAA17224@gilberto.physik.rwth-aachen.de> from "Christoph P. Kukulies" at Sep 29, 95 09:48:56 am
next in thread | previous in thread | raw e-mail | index | archive | help
>A while ago I reported a strangeness with connecting to one >of my machines. Strange is now that I can only observe >the effect with that one machine and gradually I'm beginning to >think it's hardware or a driver problem. Let me enumerate the >problems I have: > >1/ Connecting from my remote 1.1.5.1 site via slip gives the following > picture. > $ telnet gil > > Trying 137.226.31.2... > Connected to gilberto.physik.rwth-aachen.de. > Escape character is '^]'. > > FreeBSD (gil.physik.rwth-aachen.de) (ttyp2) > > (note the missing login: prompt - it only appears when I type <cr>) I've sometimes seen this symptom, and I've seen it happen when running 'telnet localhost' on a 2.0.5 machine. It doesn't always happen though. I just tried it, and the first two attempts worked OK, and the third showed the problem (I just typed ^D at the login prompts): rf900[116]> telnet localhost Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. FreeBSD (rf900) (ttypn) login: Connection closed by foreign host. rf900[117]> telnet localhost Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. FreeBSD (rf900) (ttypn) login: Connection closed by foreign host. rf900[118]> telnet localhost Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. FreeBSD (rf900) (ttypn) Connection closed by foreign host. >3/ Doing rlogin (also telnet I believe) sessions from gil to > neighboured hosts often results in getting a connection refused, > connection closed by foreign host the first time, rlogin the > second time then works. There was a time when I saw something like this, but with rsh. I may have been running the rsh from an SVR4 machine -- it was a while ago and I don't remember the details. I think this problem disappeared when I set tcp_extensions to NO in /etc/sysconfig. David
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199509291005.UAA15300>