From: Adam E. <a9...@ya...> - 2005-08-01 14:51:06
|
I am trying to boot the Gamecube to Linux 2.6.8 release found on the web (and I am fairly new to running linux on the cube). I am able to get up to the login prompt on the cube and according to the kernal messages on the screen, it appears as if SSH is started. However when I try: ssh -v -v -v root@192.168.0.254 I get the following: [root@birdo log]# ssh -v root@192.168.0.254 OpenSSH_3.6.1p2, SSH protocols 1.5/2.0, OpenSSL 0x0090701f debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Rhosts Authentication disabled, originating port will not be trusted. debug1: Connecting to 192.168.0.254 [192.168.0.254] port 22. debug1: Connection established. debug1: identity file /root/.ssh/identity type -1 debug1: identity file /root/.ssh/id_rsa type -1 debug1: identity file /root/.ssh/id_dsa type -1 ssh_exchange_identification: Connection closed by remote host debug1: Calling cleanup 0x8062c30(0x0) The /var/log/auth.log on the cube has the following message in it: Jul 29 10:13:13 cube sshd[152]: error: Bind to port 22 on 192.168.0.4 failed: Cannot assign requested address. Jul 29 10:13:13 cube sshd[152]: fatal: Cannot bind any address. I have the Listenaddress in sshd_config set to 192.168.0.4 (Linux box serving the file system), but I have also tried 192.168.0.254 (cube address). With Listenaddress set to the latter, the message in auth.log on the cube says that the address is already in use. During these ssh failures I do see some new messages in the /var/log/wcstatus.log of the Linux box serving the file system: 3063229360 : device : (Fri 29 Jul 2005 10:13:35 AM CDT) : adapterStateHasChanged: eth1 has changed link state from "active" to "inactive" 3063229360 : device : (Fri 29 Jul 2005 10:13:37 AM CDT) : adapterStateHasChanged: eth1 adapter has just become active 3063229360 : device : (Fri 29 Jul 2005 10:13:37 AM CDT) : wg_dhcp_renew_function: The adapter does not have corresponding /var/run/dhclient-eth1.pid file In /etc/init.d/ssh on the cube, these are the lines to start the ssh daemon: echo -n "Starting OpenBSD Secure Shell server: sshd" start-stop-daemon --start --quiet --pidfile /var/run/sshd.pid --exec /usr/sbin/sshd echo "." Is there anything I am missing in the setup that would cause ssh to fail in this way? Thanks --------------------------------- Start your day with Yahoo! - make it your home page --------------------------------- Start your day with Yahoo! - make it your home page |