staging.inyokaproject.org

Hallo zusammen,

ich wollte mit meinem PC via ssh auf der Server zugreifen und er greift auf seine eigene IP-Adresse. Zugriff auf den anderen Server funktioniert.

jochen@PC-T01:~$ ssh jochen@192.168.1.8
jochen@192.168.1.8's password: 

jochen@PC-T01:~$ ssh jochen@192.168.1.6
jochen@192.168.1.153's password: 

Was ist hier passiert ? Wo muss ich suchen.

Die Laufwerke des Server sind einwandfrei auf dem PC eingehängt.

Von meinem Laptop aus funktioniert der Zugriff auf beide Server.

Gruß Jochen

nachtrag

jochen@PC-T01:~$ service ssh restart
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
Legitimierung ist zum Neustarten von »ssh.service« notwendig.
Authenticating as: Jochen,,, (jochen)
Password: 
==== AUTHENTICATION COMPLETE ===
jochen@PC-T01:~$ service ssh status
● ssh.service - OpenBSD Secure Shell server
     Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled)
    Drop-In: /etc/systemd/system/ssh.service.d
             └─00-socket.conf
     Active: active (running) since Wed 2023-04-19 01:59:54 CEST; 18s ago
TriggeredBy: ● ssh.socket
       Docs: man:sshd(8)
             man:sshd_config(5)
    Process: 8554 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS)
   Main PID: 8555 (sshd)
      Tasks: 1 (limit: 9296)
     Memory: 1.3M
        CPU: 55ms
     CGroup: /system.slice/ssh.service
             └─8555 "sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups"

Apr 19 01:59:53 PC-T01 systemd[1]: Starting OpenBSD Secure Shell server...
Apr 19 01:59:54 PC-T01 sshd[8555]: Server listening on :: port 22.
Apr 19 01:59:54 PC-T01 systemd[1]: Started OpenBSD Secure Shell server.
jochen@PC-T01:~$ 

Prüfe mal, ob der wirklich auf diese IP geht. Ist was in der /etc/hosts eingetragen?

jochenv schrieb:

[…] Was ist hier passiert ? Wo muss ich suchen.

Die naheliegendste Vermutung: Der Server hat mehrere IP-Adressen.

DJKUhpisse schrieb:

Prüfe mal, ob der wirklich auf diese IP geht. Ist was in der /etc/hosts eingetragen?

vom PC

jochen@PC-T01:~$ cat /etc/hosts
127.0.0.1	localhost
127.0.1.1	PC-T01

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

jochenv schrieb:

vom PC

Wie sind die Ausgaben von:

ip a
ip n s
sudo arp-scan -I <Interface> 192.168.1.0/24
nc -zv 192.168.1.6 22
nc -zv 192.168.1.153 22

?

kB schrieb:

jochenv schrieb:

[…] Was ist hier passiert ? Wo muss ich suchen.

Die naheliegendste Vermutung: Der Server hat mehrere IP-Adressen.

ja und nein ...

der Server hat 3 Adressen x.x.1.6 und x.x.3.6 sowie die x.x.1.7 für iLo

