Wheezy Configuration de l'adresse ip fixe

Support Debian
#1

Bonjour,

Après l’installation de Debian Weezy 3.0.4, je voudrais mettre une adresse ip fixe sur mon serveur.

Par défaut le fichier “/etc/network/interface” est configuré comme ceci :

[code]auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp[/code]

J’ai m’y ceci dans mon fichier “/etc/network/interface”

[code]auto lo
iface lo inet loopback

auto eth0

iface eth0 inet dhcp

iface eth0 inet static
address 192.168.0.1
netmask 255.255.255.0
broadcast 192.168.0.255
gateway 192.168.0.254

auto eth1
iface eth1 inet dhcp[/code]

Puis j’ai redémarré le service réseau

[code]root@debian:~# /etc/init.d/networking restart
Running /etc/init.d/networking restart is deprecated because it may not enable again some interfaces … (warning).
Reconfiguring network interfaces…Internet Systems Consortium DHCP Client 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth1/f0:ad:4e:00:b2:43
Sending on LPF/eth1/f0:ad:4e:00:b2:43
Sending on Socket/fallback
Internet Systems Consortium DHCP Client 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth1/f0:ad:4e:00:b2:43
Sending on LPF/eth1/f0:ad:4e:00:b2:43
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 12
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
done.
root@debian:~# [/code]

Et quand je me connecte en ssh sur la nouvelle adresse ip fixe 192.168.0.1 ça marche pas.

laurent@laurent-Bureau:~$ sshpass -p 'xxxxxx' ssh root@192.168.0.1 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a host key has just been changed. The fingerprint for the RSA key sent by the remote host is 89:cd:d3:4a:50:bb:55:bf:43:b3:34:9d:50:90:19:a7. Please contact your system administrator. Add correct host key in /home/laurent/.ssh/known_hosts to get rid of this message. Offending RSA key in /home/laurent/.ssh/known_hosts:1 remove with: ssh-keygen -f "/home/laurent/.ssh/known_hosts" -R 192.168.0.1 RSA host key for 192.168.0.1 has changed and you have requested strict checking. Host key verification failed. laurent@laurent-Bureau:~$

Et quand je me connecte sur l’ancienne adressse ip 192.168.1.1 ça marche

[code]laurent@laurent-Bureau:~$ sshpass -p ‘xxxxxx’ ssh root@192.168.1.1
Linux debian 3.0.4 #1 PREEMPT Tue Aug 30 19:56:02 MDT 2011 armv5tel

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Jun 13 23:58:44 2014 from 192.168.1.140
root@debian:~# [/code]

Pourtant j’ai vérifié la configuration du réseau, l’ip est bien chargé ?

[code]root@debian:~# ifconfig eth0
eth0 Link encap:Ethernet HWaddr f0:ad:4e:00:b2:42
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::f2ad:4eff:fe00:b242/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:159 errors:0 dropped:0 overruns:0 frame:0
TX packets:166 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:23903 (23.3 KiB) TX bytes:22128 (21.6 KiB)
Interrupt:11

root@debian:~# ifconfig
eth0 Link encap:Ethernet HWaddr f0:ad:4e:00:b2:42
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::f2ad:4eff:fe00:b242/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:199 errors:0 dropped:0 overruns:0 frame:0
TX packets:201 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:30337 (29.6 KiB) TX bytes:27739 (27.0 KiB)
Interrupt:11

eth1 Link encap:Ethernet HWaddr f0:ad:4e:00:b2:43
UP BROADCAST RUNNING 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:15

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:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

uap0 Link encap:Ethernet HWaddr 00:24:23:45:0d:ac
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::224:23ff:fe45:dac/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:164 errors:0 dropped:0 overruns:0 frame:0
TX packets:85 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:20882 (20.3 KiB) TX bytes:10239 (9.9 KiB)

root@debian:~# [/code]

Pourquoi je n’arrive pas à me connecter en ssh sur 'ip 192.168.0.1 ?

Merci.

#2

Salut,

