Hello list I have a new laptop and I would connect it to my main machine to exchange files.But I cannot configure a valid route and only get this : /sbin/route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface localhost * 255.255.255.255 UH 0 0 0 lo loopback * 255.0.0.0 U 0 0 0 lo # ifup route ifup [DEBUG] route ifup [DEBUG] HWDESC = route CONFIG = INTERFACE = route ifup route ifup ERROR: No configuration found for route It must not be a hardware problem as the two machines can ping each other through their hostnames or IPv4 addresses. I made /etc/sysconfig/network/routes files which does not seem to be accepted this is the one of my main machine with its own address then that of the laptop 127.0.0.1 0.0.0.0 255.255.255.255 lo 192.168.0.1 0.0.0.0 255.255.255.0 eth-id-00:04:75:7f:38:25 192.168.0.3 0.0.0.0 255.255.255.0 eth-id-00:c0:9f:43:bd:d3 I have a similar one on my laptop I am not at all a network expert i just installed one long ago with SuSE 7.1, but things seem to have much changed I must be missing something obvious Could you help me ? -- ________________ Paul Ollion Proud Linux user - SuSE - 9.1
On Wednesday 20 October 2004 04:30 am, Paul Ollion wrote:
Hello list I have a new laptop and I would connect it to my main machine to exchange files.But I cannot configure a valid route and only get this :
/sbin/route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface localhost * 255.255.255.255 UH 0 0 0 lo loopback * 255.0.0.0 U 0 0 0 lo
For what you are trying to do your routing table will suffice. If both machines are on the same subnet, routing is not needed.
# ifup route ifup [DEBUG] route ifup [DEBUG] HWDESC = route CONFIG = INTERFACE = route ifup route ifup ERROR: No configuration found for route
This makes no sense as you do not have an interface "route".
It must not be a hardware problem as the two machines can ping each other through their hostnames or IPv4 addresses.
True
I made /etc/sysconfig/network/routes files which does not seem to be accepted this is the one of my main machine with its own address then that of the laptop 127.0.0.1 0.0.0.0 255.255.255.255 lo 192.168.0.1 0.0.0.0 255.255.255.0 eth-id-00:04:75:7f:38:25 192.168.0.3 0.0.0.0 255.255.255.0 eth-id-00:c0:9f:43:bd:d3
Two default gateways! NO!
I have a similar one on my laptop I am not at all a network expert i just installed one long ago with SuSE 7.1, but things seem to have much changed I must be missing something obvious Could you help me ?
You do not make (or edit) the routes file, the program /sbin/route does (in a round about way). Read man route for configuring your routing table manually or let yast do it as part of your network card setup. How are you trying to share files? nfs? scp? samba? fish? The output of ifconfig and route from both machines could be helpful also. -- Jim Barnes -- Certainly the game is rigged. Don't let that stop you; if you don't bet, you can't win. -Lazarus Long -- Linux 2.6.5-7.108-default
The Wednesday 2004-10-20 at 09:07 -0600, jim barnes wrote:
You do not make (or edit) the routes file, the program /sbin/route does (in a round about way). Read man route for configuring your routing table manually or let yast do it as part of your network card setup.
Actually, yast does edit it. -- Cheers, Carlos Robinson
On Wednesday 20 October 2004 01:51 pm, Carlos E. R. wrote:
The Wednesday 2004-10-20 at 09:07 -0600, jim barnes wrote:
You do not make (or edit) the routes file, the program /sbin/route does (in a round about way). Read man route for configuring your routing table manually or let yast do it as part of your network card setup.
Actually, yast does edit it.
How right you are. I stand corrected. Renamed /sbin/route to /sbin/route.old and then changed a route via yast. Yup, it worked as expected. I had assumed yast just called /sbin/route to work it's magic. And now back to our task at hand... Jim Barnes -- Certainly the game is rigged. Don't let that stop you; if you don't bet, you can't win. -Lazarus Long -- Linux 2.6.5-7.108-default
On Wednesday 20 October 2004 17:07, jim barnes wrote:
For what you are trying to do your routing table will suffice. If both machines are on the same subnet, routing is not needed.
# ifup route
This makes no sense as you do not have an interface "route".
You do not make (or edit) the routes file, the program /sbin/route does (in a round about way). Read man route for configuring your routing table manually or let yast do it as part of your network card setup.
Thank you Jim it looks simpler than I thought . I deactivated and simplified a lot of things I had configured and which appear unnecessary. and a lot of error messages have disappeared.
How are you trying to share files? nfs? scp? samba? fish?
You will laugh, in fact I tried to configure nearly them all, one after the other, following the manual page after page, and thinking they were all necessary. But I would appreciate if you advised me for the simplest solution. I suppose I must configure a DNS server anyway, and what else ?
The output of ifconfig and route from both machines could be helpful also.
Here is the output of Ifconfig on my main machine # ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:04:75:7F:38:25 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:10 Base address:0xec00 On my laptop I have a similar one I suppose it is correct. There is also a problem with portmap on my main machine : at boot I have messages : "Starting RPC portmap daemonportmap : fork : Success failed "no portmapper running" and when trying to mount a directory from one machine to the other with the mount command, I get the message : "RPC remote system error - no route to host" I will be grateful if you can stil help me. -- ________________ Paul Ollion Proud Linux user - SuSE - 9.1
On Wednesday 20 October 2004 04:53 pm, Paul Ollion wrote:
I will be grateful if you can stil help me.
Sure, let's start from the beginning. Post the output of ifconfig (not ifconfig ethx) from both machines. Is your main machine connected to the internet? -- Jim Barnes -- Certainly the game is rigged. Don't let that stop you; if you don't bet, you can't win. -Lazarus Long -- Linux 2.6.5-7.108-default
Sure, let's start from the beginning. Post the output of ifconfig (not ifconfig ethx) from both machines. Here it is :
On Thursday 21 October 2004 02:36, jim barnes wrote: main machine # ifconfig eth0 Link encap:Ethernet HWaddr 00:04:75:7F:38:25 inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::204:75ff:fe7f:3825/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:23 errors:0 dropped:0 overruns:0 frame:0 TX packets:74 errors:0 dropped:0 overruns:0 carrier:74 collisions:0 txqueuelen:1000 RX bytes:1538 (1.5 Kb) TX bytes:4710 (4.5 Kb) Interrupt:10 Base address:0xec00 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:145 errors:0 dropped:0 overruns:0 frame:0 TX packets:145 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:10257 (10.0 Kb) TX bytes:10257 (10.0 Kb) laptop # ifconfig eth0 Link encap:Ethernet HWaddr 00:c0:9f:43:bd:d3 inetd addr:192.168.0.3 Bcast: 192.168.0.255 Mask:255.255.255.0 adr inet6:fe80::2c0:9fff:fe43:bdd3/64 Scope:lien UP BROADCAST MULTICAST MTU:1500 METRIC:1 RX packets:5 errors:0 dropped:0 overruns:0 frame:0 TX packets:25 errors:0 dropped:0 overruns:0 carrier:3 collisions:0 lg file transmission:1000 RX bytes:490 (490.0 b) TX bytes:1758 (1.7 Kb) interruption:3 lo Link encap:local loopback inet addr:127.0.0.1 Mask 255.0.0.0 adr inet6: ::1/128 Scope:Hôte UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:52 errors:0 dropped:0 overruns:0 frame:0 TX packets:52 erors:0 dropped:0 overruns:0 carier:0 collisions:0 lg file transmission:0 RX bytes:2754 (2.6 Kb) TX bytes:2754 (2.6 Kb
Is your main machine connected to the internet? both machines have a modem and can connect, but no permanent connection.
Thanks again for your help. -- ________________ Paul Ollion Proud Linux user - SuSE - 9.1
On Thursday 21 October 2004 04:23 am, Paul Ollion wrote:
both machines have a modem and can connect, but no permanent connection.
Output of ifconfig is ok. Are you connecting the two together directly with a patch cord or might there be a switch also? If connected directly, the patch cord must be a crossover type. Pins 1-3 and 2-6 are swapped instead of being wired straight through. It's analogous to a null modem cable. A switch does this automatically. The TX (transmit) of one must be connected to the RX (receive) of the other. -- Jim Barnes -- Certainly the game is rigged. Don't let that stop you; if you don't bet, you can't win. -Lazarus Long -- Linux 2.6.5-7.108-default
On Thursday 21 October 2004 13:32, jim barnes wrote:
Output of ifconfig is ok.
Are you connecting the two together directly with a patch cord or might there be a switch also? If connected directly, the patch cord must be a crossover type. Pins 1-3 and 2-6 are swapped instead of being wired straight through. It's analogous to a null modem cable. A switch does this automatically. The two machines are connected directly with a crossover cable. it worked with another machine and SuSE 7.3 --
Paul Ollion Proud Linux user - SuSE - 9.1
What do you get with an attempted ssh login from the laptop to the main machine? $ssh -v 192.168.0.1 -- Jim Barnes -- Certainly the game is rigged. Don't let that stop you; if you don't bet, you can't win. -Lazarus Long -- Linux 2.6.5-7.108-default
On Thursday 21 October 2004 17:51, jim barnes wrote:
What do you get with an attempted ssh login from the laptop to the main machine? $ssh -v 192.168.0.1 Thanks Jim Here is the output : OpenSSH_308p1, SSH protocols 1.5/2.0, OpenSSL 0.9.7d 17 Mar 2004 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to 192.168.0.1 [192.168.0.1] port 22 debug1: connect to address 192.168.0.1 port 22: Connection refused ssh: connect to host 192.168.0.1 port 22: Connection refused
What do you think of it ? -- ________________ Paul Ollion Proud Linux user - SuSE - 9.1
On Thursday 21 October 2004 12:44, Paul Ollion wrote:
ssh: connect to host 192.168.0.1 port 22: Connection refused
What do you think of it ?
Is sshd running on 192.168.0.1? sudo /etc/ini t.d/sshd start also, make sure that /etc/init.d/rc5.d/S12sshd exists good luck, brian -- Brian Jackson Photo Sports ~ Editorial ~ People ~ Travel ~ Events http://www.BrianJacksonPhoto.com 650-218-5082
On Thursday 21 October 2004 01:44 pm, Paul Ollion wrote:
On Thursday 21 October 2004 17:51, jim barnes wrote:
What do you get with an attempted ssh login from the laptop to the main machine? $ssh -v 192.168.0.1
Thanks Jim Here is the output : OpenSSH_308p1, SSH protocols 1.5/2.0, OpenSSL 0.9.7d 17 Mar 2004 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to 192.168.0.1 [192.168.0.1] port 22 debug1: connect to address 192.168.0.1 port 22: Connection refused ssh: connect to host 192.168.0.1 port 22: Connection refused
What do you think of it ?
Do you have a firewall active? If so, turn it off and retry. If it then works, you'll know that you have to allow connections to the ports you need for access you desire. -- Jim Barnes -- Certainly the game is rigged. Don't let that stop you; if you don't bet, you can't win. -Lazarus Long -- Linux 2.6.5-7.108-default
On Thursday 21 October 2004 20:11, jim barnes wrote:
On Thursday 21 October 2004 01:44 pm, Paul Ollion wrote:
On Thursday 21 October 2004 17:51, jim barnes wrote:
What do you get with an attempted ssh login from the laptop to the main machine? $ssh -v 192.168.0.1
Thanks Jim Here is the output : OpenSSH_308p1, SSH protocols 1.5/2.0, OpenSSL 0.9.7d 17 Mar 2004 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to 192.168.0.1 [192.168.0.1] port 22 debug1: connect to address 192.168.0.1 port 22: Connection refused ssh: connect to host 192.168.0.1 port 22: Connection refused
What do you think of it ?
Do you have a firewall active? If so, turn it off and retry. If it then works, you'll know that you have to allow connections to the ports you need for access you desire.
Well, no ! there is no firewall active. but I still have the RPC portmap error at boot on my main machine. Is not it worrying ? Though It is perhaps not the first thing to be checked. Anyway I think you are very methodical, I trust you and already learnt a lot thanks to you. -- ________________ Paul Ollion Proud Linux user - SuSE - 9.1
On Thursday 21 October 2004 03:56 pm, Paul Ollion wrote:
Well, no ! there is no firewall active. but I still have the RPC portmap error at boot on my main machine. Is not it worrying ? Though It is perhaps not the first thing to be checked. Anyway I think you are very methodical, I trust you and already learnt a lot thanks to you.
ssh works without portmap running, nfs will not. One thing at a time. As Brian inquired, is sshd running? Check by issuing this command: ps aux | grep sshd The result from mine: jbarnes@shuttle:~> ps aux | grep sshd root 3618 0.0 0.1 4708 1804 ? Ss Oct19 0:00 /usr/sbin/sshd -o PidFile=/var/run/sshd.init.pid jbarnes 32049 0.0 0.0 2600 704 pts/0 R+ 18:44 0:00 grep sshd Or this command: /etc/init.d/sshd status If it is not running, then: /etc/init.d/sshd start -- Jim Barnes -- Certainly the game is rigged. Don't let that stop you; if you don't bet, you can't win. -Lazarus Long -- Linux 2.6.5-7.108-default
On Friday 22 October 2004 02:58, jim barnes wrote:
On Thursday 21 October 2004 03:56 pm, Paul Ollion wrote:
Well, no ! there is no firewall active. but I still have the RPC portmap error at boot on my main machine. Is not it worrying ? Though It is perhaps not the first thing to be checked. Anyway I think you are very methodical, I trust you and already learnt a lot thanks to you.
ssh works without portmap running, nfs will not. One thing at a time. As Brian inquired, is sshd running? Check by issuing this command:
ps aux | grep sshd
The result from mine:
jbarnes@shuttle:~> ps aux | grep sshd root 3618 0.0 0.1 4708 1804 ? Ss Oct19 0:00 /usr/sbin/sshd -o PidFile=/var/run/sshd.init.pid jbarnes 32049 0.0 0.0 2600 704 pts/0 R+ 18:44 0:00 grep sshd
Here is mine : atelier:/home/paulus # /etc/init.d/sshd status Checking for service sshd unused
Or this command: /etc/init.d/sshd status If it is not running, then: /etc/init.d/sshd start And here is what I get there : atelier:/home/paulus # /etc/init.d/sshd start Starting SSH daemon done
but sshd status still gives unused after Starting SSH daemon -- ________________ Paul Ollion Proud Linux user - SuSE - 9.1
On Friday 22 October 2004 06:02 am, Paul Ollion wrote:
Here is mine : atelier:/home/paulus # /etc/init.d/sshd status Checking for service sshd unused
Or this command: /etc/init.d/sshd status
If it is not running, then: /etc/init.d/sshd start
And here is what I get there : atelier:/home/paulus # /etc/init.d/sshd start Starting SSH daemon done
but sshd status still gives unused after Starting SSH daemon
Try ps aux | grep sshd to see if it has been issued a pid, -- Jim Barnes -- Certainly the game is rigged. Don't let that stop you; if you don't bet, you can't win. -Lazarus Long -- Linux 2.6.5-7.108-default
On Friday 22 October 2004 12:11, jim barnes wrote:
On Friday 22 October 2004 06:02 am, Paul Ollion wrote:
Here is mine : atelier:/home/paulus # /etc/init.d/sshd status Checking for service sshd unused
Or this command: /etc/init.d/sshd status
If it is not running, then: /etc/init.d/sshd start
And here is what I get there : atelier:/home/paulus # /etc/init.d/sshd start Starting SSH daemon done
but sshd status still gives unused after Starting SSH daemon
Try ps aux | grep sshd to see if it has been issued a pid,
No I just get this : atelier:/home/paulus # ps aux | grep sshd root 6796 0.0 0.5 2596 688 pts/39 D+ 15:23 0:00 grep sshd -- ________________ Paul Ollion Proud Linux user - SuSE - 9.1
On Friday 22 October 2004 07:26 am, Paul Ollion wrote:
Try ps aux | grep sshd to see if it has been issued a pid,
No I just get this :
atelier:/home/paulus # ps aux | grep sshd root 6796 0.0 0.5 2596 688 pts/39 D+ 15:23 0:00 grep sshd
Time to debug sshd. # /usr/sbin/sshd -d -or- Uninstall & reinstall. Package openssh -- Jim Barnes -- Certainly the game is rigged. Don't let that stop you; if you don't bet, you can't win. -Lazarus Long -- Linux 2.6.5-7.108-default
An afterthought, If you run sshd -d, ctrl c to stop it and get your prompt back! -- Jim Barnes -- Certainly the game is rigged. Don't let that stop you; if you don't bet, you can't win. -Lazarus Long -- Linux 2.6.5-7.108-default
On Friday 22 October 2004 13:51, jim barnes wrote:
On Friday 22 October 2004 07:26 am, Paul Ollion wrote:
Try ps aux | grep sshd to see if it has been issued a pid,
No I just get this :
atelier:/home/paulus # ps aux | grep sshd root 6796 0.0 0.5 2596 688 pts/39 D+ 15:23 0:00 grep sshd
Time to debug sshd. # /usr/sbin/sshd -d
Here is the output : # /usr/sbin/sshd -d debug1: sshd version OpenSSH_3.8p1 debug1: private host key: #0 type 0 RSA1 debug1: read PEM private key done: type RSA debug1: private host key: #1 type 1 RSA debug1: read PEM private key done: type DSA debug1: private host key: #2 type 2 DSA debug1: Bind to port 22 on ::. Server listening on :: port 22. Generating 768 bit RSA key. RSA key generation complete. It is identical on both machines.
-or- Uninstall & reinstall. Package openssh
I did it, but same results To answer your last message, yes, I am using SuSE 9.1 pro Thanks again. -- ________________ Paul Ollion Proud Linux user - SuSE - 9.1
On Friday 22 October 2004 12:55 pm, Paul Ollion wrote:
Here is the output : # /usr/sbin/sshd -d debug1: sshd version OpenSSH_3.8p1 debug1: private host key: #0 type 0 RSA1 debug1: read PEM private key done: type RSA debug1: private host key: #1 type 1 RSA debug1: read PEM private key done: type DSA debug1: private host key: #2 type 2 DSA debug1: Bind to port 22 on ::. Server listening on :: port 22. Generating 768 bit RSA key. RSA key generation complete.
It is identical on both machines.
Ok, sure looks like it starts normally, lets see if anything is changed from default in sshd_config grep -v ^# /etc/ssh/sshd_config Can you still ping between machines? -- Jim Barnes -- Certainly the game is rigged. Don't let that stop you; if you don't bet, you can't win. -Lazarus Long -- Linux 2.6.5-7.108-default
On Friday 22 October 2004 21:06, jim barnes wrote:
Ok, sure looks like it starts normally, lets see if anything is changed from default in sshd_config
grep -v ^# /etc/ssh/sshd_config I get a lot of blank lines and this on both machines
# grep -v ^# /etc/ssh/sshd_config PasswordAuthentication no UsePAM yes X11Forwarding yes Subsystem sftp /usr/lib/ssh/sftp-server
Can you still ping between machines?
Yes I can . Should I configure something in ssh ? I never used it and did not even know I had this installed. -- ________________ Paul Ollion Proud Linux user - SuSE - 9.1
On Saturday 23 October 2004 02:56 am, Paul Ollion wrote:
Can you still ping between machines?
Yes I can . Should I configure something in ssh ? I never used it and did not even know I had this installed.
You can look at the whole sshd_config (/etc/ssh/sshd_config) to see all options. We just looked at lines that have been uncommented, i.e., changed from defaults. (by SuSE in this case) Looks normal. Openssh is installed by default. From a console/terminal on your main machine do sshd -d, leave it running, and attempt a login from your laptop. sshd's output of the login attempt well display on your main machine. Try as both user and root (ssh root@192.168.0.1) man ssh is there also for interesting reading. -- Jim Barnes -- Certainly the game is rigged. Don't let that stop you; if you don't bet, you can't win. -Lazarus Long -- Linux 2.6.5-7.108-default
On Saturday 23 October 2004 15:52, jim barnes wrote:
On Saturday 23 October 2004 02:56 am, Paul Ollion wrote:
Can you still ping between machines?
Yes I can . Should I configure something in ssh ? I never used it and did not even know I had this installed.
You can look at the whole sshd_config (/etc/ssh/sshd_config) to see all options. We just looked at lines that have been uncommented, i.e., changed from defaults. (by SuSE in this case) Looks normal. Openssh is installed by default.
From a console/terminal on your main machine do sshd -d, leave it running, and attempt a login from your laptop. sshd's output of the login attempt well display on your main machine. Try as both user and root (ssh root@192.168.0.1)
Jim, I think you are finding the good solution or quite close to it, and I am beginning to see some light. Here is the output on my main machine, after 2 fruitless attempts, I got this : atelier:/home/paulus # sshd -d debug1: sshd version OpenSSH_3.8p1 debug1: private host key: #0 type 0 RSA1 debug1: read PEM private key done: type RSA debug1: private host key: #1 type 1 RSA debug1: read PEM private key done: type DSA debug1: private host key: #2 type 2 DSA debug1: Bind to port 22 on ::. Server listening on :: port 22. Generating 768 bit RSA key. RSA key generation complete. And after typing ssh paulus@192.168.0.1 on my laptop, I got the warning "permanently added '192.168.0.1' (RSA) to the list of known hosts " I was asked my password, I gave it and after giving the date and time it said 'Have a lot of fun' Which is not unpleasant, Then "Environment "USER=paulus "LOGNAME=paulus "HOME=/home/paulus "PATH=/usr/bin:/bin:/usr/sbin:/sbin "MAIL=/var/mail/paulus "SHELL=/bin/bash "SSH_CLIENT=::ffff:192.168.0.3 32779 22 "SSH_CONNECTION=::ffff:192.168.0.3 32779 ::ffff:192.168.0.1 22 "SSH_TTY=/dev/pts/49 "TERM=xterm the main machine displayed : debug1: Server will not fork when running in debugging mode. Connection from ::ffff:192.168.0.3 port 32779 debug1: Client protocol version 2.0; client software version OpenSSH_3.8p1 debug1: match: OpenSSH_3.8p1 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-1.99-OpenSSH_3.8p1 debug1: permanently_set_uid: 71/65 debug1: list_hostkey_types: ssh-rsa,ssh-dss debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: client->server aes128-cbc hmac-md5 none debug1: kex: server->client aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST received debug1: SSH2_MSG_KEX_DH_GEX_GROUP sent debug1: expecting SSH2_MSG_KEX_DH_GEX_INIT debug1: SSH2_MSG_KEX_DH_GEX_REPLY sent debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: KEX done debug1: userauth-request for user paulus service ssh-connection method none debug1: attempt 0 failures 0 Failed none for paulus from ::ffff:192.168.0.3 port 32779 ssh2 debug1: userauth-request for user paulus service ssh-connection method keyboard-interactive debug1: attempt 1 failures 1 debug1: keyboard-interactive devs debug1: auth2_challenge: user=paulus devs= debug1: kbdint_alloc: devices 'pam' debug1: auth2_challenge_start: trying authentication method 'pam' debug1: PAM: initializing for "paulus" debug1: PAM: setting PAM_RHOST to "mob.maison" debug1: PAM: setting PAM_TTY to "ssh" Postponed keyboard-interactive for paulus from ::ffff:192.168.0.3 port 32779 ssh2 debug1: PAM: num PAM env strings 0 Postponed keyboard-interactive/pam for paulus from ::ffff:192.168.0.3 port 32779 ssh2 Accepted keyboard-interactive/pam for paulus from ::ffff:192.168.0.3 port 32779 ssh2 debug1: monitor_child_preauth: paulus has been authenticated by privileged process Accepted keyboard-interactive/pam for paulus from ::ffff:192.168.0.3 port 32779 ssh2 debug1: PAM: reinitializing credentials debug1: permanently_set_uid: 1000/100 debug1: Entering interactive session for SSH2. debug1: server_init_dispatch_20 debug1: server_input_channel_open: ctype session rchan 0 win 65536 max 16384 debug1: input_session_request debug1: channel 0: new [server-session] debug1: session_new: init debug1: session_new: session 0 debug1: session_open: channel 0 debug1: session_open: session 0: link with channel 0 debug1: server_input_channel_open: confirm session debug1: server_input_channel_req: channel 0 request pty-req reply 0 debug1: session_by_channel: session 0 channel 0 debug1: session_input_channel_req: session 0 req pty-req debug1: Allocating pty. debug1: session_new: init debug1: session_new: session 0 debug1: session_pty_req: session 0 alloc /dev/pts/49 debug1: server_input_channel_req: channel 0 request shell reply 0 debug1: session_by_channel: session 0 channel 0 debug1: session_input_channel_req: session 0 req shell debug1: PAM: setting PAM_TTY to "/dev/pts/49" debug1: Setting controlling tty using TIOCSCTTY.
man ssh is there also for interesting reading.
I began to read it and if I understand what has been done, my main machine has been added to a list of my laptop's known hosts (using RSA which is the safest of the 3 authentication methods used by ssh) and I should do the reverse to authenticate my laptop in my main machine. Is that so ? Anyway, many thanks, you are a good teacher ans SuSE a good linux distro. -- ________________ Paul Ollion Proud Linux user - SuSE - 9.1
On Saturday 23 October 2004 04:48 pm, Paul Ollion wrote:
Jim, I think you are finding the good solution or quite close to it, and I am beginning to see some light. Here is the output on my main machine, after 2 fruitless attempts, I got this :
atelier:/home/paulus # sshd -d debug1: sshd version OpenSSH_3.8p1 debug1: private host key: #0 type 0 RSA1 debug1: read PEM private key done: type RSA debug1: private host key: #1 type 1 RSA debug1: read PEM private key done: type DSA debug1: private host key: #2 type 2 DSA debug1: Bind to port 22 on ::. Server listening on :: port 22. Generating 768 bit RSA key. RSA key generation complete.
Fruitless attempts and then it starts? I'm perplexed, it shouldn't be hit or miss.
And after typing
ssh paulus@192.168.0.1 on my laptop, I got the warning "permanently added '192.168.0.1' (RSA) to the list of known hosts "
This should have occurred the very first login attempt!
I was asked my password, I gave it and after giving the date and time it said 'Have a lot of fun' Which is not unpleasant, Then "Environment "USER=paulus "LOGNAME=paulus "HOME=/home/paulus "PATH=/usr/bin:/bin:/usr/sbin:/sbin "MAIL=/var/mail/paulus "SHELL=/bin/bash "SSH_CLIENT=::ffff:192.168.0.3 32779 22 "SSH_CONNECTION=::ffff:192.168.0.3 32779 ::ffff:192.168.0.1 22 "SSH_TTY=/dev/pts/49 "TERM=xterm
Now we know that ssh is indeed possible. Lets check for dropped packets, possibly indicating failure on the physical level (your patch cord and connections). A quick read of man ping, and then as root# ping -f <ip of other machine>. Wiggle the patch cord connectors gently during the test. 15-20 sec should be ample. Ctrl c to stop and view results. -- Jim Barnes -- Certainly the game is rigged. Don't let that stop you; if you don't bet, you can't win. -Lazarus Long -- Linux 2.6.5-7.111-default
On Sunday 24 October 2004 22:06, jim barnes wrote:
On Saturday 23 October 2004 04:48 pm, Paul Ollion wrote:
Jim, I think you are finding the good solution or quite close to it, and I am beginning to see some light. Here is the output on my main machine, after 2 fruitless attempts, I got this :
atelier:/home/paulus # sshd -d debug1: sshd version OpenSSH_3.8p1 debug1: private host key: #0 type 0 RSA1 debug1: read PEM private key done: type RSA debug1: private host key: #1 type 1 RSA debug1: read PEM private key done: type DSA debug1: private host key: #2 type 2 DSA debug1: Bind to port 22 on ::. Server listening on :: port 22. Generating 768 bit RSA key. RSA key generation complete.
Fruitless attempts and then it starts? I'm perplexed, it shouldn't be hit or miss.
And after typing
ssh paulus@192.168.0.1 on my laptop, I got the warning "permanently added '192.168.0.1' (RSA) to the list of known hosts "
This should have occurred the very first login attempt!
I was asked my password, I gave it and after giving the date and time it said 'Have a lot of fun' Which is not unpleasant, Then "Environment "USER=paulus "LOGNAME=paulus "HOME=/home/paulus "PATH=/usr/bin:/bin:/usr/sbin:/sbin "MAIL=/var/mail/paulus "SHELL=/bin/bash "SSH_CLIENT=::ffff:192.168.0.3 32779 22 "SSH_CONNECTION=::ffff:192.168.0.3 32779 ::ffff:192.168.0.1 22 "SSH_TTY=/dev/pts/49 "TERM=xterm
Now we know that ssh is indeed possible.
Lets check for dropped packets, possibly indicating failure on the physical level (your patch cord and connections). A quick read of man ping, and then as root# ping -f <ip of other machine>. Wiggle the patch cord connectors gently during the test. 15-20 sec should be ample. Ctrl c to stop and view results.
ping -f 192.168.0.3 PING 192.168.0.3 (192.168.0.3) 56(84) bytes of data. --- 192.168.0.3 ping statistics --- 141838 packets transmitted, 141838 received, 0% packet loss, time 29590ms rtt min/avg/max/mdev = 0.077/0.085/1.109/0.010 ms, ipg/ewma 0.208/0.084 ms Here are the results, looks normal , maybe I typed something wrong the two first times. Yesterday I tried SCP and could transfer a file from my laptop to my main machine; It is a beginning and i will be able to do some work with the laptop. Though SCP only works on console mode. Thank you Jim -- ________________ Paul Ollion Proud Linux user - SuSE - 9.1
On Friday 22 October 2004 02:58, jim barnes wrote:
Or this command: /etc/init.d/sshd status If it is not running, then: /etc/init.d/sshd start Excuse me, Jim , I had not checked on my laptop here is what is different :
-- mob:/home/paulus # /etc/init.d/sshd start Starting SSH daemon failed And many thanks for being so patient. ________________ Paul Ollion Proud Linux user - SuSE - 9.1
On Friday 22 October 2004 07:20 am, Paul Ollion wrote:
Excuse me, Jim , I had not checked on my laptop here is what is different :
-- mob:/home/paulus # /etc/init.d/sshd start Starting SSH daemon failed
It's interesting that both machines will not start sshd. It's on by default, at least in 9.1 pro. Any chance you're running the personal edition? Don't know if that would make any difference. -- Jim Barnes -- Certainly the game is rigged. Don't let that stop you; if you don't bet, you can't win. -Lazarus Long -- Linux 2.6.5-7.108-default
participants (4)
-
Brian Jackson -
Carlos E. R. -
jim barnes -
Paul Ollion