jochen@server06:~$ ifconfig
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.6  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::7210:6fff:fe3e:4180  prefixlen 64  scopeid 0x20<link>
        ether 70:10:6f:3e:41:80  txqueuelen 1000  (Ethernet)
        RX packets 227308  bytes 145078197 (145.0 MB)
        RX errors 0  dropped 58796  overruns 0  frame 0
        TX packets 59931  bytes 5471506 (5.4 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  

eno2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.3.6  netmask 255.255.255.0  broadcast 192.168.3.255
        inet6 fe80::7210:6fff:fe3e:4181  prefixlen 64  scopeid 0x20<link>
        ether 70:10:6f:3e:41:81  txqueuelen 1000  (Ethernet)
        RX packets 124628  bytes 14567633 (14.5 MB)
        RX errors 0  dropped 58796  overruns 0  frame 0
        TX packets 249  bytes 53930 (53.9 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 17  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Lokale Schleife)
        RX packets 5720  bytes 2973872 (2.9 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 5720  bytes 2973872 (2.9 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

jochen@server06:~$ 

die Adresse vom PC ist die x.x.1.153 und nach Eingabe des PC-Passwort meldet er sich auch an den PC an.

lubux schrieb:

jochenv schrieb:

vom PC

Wie sind die Ausgaben von:

ip a
ip n s
sudo arp-scan -I <Interface> 192.168.1.0/24
nc -zv 192.168.1.6 22
nc -zv 192.168.1.153 22

?

 jochen@PC-T01:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether c8:60:00:56:4b:37 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.153/24 brd 192.168.1.255 scope global dynamic noprefixroute enp2s0
       valid_lft 863650sec preferred_lft 863650sec
    inet6 fe80::8e3e:f43e:60c6:e611/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
jochen@PC-T01:~$ ip n s
192.168.1.10 dev enp2s0 lladdr b8:27:eb:ef:55:61 STALE
192.168.1.1 dev enp2s0 lladdr 3c:37:12:f3:4a:e4 STALE
192.168.1.6 dev enp2s0 lladdr 70:10:6f:3e:41:80 STALE
192.168.1.199 dev enp2s0 lladdr 18:1d:ea:21:64:d4 REACHABLE
192.168.1.204 dev enp2s0 lladdr b0:0c:d1:df:99:f8 STALE
fe80::b20c:d1ff:fedf:99f8 dev enp2s0 lladdr b0:0c:d1:df:99:f8 STALE
jochen@PC-T01:~$

apr-scan kennt er nicht ... soll ich das installieren ?

jochen@PC-T01:~$ sudo arp-scan -I <Interface> 192.168.1.0/24
-bash: Interface: Datei oder Verzeichnis nicht gefunden
jochen@PC-T01:~$ sudo arp-scan -I enp2s0 192.168.1.0/24
[sudo] Passwort für jochen: 
sudo: arp-scan: Befehl nicht gefunden
jochen@PC-T01:~$ 

und der Rest

jochen@PC-T01:~$ nc -zv 192.168.1.6 22
Connection to 192.168.1.6 22 port [tcp/ssh] succeeded!
jochen@PC-T01:~$ nc -zv 192.168.1.153 22
Connection to 192.168.1.153 22 port [tcp/ssh] succeeded!
jochen@PC-T01:~$ 

jochenv schrieb:

und der Rest

jochen@PC-T01:~$ nc -zv 192.168.1.6 22
Connection to 192.168.1.6 22 port [tcp/ssh] succeeded!
jochen@PC-T01:~$ nc -zv 192.168.1.153 22
Connection to 192.168.1.153 22 port [tcp/ssh] succeeded!
jochen@PC-T01:~$ 

Gibt es den user "jochen" auf all deinen Geräten (Server, Laptop, PC, ...)?

arp-scan muss vor der Benutzung, installiert sein:

which arp-scan
apt policy arp-scan

?

lubux schrieb:

Gibt es den user "jochen" auf all deinen Geräten (Server, Laptop, PC, ...)?

ja den gibt es.

arp-scan muss vor der Benutzung, installiert sein:

which arp-scan
apt policy arp-scan

?

jochen@PC-T01:~$ which arp-scan
jochen@PC-T01:~$ apt policy arp-scan
arp-scan:
  Installiert:           (keine)
  Installationskandidat: 1.9.7-2
  Versionstabelle:
     1.9.7-2 500
        500 http://de.archive.ubuntu.com/ubuntu kinetic/universe amd64 Packages
jochen@PC-T01:~$

jochenv schrieb:

ja den gibt es.

Hmm, ... dann versuch mal:

ssh -v 192.168.1.6

Noch besser wäre, der richtige/brauchbare Eintrag in der ~/.ssh/config, beim ssh-Client

so ... arp-scan installiert.

jochen@PC-T01:~$ which arp-scan
/usr/sbin/arp-scan
jochen@PC-T01:~$ sudo arp-scan -I enp2s0 192.168.1.0/24
Interface: enp2s0, type: EN10MB, MAC: c8:60:00:56:4b:37, IPv4: 192.168.1.153
Starting arp-scan 1.9.7 with 256 hosts (https://github.com/royhills/arp-scan)
192.168.1.1	3c:37:12:f3:4a:e4	(Unknown)
192.168.1.2	62:ff:4d:e7:80:f7	(Unknown: locally administered)
192.168.1.2	62:ff:4d:e7:80:f7	(Unknown: locally administered) (DUP: 2)
192.168.1.6	70:10:6f:3e:41:81	Hewlett Packard Enterprise
192.168.1.6	70:10:6f:3e:41:80	Hewlett Packard Enterprise (DUP: 2)
192.168.1.7	70:10:6f:3e:41:82	Hewlett Packard Enterprise
192.168.1.10	b8:27:eb:ef:55:61	Raspberry Pi Foundation
192.168.1.20	b8:27:eb:13:50:4c	Raspberry Pi Foundation
192.168.1.204	b0:0c:d1:df:99:f8	Hewlett Packard
192.168.1.199	18:1d:ea:21:64:d4	Intel Corporate
192.168.1.203	3c:37:12:f3:4a:e4	(Unknown)
192.168.1.199	18:1d:ea:21:64:d4	Intel Corporate (DUP: 2)
192.168.1.202	3c:37:12:f3:4a:e4	(Unknown)
192.168.1.201	3c:37:12:f3:4a:e4	(Unknown)
192.168.1.167	46:1b:bb:da:bc:4d	(Unknown: locally administered)
192.168.1.204	3c:37:12:f3:4a:e4	(Unknown) (DUP: 2)
192.168.1.167	46:1b:bb:da:bc:4d	(Unknown: locally administered) (DUP: 2)
192.168.1.200	00:01:e6:2b:f6:7d	Hewlett Packard
192.168.1.208	3c:37:12:f3:4a:e4	(Unknown)
192.168.1.206	3c:37:12:f3:4a:e4	(Unknown)
192.168.1.205	3c:37:12:f3:4a:e4	(Unknown)
192.168.1.205	3c:37:12:f3:4a:e4	(Unknown) (DUP: 2)
192.168.1.197	5a:54:5b:ba:5b:16	(Unknown: locally administered)
192.168.1.206	3c:37:12:f3:4a:e4	(Unknown) (DUP: 2)
192.168.1.208	3c:37:12:f3:4a:e4	(Unknown) (DUP: 2)

26 packets received by filter, 0 packets dropped by kernel
Ending arp-scan 1.9.7: 256 hosts scanned in 2.214 seconds (115.63 hosts/sec). 25 responded
jochen@PC-T01:~$

jochenv schrieb:

jochen@PC-T01:~$ sudo arp-scan -I enp2s0 192.168.1.0/24
Interface: enp2s0, type: EN10MB, MAC: c8:60:00:56:4b:37, IPv4: 192.168.1.153
Starting arp-scan 1.9.7 with 256 hosts (https://github.com/royhills/arp-scan)
192.168.1.6	70:10:6f:3e:41:81	Hewlett Packard Enterprise
192.168.1.6	70:10:6f:3e:41:80	Hewlett Packard Enterprise (DUP: 2)

Hast Du auf dem Server, zwei NICs mit identischer IP (.6)? Oder, sind diese MAC-Adressen auf verschiedenen Geräten?

lubux schrieb:

jochenv schrieb:

ja den gibt es.

Hmm, ... dann versuch mal:

ssh -v 192.168.1.6

Noch besser wäre, der richtige/brauchbare Eintrag in der ~/.ssh/config, beim ssh-Client

jochen@PC-T01:~$ ssh -v 192.168.1.6
OpenSSH_9.0p1 Ubuntu-1ubuntu7.1, OpenSSL 3.0.5 5 Jul 2022
debug1: Reading configuration data /home/jochen/.ssh/config
debug1: Executing command: 'timeout 0.4 nc -z 192.168.1.6 22  2>/dev/null'
debug1: /home/jochen/.ssh/config line 6: Applying options for 192.168.1.6
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug1: Connecting to 192.168.1.153 [192.168.1.153] port 22.
debug1: Connection established.
debug1: identity file /home/jochen/.ssh/id_rsa type -1
debug1: identity file /home/jochen/.ssh/id_rsa-cert type -1
debug1: identity file /home/jochen/.ssh/id_ecdsa type -1
debug1: identity file /home/jochen/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/jochen/.ssh/id_ecdsa_sk type -1
debug1: identity file /home/jochen/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file /home/jochen/.ssh/id_ed25519 type 3
debug1: identity file /home/jochen/.ssh/id_ed25519-cert type -1
debug1: identity file /home/jochen/.ssh/id_ed25519_sk type -1
debug1: identity file /home/jochen/.ssh/id_ed25519_sk-cert type -1
debug1: identity file /home/jochen/.ssh/id_xmss type -1
debug1: identity file /home/jochen/.ssh/id_xmss-cert type -1
debug1: identity file /home/jochen/.ssh/id_dsa type -1
debug1: identity file /home/jochen/.ssh/id_dsa-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_9.0p1 Ubuntu-1ubuntu7.1
debug1: Remote protocol version 2.0, remote software version OpenSSH_9.0p1 Ubuntu-1ubuntu7.1
debug1: compat_banner: match: OpenSSH_9.0p1 Ubuntu-1ubuntu7.1 pat OpenSSH* compat 0x04000000
debug1: Authenticating to 192.168.1.153:22 as 'jochen'
debug1: load_hostkeys: fopen /home/jochen/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: sntrup761x25519-sha512@openssh.com
debug1: kex: host key algorithm: ssh-ed25519
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: SSH2_MSG_KEX_ECDH_REPLY received
debug1: Server host key: ssh-ed25519 SHA256:KoD5C57PRelgjBLp2NXVODutGqKR58SHIZtZVdps9+I
debug1: load_hostkeys: fopen /home/jochen/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug1: Host '192.168.1.153' is known and matches the ED25519 host key.
debug1: Found key in /home/jochen/.ssh/known_hosts:6
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey in after 134217728 blocks
debug1: Will attempt key: /home/jochen/.ssh/id_rsa 
debug1: Will attempt key: /home/jochen/.ssh/id_ecdsa 
debug1: Will attempt key: /home/jochen/.ssh/id_ecdsa_sk 
debug1: Will attempt key: /home/jochen/.ssh/id_ed25519 ED25519 SHA256:e2IWMCBzTjS54lxAI+pgOVJaBYgS7cWFBmnye0NHzfI
debug1: Will attempt key: /home/jochen/.ssh/id_ed25519_sk 
debug1: Will attempt key: /home/jochen/.ssh/id_xmss 
debug1: Will attempt key: /home/jochen/.ssh/id_dsa 
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,sk-ssh-ed25519@openssh.com,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ecdsa-sha2-nistp256@openssh.com,webauthn-sk-ecdsa-sha2-nistp256@openssh.com>
debug1: kex_input_ext_info: publickey-hostbound@openssh.com=<0>
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Trying private key: /home/jochen/.ssh/id_rsa
debug1: Trying private key: /home/jochen/.ssh/id_ecdsa
debug1: Trying private key: /home/jochen/.ssh/id_ecdsa_sk
debug1: Offering public key: /home/jochen/.ssh/id_ed25519 ED25519 SHA256:e2IWMCBzTjS54lxAI+pgOVJaBYgS7cWFBmnye0NHzfI
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: /home/jochen/.ssh/id_ed25519_sk
debug1: Trying private key: /home/jochen/.ssh/id_xmss
debug1: Trying private key: /home/jochen/.ssh/id_dsa
debug1: Next authentication method: password
jochen@192.168.1.153's password: 
debug1: Authentications that can continue: publickey,password
Permission denied, please try again.
jochen@192.168.1.153's password: 

jochenv schrieb:

debug1: Next authentication method: password
jochen@192.168.1.153's password: 
debug1: Authentications that can continue: publickey,password
Permission denied, please try again.
jochen@192.168.1.153's password: 

Du musst deinen Server netzwerktechnisch so konfigurieren, dass die NIC mit der IP aus dem Subnetz 192.168.3.0/24, die Anfragen an die IP 192.168.1.6, ignoriert. Denn:

eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.6  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::7210:6fff:fe3e:4180  prefixlen 64  scopeid 0x20<link>
        ether 70:10:6f:3e:41:80  txqueuelen 1000  (Ethernet)

eno2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.3.6  netmask 255.255.255.0  broadcast 192.168.3.255
        inet6 fe80::7210:6fff:fe3e:4181  prefixlen 64  scopeid 0x20<link>
        ether 70:10:6f:3e:41:81  txqueuelen 1000  (Ethernet)

EDIT:

Versuch mal mit:

net.ipv4.conf.eno1.arp_filter = 1
net.ipv4.conf.eno1.arp_ignore = 2
net.ipv4.conf.eno1.arp_notify = 1
# ---
net.ipv4.conf.eno2.arp_filter = 1
net.ipv4.conf.eno2.arp_ignore = 2
net.ipv4.conf.eno2.arp_notify = 1

EDIT 2:

BTW: Ich empfehle dir, auf deinen Geräten, verschiedene usernamen (... für den "normalen" user, statt nur jochen) zu benutzen bzw. zu konfigurieren.