[quote=“xunil2003”]laurent@laurent-Bureau:~$ sshpass -p ‘xxxxxx’ ssh root@192.168.0.1
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
89:cd:d3:4a:50:bb:55:bf:43:b3:34:9d:50:90:19:a7.
Please contact your system administrator.
Add correct host key in /home/laurent/.ssh/known_hosts to get rid of this message.
Offending RSA key in /home/laurent/.ssh/known_hosts:1
remove with: ssh-keygen -f “/home/laurent/.ssh/known_hosts” -R 192.168.0.1
RSA host key for 192.168.0.1 has changed and you have requested strict checking.
Host key verification failed.
laurent@laurent-Bureau:~$ [/quote]

Commentes¹ l’entrée une du fichier [mono]/home/laurent/.ssh/known_hosts[/mono] suivit d’un redémarrage du service ssh.

Où,¹ supprimes cette dernière à la mano.

Mieux encore, fais ce qu’il te demande. :wink:

[07:34:46]:~$ ssh-keygen -f "/home/loreleil/.ssh/known_hosts" -R 192.168.1.14 /home/loreleil/.ssh/known_hosts updated. Original contents retained as /home/loreleil/.ssh/known_hosts.old [07:35:10]:~$

#3

Et, à quoi correspond l’interface uap0 ?

Car là, c’est à toi même que tu te connectes avec [mono]ssh 192.168.1.1[/mono].

#4

[quote=“Zbf”]Et, à quoi correspond l’interface uap0 ?

Car là, c’est à toi même que tu te connectes avec [mono]ssh 192.168.1.1[/mono].[/quote]

Interface WIFI je crois bien. GuruPlug peut être?

#5

bonjour

J’ai fait :

ssh-keygen -f "/home/laurent/.ssh/known_hosts" -R 192.168.0.1 /home/laurent/.ssh/known_hosts updated. Original contents retained as /home/laurent/.ssh/known_hosts.old

Puis je redémarre le service de connexion ssh

[code]sudo /etc/init.d/ssh restart
[sudo] password for laurent:
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service ssh restart

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the stop(8) and then start(8) utilities,
e.g. stop ssh ; start ssh. The restart(8) utility is also available.
ssh stop/waiting
ssh start/running, process 20246
laurent@laurent-Bureau:~$[/code]

Et quand j’établis ma connexion ssh

laurent@laurent-Bureau:~$ sshpass -p 'xxxxxx' ssh root@192.168.0.1 Host key verification failed. laurent@laurent-Bureau:~$

Mon fichier “/home/laurent/.ssh/known_hosts”

laurent@laurent-Bureau:~$ cat /home/laurent/.ssh/known_hosts |1|ska/4SeLRy23j6sxSRytGyXHTCg=|RvftuSFfouNUlnKL6z3NWyTDuYk= ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBO67dMNCpZ2JuY0LAy74TpvDnXwYI09rGabrAQHssWanvj0gZN7dHHtVDqbvg2EOlJTT4mpRqsCbZieh7VcIBjM= |1|K+tp6tgGmushztHlFXKtVPYjZ9I=|nZFRnSgR/0L3vrrd1tNB9s1Thr4= ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBDPjySanumSlyD0yP52AOA0LQmM3ZK9fu7s5aXHEb233wFq/S8Cj3RgvqzsDrAYvVd013g0PayG0rlH+v/lWrYs= laurent@laurent-Bureau:~$

J’ai effectué la connexion ssh directement avec ssh au lieu de sshpass
La ça a marché de suite

[code]laurent@laurent-Bureau:~$ ssh root@192.168.0.1
The authenticity of host ‘192.168.0.1 (192.168.0.1)’ can’t be established.
ECDSA key fingerprint is c9:b7:d6:c2:b9:a1:fd:cd:8a:dc:4d:e3:2e:d9:4a:3c.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added ‘192.168.0.1’ (ECDSA) to the list of known hosts.
root@192.168.0.1’s password:
Linux debian 3.0.4 #1 PREEMPT Tue Aug 30 19:56:02 MDT 2011 armv5tel

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sat Jun 14 02:13:18 2014 from 192.168.1.140
root@debian:~# [/code]

Oui exact, l’interface uap0 est la connexion wifi du Dreamplug.

Merci pour votre aide.

#6

[quote=“xunil2003”]J’ai effectué la connexion ssh directement avec ssh au lieu de sshpass
La ça a marché de suite[/quote]

Peut-on voir ta config ?

