Ftp/mail-yes. Telnet-no. Direct login-no. ????
My firewall/internal mail server/gateway machine choked on something
yesterday and went down for quite a while. I couldn't login at the
console--no response after hitting the return with the name (no printing of
request for password). But C-A-D works from there.
I can't telnet in. A connection is made, but it hangs without a login
request line.
I found I could ftp into the box.
Couldn't get through it to the outside, though. No ping, http, ftp.
I was able to boot single user into the system. Having seen several
messages about a missing int_LOG module, I surmised that part of the problem
came from iptables/ipmasq, which was surprising as I have been using it for
some time now with a 2.4.20 kernel. After much fooling around including
reinstalling a variety of packages, I removed ipmasq and replaced it with a
simpler script based on the ibm.com/developerWorks tutorial (happened to
have that one printed out). Rebuilt the kernel with its suggested kernel
options and even included an option about logging iptables.. ;-)
The system nows acts as it should for the LAN as a gateway, but still
doesn't allow a console or telnet login.
Can anyone suggest a direction for me to search in? Is this an init/getty
issue? It's the stable branch, FWIW, that went through a rough upgrade from
the last stable issue about 1-2 months ago (I'm actually pleased that the
486 works OK with the 2.4.20 kernel...).
Thanks,
Kenward
--
In a completely rational society, the best of us would aspire to be
_teachers_ and the rest of us would have to settle for something less,
because passing civilization along from one generation to the next
ought to be the highest honor and the highest responsibility anyone
could have. - Lee Iacocca
Reply to: