Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Trying to get ssh to connect on my lan at home; I have no firewall on the linux-based server (Slackware 10.2), but the Win2K box on the LAN, as well as a connection through the loopback device both fail - the server disconnects. From Win2K, I'm using PuTTY alone; I generated the private key in rsa (SSH2) format and added the public one to ~/.ssh/authorized_keys but it won't connect (Same process done in linux from the command line using ssh-keygen; I was able to connect exactly one time; I forgot how I managed to do it)
BTW: I can connect to the sourceforge.net project shell servers from the Win2K box.
Here's the verbose output from my connection attempt from linux, where "paul" is the domain I'm connecting to:
Code:
bash-3.00$ ssh -v paul
OpenSSH_4.2p1, OpenSSL 0.9.7g 11 Apr 2005
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to paul [192.168.254.5] port 22.
debug1: Connection established.
debug1: identity file /home/lilmax88/.ssh/identity type -1
debug1: identity file /home/lilmax88/.ssh/id_rsa type 1
debug1: identity file /home/lilmax88/.ssh/id_dsa type -1
debug1: ssh_exchange_identification: sshd re-exec requires execution with an absolute path
ssh_exchange_identification: Connection closed by remote host
Thanks a bunch, do I just need to read a tutorial?
no; haven't messed with them. here they are. /etc/HOSTNAME:
Code:
paul.paul.net
/etc/hosts:
Code:
#
# hosts This file describes a number of hostname-to-address
# mappings for the TCP/IP subsystem. It is mostly
# used at boot time, when no name servers are running.
# On small systems, this file can be used instead of a
# "named" name server. Just add the names, addresses
# and any aliases to this file...
#
# By the way, Arnt Gulbrandsen <agulbra@nvg.unit.no> says that 127.0.0.1
# should NEVER be named with the name of the machine. It causes problems
# for some (stupid) programs, irc and reputedly talk. :^)
#
# For loopbacking.
127.0.0.1 localhost
192.168.254.5 paul.paul.net paul
# End of hosts.
/etc/hosts.allow:
Code:
#
# hosts.allow This file describes the names of the hosts which are
# allowed to use the local INET services, as decided by
# the '/usr/sbin/tcpd' server.
#
# Version: @(#)/etc/hosts.allow 1.00 05/28/93
#
# Author: Fred N. van Kempen, <waltje@uwalt.nl.mugnet.org
#
#
ftpd: all
comsat: all
sendmail: all
mail: all
imap: all
# End of hosts.allow.
/etc/hosts.deny:
Code:
#
# hosts.deny This file describes the names of the hosts which are
# *not* allowed to use the local INET services, as decided
# by the '/usr/sbin/tcpd' server.
#
# Version: @(#)/etc/hosts.deny 1.00 05/28/93
#
# Author: Fred N. van Kempen, <waltje@uwalt.nl.mugnet.org
#
#
ALL:ALL
# End of hosts.deny.
/etc/hosts.equiv:
Code:
#
# hosts.equiv This file describes the names of the hosts which are
# to be considered "equivalent", i.e. which are to be
# trusted enought for allowing rsh(1) commands.
#
# Version: @(#)/etc/hosts.equiv 2.00 04/30/93
#
# Author: Fred N. van Kempen, <waltje@uwalt.nl.mugnet.org>
#
#
localhost
# End of hosts.equiv.
I don't know - I got rid of one of the error lines, the one about an absolute path. the last two arguments for ssh in /etc/inetd.conf needed to be "/usr/sbin/sshd /usr/sbin/sshd" However, I still get the error from ssh_exchange_identification. I verified that the permissions on the folder .ssh are 700 and that the contents are all 600. What else am I missing? hosts.deny has all:all and hosts.allow includes ssh:all and sshd:all I think I remember adding entries for smtp and sendmail, and I know those work, so my syntax is ok. (curious that there's no entry for proftpd, but there is for ftpd and FTP works under the proftpd according to inetd) I've followed all the tutorials so far... what have I missed?
side note: how do you like your rig? is the Athlon64 working out with FC4? thinking about adding FC to my boot configuration. (instead of the old mandrake that I have on there right now.)
I don't know - I got rid of one of the error lines, the one about an absolute path. the last two arguments for ssh in /etc/inetd.conf needed to be "/usr/sbin/sshd /usr/sbin/sshd" However, I still get the error from ssh_exchange_identification. I verified that the permissions on the folder .ssh are 700 and that the contents are all 600. What else am I missing? hosts.deny has all:all and hosts.allow includes ssh:all and sshd:all I think I remember adding entries for smtp and sendmail, and I know those work, so my syntax is ok. (curious that there's no entry for proftpd, but there is for ftpd and FTP works under the proftpd according to inetd) I've followed all the tutorials so far... what have I missed?
I'm not familiar with Mandrake, but ordinarily I thought sshd runs standalone -- not in inetd. Maybe Mandrake is different. Have you tried running it standalone? Disable it in inetd and just fire it up from the command line. /usr/[s]bin/sshd and see if the indications change.
side note: how do you like your rig? is the Athlon64 working out with FC4? thinking about adding FC to my boot configuration. (instead of the old mandrake that I have on there right now.)
I like it a lot. I have to run a 32-bit web browser because there's no 64-bit Sun Java plugin yet, nor is there a 64-bit Macromedia Flash plugin yet (and I like to have both available in my browser), but everything else is great. It runs 32- or 64-bit apps just fine.
I have tried to just run sshd, but it doesn't show up on "ps -x" or on "netstat -nlp" like various tutorials have recommended. I know that it is run on boot, because I threw a comment into the rc.sshd file that is run by rc.inet2 immediately before the command is given and so it must be executed. Here are some key files from ssh and a more detailed verbose output. I tried a dsa key this time.
You might also look in /var/log/secure to see if any illuminating messages can be found. (I presume that's the log file for ssh in Mandriva. It is in Fedora.)
new version didn't help at all - exact same errors. the sourceforge server that works fine is using an earlier version like 4.1, I think. This isn't supposed to be that hard.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.