Pourquoi lances tu une connexion root [mono]$ ssh root@…[/mono] d’entrée ?

Tu n’as pas une clé privée/publique qui traîne (/home/user/.ssh où /root/.ssh) ?

[mono]sshpass[/mono], je ne suis guère très chaud dans son utilisation. Quelle raison à cela ?

#7

Bonsoir,

je n’ai pas de raison particulière à utiliser sshpass c’est une vieille habitude.

[quote]
Tu n’as pas une clé privée/publique qui traîne[/quote] Non

[code]serveur@debian:~$ cat /etc/ssh/sshd_config

Package generated configuration file

See the sshd_config(5) manpage for details

What ports, IPs and protocols we listen for

Port 22

Use these options to restrict which interfaces/protocols sshd will bind to

#ListenAddress ::
#ListenAddress 0.0.0.0
Protocol 2

HostKeys for protocol version 2

HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_dsa_key
HostKey /etc/ssh/ssh_host_ecdsa_key
#Privilege Separation is turned on for security
UsePrivilegeSeparation yes

Lifetime and size of ephemeral version 1 server key

KeyRegenerationInterval 3600
ServerKeyBits 768

Logging

SyslogFacility AUTH
LogLevel INFO

Authentication:

LoginGraceTime 120
PermitRootLogin yes
StrictModes yes

RSAAuthentication yes
PubkeyAuthentication yes
#AuthorizedKeysFile %h/.ssh/authorized_keys

Don’t read the user’s ~/.rhosts and ~/.shosts files

IgnoreRhosts yes

For this to work you will also need host keys in /etc/ssh_known_hosts

RhostsRSAAuthentication no

similar for protocol version 2

HostbasedAuthentication no

Uncomment if you don’t trust ~/.ssh/known_hosts for RhostsRSAAuthentication

#IgnoreUserKnownHosts yes

To enable empty passwords, change to yes (NOT RECOMMENDED)

PermitEmptyPasswords no

Change to yes to enable challenge-response passwords (beware issues with

some PAM modules and threads)

ChallengeResponseAuthentication no

Change to no to disable tunnelled clear text passwords

#PasswordAuthentication yes

Kerberos options

#KerberosAuthentication no
#KerberosGetAFSToken no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes

GSSAPI options

#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes

X11Forwarding yes
X11DisplayOffset 10
PrintMotd no
PrintLastLog yes
TCPKeepAlive yes
#UseLogin no

#MaxStartups 10:30:60
#Banner /etc/issue.net

Allow client to pass locale environment variables

AcceptEnv LANG LC_*

Subsystem sftp /usr/lib/openssh/sftp-server

Set this to ‘yes’ to enable PAM authentication, account processing,

and session processing. If this is enabled, PAM authentication will

be allowed through the ChallengeResponseAuthentication and

PasswordAuthentication. Depending on your PAM configuration,

PAM authentication via ChallengeResponseAuthentication may bypass

the setting of “PermitRootLogin without-password”.

If you just want the PAM account and session checks to run without

PAM authentication, then enable this but set PasswordAuthentication

and ChallengeResponseAuthentication to ‘no’.

UsePAM yes
serveur@debian:~$ [/code]

Merci.

#8

[mono]$ ssh user@192.168.0.1[/mono] Suffit amplement, la connexion établit tu passes ensuite en root.

[mono][19:39:30]:~$ ssh 192.168.1.14
Linux Zen 3.2.0-4-686-pae #1 SMP Debian 3.2.57-3+deb7u2 i686

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sat Jun 14 13:29:18 2014 from pc-2-loreleil.home
[19:38:50]:~$

[19:39:29]:~$ su -
Mot de passe :
[19:39:38] ~ #[/mono]

Ainsi tu peux neutraliser l’accès ssh root en [mono]PermitRootLogin no[/mono].

J’opterai pour un jeu de clé (+ passphrase) … :wink:

Note: tu devrais revoir ta config, il-y-a des incohérences, exemple : [mono]#PasswordAuthentication yes[/mono]

#9

Bonjour,

Maintenant que la mise à jour du système Debian Wheezy est effectuée, voir poste ici :
mise-a-jour-du-systeme-debian-wheezy-t48766-25.html#p487327
Je reviens sur celui-ci.

[quote]
Ce n’est plus du ressort des connexions ssh, (l’upgrade étant régler) mais de ton réseau local, à revoir entièrement.

xunil2003 a écrit:

[…] mon réseau local, et composé de plusieurs postes sous Linux et Windows, imprimante ip, camera IP, Thermostat IP, domotique x10, Freebox V5.

Tous ont une Adresse IP fixe spécifique correspondent au router de la Freebox pour les ports tcp et udp, sauf le pc kubuntu et le plug sont en dhcp.[/quote] Je ne pense pas quand même.

Actuellement mon réseau :

[code]laurent@laurent-Bureau:~$ nmap -sP 192.168.0.0-254

Starting Nmap 5.21 ( http://nmap.org ) at 2014-06-16 13:12 CEST
Nmap scan report for 192.168.0.1
Host is up (0.00037s latency).
Nmap scan report for 192.168.0.5
Host is up (0.00075s latency).
Nmap scan report for 192.168.0.6
Host is up (0.00014s latency).
Nmap scan report for 192.168.0.45
Host is up (0.0021s latency).
Nmap scan report for 192.168.0.100
Host is up (0.010s latency).
Nmap scan report for 192.168.0.254
Host is up (0.012s latency).
Nmap done: 255 IP addresses (6 hosts up) scanned in 2.94 seconds
laurent@laurent-Bureau:~$
[/code]

Détail ip réseau :
[ul]192.168.0.1 —> Serveur
192.168.0.5 —> Box domotique
192.168.0.6 —> Mon poste actuel
192.168.0.45 —> Imprimante
192.168.0.100 —> Téléphone sip
192.168.0.254 —> Box adsl[/ul] les autres postes sont éteint pour l’instant

Y a aucun conflit d’adresse ip.
Avec Debian Squeeze, je n’ai jamais eu de problème concernant la configuration du réseau, y compris pour me connecter sur le serveur en ssh depuis un poste clients ?

Je vais faire un test sur un autre poste et je reviens vous dire ce qui si passe.

Merci.

#10

Bonjour,

Je viens de faire un essai de connexion ssh sur le serveur depuis un autre poste est ça marche.

[code]laurent@MSI-GT683:~/python$ ssh serveur@192.168.0.1
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
89:cd:d3:4a:50:bb:55:bf:43:b3:34:9d:50:90:19:a7.
Please contact your system administrator.
Add correct host key in /home/laurent/.ssh/known_hosts to get rid of this message.
Offending RSA key in /home/laurent/.ssh/known_hosts:1
remove with: ssh-keygen -f “/home/laurent/.ssh/known_hosts” -R 192.168.0.1
RSA host key for 192.168.0.1 has changed and you have requested strict checking.
Host key verification failed.
laurent@MSI-GT683:~/python$ ssh-keygen -f “/home/laurent/.ssh/known_hosts” -R 192.168.0.1
/home/laurent/.ssh/known_hosts updated.
Original contents retained as /home/laurent/.ssh/known_hosts.old
laurent@MSI-GT683:~/python$ ssh serveur@192.168.0.1
The authenticity of host ‘192.168.0.1 (192.168.0.1)’ can’t be established.
ECDSA key fingerprint is c9:b7:d6:c2:b9:a1:fd:cd:8a:dc:4d:e3:2e:d9:4a:3c.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added ‘192.168.0.1’ (ECDSA) to the list of known hosts.
serveur@192.168.0.1’s password:
Linux debian 3.0.4 #1 PREEMPT Tue Aug 30 19:56:02 MDT 2011 armv5tel

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Mon Jun 16 09:20:47 2014 from 192.168.0.6
serveur@debian:~$ uname -r
3.0.4
serveur@debian:~$[/code]

Donc ça vient de mon poste client “laurent@laurent-Bureau”.
Je suis retourné voir.
J’ai fait une mise à jour et rebooté le pc est ça marche .
J’ai édité le fichier “/home/laurent/.ssh/known_hosts” avec nano et j’ai supprimé la dernière ligne Puis j’ai fait :

[code]laurent@laurent-Bureau:~$ ssh serveur@192.168.0.1
The authenticity of host ‘192.168.0.1 (192.168.0.1)’ can’t be established.
ECDSA key fingerprint is c9:b7:d6:c2:b9:a1:fd:cd:8a:dc:4d:e3:2e:d9:4a:3c.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added ‘192.168.0.1’ (ECDSA) to the list of known hosts.
serveur@192.168.0.1’s password:
Linux debian 3.0.4 #1 PREEMPT Tue Aug 30 19:56:02 MDT 2011 armv5tel

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Mon Jun 16 11:36:11 2014 from 192.168.0.3
serveur@debian:~$ exit
logout
Connection to 192.168.0.1 closed.
laurent@laurent-Bureau:~$[/code]

J’ai arrêter le serveur pour faire une sauvegarde et l’ai remis en marche une fois la sauvegarde terminé, çà marche plus

La clé ssh a encore changé.
Pourquoi me change t’il a chaque fois la clé ssh ???

laurent@laurent-Bureau:~$ ssh serveur@192.168.0.1 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a host key has just been changed. The fingerprint for the ECDSA key sent by the remote host is 6b:e3:f0:81:c8:a3:9b:9e:6d:20:a5:9d:58:a1:c4:0e. Please contact your system administrator. Add correct host key in /home/laurent/.ssh/known_hosts to get rid of this message. Offending ECDSA key in /home/laurent/.ssh/known_hosts:3 remove with: ssh-keygen -f "/home/laurent/.ssh/known_hosts" -R 192.168.0.1 ECDSA host key for 192.168.0.1 has changed and you have requested strict checking. Host key verification failed. laurent@laurent-Bureau:~$

C’est pas fiable ???
Comment faut il faire si il me change la clé ssh a chaque fois, je m’en sort plus ???

et quand je fait ce qu’i l me dit, ça marche pas non plus

laurent@laurent-Bureau:~$ ssh-keygen -f "/home/laurent/.ssh/known_hosts" -R 192.168.0.1 /home/laurent/.ssh/known_hosts updated. Original contents retained as /home/laurent/.ssh/known_hosts.old laurent@laurent-Bureau:~$ ssh serveur@192.168.0.1 The authenticity of host '192.168.0.1 (192.168.0.1)' can't be established. ECDSA key fingerprint is 6b:e3:f0:81:c8:a3:9b:9e:6d:20:a5:9d:58:a1:c4:0e. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '192.168.0.1' (ECDSA) to the list of known hosts. serveur@192.168.0.1's password: Permission denied, please try again. serveur@192.168.0.1's password: Permission denied, please try again. serveur@192.168.0.1's password: Permission denied (publickey,password). laurent@laurent-Bureau:~$

Idem si je supprimer la dernière ligne du fichier “/home/laurent/.ssh/known_hosts” et fait :

laurent@laurent-Bureau:~$ ssh serveur@192.168.0.1 The authenticity of host '192.168.0.1 (192.168.0.1)' can't be established. ECDSA key fingerprint is 6b:e3:f0:81:c8:a3:9b:9e:6d:20:a5:9d:58:a1:c4:0e. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '192.168.0.1' (ECDSA) to the list of known hosts. serveur@192.168.0.1's password: Permission denied, please try again. serveur@192.168.0.1's password: Permission denied, please try again. serveur@192.168.0.1's password: Permission denied (publickey,password). laurent@laurent-Bureau:~$

J’ai redémarrer de nouveau le serveur, il m’affiche une nouvelle clé ssh

laurent@laurent-Bureau:~$ ssh serveur@192.168.0.1 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a host key has just been changed. The fingerprint for the ECDSA key sent by the remote host is c9:b7:d6:c2:b9:a1:fd:cd:8a:dc:4d:e3:2e:d9:4a:3c. Please contact your system administrator. Add correct host key in /home/laurent/.ssh/known_hosts to get rid of this message. Offending ECDSA key in /home/laurent/.ssh/known_hosts:3 remove with: ssh-keygen -f "/home/laurent/.ssh/known_hosts" -R 192.168.0.1 ECDSA host key for 192.168.0.1 has changed and you have requested strict checking. Host key verification failed. laurent@laurent-Bureau:~$

Pourquoi ?

Merci.

#11

Le “résolu” dans le titre est normal ? Tu as encore des problèmes il semblerait.

#12

Bonsoir

Oui un oublie, j’ai rectifié.

Le serveur réagit bizarrement je trouve.

serveur@debian:~$ uname -r -bash: uname: command not found serveur@debian:~$ ls -bash: ls: command not found serveur@debian:~$ echo $HOME /home/serveur serveur@debian:~$ ls -bash: ls: command not found serveur@debian:~$ ls -al -bash: ls: command not found serveur@debian:~$ pwd /home/serveur serveur@debian:~$
Certaines commandes ne répondent plus par moments et quand il arrive cela, après je n’arrive plus à me reconnecter au serveur en ssh.

laurent@laurent-Bureau:~$ ssh serveur@192.168.0.1 serveur@192.168.0.1's password: Connection closed by 192.168.0.1 laurent@laurent-Bureau:~$
je suis obligé de le redémarrer.
Que faire ?

Edité le : 17/06/2014
J’ai voulu remettre ma carte mémoire sdhc dans le serveur de Debian Squeeze.
Bizarrement sa me fait exactement la même chose qu’avec Wheezy, alors qu’avant non ?

Avec l’ancienne carte mémoire de debian squueze.

laurent@laurent-Bureau:~$ ssh serveur@192.168.0.1 serveur@192.168.0.1's password: Permission denied, please try again. serveur@192.168.0.1's password: Permission denied, please try again. serveur@192.168.0.1's password: Permission denied (publickey,password). laurent@laurent-Bureau:~$ nano /home/laurent/.ssh/known_hosts laurent@laurent-Bureau:~$ ssh serveur@192.168.0.1 The authenticity of host '192.168.0.1 (192.168.0.1)' can't be established. ECDSA key fingerprint is 6b:e3:f0:81:c8:a3:9b:9e:6d:20:a5:9d:58:a1:c4:0e. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '192.168.0.1' (ECDSA) to the list of known hosts. serveur@192.168.0.1's password: Permission denied, please try again. serveur@192.168.0.1's password: Permission denied, please try again. serveur@192.168.0.1's password: Permission denied (publickey,password). laurent@laurent-Bureau:~$

laurent@laurent-Bureau:~$ ssh serveur@192.168.0.1 serveur@192.168.0.1's password: Permission denied, please try again. serveur@192.168.0.1's password: Connection closed by UNKNOWN laurent@laurent-Bureau:~$

Esce que cela peut venir du poste sur lequel je me connecte au serveur ?
Je ne sais plus quoi faire ?

Merci.

#13

Que dit dmesg ? On pourrait croire que la partition qui héberge /usr n’est d’un coup plus accessible à ton système.

Et comme tu le décris, ça pourrait être un problème matériel du lecteur de carte.

#14

Bonsoir,

Voilà le résultat :

[code]serveur@debian:~$ dmesg
Initializing cgroup subsys cpu
Linux version 3.0.4 (kelly@speedy) (gcc version 4.5.3 (PlugComputer G++ 20110530) ) #1 PREEMPT Tue Aug 30 19:56:02 MDT 2011
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
CPU: VIVT data cache, VIVT instruction cache
Machine: Marvell GuruPlug Reference Board
Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 131072
free_area_init_node: node 0, pgdat c0533b04, node_mem_map c0602000
Normal zone: 1024 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 130048 pages, LIFO batch:31
pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
pcpu-alloc: [0] 0
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048
Kernel command line: console=ttyS0,115200 root=/dev/sdb2 panic=10 rootwait
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 512MB = 512MB total
Memory: 513604k/513604k available, 10684k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
vmalloc : 0xe0800000 - 0xfe800000 ( 480 MB)
lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.init : 0xc0008000 - 0xc002f000 ( 156 kB)
.text : 0xc002f000 - 0xc05021e8 (4941 kB)
.data : 0xc0504000 - 0xc0536140 ( 201 kB)
.bss : 0xc0536164 - 0xc0601608 ( 814 kB)
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Preemptible hierarchical RCU implementation.
NR_IRQS:114
sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474ms
Console: colour dummy device 80x30
Calibrating delay loop… 1191.11 BogoMIPS (lpj=5955584)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
NET: Registered protocol family 16
Kirkwood: MV88F6281-A1, TCLK=200000000.
Feroceon L2: Cache support initialised.
initial MPP regs: 01112222 11113311 33331111 33333333 00003333 00000222 00000000
final MPP regs: 01112222 11113311 33331111 33333333 00003333 00000222 00000000
bio: create slab at 0
vgaarb: loaded
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Switching to clocksource orion_clocksource
Switched to NOHz mode on CPU #0
FS-Cache: Loaded
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 32
FS-Cache: Netfs ‘nfs’ registered for caching
JFS: nTxBlock = 4012, nTxLock = 32100
msgmni has been set to 1003
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
console [ttyS0] enabled
brd: module loaded
loop: module loaded
mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
mv643xx_eth_port mv643xx_eth_port.0: eth0: port 0 with MAC address f0:ad:4e:00:b2:42
mv643xx_eth_port mv643xx_eth_port.1: eth1: port 0 with MAC address f0:ad:4e:00:b2:43
ehci_hcd: USB 2.0 ‘Enhanced’ Host Controller (EHCI) Driver
orion-ehci orion-ehci.0: Marvell Orion EHCI
orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver…
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
mousedev: PS/2 mouse device common for all mice
rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
i2c /dev entries driver
cpuidle: using governor ladder
cpuidle: using governor menu
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright© Pierre Ossman
mmc0: mvsdio driver initialized, lacking card detect (fall back to polling)
Registered led device: guruplug:red:health
Registered led device: guruplug:green:health
Registered led device: guruplug:red:wmode
Registered led device: guruplug:green:wmode
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
oprofile: hardware counters not available
oprofile: using timer interrupt.
TCP cubic registered
NET: Registered protocol family 17
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL’
Registering the dns_resolver key type
Gating clock of unused units
before: 0x00dfc3fd
after: 0x00cf41d9
registered taskstats version 1
rtc-mv rtc-mv: setting system clock to 2014-06-17 16:25:37 UTC (1403022337)
Waiting for root device /dev/sdb2…
mmc0: new high speed SDIO card at address 0001
usb 1-1: new high speed USB device number 2 using orion-ehci
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usb 1-1.1: new high speed USB device number 3 using orion-ehci
scsi0 : usb-storage 1-1.1:1.0
usb 1-1.2: new low speed USB device number 4 using orion-ehci
usb 1-1.3: new high speed USB device number 5 using orion-ehci
hub 1-1.3:1.0: USB hub found
hub 1-1.3:1.0: 4 ports detected
usb 1-1.4: new full speed USB device number 6 using orion-ehci
input: C-Media USB Headphone Set as /devices/platform/orion-ehci.0/usb1/1-1/1-1.4/1-1.4:1.3/input/input0
generic-usb 0003:0D8C:000C.0001: input: USB HID v1.00 Device [C-Media USB Headphone Set ] on usb-orion-ehci.0-1.4/input3
usb 1-1.3.4: new high speed USB device number 7 using orion-ehci
hub 1-1.3.4:1.0: USB hub found
hub 1-1.3.4:1.0: 4 ports detected
scsi 0:0:0:0: Direct-Access Generic STORAGE DEVICE 9910 PQ: 0 ANSI: 0
sd 0:0:0:0: Attached scsi generic sg0 type 0
scsi 0:0:0:1: Direct-Access Generic STORAGE DEVICE 9910 PQ: 0 ANSI: 0
sd 0:0:0:0: [sda] 15759360 512-byte logical blocks: (8.06 GB/7.51 GiB)
sd 0:0:0:1: Attached scsi generic sg1 type 0
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 0b 00 00 08
sd 0:0:0:0: [sda] No Caching mode page present
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:1: [sdb] 32243712 512-byte logical blocks: (16.5 GB/15.3 GiB)
sd 0:0:0:1: [sdb] Write Protect is off
sd 0:0:0:1: [sdb] Mode Sense: 0b 00 00 08
sd 0:0:0:1: [sdb] No Caching mode page present
sd 0:0:0:1: [sdb] Assuming drive cache: write through
sd 0:0:0:0: [sda] No Caching mode page present
sd 0:0:0:0: [sda] Assuming drive cache: write through
sda: sda1 sda2
sd 0:0:0:1: [sdb] No Caching mode page present
sd 0:0:0:1: [sdb] Assuming drive cache: write through
sdb: sdb1 sdb2
sd 0:0:0:0: [sda] No Caching mode page present
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Attached SCSI removable disk
sd 0:0:0:1: [sdb] No Caching mode page present
sd 0:0:0:1: [sdb] Assuming drive cache: write through
sd 0:0:0:1: [sdb] Attached SCSI removable disk
EXT3-fs: barriers not enabled
EXT3-fs (sdb2): warning: checktime reached, running e2fsck is recommended
kjournald starting. Commit interval 5 seconds
EXT3-fs (sdb2): using internal journal
EXT3-fs (sdb2): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 8:18.
devtmpfs: mounted
Freeing init memory: 156K
udevd[723]: starting version 175
Bluetooth: Core ver 2.16
NET: Registered protocol family 31
sata_mv sata_mv.0: version 1.28
sata_mv sata_mv.0: slots 32 ports 1
Bluetooth: HCI device and connection manager initialized
scsi1 : sata_mv
Bluetooth: HCI socket layer initialized
cfg80211: Calling CRDA to update world regulatory domain
ata1: SATA max UDMA/133 irq 21
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
ata1: SATA link down (SStatus 0 SControl F300)
Bluetooth: vendor=0x2df, device=0x9105, class=255, fn=2
libertas_sdio: Libertas SDIO driver
btmrvl_sdio_interrupt: sbi_interrupt(df063200) card or priv is NULL, card=de4a5200

libertas_sdio: Copyright Pierre Ossman
usbcore: registered new interface driver snd-usb-audio
btmrvl_sdio_download_helper: request_firmware(helper) failed, error code = -2
btmrvl_sdio_download_fw: Failed to download helper!
btmrvl_sdio_probe: Downloading firmware failed!
libertas_sdio: failed to find firmware (-2)
libertas_sdio: probe of mmc0:0001:1 failed with error -2
uap_probe: vendor=0x02DF device=0x9104 class=0 function=1
sbi_interrupt: sbi_interrupt(df063000) card or priv is NULL, card=de520000
UAP FW is active
NET: Registered protocol family 10
ADDRCONF(NETDEV_UP): eth0: link is not ready
ADDRCONF(NETDEV_UP): eth1: link is not ready
mv643xx_eth_port mv643xx_eth_port.0: eth0: link up, 1000 Mb/s, full duplex, flow control disabled
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
eth0: no IPv6 routers present
ADDRCONF(NETDEV_UP): uap0: link is not ready
ADDRCONF(NETDEV_CHANGE): uap0: link becomes ready
uap0: no IPv6 routers present
serveur@debian:~$ [/code]

Verification si il y a une fail ou erreur :

serveur@debian:~$ dmesg | grep fail btmrvl_sdio_download_helper: request_firmware(helper) failed, error code = -2 btmrvl_sdio_probe: Downloading firmware failed! libertas_sdio: failed to find firmware (-2) libertas_sdio: probe of mmc0:0001:1 failed with error -2 serveur@debian:~$

Depuis hier soir il marche impec, je n’y comprend plus rien ?

Merci.

#15

Tu peux te renseigner sur les messages d’erreur que tu as cité, car mmc0 c’est le lecteur de carte.

On ignore pourquoi le firmware ne parvient pas à se charger, peut-être est-il tout simplement absent.

Il se peut que ce soit un classique, et que la communauté Dreamplug ait des infos là dessus.

#16

Bonjour,

Je pense que c’est la mémoire interne de 8Go du plugcomputer car je boot actuellement avec la carte mémoire de 16G0 sdhc.

Mais je vais me renseigner.

[code]root@debian:~# fdisk -l

Disk /dev/sda: 8068 MB, 8068792320 bytes
125 heads, 62 sectors/track, 2033 cylinders, total 15759360 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0009619b

Device Boot Start End Blocks Id System
/dev/sda1 2048 201499 99726 6 FAT16
/dev/sda2 201500 15630335 7714418 83 Linux

Disk /dev/sdb: 16.5 GB, 16508780544 bytes
64 heads, 32 sectors/track, 15744 cylinders, total 32243712 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x2ce01ffe

Device Boot Start End Blocks Id System
/dev/sdb1 32 104447 52208 6 FAT16
/dev/sdb2 104448 32243711 16069632 83 Linux
root@debian:~# [/code]

Merci.